Using the Sage 50 Database Repair Utility

Using the Sage 50 Database Repair Utility

Support Team Asked on December 30, 2017 in Sage.
Add Comment
  • 1 Answer(s)


    Special attention must be used in environments with multiple releases of Sage 50. When uninstalling/reinstalling Pervasive, use the version of the tool that coincides with the latest version installed in the environment. For example, if versions R2011, R2012, and R2013 are installed on the same machine, you would need to use the 2013 version of the tool when uninstalling/reinstalling Pervasive. However, when troubleshooting a suspected bad data path for the R2012 version of Sage 50, you would need to use the 2012 version of the tool for data path troubleshooting.

    Start the Tool

    1. When the tool is started, all of the files necessary for the tool to function will be extracted.


    2. In the following message you can select the link to view a Sage Knowledgebase article if you want to find out more about this tool.


    3. Read the End User License Agreement – click Agree if you agree to all terms and conditions to start using the tool.


    4. You have three available options within the tool:
      • Remove Pervasive
      • Install Pervasive
      • Create New Local Data path


    Remove Pervasive

    The Remove Pervasive utility will uninstall Pervasive from the local computer. This utility is usually used in conjunction with the Install Pervasive utility. It is important to ensure that all users have logged out and closed Sage 50 before using this utility – upon starting this utility; a message will provide a reminder:

    Note: The initial attempt to uninstall Pervasive will usually fail. This is normal and is caused by Pervasive being started during the uninstall process. Just run the process again to successfully uninstall Pervasive.


    Install Pervasive

    The Install Pervasive utility will install Pervasive to the local computer and automatically patch it with necessary updates. This utility is usually used in conjunction with the Remove Pervasive utility. It is important to ensure that all users have logged out and closed Sage 50 before using this utility – upon starting this utility; a message will provide a reminder:


    Note: If the install process fails more than twice, there is a high probability that there is a registry issue and you are getting Error 1402 – error.

    Create New Local Data path

    The Create New Local Data path utility generates a new Sage 50 data path directory with factory-default files. This provides a clean set of files for Sage 50 to work with to troubleshoot issues with the existing data path. You can also copy a Sage 50 company into the new data path directory to test an existing company with the new data path.

    Note: The Create New Local Data path utility is an advanced option, so we recommend that you only use it with the guidance of Sage 50 Customer Support.

    1. Verify the location of the new data path, It should be in a location that previously did not exist on the PC.


    2. Company to Copy feature will move the entire directory from the previous data path to the newly created data path. If the copy feature fails, it is due to SmartPosting and / or Pervasive running on the PC. You may need to manually stop these services by going to Services.msc.

      Note: When copying a company to the new data path it will copy the entire directory, including backups, attachments, etc. This process could take a long time depending on the size of the directory and the speed of the computers / network doing the file transfer.

    3. Manage INI Files allows you to revert back to the initial data path. Select the original data path and select Make Active. Then Close out of the Database Repair Tool.

    4. If the newly created data path is working and you desire to use it permanently moving forward, you will also need to complete the following steps to ensure future updates will function correctly:
      1. Navigate to the following registry key (replace <version number> with 18 for 2011, 19 for 2012, 20 for 2013)
        • 64-bit machine – HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Peachtree\Version\<version number>\Online Update
        • 32-bit machine – HKEY_LOCAL_MACHINE\SOFTWARE\Peachtree\Version\<version number>\Online Update
      2. Update the String Values for “Path” and “UpdatePath” to match the new data path that you have chosen above.
      3. For Release 2011 and 2012 only (skip to step 6 if on Release 2013): Navigate to the following registry key (replace <version number> with Version 18 for 2011, Version 19 for 2012
        • 64-bit machine – HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Peachtree\Application\<version number>
        • 32-bit machine – HKEY_LOCAL_MACHINE\SOFTWARE\Peachtree\Application\<version number>
      4. On the right pane of the window, right-click the Version string and select Modify.
      5. In the Value Data field, change the last digit in the value to 0. Click OK. Close the registry editor
      6. Reinstall the latest Sage 50 Service Release.

    Source: Sage Community forums.

    Disclaimer: Sage Accounting Solution is an independent provider of Sage Related services and is not affiliated with Sage.

    See More: Support for this issue is available either by self-service or paid support options. Experts are available to resolve your Sage issue to ensure minimal downtime and continue running your business. First try to resolve the issue yourself by looking for a resolution described below. If you are experiencing too many issues, you may want to more info Call Sage Support Phone Number

    Support Team Answered on December 30, 2017.
    Add Comment
  • Your Answer

    By posting your answer, you agree to the privacy policy and terms of service.