The information in this article applies to:
An error 1310 results when the software attempts to open a file but the operating system could not complete the request.
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."
1310-x-12-32
1310-x-12-x
1310-x-12-1450
1310-1-12-0
1310-1-12-64
1310-x-x-64
1310-1-13-0
1310-x-14-x
1310-x-22-x
1310-x-36-x
1310-x-36-1450
1310-x-36-0
1310-1-36-183
1310-x-40-0
1310-x-53-0
1310-1-127-10053
1310-x-150-10093
1310-x-798-x
The File Handler error 12 is "Could not open file; check sysiocod value." This is found on the File Handler Errors list.
The Operating System Error Code 32 is "ERROR_SHARING_VIOLATION. The process cannot access the file because it is being used by another process." This is found on the Operating System Errors list.
This error indicates the file is in use.
A file can be opened in one of two modes: Exclusive mode or Shared mode. If a file is opened in Exclusive mode, no other program can open the file (in either mode). If a file is opened in Shared mode, no other program can open the file in Exclusive mode. Tabs3 and PracticeMaster Programs open data and index files in Shared mode 95% of the time. It is normal for a file such as T3CLIENT.DAT to be open many times. Certain exclusive options, such as Reindex Files, may open files in Exclusive mode. This error indicates the server believes there is a conflict with how the file was opened (i.e., Exclusive mode vs. Shared mode).
Check for unexpected open files.
Causes
Troubleshooting Steps
The File Handler error 12 is "Could not open file: check sysiocod value." This is found on the File Handler Errors list. This error indicates that the user does not have proper access to the file.
Check for unexpected open files.
Causes
Troubleshooting Steps
Windows XP & Windows 2003 Server Note: When a directory is shared in Windows XP or Windows 2003 Server, the default Share Permissions for other users is set to Read Only. The behavior is different from earlier versions of Windows where the default Share Permissions for other users is set to Full Control.
Note: If a firm is using NTFS, this may be limiting the rights that the user(s) has to the directory. A good way to test this is to open a Command Prompt and change to the Tabs3 program directory and perform the following: 1) create a file; 2) rename the same file; and 3) delete the same file. If a user is able to do these three steps, then the user has sufficient NTFS rights to that particular directory.
Note: Additional information regarding sharing files and folder over a network can be found in Microsoft's Knowledge Base at www.support.Microsoft.com. Article 324267 deals with a Windows Server 2003 domain environment and Article 301198 deals with a Windows 2000 environment.
Make sure the current working directory is correct.
Check for the specified file and the associated IDX file. Does it exist? Can you copy it to another directory?
If you receive a fatal error message affecting CMARC0.IDX, run a Data File Integrity Check with the Check E-mail Attachments check box selected; this may provide additional information for troubleshooting purposes. We have had reports of a 1310-x-12-x in CMARC0.IDX when adding E-mail Journal records while Data File Integrity Check warnings exist. Correct all warnings using the information found in KB Article R11008, "Journal Attachment Errors" and attempt to add the Journal record again.
Check the workstation's CONFIG.SYS file for the maximum number of open files allowed. Try increasing the number of files to 100 and restarting the computer (i.e., rebooting). If the workstation uses Windows 95 and no CONFIG.SYS file is present, Windows 95 defaults to 60 files, which may or may not be enough. Try creating a CONFIG.SYS file that has the line FILES=100 and then restarting the computer. The CONFIG.SYS file should be created in the root directory of the boot disk. (Note: Windows NT does not use CONFIG.SYS. There is no open file limit on the server or workstation.)
Check the amount of hard disk space available.
The Microsoft Knowledge Base indicates this error is likely due to low kernel memory availability at the server. This may be a temporary condition. Try the operation again in a few minutes. If this error is repeated, you may need to reboot the server. Newer 64-bit server operating systems such as Windows Server 2008 have vastly increased kernel memory limits that may reduce or eliminate this "Insufficient System Resources" error. See MS KB Article 294418 for additional information.
The File Handler error 12 is "Could not open file: check sysiocod value." This is found on the File Handler Errors list. This error indicates that the user does not have proper access to the file.
See also: 1310-x-12-x
Run the Data File Integrity Check program and/or Archive File Integrity Check (Tabs3) if possible. The Data File Integrity Check and Archive File Integrity Check should detect errors when the IDX files have become corrupted. If a DAT file is corrupted, there is a strong possibility that the system will crash during the integrity check programs thereby requiring that you restore your data.
Make a temporary backup and run the Reindex Files program for the file specified in the error message. The Reindex Files program deletes the existing index files for the selected data files and recreates them. The ability to recreate the index files allows for the possibility of salvaging data if the index files become corrupted due to hardware failure. See KB Article R10102 - How Reindex Data Files Affects Your Data.
If the error is in the STUSER.IDX file, start System Configuration and reindex the User file. Refer to KB Article R10913, "Reindexing the System Configuration User File".
Run the Data File Integrity Check (DFIC) and/or the Archive File Integrity check (AFIC) after reindexing to verify there are no errors. If the DFIC or AFIC errors remain, you must restore the data files from a backup.
This error can result from having SMB enabled on a Windows 2000 Server and running a Windows XP Workstation. See KB Article R10705 - Issues Running Tabs3 and PracticeMaster Software under Windows 2000/XP.
The file handler error 13 is "unknown file type" which indicates the file has become corrupted. This is found on the File Handler Errors list. This type of corruption may be unrepairable.
The File Handler error 14 is "File Corrupt At Open." This is found on the File Handler Errors list.
The file handler maintains a safety flag in the header of each file. When the program is going to modify the file, this flag is set. After the file is safely updated to disk, the safety flag is reset. If something happens to interrupt the file updating to disk before the safety flag is reset (e.g., the program hangs, the computer is reset, the network goes down, the power is lost, etc.), the program will detect that the file was not updated properly the next time the program opens the file. The error shown above will be the result.
This error can be a serious problem since the program did not completely update the file in the proper manner. We are not able to determine if the data file is valid or not.
If restoring from a backup is not possible, you can try to reset the safety flag using the Reindex Data Files program. The Reindex Data Files program will let you select files individually or you can select all files. Once the reindex is finished, you should run the Data File Integrity Check (DFIC). See KB Article R10102 - How Reindex Data Files Affects Your Data.
If the Reindex Data Files program does not solve the problem restoring from backup is the only option.
If this error occurs while trying to load Tabs3 and the error message references one of the following files: T3CLIENT, T3MACRO (T3TMACRO Version 9) or T3EMPL, refer to KB Article R10001 - Starting Tabs3 Generates Fatal Error.
EXAMPLE: You run the Change Key Type program and change the matter length from 4 to 5. After the data has started processing, the power to your office goes out. Once power is restored, you go into the Client file and receive an error 1310-0-14-0 in T3CLIENT. When you run the Data File Integrity Check, you get the same error. When you run the Reindex Data Files program and reindex only the client file, the program finishes without errors. When you go into the Client file there is not an error anymore. However, when you run DFIC there are 108,642 errors. Most of the errors are 51s and 54s. This indicates that there is a problem with the client IDs. This is a case where the BEST thing to do is restore your data files.
Note: A common misconception is that this error is caused by open files. Checking for open files has nothing to do with this particular error.
This error can occur when PracticeMaster is configured to display separate tabs in the Client window for the Area of Practice files and multiple Client windows with Area of Practice tabs are opened at the same time. Displaying separate tabs for Area of Practice files is optional and is configured by selecting the Area of Practice Pages check box in the Configure Client Pages program (File | Open | Client | Edit | Configure Client Pages).
To prevent this error from occurring, use one of the following options:
The File Handler error 36 is "Read error: check sysiocode error." This is found on the File Handler Errors list.
If you receive a fatal error message affecting CMARC#.*, rebuild the E-mail Attachments file. We have had reports of a 1310-x-36-x in CMARC#.* when attempting to run a Data File Integrity Check with the Check E-mail Attachments check box selected while one of the CMARC#.* files are missing or corrupted. If rebuilding the E-mail Attachments file does not correct this issue, it may be necessary to restore from a backup made prior to these errors occurring.
If the system is running on a network, determine if other workstations are having a problem. If the error does not occur on other workstations, there may be a problem with the workstation on which the error occurs.
If the error is happening on other workstations, try copying the software to a local drive to see if the error continues.
The Microsoft Knowledge Base indicates this error is likely due to low kernel memory availability at the server. This may be a temporary condition. Try the operation again in a few minutes. If this error is repeated, you may need to reboot the server. Newer 64-bit server operating systems such as Windows Server 2008 have vastly increased kernel memory limits that may reduce or eliminate this "Insufficient System Resources" error. See MS KB Article 294418 for additional information.
The File Handler error 36 is "Read error: check sysiocode error." This is found on the File Handler Errors list.
Check the size of the data file. If the file size is very small, then the data file is most likely corrupted. Restore from a complete backup and run Data File Integrity Check to insure the data is error free.
This error can result from having SMB enabled on a Windows 2000 Server and running a Windows XP Workstation. See KB Article R10705 - Issues Running Tabs3 and PracticeMaster Software under Windows 2000/XP.
This error can occur if running a non-Client/Server application with data that is Client/Server data. For example, if using the Client/Server version of Tabs3 and using Tabs3 Remote, this error will occur when starting Tabs3 Remote if the Tabs3 Remote validation files were created using the Tabs3 Client/Server version but the Tabs3 Remote program has not yet been updated to the Client/Server version. Another reason this error can occur is if a Client/Server version was installed and used and now you want to revert to a non Client/Server version.
To determine whether the software is a Client/Server version, select Help | About. The software is Client/Server version if the serial number is part of the 90000 series.
When starting a Version 15 or 14.3 Client Server Version (CSV) software product that has not yet been converted from the standard version to CSV, a message similar to the following may be displayed:
Error (53) occurred while attempting to open the user file. The program will now exit with an error. The CSConv14.exe program must be run before this program can continue.
Clicking OK on this message will generate a 1310-14-53-0 error. You need to stop the STI Director service, and then run the correct conversion program depending on the Version of Tabs3 and PracticeMaster the firm is using.
If you fail to stop the STI Director service before running the conversion program, you will receive a 1020-1-32 error.
Note: This error message can occur in both CSV and non-CSV installations in Version 15.
Additional information on the Client Server Data Conversion program is available in KB Article R11177, "Converting and Updating CSV Software."
The cause for these errors is related to users being in the software when
reset, or users in the software when the STI Server is shut down. If you receive
this error, you can check the error and reset logs to verify that this was the
case. These log files can be accessed via the View | Log Files menu options.
If the user who received this error appears in the reset log
around the same time as the error occurred, it is probable that the reset caused
the fatal error. In this case, verify that the STI Server is running, and
attempt to log into the software again. If the error persists when attempting
subsequent logins, contact technical support.
If the above situation is not applicable, the next section
may apply.
This error can occur if running the Client Server Version of Tabs3 or PracticeMaster software on a Vista workstation. The error occurs on Vista workstations after a period of inactivity with Version 14.1 and earlier Tabs3 or PracticeMaster Client Server software, using STI Server Version 6.11.36. To resolve this error, update to the current Tabs3 PracticeMaster Client Server software and update the STI Server software. (Note: The Tabs3 PracticeMaster Client Server software must be updated to at least Version 14.3 and the STI Server Version to 8.27.143 to resolve this issue.)
This error can occur if running the Client/Server version of Tabs3 or PracticeMaster software. This error indicates that the program was attempting to open a file and during that routine the STI Server was shut down. The opening of the file could not complete because the program detected that the STI Server was shutting down and could not continue to run. To resolve the error, restart the STI Server and repeat the process that produced the error earlier.
This error can occur if running the Client/Server version of Tabs3 or PracticeMaster software. This error indicates that the server has a file locked that was not released, typically due to a user running an exclusive task when the STI Director was closed/aborted without the STI Server having been restarted. Basically, the STI Director component and STI Server are "out of synch". To resolve this error, make sure all users have exited, and then shut down the STI Director and STI Server and restart them. Repeat the process that produced the error earlier.
Run the Data File Integrity Check (DFIC) and/or Archive File Integrity Check (AFIC) if possible. The DFIC and AFIC will report errors if the data has become corrupted. If errors are reported, correct them and then try to recreate the fatal error.
The index file could be corrupted. Run reindex files for the specific file (see KB Article R10102 - How Reindex Data Files Affects Your Data for information on reindexing).
The program file may be damaged. Reinstall the software. See KB Article R11257 - How to Reinstall Tabs3 and PracticeMaster Version 15 Software.
If the specific file is CMSYSTEM\CMXREF, you must select the Related Party file (CMSYSTEM\CMRELATE) with the Compact Selected Files option marked. For more information about this procedure, see KB Article R11286, "Rebuilding the PracticeMaster Cross Reference File".
The data file is corrupted. It may be possible to correct the error by reindexing the file and choosing the Compact Data Files option. If the reindex does not resolve the issue restore from a complete backup and run Data File Integrity Check to insure the data is error free..
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-2010 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
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}