1020 - Error Opening File  

Last reviewed: 07/21/2011
Article ID: R10032

The information in this article applies to:

• All Products

SUMMARY

The software attempted to open a file but the operating system could not complete the request. 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.

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

1020-x-0
1020-x-2
1020-x-3
1020-x-4
1020-x-5
1020-x-8
1020-x-32
1020-x-51
1020-x-53
1020-x-64
1020-x-65
1020-x-1231
1020-x-1450

Error Not Listed

RESOLUTION

1020-x-0 (Error opening file)

• Check the GLS Data Path. If a GLS Client data path cannot be found, a fatal error 1020-x-0 can occur. The data path must be restored, or a new path specified, for that GLS Client. More information about GLS Clients can be found in KB Article R10837, "All About GLS Clients."
• See: General Troubleshooting

page top

1020-x-2 (File not found)

• Verify that the filename referenced exists in the program directory or specified data directory. If not, it may be necessary to RESTORE FROM A BACKUP.

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

• See also: General Troubleshooting

page top

1020-x-3  (Path not found)

• Check the GLS Data Path. If a GLS Client data path cannot be found, a fatal error 1020-x-3 can occur. The data path must be restored, or a new path specified, for that GLS Client. More information about GLS Clients can be found in KB Article R10837, "All About GLS Clients."

• See also: General Troubleshooting

page top

1020-x-4 (Too many open files)

• If using an operating system that doesn't have unlimited open files, increase file handles on the workstations and/or file server (maximum of 255 file handles each on the workstation or server).

• See Also: General Troubleshooting

page top

1020-x-5 (Access denied)

• If using an operating system with User Account Control (i.e., Windows 7 or Vista), this error can occur when attempting to run Tabs3 or PracticeMaster software when the data files are installed to a protected system folder, such as C:\Windows or C:\Program Files. It is recommended that Tabs3 and PracticeMaster software be installed to C:\Tabs3. Note that this does not affect workstation installations. When using SETUP.EXE to configure your workstation(s), you can continue to use the default location of C:\Program Files\Tabs3. For additional information about this situation, see KB Article R11238, "How Windows 7 and Vista Affect Tabs3 and PracticeMaster Software".

• If this error occurs when starting the program, and the error references a file stored in another path, make sure you have full access rights to the path where the file is stored.

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

• Note: When files are restored from a CD, they are restored as read-only.
   
• See also: General Troubleshooting

page top

1020-x-8 (Not Enough Memory)

• Please call our Technical Support Department with the following information:

  • What Operating System?

  • Running on a network? If Yes, what Redirector is used and what are the settings?

  • Full information regarding the error, including what was being done in the program at the time.

• See also: General Troubleshooting

page top

1020-x-32 (Sharing violation)

• Windows CSV Note: This error can result from attempting to run the Client Server Data Conversion program (CSCONV14.EXE) after the STI Director service has been started. This can occur if a user has attempted to open the version 14.3 Client Server Version software before successfully completing CSCONV14.EXE (i.e., the STTASK.DAT file is locked by the STI Director Service). To fix this issue, stop the STI Director Service and run CSCONV14.EXE, located in the Tabs3 and PracticeMaster program directory. Once the conversion successfully completes, start the STI Director Service and then start the software again.

page top

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

1020-x-51 (The remote computer is not available)

• This error can result from a loss of Network Connection.  (Version 14 or greater)

page top

1020-x-53 (Network path not found)

• This error can result from a loss of Network Connection.  (Version 14 or greater)

• If using a peer to peer network such as Windows NT or Windows 95 networking, make sure that the workstations do not have the Tabs3 and PracticeMaster software running in a "mapped root" directory. This can be determined by checking the Help|About Tabs3 information and checking the "Program Directory". If it is something like F:\ or F: then the software is running from a mapped root. If this is the case, either the drive letter needs to be mapped differently or the software needs to be moved.

• See also: General Troubleshooting

page top

1020-x-64 (The specified network name is no longer available)

• 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

page top

1020-x-65 (Network 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.

• See also: General Troubleshooting

page top

1020-x-1231 (The remote network is not reachable by the transport)

• This error can result from a loss of Network Connection.

• See also: General Troubleshooting

page top

1020-x-1450 (Insufficient system resources exist to complete the requested service)

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

• See also: General Troubleshooting

page top

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.

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

• Reboot the workstation.

• Check the amount of hard disk space available.

References

• KB Article R10044 - How to Interpret Fatal Error Messages
• KB Article R10181 - How to Check for Open Files on Novell NetWare
• KB Article R10028 - How to Check for Open Files on Windows NT4/2000/XP
• KB Article R10200 - Redirector Problems and Other Network Problems
• KB Article R10751 - Sharing Violation Errors

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