Free Online Support - Program Errors
Home
Free Support
Tips & Tricks
QUICK TIP: Any time you get an error message in a program, try re-booting the computer before you try anything else.
INDEX - Click on a topic to jump to that section
Program Errors
  • P1 - GPF Error Message, error 3000, Stack error
  • P2 - 'Calc_Overflow' or other Program Errors/Erratic Program Behavior/Won't Save New Entries/New Clients
  • P3 - 'Application Already Open' 3024 error or 3051 Error
  • P4 - BSA.MDB or CCDB.MDB File Missing Error or Disk I/O Error 3040
  • P5 - 'Out of Memory' Error
  • P6 - Password Doesn't Work/Reinstalling Program/Moving Program to a New Computer
  • P7 - License Agreement Error
  • P8 - Out of Stack Space/Multiple Pages Error
    		•
  • P9 - Uncompress Error on Retrieval
  • P10 - Win16 Error
  • P11 - autoexec.nt or nt.dll error
  • P12 - Type Mismatch Error
  • P13 - Unable to open stand alone program - Vista
  • P14 - Corrupt database - reinstallation

    • P1. Problem: I get a message that the program has caused a General Protection Fault (GPF), a Stack Error, Error 3000 or similar system error.
  • Solution: Quit all applications, exit Windows, re-boot the computer (or 'server' in a network version) and re-start the program. Such errors are, unfortunately, quite common in the Windows operating system. They result from an application being unable to safely access its protected memory area. They are not necessarily caused directly by the application that is running when the error occurs. In other words, BSA/CC did not necessarily cause the error. The only sure solution is to re-boot the computer (the 'server' in a network version) to clear the memory area. If the error keeps happening, it is likely you have a hardware memory error or a corrupt database. See the next question for more on corruption.

    P2. Problem: I get a "Calc_Overflow" (or similar) error or the program won't save new entries/clients/matters or my program is acting erratically in various ways.
  • Solution: Your database may be corrupt. First, quit all applications, exit Windows, re-boot the computer and re-start BSA (or Conflict Checker).  If the error continues, your database is corrupt.
      Next, Repair the database using the built in Repair feature. This requires that you read the Help file first so you can get the Repair code. The repair code is:  E51
      After you run the Repair, BE SURE TO IMMEDIATELY PERFORM A HOUSECLEANING by selecting that function from the Utilities.
      If that does not solve the problem, you'll need re-store from a recent back up. From Home Menu, select BACKUP (or 'Utilities' and then 'Backup' in BSA Pro) and then Retrieve. Then, Replace all Data | Retrieve from the A (or B) floppy drive. After the retrieval, you will need to check to be certain the program acts properly and re-enter any data that was entered after the back up was made.
      If the problem continues, your back up was also corrupt. Continue going back through your back up disks until you restore from one that is not corrupt.
    Database corruption can occur from a number of sources. Most of the causes relate to mixing databases from different machines and from power fluctuations and faulty hardware. Once corrupt, a database application such as BSA can act unpredictably. In some cases, BSA can automatically detect the corruption and repair it. Often, however, the ONLY solution is to restore your database from an uncorrupted back up file. That is why it is so important to make frequent back ups on new floppies.
      If you are using a very old version of BSA that doesn't have the Repair Database feature built in, we offer a free utility in our download area that you can use to attempt to repair your database. If you have no back up disks or all your back ups are also corrupt, you can try this utility as a last resort to repair your database.     CLICK HERE to go to the FREE download area.
      Finally, we offer a Data Recovery service that specializes in recovering data from corrupt databases. seaBILL customers who wish to use this service can have their corrupt database analyzed and repaired for a flat fee $200 which is 1/3 off the normal minimum cost for this service. If the database is not corrupt or cannot be repaired there will be no charge. If you suspect your database is corrupt and you wish to use this service, please visit the seaBILL Secure Upgrade Store and order the Data Recovery service. When your order is received, you will receive detailed instructions for transmitting your database to seaBILL via email. It will then be forwarded to a Data Recovery specialist for analysis. If the database can be repaired and the data recovered, your database will be returned to you electronically and only then will the charge be processed. The analysis and recovery process normally takes 3-5 business days. If a longer time is needed, you will be notified.

    P3. Problem: I get an error that the application is already open by another user, error 3024 or error 3051 and this is not a network version of the program or no one else is in the program.
  • Solution: For stand alone users (non-network), Windows thinks there is another copy of the program running. This may not be true but since Windows thinks it is, you have no choice but to follow the instructions in the error message: Quit all applications and re-boot your computer.
     For all users, including network users, another possibility is that your database file (BSA.MDB or CCDB.MDB) file is missing or corrupted. This can occur if you accidentally delete it or if you have a corrupt database. See the answer to number P2 above or P4 below for more info.

    P4. Problem: I get an error that my BSA.MDB file (or Conflict Checker database file) is missing or a Disk I/O Error 3040 or some other similar error message and then I can't start BSA.
  • Solution: This error occurs when the database has been accidentally deleted by someone or is so badly corrupted, it is not even recognizable as a database or when your hard drive is defective and the database file cannot be read.  The program attempts to correct the error automatically and, if it fails, it tries to perform an automatic upgrade to the database to attempt to correct the problem.  If you see this error message, it means that all the automatic efforts to retrieve the database have failed. In this case, you effectively have lost your database file and you will need to reinstall the program.
    Before proceeding, if the 'bsa.mdb' (or ccdb.mdb for Conflict Checker) file is still in the program folder, make a copy of it and store it in a safe place in case it is possible to repair it. Also, make a copy of the file 'zzzbsa1.zip' if that file exists and store it in a safe place. This is an automatic back up file made by the program before bills are finalized in BSA Pro.
     Also, copy and store any other back up files you might have placed in the program folder.
     Then, completely uninstall the program and reinstall it from the CD and get a new password as discussed     here.
     After you enter the new password, retrieve your data from a back up from within the program. You MUST retrieve from WITHIN THE PROGRAM. Do not simply copy and paste the database file to the new program folder.  This will void the password.
      If you don't have a back up, you can try retrieving from the 'zzzbsa1.zip' file.
      If that is not successful, you can submit the original, corrupt 'bsa.mdb' file to us for analysis and possible repair. Visit the seaBILL Secure Upgrade Store and order the Data Recovery service. When your order is received, you will receive detailed instructions for transmitting your database to seaBILL via email. It will then be forwarded to a Data Recovery specialist for analysis. If the database can be repaired and the data recovered, your database will be returned to you electronically and only then will the charge be processed. The analysis and recovery process normally takes 3-5 business days. If a longer time is needed, you will be notified.

    P5. Problem: We got an "OUT OF MEMORY" or "OUT OF STACK SPACE" message. What's Up?
  • Solution: The operating system (Windows 95/98, Windows NT, etc.) generates this message when there is insufficient system memory to perform the operation in question. This is not a message generated by BSA or Conflict Checker. This can occur from time to time if you haven't re-booted your computer in a long time or if you have several programs open at once, etc. The simplest answer is to acknowledge the message, close all applications, exit the operating system, power down the computer (cold boot) and re-start the operating system and the program. If this occurs frequently, you probably have a hardware problem related to memory. This should be diagnosed and resolved by a competent hardware technician.

    P6. Problem: I tried to install (or re-install) one of your programs again and the password you gave me doesn't work.
  • Solution: The password won't work the second time. Installing multiple copies of the programs not only violates the seaBILL Limited Use License Agreement but also increases the chances of corrupting your database. Thus, you should not attempt to run multiple copies of our programs simultaneously.
     For help moving the program to a new computer Click Here.

    P7. Problem: We get the following message: "There is a problem running BSA (or Conflict Checker) on this computer. The license agreement allows only one copy of BSA (or Conflict Checker) to be used for each password. If you are trying to run BSA (or Conflict Checker) on another computer, you will need to purchase an additional site license. If you believe you have received this message due to a technical problem, please contact technical support." What do we do?
  • Solution: This message does not appear in licensed copies of BSA or Conflict Checker unless you have made a change in your computer, have mixed databases from different machines or some other change such as an upgrade has occurred. This message normally appears when you try to run BSA on a machine that has not been licensed to run it or when you mix databases from different licensed machines or when you have changed the basic configuration of a machine upon which BSA or Conflict Checker was installed and licensed.
       This message will also appear if you manually move a copy of the database file from one installation of the program to another. To avoid this problem, you must use the built in Retrieve feature in the program. If this is the case, then you should uninstall the program, reinstall it and request a new password. Then, retrieve your old data from within the program using the built in feature. DO NOT copy the old database file into the new program folder or you will get this error message again.
      If you're using Vista and there's no other reason from above that you would be getting this message, chances are that Vista has changed your system without your knowledge or left the database file marked as open from the last time you used the program even though the database file is actually closed. This is a bug in Vista. In that case, REBOOT the computer and the problem should go away.
       If you did not copy the database file in manually and you are a registered user of BSA or Conflict Checker and are not attempting to violate the license agreement (which allows only one copy of the program to be installed on one computer), you will need to use the Support Form to request support. If your free support period has expired, you will need to purchase additional email support on the upgrade store.     Click Here to go to the Upgrade Store.

    P8. Problem: We get an 'Out of Stack Space' error or we get many, many pages trying to print/print preview when we print/preview a Report. What do we do?
  • Solution: This problem is usually caused by an out of date printer driver that is sending infinite page break commands. You should visit the printer manufacturer's web site and download and install the latest printer driver.
     Even though the printer may be acting fine in other programs such as Word or WordPerfect, it is still most likely an obsolete printer driver. These other programs are much less demanding in their print routines and do not tax the driver's abilities nearly as much as BSA can in a print job.
     Also, if the report you are trying to print has an option to 'Page Break after Matters' or 'Skip zero bal Matters' or something similar, select that option to see if that helps. Sometimes, forcing a page break early solves the problem since the printer driver does not get a chance to send its own page break commands.
      Also, try using Selected Matters for the report rather than All Matters. This may cause the print job to be small enough to complete.
      Also, if you have another printer driver installed, make it the default printer and test it to see if it works in Print Preview mode (you don't have to have the printer connected).
      Even if you don't have another printer installed, you can install one of the many pre-loaded printer drivers in Windows by simply selecting the option to Add a New Printer from Control Panel and selecting one of the more popular printers. After you install the driver, make it the default printer and try a 'Print Preview' in BSA of the report. If it works, you know the actual printer driver is causing the problem and you should download a new one for your actual printer from the printer manufacturer's web site.
     Finally, you can try another printer if possible.

    P9. Problem: I get an 'Uncompress' error when I try to retrieve data from a back up. What's wrong?
  • Solution: If your back up media (usually a floppy disk) contains a valid BSA or Conflict Checker back up file, you will not get this error. So, the problem is either that the disk does not contain a BSA back up file or the file it contains is not valid (something's wrong with the file).
     You can check the contents of the disk using Windows Explorer to see if it contains a BSA back up file name. The default back up file name is BSABAKUP.ZIP (or CCBAKUP.ZIP for Conflict Checker). If you changed the name of the back up file, then it will be named what ever you changed it to.
     If the disk contains a valid back up file name and you can't retrieve from it, then the back up file is bad. You can confirm this by trying to Unzip the file in some other program. BSA, Conflict Checker and PORTABLE bsa all use a standard compression algorithm when they make a back up in order to save space. The compression algorithm is a version of PKZIP technology that is commonly supported by virtually all freely available compression software tools. So, you can try to unzip the file in something other than BSA (WinZip for example). If you can't do this, then something is wrong with the file. If you can do this in some other program, then BSA, Conflict Checker and PORTABLE bsa will be able to open it and retrieve from it as well.

    P10. Problem: When I try to start the program, I get an error that refers to the 'Win16 Subsytem' or a '16 bit Windows application' or the 'WOW'. What's wrong?
  • Solution: Your operating system (usually XP or Windows 2000) was not completely and fully installed when the computer was first set up. As a result, certain required DLL or other similar 'helper' files are missing or obsolete which causes the NTVDM to fail. The simplest solution is to re-install the operating system. Here's a link to a Microsoft Knowledge Base article that, though inartfully entitled, discusses the concept and offers suggestions: Microsoft Knowledge Base Article 165214

    P11. Problem: When I try to start the program, an error message shows: C:windows\system32\autoexec.nt. Or, I get an ntdll.dll error message. What's wrong?
  • Solution: The error message indicates your Windows operating system files have been corrupted, possibly by a virus. The autoexec.nt file has been damaged. While we do not support Windows, it's possible the following will help: Go to C:\windows\repair (or wherever your windows folder is located). Look for the autoexec.nt file and copy and paste it back into the windows\system32 folder. You can also contact Microsoft for help. Here's a link to a free Microsoft Knowledge Base article that explains in much more detail: Microsoft Help

    P12. Problem: When I try to start BSA or Conflict Checker, an error message shows: Type Mismatch Error. What's wrong?
  • Solution: Look at how dates are displayed in the program. They MUST show as month/day/year IN THAT ORDER as in 10/15/1999 (October 15, 1999). If they don't show that way, the program will not run.  So, you probably have your Regional Settings/Short Date style set to something other than English US. Our programs are written in the US and are designed for use primarily in the US. To change your Regional Settings, from your Desktop in Windows 95/98/2000/XP/NT, select START | SETTINGS | CONTROL PANEL, then select REGIONAL SETTINGS and make certain you are set to English(United States). Then select the DATE tab and check your Short Date style. It should be mm/dd/yyyy (for month/day/year) and the Date Separator should be a forward slash (/). After setting these options, select APPLY and then OK to close the small window. Then, you may have to re start your computer for the changes to take effect.

    P13. Problem: When I try to start BSA, PORTABLE bsa or Conflict Checker under Windows Vista, an error message shows:

    For BSA:
    The database could not open. The database may already by opened exclusively by another user. Error No. 3051. This application will now exit.

    For CC:
    An error has occurred in attempting to open your CC Database. Please contact technical support for assistance. 3051. Couldn't open file [file name].

    For PORTABLE bsa:
    Object variable not Set (Error 91).

    I'm not trying to run the program across a network. What's wrong?
  • Solution: You need 'administrator' privileges to run the program under Microsoft's new operating system, Vista. Please consult the Vista documentation for help setting up Vista.

    P14. Problem: I think my database is corrupt. Can I just reinstall the program or buy a license for a new version to fix it?

    Solution:     No. Reinstalling the program won't repair a corrupted database.
      BSA Pro and Conflict Checker are database applications. Like all database applications, they have a 'front end' and a 'back end.' The part of the program you see when you use it is the front end. The database file is the back end. It's where your data is stored as you use the program over time.
      If your database file is corrupted, the file must be repaired. Reinstalling the program will only reinstall the front end again and an EMPTY database file. Your data won't be there because it's not part of the original program.
      There's no way to re-create all the data you've entered into the program without a back up. Obviously, the program doesn't ship with all your past, present and future data in it. It ships with an EMPTY database file that you will fill up with your data over time.
      So, again, if your database is corrupt, you need to repair or replace it to keep using it. Reinstalling the program or buying a new version won't repair the database file.
      This is why it's important to make regular back ups to new media.

    (c) seaBILL Co.