3001 - Access Violation
The information in this article applies to:
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.
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.
Note: The "x" in the following error message(s) acts as a numeric wildcard and can represent any number. Information about these numbers and the codes they represent can be found in KB Article R10044, "How to Interpret Fatal Error Messages."
3000-0-EEDFADE
3000-0-C06D007E
3000-0-C0000006
A known cause of the above error is a result of including a large image file, such as an 8.5x11 bitmap, on your statement. When printing statements to PDF or DropBox while including a large image file, the error may occur after several pages have been printed. This error is not limited to .BMP image files; it's strictly size related.
Due to the fact that this is a file size limitation, the resolution is to use a smaller image file. Using a smaller image file, such as a .JPG or .PNG file, will most likely resolve this issue. If you are using a .BMP file, try using an image editing program to convert or save the image to a .JPG or .PNG file. Cropping down a large image file will also decrease the overall size of the file.
This error can be caused by if the user does not have read/write access rights to a file required by the program. Users must have full read and write access to all files in the Tabs3 and PracticeMaster current working directory. Information about system user rights and how they must be configured can be found in KB Article R11258, "User Rights Needed to Install and Use Tabs3 and PracticeMaster Software."
Caution: We recommend you check with your system administrator before making any security changes.
Lost network connections are one cause of this specific error. This usually is caused by a "network glitch" between the workstation and the file server.
Another known cause of this specific error is Terminal Services related. The following is an example of the Fatal Error log including the full Traceback Path when the 3000 error is Terminal Services related.
System: T3 Date: 2009-05-26 Time: 13:29:16 User: Computer Name: \\S2008X32 Error Number: 3000 - 0 - C0000006 File Name: N/A Source File: STERR.CPP File Handler: None Release Date: 05/13/09 Version: 15.1.5.644 Current Working Directory: \\s2008x64\sti\ Error Message: Error 3000-0-C0000006 Program Exception has occurred in STERR.CPP. Traceback Path: CleanTempDirectory::addToNumProcesses CleanTempDirectory::CleanTempDirectory setTempPath STIApp::readDataConfig CWtabsApp::InitInstance
If using Terminal Server 2008 and the error received has the Traceback Path as shown above, then install the latest program files. The current version works around the Terminal Server 2008 issue by installing the STUINFO.DLL file locally.
If you are not using Terminal Server 2008, use the troubleshooting steps below:
This error can be caused by a number of different things including network glitches, corrupted data files, corrupted exe or dll files, or corrupted printer driver files.
When troubleshooting this error, it is important to look at the Traceback Path.
A number of the more common causes are listed below, along with steps to follow to resolve the issue.
To troubleshoot this error:
Note: Additional troubleshooting information can be found in the General Troubleshooting section.
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-c0000005. If you suspect this problem, run a Data File Integrity Check.
Some common situations and resolutions are listed below. If none of these situations apply to you, please continue on to the General Troubleshooting Steps:
Warning: 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.
Caution: Data integrity may be compromised if the STTASK.DAT file is deleted while a user is accessing the software. Furthermore, deleting the STTASK.DAT file while other users are active may cause Fatal Errors to occur during program execution. Do not delete the STTASK.DAT file unless you are absolutely sure no Tabs3 and PracticeMaster software is being used.
Platinum Note: For Version 14.3 and later Platinum users (formerly CSV), deleting STTASK.DAT will have no effect as a troubleshooting step. Beginning with Version 14.3, STTASK.DAT is an empty file that is locked while the STI Director Service is running to prevent any issues with non-Platinum software attempting to use the file.
The following article contains a quick troubleshooting guide and gives detail information on exception errors and how to resolve them. Please consult:
The following articles contain additional information on how to resolve fatal error messages.
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.
© 1999-2012 Software Technology, Inc. All rights
reserved. Terms of Use
The maker of Tabs3 and PracticeMaster
Tabs3, PracticeMaster, and the “pinwheel” symbol (
) are registered trademarks of Software Technology, Inc.
e-Mail Suggestions for the Knowledge Base to: kb@Tabs3.com
Technical Support via e-mail is not available.
Knowledge Base: http://support.Tabs3.com
Web Site: http://www.Tabs3.com
