14.2 Reporting the Status of the Databases

In the Repair tool, you can run a report to check the consistency of the database files. You might need to generate a report if the Service cannot open a pair, policy, schedule, or cloud account. You should also verify their status if a database error is reported in the Windows Event Logger after a Service start.

  1. Log in to the DynamicFS server as a user with file system rights on both the primary and secondary paths of the pair you want to manage.

    If remote shares are being used, ensure that you have sufficient access rights on the secondary locations.

  2. Stop the Service as described in Section 6.4.3, Stopping the Dynamic File Service.

  3. On the server, start the Repair tool by right-clicking the Service Controller icon in the notification area and selecting Repair Tool from the menu.

  4. Select Run a Report, then click Run.

    The output of the report is printed to the data window.

  5. View the report.

    A full report includes the following:

    • Policy database status and errors

    • Pair database status and errors

    • Schedule and schedule association errors

    • Cloud account errors

    • DswCore.xml file status and errors

  6. (Optional) Save the report by using one of the following methods:

    • Click Save, browse to locate the folder where you want to save the file, specify a file name, then click Save.

      The default file name is ..\Dynamic File Services\dswrepair.log.

    • Select the file output, right-click and select Copy to save the content to the Windows clipboard, then paste the information in any text file.

  7. (Optional) Click Clear to erase the report from the data window.

  8. When you are done, click Close to close the Repair tool.

    You cannot restart the Service while the Repair tool dialog box is open.

  9. Right-click the Service Controller icon, select Start Service, then click Yes to run Service as Administrator.