Various Problems/Fixes

• Unknown error message while trying to bring up the system.
  
  Note: I has one instance where the client was getting this message even before the beginning Splash Screen appeared. It was having a problem with the Distrib.mdb file. I tried having them install the latest MSJET40 and MDAC updates, but this didn't help.
  
  It turned out that the msjtes40.dll file was missing from the System32 folder. Which was strange as the MSJET SP8 I installed should have copied this file to the System32 folder and registered it. I had to copy it from the System32\dllcashe folder and register it.
  
  regsvr32 msjtes40.dll
  
  Once this happened the system came right up, as the msjtes40.dll is used to open Access Database tables.
  
  Note: I had one instance where registering msjtes40.dll didn't help but registering DAO306.dll and Scrrun.ddl solved the problem.
  
  
• The system locks up on the OK / EXIT screen.
  
  
  • The System.mdb is corrupt. Deleting the file and letting the system recreate one usually fixes the problem.
    
    Note: You may want to make a copy just in case this isn't the problem.
    
    
  • I had a couple cases where the problem was caused by the Distrib.mdb. It was either missing or the wrong one.
    
    
  • I had one instance that I haven't confirmed yet where I think the problem was cased by the CdirList.mdb being corrupted. I deleted the file and the system came up. The customer thought it was the next item.
    
    
  • If the default printer is a true network printer (ie: \\192.168.0.100) and its either turned off or the computer has lost connection, then the program will hang.
  
  
• The system is taking a long time to come up or activating a client seems to take forever.
  
  I had it happen here once and it turned out that MSVBVM60.DLL wasn't registered properly. Once I re-registered it the system ran at normal speed.
  
  regsvr32 msvbvm60.dll
  
  
• System is suddenly acting slow when working with Client Data.
  
  
  1. Reboot the computer with a Restart.
  2. Shutdown the computer and actually turn it off.
  3. 1. Repair the System.mdb
     2. Repair the client data
     3. Run Version Control on the client data
     4. Move back (1) period
     5. Move forward to the current period
  
  
• The screen looks strange (ie: White block at the end of the Icon Bar) and/or the Scroll Bar is missing or only half there. (ie: Activate Client Screen)
  
  It turned out that the Font Size was set to Other - 110%. Once we changed it back to Small Fonts / Standard the screens looked normal.
  
  
  1. Right Click on the Desktop
  2. Left Click on Properties
  3. Click on the Settings Tab
  4. Click on the Advanced Button
  5. On the Font Size pull-down change the font size to Small Font
     
     Note: The system should say that the fonts already exist on the computer and do you want to use them, say "Yes". Otherwise it will ask for the original CD-ROM to reinstall the fonts.
     
     
  6. Click Apply and then OK
  
  Note: The system may want to reboot.
  
  
• System Information Window Messages:
  
  
  1. GL Transaction out of reporting period has been changed, added or deleted. You may need to run Utilities -> Print Out of Period Transactions to help resolve this.
     
     You have changed/added or deleted a transaction that falls outside the Current Reporting Period. All you have to do to resolve this message is to reselect the Current Reporting Period.
     
  
  
• G/L Transaction Date to Early (CWU) - This means you have a transaction entered that has a date before the Initial Balance Date.
  
  If there are not a lot of transactions simple call the transaction back up and fix the date on the transaction(s).
  
  Note: You can determine the Initial Balance Date by:
  
  Setup -> Accounts -> Initial Balances
  
  
• Income and Expense Accounts Not Zeroing - If you start a new fiscal year and the Income and Expense Account figures are carrying forward the figures from last year then:
  
  
  1. Go back to the previous year end.
  2. Run Trans Prep
  3. Run a Trail Balance to check the figures.
  4. Return to the Current Accounting Period.
  5. Run Trans Prep
  
  
• Invalid Cost Center - If you get this message and do not have Cost Centers setup then run Version Control on the data. The Cost Center field has "0" in it instead of a "blank". Version Control fixes this.
  
  
• Locate Setup Errors - This option will search the files and replace any null characters found with a string length of zero. This should be run if you get any error dealing with null characters found.
  
  
• Automation Erros
  
  
  1. Run Time Error 2147023782 (8007045a) - A dynamic link library (DLL) initialization routine failed.
     
     I had one person get this error when they went to run Version Control. I re-registered Msvbvm60.dll, Scrrun.dll and DAO360.dll and the error went away.
     
     
  2. Run Time Error 2147024703 (800700c1) - %1 is not a valid win32 application.
     
     I had one person get this error when they tried to bring the program up. I tried uninstalling and reinstalling the program. Without luck, but the installation did complain about DAO360.dll and MsJet40.dll. It turned out that a Windows Update corrupted the MsJet40 Database Engine. I had to reload update MS08-028 - (950749). Which solved the problem.
     
     Note: I had to search for MsJet40 4.0.9511.0 even to find this update. Microsoft wouldn't let me install MsJet40 (Sp8), said what was on the computer was newer. I had to hunt for a newer version.
     
     
  3. Run Time Error 2147024770 (8007007e) - The specified module could not be found.
     
     I had one person get this error when they went to run Version Control. I re-registered Msvbvm60.dll, Scrrun.dll and DAO360.dll and the error went away.
     
     
  4. Run Time Error 2147319779 (8002801d) - Library not registered.
     
     One or more of the activate X controls used by the program are not registered correctly. Run Regsvr32 and reregister the controls.
     
     I had one person get this error when they went to print payroll checks. I reregistered the (4) OCX files used by the option and the error disappeared.
     
     
  5. Run Time Error 2147319783 (80028019) - Old format or invalid type library. (Q186063)
     
     I had one person get this when they tried to run Version Control. I had the person try running VBRUN60.DLL from the CD, but it said it couldn't register MSVBVM60.DLL. I had them reboot and run VBRUN60.DLL again. This time is ran without error messages and Version Control ran fine. Maybe I just had to reboot.
     
     
  6. Run Time Error 2147417848 (80010108) - The object invoked has disconnected from its clients.
     
     I had one person get this message when they tried to print checks. Turned out that the computer the network printer was hooked to wasn't turned on.
     
     While trying to backup. There was a problem introduced into the system concerning the XCEEDZIP control. The Use Temp File property was accidentally turned off. It only effected Multi Disk backups. Send the person v5.74.06 or higher.
     
     
  
  
• File Cryp95e.dll could not be found - You get this message on Windows XP when trying to bring the system up, even though the file is in the \PCSW folder. This means the Compatibilty Mode is turned on for the files (WinCWU / WinCCB). Turn the Compatibility Mode off.
  
  Properties -> Compatibility (Tab) -> Run this program in compatibly mode for (checkbox)
  
  
• Invalid Import from: Kernel32.dll - This is a compatibility problem.
  
  I have only run into this problem once, when someone installed v3.71.02 onto a Windows XP computer.
  
  
• NTLDR is Missing message while computer is booting. - They have a diskette in the drive. Remove the disk and press enter to reboot the computer.
  
  
• Program not Authorized - This means the System cannot find or read the hidden files holding the Site Key. They may have run defrag, removed the directory holding the files or the file maybe damaged. Reissuing them a Site Key will solve the problem.
  
  
• Unkown Error Invalid Property Error 382 - Try the following to see if it solves the problem.
  
  
  1. Activate another client
  2. Run Repair Data on the client you got the error on
     
     Utilities -> Repair Data
     
     
  3. Activate the client you were getting the error on and run a Version Control
     
     Utilities -> Version Control
  
  
• Error 5: Invalid Procedure Call - This usually means that and OCX file or one of it's Dependancy Files is missing, damaged or the wrong version.
  
  Check the size and date of the five (5) OCX files we send to make sure they match ours. You may have to reinstall them if they are Out of Date.
  
  Note: I had one person get this messages when they tried to run a Balance Sheet. It turned out that an account had some garbage characters at the end of account description. Once the characters were removed the report ran fine.
  
  Note: I had one person get this message after clicking on the [List] button next to the Cash Account Field on the Checks & Receipts screen. It turned out that the Cash Account that first appeared in the field had undefined Disbursment and Receipts Journal Codes. Once I added the Journal Codes to the system the error disappeared.
  
  
• Error 6: Overflow - You are trying to enter too large a number into a field.
  
  Note: I had (1) instance where the customer was getting this message after clicking the Print Check button. It turned out that there wasn't any communication between the computer and the network printer. I couldn't even print a test page. We have to reboot the server to reestablish communication.
  
  Note: I had (2) instances where the customer was getting this message any time they tried to print anything. (ie: Click on Print button or brought up a Report Option). But the old 8.10.02 version worked fine. After much time I was able to determine the system didn't like the print driver the printer was using. I added a new printer using a different driver for that printer and it worked just fine. They was able to print reports.
  
  The old print driver they were using was for a 4050 Color Laser, (Color Management Tab) which they didn't have? So once we determined the new printer worked, I deleted the old printer.
  
  Note: I had (1) instance where a customer was getting this message when entering the Gross Amount on the Write Payroll Checks Screen. It turned out that the System.mdb file was corrupt. Letting the system generate a new one solved the problem. Repair did not solve the problem.
  
  Note: I have several instances where the customer gets this message while trying to enter a payroll check on an employee that uses a Time Card. The problem is the program is trying to convert the Transaction Number into an integer (CINT). But "CINT" only works with numbers up to 32767. If the Transaction Number is over 32767 you get this error. The problem was solved in v5.55.02.
  
  The customer can do the following to get past the error:
  
  
  1. Backup the data
  2. Run Utilities -> Transaction Utilities -> Renumber Transactions
     
     This option will renumber both Payroll and General Ledger Transactions. This should lower the numbers enough so the error will disapper.
  
  
• Error 7: Out of Memory - This could mean they have run out of RAM or disk space. It could also be a false error and it is another problem all together.
  
  I had once instance where the client installed another program and it wiped out the OCX files used by our program in the system directory and installed some of them into its owe directory. I just copied the files back into the systems folder and registered them.
  
  
• Error 9: Subscript Out of Range - You are trying to add data to a field or array that is too small.
  
  Note: Had one person getting this error while trying to change periods. Got the data here and it worked fine. Had them exit the program and come back in and this fixed the problem.
  
  Note: Had one person get is error while trying to print a Bank Reconciliation Report. Turned out that they had 1600 Adjustments and the system was only setup for 200. The program was changed to re-dimension the array. (6.83.05)
  
  
• Error 13: Type Mismatch - The variable is the wrong type for the field it is trying to fill. Have the person run a Version Control and/or Repair Data to see if solves the error. Also check specific support page for this error.
  
  
• Error 48: Error Loading DLL - The program is trying to find/load a missing DLL. The DLL can be either missing or not registered correctly. Try uninstalling and reinstalling the program first. If this doesn't work then manually register the OCX and DLL files called by the program option.
  
  Note: The missing file could be a missing dependency file. In other words a DLL need by a DLL our program uses. But not included with program.
  
  Note: I had one instance where the person was getting this message while trying to run a Version Control. I tried uninstalling and reinstalling the program without success. So, I manually registered Msvbvm60.dll, Comctl32.ocx, Scrrun.dll and DAO260.dll, which are the main calls made from Version Control, and the error went away.
  
  
• Error 52: Bad File Name or Number - This usually means the system can't read or didn't find a floppy in drive A.
  
  Note: I had one instance where the customer for some strange reason set the Default Data Directory to drive A. So every time you brought the system up you would get this error between clicking OK and when the main screen appeared. We changed the Default Data Directory to the correct location and the error disappeared.
  
  
• Error 53: File Not Found - The program is trying to find/access a file it can't find.
  
  Note: I had one instance where the customer was getting this message when they went to print checks, but the test page printed fine. It turned out that they had entered the company name into the first logo field on the Cash Account. Once we blanked out the name the error went away.
  
  Note: I had one instance where the client was getting this message while trying to bring up the Activate Client Screen it turned out that they were missing the BlankDir.mdb file. Putting the file back on solved the problem.
  
  
• Error 70: Permission Denied - It can either mean you have insufficient permissions to access the file or the file is being used by another program. (ie: They have more than one instance of the program up, or some other program is trying to access the file.)
  
  So check the permissions on the directory and file. I would also recommend rebooting the computer to make sure no other program has a hold of the file.
  
  Note: The first time I saw this message was when I tried to run Repair Data on a file that some how locked by AOL. They said they had tried to email the file to someone and it had a problem. Didn't tell me this until later.
  
  
• Error 75: Path/File Access Error - The file/folder is most likely set to read only or it's a permission problem.
  
  
• Error 76: Path not Found - The path specified does not exist or the system cannot access it. Check the path to make sure it is valid and the computer can access it's contains.
  
  You usually get this error while trying to Activate a client or when going into Setup -> System -> Default Data Directory. Which means the customer is most likely trying to access a Network Drive and the computer cannot find it. You may have to re-map the drive.
  
  Note: I have had several instances on this on XP computers, where everything looks fine but you still get this error. I believe that the field holding the Default Data Directory must have some sort of garage in it that doesn't get over written unless you do the following.
  
  
  1. Setup -> System -> Default Directory
  2. Select another folder other than PCSW (ie: C:\temp)
  3. Click Ok
  4. Setup -> System -> Default Directory
  5. Select the PCSW folder
  6. Click Ok
  
  Note: I had one person get this error while trying to print payroll checks. It turn out that they were using a signature BMP, but they had the location mapped to 2 different drive letters. So it worked on one machine by not the other. Once I changed it so both machines were using the same mapped drive letter.
  
  Setup -> Account -> Cash Account -> Check Writing Logos
  
  
• Error: 91: Object Variable or with Block Variable not Set - You will get this message it the data hasn't been converted to the new file layouts. Either the system has not converted the System.mdb file to the new version layout or the client data haven't been converted. Check the SYSNEW.mdb and BLANK.mdb files on their computer. It is either missing or the date/size does not match the version they installed. To fix the problem, uninstall the system and reinstall it. This should install the correct versions of the SYSNEW and BLANK files.
  
  Note:Also check the properties on the Icon. You will get this error if the Target or Start In properties are incorrect.
  
  Note:Also check the EXE. If the file is corrupted or the wrong version is installed you will get this error.
  
  Note:If you get this message after clicking [OK], the permissions on the C:\PCSW folder are incorrect. The person doesn't have write/read permissions on the folder.
  
  
• Error 94: Invalid Use of Null - Most likely you have a Null character (chr(0)) instead of a Null string ("") entered into a field.
  
  Note: If you really need/want an empty field you should enter "" into the field.
  
  Note: If Fixed Assets and running Version Control on both the System and Client data doesn't help, then run Setup -> System -> Copy Classification from Master.
  
  
• Error 105: Setup Initialization Error Setup is unable to find installation languages in {name} file. You will get this message if the Windows TEMP folder contains garbage. (ie: Setup*.* files).
  
  Remove the garbage and try reinstalling.
  
  
• Error 339: If you get a message similar to this Run-time error '339' Component 'COMDLG32.OCX' or one of its dependencies not correctly registered: a file is missing or invalid. You have one or more OCX files missing. To correct this:
  
  
  1. Make sure are CD-ROM is in the drive and verify the drive letter.
  2. Go to a MS-DOS/Command prompt.
  3. At the C:\ prompt type in:
     
     WIN 9X & ME - CD\Windows\System
     Windows XP - CD\Windows\System32
     Windows 2000 - CD\WinNT\System32
     
     
  4. Type in Copy {CD drive}:\System32\Redist\MS\System\*.ocx
  5. You can either tell Windows to over write all or not to overwrite any existing OCX files.
  6. Now you need to register the controls.
     
     regsvr32 comctl32.ocx
     regsvr32 comdlg32.ocx
     regsvr32 mschrt20.ocx
     regsvr32 msmask32.ocx
     regsvr32 tabctl32.ocx
     
     
  7. Exit and try the program
     
  
  
• Error 340: Control array element '0' does not exist - The program is trying to use an array element that doesn't exist. This means the program needs to be changed. Have the person tell you the exact steps they did to get the error and try reproducing it here. If you can't, then send them a new version of program to see it this solves the problem. If you can reproduce the error then have a programmer change the program and send the person the new version once its compiled.
  
  Note: The array number can be any number.
  
  Note: Once instance of this was caused by clicking on the [List PR Items] button on the 1099 Amt Setup screen, if you hadn't selected a field first.
  
  
• Error 372: Failed to load control {name} from {name}.OCX. Your version of {name}.OCX may be outdated. Make sure that you are using the version of the control that vas provided with your application.
  
  I have run into several instances where the installation will not overwrite the old OCX files on the client's computer. I had to manually install and register them (Error 339).
  
  Uninstall the program and reinstall it. I have one instance where they installed the wrong Windows version of the program. Uninstalling and installing the Windows 2000 version corrected the problem.
  
  
• Error 380: Invalid Property Value - This means you are trying to access a property that is invalid or out of range.
  
  Note: I had one instance where the client got this error while trying to print checks. It turned out that they didn't have the right check printer selected.
  
  Another time the problem was the computer had lost communication with the printer. I couldn't even get a test page to print. I rebooted the computer and checked to make sure I could get a test page to print. Once this happened I was able to print checks.
  
  Note: I had one instance where the client got this error because they didn't input a point size on the first screen of Mailing Labels. (ie: Changed the point size from "0" to "8").
  
  Note: I had one instance where the client was getting this message when trying to access any screen that had a date on it. It turned out that the Regional Date Setting was using a backslash "\" to separate the date fields. Once I set it to use the standard forward slash "/" the error went away.
  
  Start -> Settings -> Control Panel -> Regional Options -> Date (Tab)
  
  
• Error 381: Invalid Property Array Index - This is an array overflow error. It means you are trying to load to many items into an array. (ie: Vender Maintenance use to allow you to specify 48 accounts to distribute a check to, but Write Vendor Checks only allows 20. So if you input more than 20 accounts in Vendor Maintenance, you would get this error when you went to write this vendor a check)
  
  Note: I had one instance where the client was getting this error when trying to access Calendar Years. I fixed it by registering VSFLEX6D.ocx and RESIZE32.ocx, which are both used by the Calendar Years option.
  
  I had another person get this message on both Calendar Years and Vendor File Maintenance. It turned out that another program installed a version of VSFLEX6D.ocx into the System32 directory. Running regsvr32 C:\PCSW\vsflex6d.oc solved the problem.
  
  
• Error 424: Unknown error: object required - This is a programming error. You need to check to see if a later version corrects this problem. If not then you need to get the data if you cannot reproduce it here.
  
  Note: Version 4.89.01 had this problem which was fixed in version 4.89.03.
  
  
• Error 429: ActiveX component can't create object - This error can occur if one of the components needed by the program is not registered correctly or is missing.
  
  Note: I had one instance where the person download some updates form Microsoft and then got this error. I had them enter the following commands.
  
  
  1. regsvr32 scrrun.dll
  2. regsvr32 "C:\Program Files\Common Files\Microsoft Shared\DAO\DAO350.dll"
  3. regsvr32 "C:\Program Files\Common Files\Microsoft Shared\DAO\DAO360.dll"
  
  
• Error 457: This key is already associated with an element of this collection - You are trying to add an element that already exists in the array.
  
  Note: I had one person get this error while trying to write payroll checks. Running Locate Setup Errors fixed the problem.
  
  
• Error 713: Class not registered. You need the following file to be installed on your machine {name} - This means you are missing a file needed to run the system.
  
  Restore the missing file and if need be register it (regsvr32).
  
  Note: We had one person who couldn't bring up the Tax Tables. It would not give and error, but the screen wouldn't display. Turned out that the \Windows\System\MSSTDFMT.DLL file was missing. I copied from our CD and registered it and this solved the problem.
  
  
• Error 1305: Error Reading File - This error means either:
  
  
  1. Bad Media
  2. Hardware problem
  
  So either the CD-ROM is damaged, dirty or the CD-ROM drive is bad or not Windows compatible (doesn't show up under Device Manager).
  
  
• Error 1308: Source file not found - This means the file the system is looking for doesn't exist, the permissions are wrong or the place where the file resides can't be read. (ie: The file is missing on the CD-ROM, the computer can't read the CD-ROM, etc)
  
  
• Error 1309: Error reading from file {name} Verify that the file exists and you can access it. - This error usually means either:
  
  
  1. Bad Media
  2. Hardware problem
  
  
• Error 1312: Cannot create the directory {name}. A file with this name already exists - The directory/folder listed or the files contained within the folder are corrupted or the permissions are wrong. Thus preventing the installation from continuing.
  
  Mary had a customer get this message while trying to reinstall our program. I had her explore to the C:\Windows\Installer folder and rename the folder {5BFF4D05...} to {5BFF4D05...}.old and reinstall.
  
  
• Error 1324: The path My Documents contains an invalid character - This means the Windows Registry entry for My Documents is pointing to an invalid location (ie: Drive D, and this is no drive D)
  
  They will have to run regedit and correct the problem before we can install our program.
  
  
• Error 1327: Invalid Drive E:\ - You get this message while installing/uninstalling our program or any program for that matter. This message will occur if the path listed cannot be found. It seems to result from the user changing the default location of My Documents or one of the standard folders under My Documents and that location can no longer be accessed/found.
  
  See Error 1606 for the solution to the problem.
  
  
• Error 1402: - This error appears in version 4.64.03+. It means the person forgot to input a User and/or Company Name while installing the program. They need to uninstall the program and reinstall it entering some sort of User and Company Name when prompted.
  
  Note: If their version does not prompt for a User and Company Name you will need to sent them a newer version of the program.
  
  
• Error 1606: Could not access network location - You get this message while installing/uninstalling our program or any program for that matter. This message will occur if the path listed cannot be found. It seems to result from the user changing the default location of My Documents or one of the standard folders under My Documents and that location can no longer be accessed/found.
  
  (ie: \\servername\path\My Pictures\)
  
  
  1. Left click on Start on XP machines, otherwise point to the My Documents Icon on the Desktop.
  2. Right click My Documents
  3. Left click on Properties
  4. Click on the Target (Tab)
  5. Click on the Restore Default Button
  6. Click Apply
  7. Say Yes that you want to move your documents to the new location.
  8. Click Ok and close
  
  These steps will resulting in resetting My Documents back to is original location - C:\Documents and Settings\{user name}\My Documents
  
  Note: I had one person get the following message under Vista while trying to uninstall Adobe and install a newer version.
  
  Error 1606: Could not access network location %APPDATA%\
  
  The registry entry for AppData was corrupt. It wasn't pointing to the correct (default) location. I had to run regedit and correct the value.
  
  
  • Start -> Run -> Regedit
  • Locate HKEY_CURRENT_USER -> Software -> Microsoft -> Windows -> CurrentVersion -> Explorer -> User Shell Folders
  • Look for AppData on the right hand side of the screen. It should look like the line below for Vista
    
    AppData - REG_EXPAND_SZ - %USERPROFILE\AppData\Roaming
    
    
  • Since everything was fine accept the data value I right clicked on AppData and took the Modify option. I then had them type in the correct value and OK it.
  
  The data value for XP if completely different. For detailed information look at knowledge database #886549.
  
  
• Error 1904: Module {name} failed to register - If you get this message while installing the program there is a damaged file on the computer that needs to be replaced before we can install our software. Cancel out of the installation. They will either need their Windows CD or the "CAB" files need to be located on the hard drive.
  
  NOTE: This can also be caused by the person trying to install the program to a network drive (ie: F:, G:, etc) instead to the local hard drive.
  
  Ask if they have installed Tax Works tax program. This program damages a couple of files. You can check to see if this is the problem by:
  
  
  1. Click on Start
  2. Click on Programs
  3. Click on Accessories
  4. System Tools
  5. System Information
  6. You will get the following message:
     
     Msvcirt.dll file is linked to missing export msvcrt.dll: ??_u@yapaxi@z
     
     
  7. Get back to the desktop

  To fix the files (Q296551)
  
  

  1. Make sure our programs has been uninstalled
  2. Make them find their Windows CD-ROM.
  3. Click on Start
  4. Click on Run
  5. Type in SFC and click Start
  6. The System File Checker Utility will come up.
  7. Take the second option - Extract one file from installation disk.
  8. Type in Msvcrt.dll and click Start
  9. Make the Restore from box points to the Windows CD-ROM (ie: D:\WIN98)
  10. The system will know where to restore them to (ie: C:\Windows\System)
  11. Click Ok
  12. Click Skip to bypass saving a copy of the old file.
  13. You should get the message:
      
      The file has been successfully extracted
      
      
  14. It will say you need to reboot but say NO. You need to restore the other file first.
  15. You should be back at the SFC screen.
  16. Type in Msvcirt.dll and click Start
  17. Follow steps 9-15
  18. Close everything and remove the Windows CD-ROM
  19. Reboot the computer and install our software.
      
  
  
• Error 1931: The Windows Installer cannot update the system file {name} - The file is protected by Windows. Just click OK to skip the file and to continue the installation. I haven't encountered any problems if we don't install the version of the program it is complaining about.
  
  Note: This is a Windows File Protection scheme and we cannot get around it. Windows protects what it considers "System Files" and will not let anyone but Microsoft over write them.
  
  
• Error 2229 (While Installing - The computer is having problems reading the CD. The CD can be damaged or the CD-ROM drive just can't read the CD.
  
  The only time I got this we were able to install the program using a networked CD-ROM drive.
  
  
• Error 2889 (While Installing) - This occurs if the computer is infected with the W32.Nimda.A@mm virus. System will not install until this virus has been removed from the computer.
  
  The worm modifies the System.ini file as follows:
  
  shell = explorer.exe load.exe -dontrunold
  
  It also replaces the file riched20.dll which is a legitimate Windows file that is used by such programs as Word.
  
  
• Error 2894 (While Installing) - This occurs if the computer is infected with the W32.Nimda.A@mm virus. See Error 2889 for more info.
  
  Note: This error can occur if the computer had the W32.Nimda.A@mm virus, but was removed with anti-virus software. The riched20.dll is now missing and needs to be reinstalled from the CD-ROM by either using EXTRACT or SFC.
  
  
• Error 3001: Invalid Argument - The application is using arguments that are of the wrong type, are out of acceptable range or are in conflict with another one.
  
  The only way I have found to fix this is to have the person send me the file. I then have to run Compact and Repair Database under MS Access or create a new database and copy the tables in.
  
  
• Error 3011: Microsoft Jet database engine could not find object {name} - This means the object (table) is missing from the database. Run Version Control first if this doesn't help then run Repair Data. Finally check the size and date on the Blank.mdb, BlankTax.mdb and Sysnew.mdb files to make sure they have the correct files installed.
  
  Note:I had one instance where the customer was getting this message when trying to Write Vendor Checks it was complaining about TaxForm. I had them repair the System.mdb file (see 3022) and this solved the problem.
  
  Note: I once got this message while running Version Control and an old version of the BlankTax.mdb file was installed. I copied the latest version from the CD and everything worked great.
  
  Note: I once got this message when the person went to run a Chart of Accounts, it was complaining about TemChart. It turned out that the Blank.mdb file wasn't the correct version. I copied the file off the CD and ran Version Control on both the System file and client data.
  
  Note: I once got this message then the person went to run W2's, it was complaining about Databases. The D###Tax.mdb file was totally corrupted, since there is no Databases table. I had to manually delete the tax file.
  
  
• Error 3020: Update without AddNew or Edit - This is a programming problem. Get as much information as you can and if you cannot reproduce the error have then send their data.
  
  
• Error 3021: No Current Record - The record you are searching for cannot be found.
  
  Note: I had one instance where the client was getting this error, while trying to print Vendor Checks. Repair Data, Version Control and Locate Setup Errors didn't help. They rebooted the computer and the problem went away.
  
  Note: If you get this error while trying to run a Trans Prep then the System.mdb could be corrupted. I had one instance where the client was getting this error on every customer, when trying to run a Trans Prep. I finally had to copy a System.mdb from another computer to get past this error.
  
  I had one person send me their System.mdb file and the problem was the CalendarYear Table was empty. So check Setup -> System -> Calendar Year.
  
  Note: I had one person get this error while trying to run the Laser 941 option. Repairing both the client data and system data didn't help. Neither did a Version Control. I had them send their data and it turned out that the Form941 table was damaged. It recreated the table and the error went away.
  
  Note: I had one person get this error while trying to run either the Laser941 or Payroll Setup. It turned out that the Preparer table in the System file was damaged. It should have had at least 1 record in it and there was none. Nothing you could run in the system would fix the table. I had to manually remove the table and let the system recreate it. Starting with Verions 6.41.01, running Repair System Data will fix this problem.
  
  Note: I had a similar problem with someone trying to run reports (Bank, General Ledger, etc). It turned out the TypeFace table was damaged and it didn't have any records in it.
  
  NOTE: You will get this error if you are running 7.20.01 - 7.23.01 and you are trying to enter G/L transactions on a new customer, starting with transaction number (1). You need to either enter Initial Balances or a better bet would be to enter a least one Journal Entry. The program works fine if there is at least (1) G/L transaction in the system.
  
  NOTE: You will get this error if you are running a Trans Prep on 8.10.02 and you setup Corporate Tax Tables. You will need to add Cost Center - 10 and just call it Test, to get around the error.
  
  
• Error 3022: The change you requested to the table were not successful, because this would create duplicate values in the index, primary key or relationship.
  
  Run Repair Data with Rebuild Data Structures.
  
  Note: You need to run this on the System.mdb file if you get this message while:
  
  
  • Updating Tax Tables - CCB
  • Adjust Field Positions - W2
  
  
  1. Utilities -> System Utilities -> Repair System Data
  2. Utilities -> Repair Data -> Rebuild Data Structures
     
     Make sure Repair Data is looking at "C:\PCSW" or where ever the system is installed on the local hard drive.
     
     
  3. Utilities -> System Utilities -> Process System Data Update
  
  Note: This error could also be caused if you try converting data more than once to the same customer number. Running one of our conversion programs to import data will create tables containing data. If you run the conversion again without first deleting the customer or starting a new one the program will try to create the tables again. Which it cannot do, as the tables already exist.
  
  
• Error 3024: Could not find file 'system.mdb' - This error is generated if they are using a Network drive as the Default Data Directory and the program is not installed on the Network drive and they have the Tax Tables checkbox enabled in the Copy Tables from Default Data Directory (ie: server) section. Since there is no System.mdb file on the server you get this error. Get uncheck this option to solve the problem.
  
  Setup -> System -> Default Data Directory -> Tax Table checkbox
  
  You can also get this error if you run Version Control for all customers and a customer on the list no longer exists, has wrong permissions or is corrupt. If this happens the system will appear locked up. You need to click on File -> Exit to clear the machine. Then run Utilities -> Rebuild File List and run Version Control again.
  
  
• Error 3043 (Disk or network error) - This message can be caused by numerous things, Network problem, NIC, cabling, traffic, lost connection, lost drive mapping, corrupt database, etc. It can also result when you run multiple instances of the CWU program and you are trying to perform data access on the same client database.
  
  The error will occur when the second instance of the program tries to work on the same client data.
  
  Note: I had one instance where the data got corrupted and this message would come up when they tried to run Version Control or enter payroll. We finally solved the problem by running Repair Data and Version Control from the server.
  
  Note: Check to see if the NIC card has the Save Power Option enabled. When enabled this option allows the computer to power down the NIC card. Which will result in the connection with the server being lost. Disabling this option may help the situation.
  
  Device Manager -> Network Adapters -> Card -> Power Management (tab)
  
  Look for Allow the computer to turn off this device to save power. If enabled, disable it.
  
  Note: Also check Network Problems.
  
  
• Error 3044: Item isn't a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.
  
  Most likely the clients computer has lost the network connection and our system can't find/access the data anymore.
  
  
  1. Close the program
  2. Click on My Computer
  3. Look for the network drive (F,X, etc) and double click on it to reestablish the network connection.
  4. Go back into the program and retry the operation.
  
  
• Error 3049: Can't open database. File is corrupt or not a Microsoft Jet Database. - The database is corrupted. Make a backup of the file and try running Repair Data.
  
  Note: Also see Error 70. The person first called with this message while trying to backup. Once he got out of AOL the message went away.
  
  
• Error 3050: Could not lock file - The permissions are wrong. Access will want to create a D#.ldb file in the same directory as the database, and it can't. You will need to give the user Full Access to the directory.
  
  Note: I had one instance where the customer was getting this message when you tried using Advanced Copy to backup to a Thumb Drive. It turned out that the drive was somehow Write Protected. I couldn't even copy a file under Windows (Copy & Paste, Command Prompt Copy).
  
  Look at Error 0x80070052 to see if this will fix it.
  
  
• Error 3051: The Microsoft Jet database engine cannot open the file {name}. It is already opened exclusively by another user, or you need permission to view its data.
  
  Check the Permissions/Attributes on the file. A file marked Read Only will generate this error.
  
  Note: Any file copied from a CD-ROM will be marked Read Only
  
  Note: To remove the Read Only Attribute for all files in a directory:
  
  
  1. Right click on the Start button.
  2. Click on the directory you want of change (ie: "\PCSW")
  3. Click on Edit and take the Select All option.
     
     All the files on the right hand side of the screen should now be highlighted.
     
     
  4. Click on File and take the Properties option.
     
     Note: It make take awhile before the Properties Window pops up. The system has to count all the files and folders in the directory. If there are a lot of files to count and they have a slow system this may take some time.
     
     
  5. Disable the Read Only (checkbox) and click Apply to remove the Read Only Attribute from the files.
     
     If the directory contains folders another window will pop up and ask you:
     
     
     • Apply changes to the selected items only
     • Apply changes to the selected items, subfolders and files
     
     
  
  
• Error 3075: Error description syntax error in {name} in query expression - The {name} describes the type of query the system is having a problem with. In some cases it might be a simple change to the data that will solve the problem, in others the program itself may need to be changed.
  
  
  • Date - The date being used in the database query in invalid. Check the date being used and see where it came from.
    
    
  • Missing Operator - Most likely the system is having a problem with an apostrophe (').
    
    'Ucase(Trim(fdPay1099CoName)) = 'John's Pest Control'
    
    The apostrophe in the 1099 Company Lookup Name is causing the error. In this case by simply removing the apostrophe in the Lookup Name the error goes away.
    
    
  • Missing Operator - You did a Seek (search) and nothing was found. Which resulted in a Null search object. You will need to check the program and you might want to get the data.
    
    Check to see if they were also getting Error 3251 first.
  
  
• Error 3077: Syntax Error (Missing Operator) in Expression - They expression you are trying to create results in a Syntax Error. The client will have to send the data if its not obvious what is wrong.
  
  Note: I had one instance where the client was getting this message when they tried to print a Payroll Summary. The problem turned out to be a corrupted Custom Payroll Item Selection Group (BROWN'S). Once I deleted the group (they only had 1 group setup) everything worked fine.
  
  
• Error 3159: Not a Valid Bookmark - The database is corrupted.
  
  Utilities -> Repair Data -> Rebuild Data Structure
  
  Note: I has one instance where the person was getting this error while trying to run a Trans Prep.
  
  
• Error 3163: Data Field too Small - The field in the table is set to small for all the data being written to be saved. Check the variable length against the data field size
  
  Note: I had one instance where the client was getting this message when they tried to enter an Account Number for a Vendor on the Vendor Maintenance Screen. The problem was the Account Description was over 40 characters in length, which is the maximum length the Vendor Standard Detail Account Description (tbVendorStdDetail) field can hold.
  
  Note: I had one instance where the client was getting this message when they tried to print Print Payable Checks. Going to Select Invoices to Pay showed an invoice having a 7 digit Invalid Account Number. Went into Input Invoices brought up the invoice and changed the posting account to a valid account number. The checks printed just fine after that.
  
  Note: I had a couple people get this on the W2 Setup option. It turned out that the bottom City field on the Company -> Payroll Reports/Tax Forms Tab was too large. (ie: Charlotte North Carolina)
  
  Note: I had one person get this message when they went to enter a Customization Code. It turned out that there was a blank character stored for this field and adding a three character code, added up to four. Running Locate Setup Errors removed the blank character and solved the problem.
  
  
• Error 3164: Could not Update Field - The most likely cause is, you are trying to rewrite the Primary Key of an existing record with a new value (ie: Transaction Number 33 -> Transaction Number 34) while the transaction is being used. You cannot do this.
  
  
• Error 3167: Record is Deleted - The index on a table is corrupted. Run Repair Data and Rebuild Data Structures.
  
  Note: The customer has a power failure while entering data and got this message when they tried to run a Trans Prep. Repairing the data solved the error problem.
  
  
• Error 3197: The Microsoft Jet database engine stopped the process because you and another user are attempting to change the same data at the same time - The database is corrupted. You can try running Repair Data, but I didn't have any success with the (1) client I had. They had to send the data here.
  
  Note: I had once instance where by running Repair Data and selecting Access 97. It repaired fine and I could run Version Control without incident. I then ran Repair Data again and selected Access 2002 and Rebuild Data Structures.
  
  
• Error 3202: Couldn't save; currently locked by another user - This means that someone else has a hold of the file. It can also mean that the lock files is damaged or that the computer is confused and things someone has the file open.
  
  Make sure that no one else has the data open and check for LDB and OPN files. If found delete them. If you can't then reboot compute, if the data is on a server you will have to reboot the server.
  
  Note: I had one instance where after doing the above things it still gave this error message. I then tried running Repair Data. Which solved the problem.
  
  
• Error 3204: Database already exists - You are trying to create a database that already exists. You will need to determine what is going on in the program to see if the existing file needs to be removed.
  
  Note: I have had several instances where a person gets this error while trying to backing up. Its caused by either (1) of both of the following temporary files being left behind.
  
  
  1. H#.mdb - Hold File
  2. T#.mdb - Compacted Hold File
  
  
• Error 3218: Couldn't update; currently locked - This means that someone else has a hold of the file. It can also mean that the lock files is damaged or that the computer is confused and things someone has the file open.
  
  Make sure that no one else has the data open and check for LDB and OPN files. If found delete them. If you can't then reboot compute, if the data is on a server you will have to reboot the server.
  
  Note: I had one instance where after doing the above things it still gave this error message. I then tried running Repair Data. Which solved the problem.
  
  Note: I had one instance where the person was getting this message when they tired to print a Payroll Summary. But changing the Default Data Directory to the correct network drive and folder solve the problem?
  
  Note: I had a couple people get this error when they went into Advanced Payroll -> Time Card Entry. It turned out the server was running Novells NetWare, so had them increase the following settings and the error disappeared.
  
  Maximum Record Locks per Connection (ie: 500 -> 1000)
  Mazimum File Locks per Connection (ie: 250 -> 500)
  
  I suggest doubling what ever number there are currently set to.
  
  
• Error 3251: Error Description Operation is not supported for this type of object - This usually means you are doing a Seek (search for a variable) and nothing is being found, because the field you are searching is not the Primary Key and you didn't temporarily set the field you wanted to search as being the Primary Key.
  
  This error requires a program change.
  
  
• Error 3260: Couldn't Update; Currently locked by user {name} on machine {name} - This means that someone else has a hold of the file. It can also mean that the lock files is damaged or that the computer is confused and things someone has the file open.
  
  Make sure that no one else has the data open and check for LDB and OPN files. If found delete them. If you can't then reboot compute, if the data is on a server you will have to reboot the server.
  
  
• Error 3265: Item not found in this collection - There is a field missing in a table.
  
  
  • If you get this message while trying to run Version Control. Make sure that they have the correct Blank.mdb and Sysnew.mdb files installed for their version and then run Version Control again.
    
    
  • If you get this message while trying to Activate a client. Then run Repair Data on the client and try activating them again.
    
  
  Note: I had (1) person who got this error when trying to run Payroll Liability Lists. It turned out they had setup a TE - Texas Exempt in the State Setup. Once TE was removed the error went away.
  
  Note: I had (1) person who got this error when trying to run Unemployment Reports. Turned out they had setup NZ - New Zealand in the State Setup. Once NZ was removed the error went away.
  
  Note: I had (1) person get this error while trying to run the Setup 1099's option in the W2 Program. I solved the problem by running Repair Data and Alternate Version Control on the main database (ie: D950.MDB).
  
  
• Error 3315: Error Description File Cannot be Zero Length String - Run Repair Data and check Rebuild Data Structure.
  
  
• Error 3320: Syntax error (comma) in table-level validation expression - I am not sure about this error because the customer who got it was going to be getting a new computer in a few days.
  
  I believe the problem had to do with the MFC40.DLL file being the wrong version. They were running Windows 98 SE but the file was from a Windows 98 OEM machine.
  
  
• Error 3343: Unrecognized database - The database is corrupted and needs to be sent here to see if we can fix it. This is typically caused when the Jet database engine was improperly shut down during the process of writing to disk.
  
  
• Error 3356: The database is opened by user {name} on machine {name} - The computer/network thinks the file is locked by the machine name listed. Which may or may not be the case. The only way to solve this is to reboot the computer shown in the error message. If they can't figure out which computer that is, then you will have to reboot the entire network.
  
  
• Error 3420: Object invalid or no longer set - You usually get this error after loading an update. The System.mdb is corrupted or the system was unable to convert it.
  
  
  1. Cannot get into the program at all.
     
     
     1. Register the DAO360.dll file.
        
        regsvr32 "C:\Program Files\Common Files\Microsoft Shared\DAO\DAO360.dll"
        
        
     2. If this doesn't help then the System.mdb file is corrupted and you will need to do the following:
        
        Copy SysNew.mdb to System.mdb
        
        or
        
        Copy System.mdb from another computer to this one.
        
     
     
  2. If you can get into the program test if System.mdb file is good.
     
     
     1. Run Utilities -> System Utilities -> Repair System Data
     2. Run Utilities -> System Utilities -> Process System Data Update
     
     If you get an error on either step then go to the Cannot get into the program at all step.
     
  
  Note: I had one instance where a customer was getting this message while trying to print a 944. I had them exit the program and come back in and this solved the problem.
  
  
• Error 3421: Data Type Conversion Error - A field in the database is damaged and is set to a unexpected data type. The system can't write/read the data field.
  
  Note: I had one instance where the client was getting this message when they tried to print a Balance Sheet or Income Statement. It turned out that the System file as damaged. Once I ran Repair Data with Rebuild Data Structures on the system file the error went away.
  
  
• Error 3633: Can not load DLL {name} - The DLL is either missing or corrupt. You will have to reload the DLL and if need be, make sure it registers correctly.
  
  Note: I had one instance where Windows was complaining about MsJet40.dll. I tried removing and reloading the program, but got the same error. I had to manually copy the MsJet40.dll from the CD and register it.
  
  
• Error 3709: The search key not found in any record - A memo field created with an index on that field (or a field that includes text that is automatically indexed), can only handle a specific amount of text. Once you reach this limit (approximately 3450 characters), you can enter no more text and you can also not edit the existing data.
  
  Note: I had one customer get this message while trying to run a report. I had them run Alternate Version Control and Locate Setup Errors. This fixed the problem.
  
  Note: I had one customer get this message while trying to run a Trans Prep. The cause didn't make sense so I had them run Repair Data, which solved the problem.
  
  
• Error 3799: Could not find field Description - The table definition in one of the tables is damaged. You will need to have the client send the data here. First try running the Access Repair option. If this doesn't work then you will then want to extract all non-corrupted tables into a new access database. Using the import option. Then reconstruct the damaged table.
  
  
• Error 3800: {Key Name}is not an index in this table.
  
  Run Repair Data and select Rebuild Data Structures
  
  
• msjet35.dll
  
  
  • Any error referencing this file, usually means they installed the wrong version of the program for their operating system.
    
    (i.e. Installed Windows 98 version on a Windows 2000 computer.
    
    
  • If you are getting it only on one client then try:
    
    
    1. Uninstalling the program (it maybe damaged), removing all shared programs, DO NOT REBOOT THE COMPUTER (this could cause problems do to the damage.
    2. Reinstall the program.
  
  
• 1 File Failed to Register - If you get this message while trying to install the system try the following:
  
  
  • uninstall the program
  • CD-ROM -> Utils Folder -> vbrun60 (executing this file will install some DLL's the system needs)
  • reinstall the program
  
  
• Error 0x80070052 - The directory of file can not be created - The USB drive is either.
  
  
  • Out of disk space - Check the amount of free space.
  • The root directory has to many files in it - See how many files are listed. If there is a lot, then create a new folder or better yet use and existing folder and copy some of the files into it. If you can't create a folder, copy one of the files off the drive. Delete it and try creating a folder.
  
  If nothing seems to work then copy off all the desired data and reformt the drive.

Last Modified: