3000 - Program Exception
3001 - Access Violation

Last reviewed: 11/25/2003
Article ID: R10057

The information in this article applies to:

PracticeMaster Version 11 & 10 (formerly Case Master)
System Configuration Version 11 & 10
Tabs3 Version 11, 10 & 9
Tabs3 Remote Version 11, 10 & 9
TAS Version 11 & 10

SUMMARY

An exception error or access violation error signifies that something unexpected has happened within the Windows environment, typically an improper memory access such as when an application reads or writes to a memory location that has not been allocated to it thereby overwriting and corrupting other program code already in that area of memory.

MORE INFORMATION

Normally, when an exception error or access violation error occurs, it is usually non-recoverable and the system must either be restarted or shut down. Troubleshooting any of these errors can be difficult to diagnose especially if the error is not reproducible.

3001-0-c000005

A known cause of this error is a result of importing or converting transactions that have an invalid date. Normally there are precautions built into the software to check for invalid dates. However, some versions of the merge program in Tabs3 allowed a date of "mm/dd/yyyy" to be imported or transactions with a valid formatted date but invalid in that it was before 01/01/1970. For example, importing a transaction dated 03/03/33 should be imported as 2033. However, if it is imported as 1933, this will cause the error when running certain reports. The Data File Integrity Check will check for these errors. However, if you run a Detail WIP Report or other report that works with the transactions, you may receive an error 3001-0-c000005. If you suspect this problem, you can run a Transaction File List with a cut-off date of 01/01/1970.

RESOLUTION

Some common situations and resolutions are listed below:

Although the error may appear to be cleared up by rebooting, the error may be random and indicative of other problems. Review the STERROR.LOG file to determine if other errors for other workstations have occurred. Analyzing whether or not other errors have occurred and then troubleshooting those errors may be more productive than troubleshooting the wrong error. KB Article R10757, Anatomy of a Fatal Error Message, contains detailed information regarding the information tracked in the STERROR.LOG file.
If the error occurs when printing, first try duplicating it. If it occurs again, try printing to a different printer driver. If the error doesn't occur when printing using a different printer driver, reinstall the printer driver that was used when the error occurred.
(The following resolution was successful when Novell Client 32 Ver 3.2 was corrupting the task file. The following resolution is valid only when the errors occur as a result of an action where the task file is being accessed, such as when loading an exclusive task.)

The STTASK.DAT (Version 10 or later) or STITASK.DAT (Version 9) file could be corrupted. Have all users close all open tasks. The Active User List can be used to determine which users are accessing which tasks. Once all users have exited, delete the appropriate file (STTASK.DAT or STITASK.DAT depending on your version) found in the Tabs3 and PracticeMaster program directory and attempt to duplicate the error.

Caution

The STILOCK.DAT file could be corrupted. Treat this the same as the STTASK.DAT (or STITASK.DAT) file above with the same cautions.
The STI.INI file could be corrupted. The error should not be reproducible on other machines. Try renaming the STI.INI file to STI.TMP and rerunning the application to see if the error is eliminated. The STI.INI file resides in the workstation's Windows directory.
Note: Renaming the STI.INI file will cause a new one to be created with new workstation defaults which affects all Tabs3 and PracticeMaster Windows products used on the workstation.
Check the user's network permissions, especially when running Windows NT/2000/XP. You could get this error if the user doesn't have administrative rights in the program or working directories.
There may be a conflict between the program and a virus protection application, screen saver or power-saver feature. Disable these functions and try to reproduce the error. Several related links are listed under References below.
If you get this error while previewing a verification list in Tabs3 Remote, it is most likely caused by an older version's verification files. To resolve this error, delete R3FEEVER.* and R3CSTVER.* in the Tabs3 Remote directory.
There have been instances of data corruption that will cause this error. If all of the steps listed above have been followed and you still receive the error, eliminate the network factor entirely. Copy the entire program directory locally and try to duplicate the error. If the error is duplicated, you must restore from a backup, or you may want to make arrangements with a Technical Support Representative to send in your data for evaluation/repair. Please note that standard data repair charges apply for this procedure.

The following article contains a quick troubleshooting guide and gives detail information on exception errors and how to resolve them. Please consult:

KB Article R10011 - Troubleshooting Invalid Page Fault and Other Exception Errors.

REFERENCES

The following articles contain additional information on how to resolve fatal error messages.

KB Article R10044 - How to Interpret Fatal Error Messages
KB Article R10757 - Anatomy of a Fatal Error Message
KB Article R10760 - Antivirus Software Information
KB Article R10008 - Troubleshooting Performance & Speed
KB Article R10061 - Screen Saver Conflicts
KB Article R10339 - Power Management Issues with Tabs3 and PracticeMaster Software Products

THE INFORMATION PROVIDED IN THE SOFTWARE TECHNOLOGY, INC. KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SOFTWARE TECHNOLOGY, INC. DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SOFTWARE TECHNOLOGY, INC. OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF SOFTWARE TECHNOLOGY, INC. OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

3000 - Program Exception 3001 - Access Violation