1360 - Error Writing File 
Last reviewed: 07/26/2011
Article ID: R10214
The information in this article applies to:
- Tabs3 Billing Software Version 16, 15, 14 and 12
- PracticeMaster Version 16, 15, 14 and 12
- System Configuration Version 16, 15, 14 and 12
- Tabs3 Remote Entry Software Version 16, 15, 14 and 12
- Tabs3 Trust Accounting Software (TAS) Version 16, 15, 14 and 12
- Tabs3 General Ledger Software (GLS) Version 16, 15, 14 and 12
- Tabs3 Accounts Payable Software (APS) Version 16, 15, 14 and 12
SUMMARY
The program was not able to update a record in the specified file. This
could be due to an error returned by the Operating System or
a data corruption problem.
Specific Errors
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."
1360-x-2-x
1360-x-3-x
1360-x-4-x
1360-x-147-x
1360-x-x-64
Error Not Listed
RESOLUTION
1360-x-2-x
1360-x-3-x
1360-x-4-x
1360-x-147-x (general index problems)
- Run the Data File Integrity Check (DFIC) program and resolve any errors
that are reported. If the problem is in Tabs3, also run the
Archive Data Integrity Check and resolve any errors that are reported.
It is likely that these integrity check programs will abort with a
1400-x-160-x error. This indicates that the index file(s) are corrupt.
- Make a temporary backup and run the Reindex Files program for the
specified file 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.
- Run the Data File Integrity Check and/or Archive File Integrity Check
after reindexing to verify there are no errors.
- Reindexing the file may resolve the immediate problem but does not address
why the error was received in the first place. In a network environment,
make sure that the file server is updated to the LATEST patch level, all
client redirectors have been updated and the appropriate registry changes
(i.e., opportunistic locking) have been made. See KB Article R10200,
"Redirector Problems and Other Network Problems".
- Note specifically for 1360-x-2-x errors: If running Tabs3 and PracticeMaster
Platinum Version software,
update to the most current release of the STI Server software.
- Note specifically for 1360-x-4-x errors: This error will more than likely not be written to the STERROR.LOG file
that exists in the Tabs3 Program Directory. Therefore, it is very important all
the information for this error is either written down or a screen shot is saved
so the information can be presented to our Technical Support Department if necessary.
page top
1360-x-x-64
- This error can result from a temporary loss of Network Connection.
- See KB Article R11289, "Troubleshooting Error Code 64: Network Name No Longer Available"
- See KB Article R10184, "Network Troubleshooting Guide"
- This error could be caused by corrupted data or by hardware
problems. Run the Data File Integrity Check (DFIC) program and resolve
any errors that are reported. If the problem is in Tabs3, also run the
Archive Data Integrity Check and resolve any errors that are reported.
- 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".
- If the third segment of the error code is a 37, a hardware or network
error of some type is indicated. Look at the fourth segment for the
Operating System error code. If you are on a
network, refer to KB Article R10184, "Network
Troubleshooting Guide". Also, if you are on a Windows network, determine whether
disk space quotas are enabled. For more information, please see KB Article
R10957, "How Disk Space Quotas Affect Tabs3 and PracticeMaster
Software".
References
- KB Article R10200 - Redirector Problems and Other Network Problems
- KB Article R10044 - How to Interpret Fatal Error Messages
- KB Article R10307 - Operating System Error Codes
- KB Article R10184 - Network Troubleshooting Guide
- KB Article R10957 - How Disk Space Quotas Affect Tabs3 and PracticeMaster Software
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