1460 - Error Rebuilding Index File 
Last reviewed: 06/11/2010
Article ID: R10189
The information in this article applies to:
- Tabs3 Billing Software Versions 15, 14, 12 and 11
- PracticeMaster Versions 15, 14, 12 and 11
- System Configuration Versions 15, 14, 12, and 11
- Tabs3 Remote Entry Software Versions 15, 14, 12 and 11
- Tabs3 Trust Accounting Software (TAS) Versions 15, 14, 12 and 11
- Tabs3 General Ledger Software (GLS) Version 15, 14, 12 and 11
- Tabs3 Accounts Payable Software (APS) Version 15, 14, 12 and 11
SUMMARY
An error 1460 occurs when a problem is encountered during the Reindex Files program and
the Compact Select Files option is not checked.
More Information
Tabs3 maintains two types of files: data files and index files. Data files (*.DAT)
contain the information that has been entered in the file. Index files (*.IDX) are
"pointer" files used by Tabs3 to locate the position of specific records
within the data file. If an index file is corrupted, missing or not in sync with the data
file, the Reindex Files program can generate a new index. An Error 1460 indicates an
error occurred during the rebuild process. The *.IDX file may have become corrupted due to
hardware failure or network software 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."
1460-x-12-x
1460-x-12-32
1460-x-13-x
1460-x-16-x
1460-x-30-x
1460-x-32-x
1460-x-36-x
1460-x-37-5
1460-x-37-112
1460-x-43-x
1460-x-48-x
1460-x-55-x
1460-x-122-x
1460-x-123-x
1460-x-401-x
1460-x-484-x
1460-x-485-x
1460-x-493-x
1460-x-496-x
1460-x-512-x
1460-x-527-x
1460-x-x-64
Error Not Listed
RESOLUTIONS FOR SPECIFIC ERRORS
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.
page top
1460-x-12-32 (could not open file: sharing violation)
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
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.
page top
1460-x-16-x (could not create index file)
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.
Copy the program directory to a local hard disk and run the program locally. Be sure to
change any paths, such as the archive path in Tabs3, before testing if necessary.
If the system runs fine on a local hard disk, this usually indicates that there is a
problem with the network hardware or software.
If the problem is corrected when the program is run locally, further troubleshooting
into the network is needed. See R10184 - Network Troubleshooting
Guide.
- See also: General Troubleshooting
page top
1460-x-13-x (unknown file type)
1460-x-30-x (drn exceeds logical end of file)
1460-x-32-x (attempt to delete record twice in a
row)
1460-x-43-x (version incompatible)
1460-x-48-x (operation incompatible with type of
file)
1460-x-122-x (attempt to change fixed vs. variable length)
1460-x-123-x (variable length header has bad record link)
1460-x-401-x (resources not enabled)
1460-x-512-x (data file loop detected)
1460-x-527-x (BIDX.ERR index must be rebuilt: see CTSTATUS)
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
(AFIC) 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.
The data file is corrupt, it may be possible to correct the error by reindexing the file
and choosing the Compact Data Files option. Make a temporary backup and run the Reindex
Files program for the specific file referenced in the error message (see R10102, "How The Reindex Files Program Affects Your Data Files"
for information on reindexing). 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.
The program file may be damaged. Reinstall the software. See KB Article
R11257, "How to Reinstall Tabs3 and PracticeMaster
Version 15
Software."
If you are running in a network environment see KB Article R10184,
"Network Troubleshooting Guide."
- The data file is corrupted and cannot be repaired. Restore from a complete backup and
run the DFIC and AFIC programs to insure the restored data is error free. If it is not
possible to restore from a backup, contact Technical Support at 402-419-2210. Please
have your program serial number and all of the error information available to help
expedite your support call.
page top
- If the system is running on a network, determine if other workstations are having a
problem.
- If the error is limited to an individual workstation, there is a problem with the
workstation receiving the error.
- If the error occurs on multiple workstations, copy the program directory to a local hard
disk and run the program locally. Be sure to change any paths, such as the archive path in
Tabs3, before testing if necessary. If the system runs fine on a local hard disk,
this usually indicates that there is a problem with the network hardware or software.
- See KB Article R10184, "Network Troubleshooting Guide."
page top
- 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:
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, you will also
need to 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, you will also
need to 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.
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.
page top
1460-x-37-112 (write error / there is not enough space on the disk)
This error indicates that there is not enough space on the hard disk.
- Check the amount of hard disk space available.
- If you are using a Windows network, determine whether disk space quotas are enabled. If you are
limited to a fixed amount of disk space, this error will occur if reindexing the selected data file(s)
causes you to exceed that limit. For more information, please see KB Article R10957,
"How Disk Space Quotas Affect Tabs3 and PracticeMaster Software."
page top
1460-x-55-x (file deletion failed)
- 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 Windows Explorer.
- Select the program directory.
- Right-click on the file that is listed in the error message.
- Select Properties.
Clear the Read Only check box under Attributes.
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 (R10200).
See KB Article R10184, "Network Troubleshooting Guide."
- See also: General Troubleshooting
page top
1460-x-484-x (error opening sortwork file)
1460-x-485-x (error creating sortwork.00x)
1460-x-493-x (error renaming sortwork.00x)
- 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:
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, you will also
need to 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, you will also
need to 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.
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.
Check the amount of hard disk space available.
Copy the program directory to a local hard disk and run the program locally. Be sure to
change any paths, such as the archive path in Tabs3, before testing if necessary.
If the system runs fine on a local hard disk, this usually indicates that there is a
problem with the network hardware or software.
If the problem is corrected when the program is run locally, further troubleshooting
into the network is needed. See R10184, "Network Troubleshooting
Guide."
- See also: General Troubleshooting
page top
1460-x-496-x (insufficient disk space)
page top
1460-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
page top
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 R10102, "How The Reindex Files Program Affects Your Data Files"
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."
The data file is corrupted. Restore from a complete backup and run the Data File
Integrity Check and Archive File Integrity Check to insure the data is error free. If it
is not possible to restore from a backup, it may be possible to correct the error by
reindexing the file and choosing the Compact Data Files option.
- If you are running in a network environment see KB Article R10184,
"Network Troubleshooting Guide."
page top
REFERENCES
- KB Article R10044 - How to Interpret Fatal Error Messages
- KB Article R11257 - How to Reinstall Tabs3 and
PracticeMaster Version 15 Software
- KB Article R11010 - How to Reinstall Tabs3 and PracticeMaster Software
( Version 14 & 12)
- KB Article R10888 - How to Reinstall Version 11 Tabs3 and PracticeMaster Software
- 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-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}