Errors
Contents
General Errors
Error 52
Error 52 - Bad file name or number
Similar to Error 53, it generally occurs when using EXE tags as the print job is sent directly to the LPT1 port. If using a printer on a different port such as USB, the printer needs to be shared and mapped to the LPT1 port. Once mapped, it will now accept traffic from the LPT1 port. This error is caused by trying to send the print file directly to LPT1 when it is not available or disconnected.
See Printer Mapping to USB for more details.
Error 53
Error 53 - File not found.
Tag Printing
When using EXE tags, the print job is sent directly to the LPT1 port. If using a printer on a different port such as USB, the printer needs to be shared and mapped to the LPT1 port. Once mapped, it will now accept traffic from the LPT1 port. See Printer Mapping to USB for more details.
File Browser
When trying to use the file browser to add images or link data paths, the workstation needs to have MemCpy.dll installed to use the file browse buttons.
To fix this, copy File:MemCpy.dll and paste it in your C:/Windows/System32 folder. This will need to be done on all computers experiencing the issue. For 64 bit machines, put it in the C:/Windows/SysWOW64 folder as well.
Error 75
Error 75 - Path/File Access Error Tag Printing Path Issue, see Printer Mapping to USB for more details.
Error 76
Error 76 - Path Not Found
Opening Reports
The reports startup is incorrect. Go to Maintenance->System->Store Setup and check the Reports Startup field. Refer to the following examples to correct the path. For custom installations, other paths may be required.
2008 Version, 32 Bit Computer
"C:\Program Files\Microsoft office\Office11\MSACCESS.EXE" /Runtime "C:\Executive\ExecutiveReports.mdb" /WrkGrp "C:\Executive\system.mdw"
2008 Version, 64 Bit Computer
"C:\Program Files (x86)\Microsoft office\Office11\MSACCESS.EXE" /Runtime "C:\Executive\ExecutiveReports.mdb" /WrkGrp "C:\Executive\system.mdw"
2007 Version, 32 Bit Computer
"C:\Program Files\Microsoft office\Office11\MSACCESS.EXE" /Runtime "C:\Program Files\Executive\ExecutiveReports.mdb" /WrkGrp "C:\Program Files\Executive\system.mdw"
2007 Version, 64 Bit Computer
"C:\Program Files (x86)\Microsoft office\Office11\MSACCESS.EXE" /Runtime "C:\Program Files\Executive\ExecutiveReports.mdb" /WrkGrp "C:\Program Files\Executive\system.mdw"
Tag Printing
Tag Printer Path Issue, see Printer Mapping to USB for more details.
Error 94
Error 94 - Invalid Use of Null
A required field has been left blank. If printing something customer related, check the customer profile and ensure that the Customer Type is not blank. If it is blank, set it to Retail and try printing again.
Error 429
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. It may point to a component of Access that has been modified, such as by installing Office 2007 over top of Access 2003 Runtime.
Try the code below if it's believe to be a registry issue, if not, try using the Access 2007 Runtime instead as it may not have the same registry issues.
|
regsvr32 scrrun.dll
|
Error 2001
Error 2001 - The previous operation was cancelled
The ReportsExportPath column is missing in the setup file. This error generally comes up when trying to open reports. Find a correct setup file on a workstation that doesn't have this error, and then replace problematic setup file to resolve the issue.
Error 2046
Error 2046 - The command or action 'save record' isn't available now.
This is generally given after a message that a Job Bag is locked by a user/computer. To unlock the Job Bag, reopen and close it from that user/computer, then retry from the initial workstation.
Error 2114
Error 2114 - Error 2114: Microsoft Access doesn't support the format of the file "filename", so it can't load the picture.
The Microsoft Graphic Filters are required to view images in MS Access. If the workstation doesn't have Microsoft Office installed, the Graphic Filters need to be installed manually, see Downloads for more information.
Error 3027
Error 3027 - Cannot update. Database or object is read only.
The file in use is being restricted to Read Only, but requires Read/Write permissions. Grant 'Everyone' Read/Write Access on this file (for example, ExecutiveReports.mdb), and reopen the file to ensure permissions are now correct.
Error 3031
Error 3031 - Not a Valid Password
This error means that a file is not linked properly, a permissions issue may be preventing access, or a setup/data file being of the wrong version so the password is unable to open it.
Error 3043
Error 3043 - Disk or Network Error
The network connection or drive mapping is not finding the data file on startup. Try going to Computer (My Computer in XP), locating the mapped network drive, and double clicking it.
- If it connects without issue, try opening Executive again, as the connection should be restored
- If it fails, the server may not be turned on or something may be preventing connection such as a permissions issue
- If the mapped network drive isn't showing up, it will need to be remapped. See Mapping Network Drives for more information.
Go to Maintenance->System->Link Data and ensure that the paths are all correct, as they must be pointing at valid files.
Error 3044
Error 3044 - Item isn't a valid path
The network path is not finding the desired file. Refer to Error 3043.
Error 3051
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.
Compacting Data
During data compacting, this means that the file is open on another workstation. Since compacting the data requires everyone to be out of the database, the other workstation must exit Executive before compacting the data. Log everyone off and try again.
On Startup
On startup, this error warns that permissions are not set up correctly.
- Try logging onto Windows as Administrator. If the error doesn't appear, it is due to a user permissions issue.
- Ensure that the local Executive folder allows full read/write access to Everyone.
- Ensure that the server's shared folder allows full read/write access to Everyone for Executive files. For more information, see Mapping Network Drives
Error 3075
Error 3075 - Syntax error (name) in query expression
Error 3086
Error 3086 - Could not delete from specified tables
When encountered during startup, it generally points to a permissions issue, refer to Error 3043. Once everything is set up properly, relink the data and restart Executive.
Error 3343
Error 3343 - Unrecognized Database Format
When opening Executive, this error warns that the database may be badly corrupted. Backup your file and compact it, to confirm the corruption. Restore from your latest clean backup, as the file likely cannot be repaired.
This is typically caused when the Jet database engine was improperly shut down during the process of writing to disk, such as the program being shut down unexpectedly, power loss, or network loss.
Other Issues
Desktop Shortcut not working
If the desktop shortcut to open Executive isn't working, Right Click it and Click Properties. Find the Target field. May need to scroll left and right to read the entire thing. Compare it to the following paths and verify that the existing path is correct based on your setup.
2008 Version, 32 Bit Computer
"C:\Program Files\Microsoft office\Office11\MSACCESS.EXE" /Runtime "C:\Executive\Executive.mdb" /WrkGrp "C:\Executive\system.mdw"
2008 Version, 64 Bit Computer
"C:\Program Files (x86)\Microsoft office\Office11\MSACCESS.EXE" /Runtime "C:\Executive\Executive.mdb" /WrkGrp "C:\Executive\system.mdw"
2007 Version, 32 Bit Computer
"C:\Program Files\Microsoft office\Office11\MSACCESS.EXE" /Runtime "C:\Program Files\Executive\Executive.mdb" /WrkGrp "C:\Program Files\Executive\system.mdw"
2007 Version, 64 Bit Computer
"C:\Program Files (x86)\Microsoft office\Office11\MSACCESS.EXE" /Runtime "C:\Program Files\Executive\Executive.mdb" /WrkGrp "C:\Program Files\Executive\system.mdw"
If you are unable to find the error on this page, you may want to refer to http://www.iasonline.com/john/pcsa/fixes.html for similar Access Error explanations.
