1510 - Unable to Restore Data Files  

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

The information in this article applies to:

• Tabs3 Billing Software Version 15, 14 & 12
• PracticeMaster Version 15, 14 & 12
• System Configuration Version 15, 14 & 12
• Tabs3 Trust Accounting Software (TAS) Version 15, 14 & 12
• Tabs3 General Ledger Software (GLS) Version 15, 14 & 12
• Tabs3 Accounts Payable Software (APS) Version 15, 14 & 12

SUMMARY

The "Unable to Restore Data Files" error may occur when using the Restore Data Files program supplied with Tabs3 and PracticeMaster Version 15, 14, 12, 11, and 10 software or Tabs3 Version 9. The Restore Data Files program is used to restore the last backup made using the Back Up Data Files program.

MORE INFORMATION

If the Restore Data Files program aborts for any reason, Do Not continue to use the software. You must successfully restore your data files before continuing.

Version 16

The backup files are stored in a folder (or subdirectory) named BACKUP that is located under the program directory. Each time the backup program is run, the information is backed up to a file named STBACK.ARQ and placed in a folder named using the yyyymmddnn format (year, month, day, number of the backup for that day). So a folder named 2011091401 would be the first backup done on September 14th, 2011. Additionally, any CMARCXX.DAT and CMARCXX.IDX files are copied into the folder. The backup program will create up to three backups of all software products. When restoring a file, you can select which of the up to three available backups you want to restore. If the Store current data in a secondary backup file before restoring option is selected, the current data files are backed up to a new folder before the data is restored, and once the restoration is complete the oldest backup is deleted.

See KB Article R11330, "Built-In Back Up and Restore Programs" for more information on Version 16 backup files.

Prior Versions

The backup files are stored in a folder (or subdirectory) named BACKUP that is located under the program directory. Each time the backup program is run, the information is backed up to a file named ??BACK.ARQ. If an *.ARQ file already exists, the backup program renames the *.ARQ file to ??BACK.BAK before beginning the backup procedure. Likewise, if the "Store current data in a secondary backup file before restoring" check box is checked, the current data files will be backed up to a file named ??BACK.SND.

RESOLUTION

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

• Check the amount of hard disk space available. You will need to free up enough hard disk space to restore the data files if there is not enough hard disk space available.

• It is possible that the *.ARQ file is corrupted. Try to restore a prior backup. See KB Article R11420, "Troubleshooting the Built-In Backup Program (Version 16)". In prior versions, try to restore the *.BAK or *.SND files (if they are recent). You must manually rename the *.SND or *.BAK to *.ARQ (outside of the program) and then run the Restore Data Files program. See KB Article R10278, "Troubleshooting the Built-In Backup Program (Versions 15, 14, 12 & 11)" .

• It is possible that there is a network communications problem. Copy the Tabs3 and PracticeMaster directory to a local hard disk and run the program locally. If the system restores fine on a local hard disk, this indicates that there is a problem with the network hardware or software. See KB Article R10184 - Network Troubleshooting Guide.

• Try restoring the data files from the firm's nightly backup tape or disk(s) rather than using the Restore Data Files program.

REFERENCES

• KB Article - R10012 - Using Universal Naming Convention (UNC) Paths
• KB Article - R10044 - How to Interpret Fatal Error Messages
• KB Article - R11420 - Troubleshooting the Built-In Backup Program (Version 16)
• KB Article - R10278 - Troubleshooting the Built-In Backup Program (Versions 15, 14, 12 & 11)
• 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