1370 - Error Deleting Records  

Last reviewed: 07/29/2011
Article ID: R10215

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

An error 1370 results when there is a problem when the program attempts to delete a record. This error is typically associated with index file problems.

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."

1370-x-3-0
1370-x-69-0
1370-x-146-0
1370-x-36-5
1370-x-105-5
1370-x-2-33
1370-x-3-33
1370-x-36-33
1370-x-50-33
1370-x-x-64

Error Not Listed

RESOLUTION

1370-x-3-0
1370-x-69-0
1370-x-146-0
1370-x-2-33
1370-x-3-33 (general index file problems)

• 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".

• Run the Data File Integrity Check after reindexing to verify there are no errors. If the error is in Tabs3, also run the Archive Integrity Check to verify there are no errors.

• Reindexing the file may resolve the immediate problem but does not address why the index was corrupt 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 & Other Network Problems".

1370-x-36-5 (access denied)

• Check network directory permissions. Each user must have all rights to the files in the program directory. You can check rights on a Novell network by typing "RIGHTS" at the network directory DOS prompt. If using a Windows Server, check for permissions by doing the following at the server:

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.

• Check the file attributes. If the file has a "Read Only" attribute, change it to a "Read Write" attribute by performing the following steps.
1. Open the Windows Explorer.
2. Select the Tabs3 program directory.
3. Right-click the file that is listed in the error message.
4. Select Properties.

5. Clear the Read Only check box under Attributes.

• This error can be caused by some virus checking software. Make sure the Tabs3 program directory is excluded from continuous virus scanning. You may want to temporarily disable antivirus software to determine if the problem is eliminated. KB Article R10760, "Antivirus Software Information", provides additional information regarding issues with antivirus software.

• 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. Note that not all cases of corrupted data can be caught by these programs. Therefore, even if the integrity check reports no errors, corrupted data is still a possibility.

• If the Data File Integrity Check reports no errors, make a temporary backup and run the Reindex Files program for the specified file in the error message. Rerun the Data File Integrity Check again (or Archive Integrity Check if the error was in an archive file).

• If no errors are found, attempt to duplicate the error. If you cannot duplicate the error, then most likely the problem is with the network.

• 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 persists, refer to KB Article R10184, "Network Troubleshooting Guide", and the General Troubleshooting section of this article.

1370-x-105-5 (could not undo ISAM update. rebuild files)

• Check network directory permissions. Each user must have all rights to the files in the program directory. You can check rights on a Novell network by typing "RIGHTS" at the network directory DOS prompt. If using a Windows Server, check for permissions by doing the following at the server:

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.

• Check the file attributes. If the file has a "Read Only" attribute, change it to a "Read Write" attribute by performing the following steps.
1. Open the Windows Explorer.
2. Select the Tabs3 program directory.
3. Right-click the file that is listed in the error message.
4. Select Properties.

5. Clear the Read Only check box under Attributes.

• This error can be caused by some virus checking software. Make sure the Tabs3 program directory is excluded from continuous virus scanning. You may want to temporarily disable antivirus software to determine if the problem is eliminated. KB Article R10760, "Antivirus Software Information", provides additional information regarding issues with antivirus software.

• 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. Note that not all cases of corrupted data can be caught by these programs. Therefore, even if the integrity check reports no errors, corrupted data is still a possibility.

• 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 persists, refer to KB Article R10184, "Network Troubleshooting Guide", and the General Troubleshooting section of this article.

1370-x-50-33
1370-x-36-33 (lock violation)

• If the Novell Client 32 Redirector is being used, it needs to be the latest version and latest Service Pack available for the version being used. We have had reports of certain versions of Client 32 being responsible for these errors. STI Article R10200, "Redirector Problems and Other Network Problems", includes detailed information regarding the Novell Client 32 Redirector.

• Check for an anti-virus program on the workstation and servers. Sometimes an anti-virus program causes interference with the operation of other programs. This includes potentially interfering with STI applications' ability to obtain file locks. Try disabling the virus scanner, or at least exclude the STI program directory from being scanned, and see if the error persists. STI Article R10760, "Antivirus Software Information", provides additional information regarding issues with antivirus software.

1370-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 also: General Troubleshooting

• See KB Article R10184, "Network Troubleshooting Guide"

General Troubleshooting

• Check for unexpected open files.

    Causes
  
  This error may be a one-time only error or a recurring error. Troubleshooting steps vary depending on whether you simply want to get up and running as quickly as possible or you want to determine why these errors are occurring. Our recommendation is to always determine causes of errors whenever possible. Common causes of unexpected open files include but are not limited to:

  1. Someone may have reset user(s) in the Tabs3/PracticeMaster software (R10789).
  2. Other software may have files open, such as:
     • Antivirus software - Make sure the Tabs3 program directory is excluded from continuous virus scanning (R10760).
     • External backup software - Make sure backups are not being made while anybody is using the Tabs3/PracticeMaster software. Additional precautions are required for Client Server Version (CSV) software (R11213).
     • Disk shadowing software or other software.
  3. A workstation may have frozen up on the network.

  Detailed information regarding what causes these errors can be found in R10751, "Tech Tip:  Sharing Violation Errors".

    Troubleshooting Steps
  
  Any of the following steps may be used to troubleshoot this error:

  • Try the task again. If the open file was due to other software using the file, the file may no longer be open.

  • Check the Reset Log. Determine whether any users have been reset recently by checking the Reset Log file (View | Log Files | Reset Log).
    1. If reset user(s) are found, verify the user(s) that were reset are not still in the software.
       • If the user(s) that was reset is frozen, then end the program. Use the Task Manager if necessary.
       • Nobody should use the Tabs3/PracticeMaster software until the reset user has exited.
    2. After the reset user(s) have exited the software, have the reset user(s) either:
       • Log out of the network and log back in; or
       • Reboot and log back into the network.
    3. Try the task again. If the error no longer occurs, run a Data File Integrity Check to ensure there are no errors in the data.
    Note: Detailed information regarding the consequences of resetting users can be found in R10789, Resetting Users.

  • Check the Error Log. Determine whether any users have had any problems on the network or in Tabs3 by checking the Error Log file (View | Log Files | Error Log).
    1. For users who have recently had problems on the network, verify that those users are not still in the software.
       • If the user(s) that had problems is frozen, then end the program. Use the Task Manager if necessary.
       • Nobody should use the Tabs3/PracticeMaster software until those user(s) have exited.
    2. After those user(s) have exited the software, have the user(s) either:
       • Log out of the network and log back in; or
       • Reboot and log back into the network.
    3. Try the task again. If the error no longer occurs, run a Data File Integrity Check to ensure there are no errors in the data.

  • Check the file server for open files.
    • KB Article R10028 contains information on how to check for open files on Windows servers. KB Article R10181 contains information on how to check for open files on Novell NetWare.
      1. DO NOT close the open files using these utilities. Once you determine which files are open on which workstation, have those workstations either:
         • Log out of the network and log back in; or
         • Reboot and log back into the network.
      2. Try the task again. If the error no longer occurs, run a Data File Integrity Check to ensure there are no errors in the data.
    • Note: Be aware that the above techniques only find files that were opened on the server across the network. They do not find files that were opened by programs running locally on the file server (e.g., CSV components, antivirus software, etc.) You may need to use a utility that checks for locally opened files on the file server such as Process Explorer (see Microsoft KB How to Article 242131, Display a List of Processes That Have Files Open).

  • Restart STI Server and the Director. If using the Client Server Version (CSV), try restarting the STI Server and the Director.
    • After rebooting, try the task again. If the error no longer occurs, run a Data File Integrity Check to ensure there are no errors in the data.

  • Reboot all workstations. Keep in mind that simply rebooting the workstation does not close the file it opened on the file server; logging back into the network closes the open file.
    • If using Terminal Services, reboot the Terminal Server.
    • After rebooting, try the task again. If the error no longer occurs, run a Data File Integrity Check to ensure there are no errors in the data.

  • Reboot the file server. Although rebooting the file server will close any open files, it is typically not a practical troubleshooting step when other courses of action are available.
    • After rebooting, try the task again. If the error no longer occurs, run a Data File Integrity Check to ensure there are no errors in the data.

• Check permissions. Each user must have all rights to the files in the program directory. You can check rights on a Novell network by typing "RIGHTS" at the network directory DOS prompt. If using a Windows Server, check for permissions by doing the following at the server:

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.

• Check the file attributes. If the file has a "Read Only" attribute, change it to a "Read Write" attribute by performing the following steps.
1. Open the Windows Explorer.
2. Select the Tabs3 program directory.
3. Right-click the file that is listed in the error message.
4. Select Properties.
5. Clear the Read Only check box under Attributes.

Error Not Listed

• 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. Note that not all cases of corrupted data can be caught by these programs. Therefore, even if the integrity check reports no errors, corrupted data is still a possibility.

• If the Data File Integrity Check reports no errors, make a temporary backup and run the Reindex Files program for the specified file in the error message. Rerun the Data File Integrity Check again.

• If no errors are found, attempt to duplicate the error. If you cannot duplicate the error, then most likely the problem is with the network.

• 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 persists, refer to KB Article R10184, "Network Troubleshooting Guide", and the General Troubleshooting section of this article.

REFERENCES

• KB Article R10044 - How to Interpret Fatal Error Messages
• KB Article R10200 - Redirector Problems and Other Network Problems
• KB Article R10184 - Network Troubleshooting Guide

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