1350 - Error Reading File 
Last reviewed: 07/22/2011
Article ID: R10193
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 read 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
1350-x-x-64
1350-x-36-1450
Error not listed
RESOLUTIONS
1350-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"
1350-x-36-1450
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
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:
- Someone may have reset user(s) in the Tabs3/PracticeMaster software (R10789).
-
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.
- 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).
- 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.
- 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.
- 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).
- 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.
- 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.
- 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.
- 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.
- 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:
Server 2008, Server 2008 R2, Windows 7 & Vista Steps
- Open the Windows Explorer.
- Select the Tabs3 program directory and right-click it.
- Select Properties.
- Select the Sharing tab. Note: This tab is
only available when performing this procedure at the server.
- Click the Advanced Sharing button. View screenshot.
- If you receive a UAC prompt, click the Continue button.
- Select Share this folder.
- Click the Permissions button. View screenshot.
- The Permissions for Full Control should be set to
Allow for all users who have access to the software. View screenshot.
Note: In some instances, the Properties window may also contain a
Security tab. If this is the case with your system, perform the
following steps:
- Select the Security tab.
- The Permissions for Full Control should be set to
Allow for all users who have access to the software. View screenshot.
2000 Pro, 2000 Server, 2003 Server & XP Pro Steps
- Open the Windows Explorer.
- Select the Tabs3 program directory and right-click it.
- Select Properties.
- Select the Sharing tab. Note: This tab is
only available when performing this procedure at the server.
- Click the Permissions button. View screenshot.
- The Permissions for Full Control should be set to
Allow for all users who have access to the software. View screenshot.
Note: In some instances, the Properties window may also contain a
Security tab. If this is the case with your system, perform the
following steps:
- Select the Security tab.
- The Permissions for Full Control should be set to
Allow for all users who have access to the software. View screenshot.
XP Home, XP Pro (using Simple File Sharing) Steps
- Open the Windows Explorer.
- Select the Tabs3 program directory and right-click it.
- Select Properties.
- Select the Sharing tab. Note: This tab is
only available when performing this procedure at the server.
- The Share this folder on the network and the Allow network users to
change my files check boxes should be checked. View screenshot.
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.
- Open the Windows Explorer.
- Select the Tabs3 program directory.
- Right-click the file that is listed in the error message.
- Select Properties.
- Clear the Read Only check box under Attributes.
- 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.
- Make a temporary backup and run the Reindex Files program for the specific
file referenced 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.
- If you are running in a network environment see KB Article R10184,
"Network Troubleshooting Guide".
REFERENCES
- KB Article R10044 - How to Interpret 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
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}
){kind=link}