Configuring access to the Client Data Management Utility

Show expandable text

Whether Accounting CS is installed locally or in a network environment, the Client Data Management Utility uses a temporary path during the backup and restore processes. The default folder used for the temporary path is the SQL server data location, such as X:\Program Files\Microsoft SQL Server\<SQL_Instance_Name>\MSSQL\Data (where X represents your local or network drive).

CDMU calls can be handled by non-System reps. Remember, System reps are not trained on CDMU.

You cannot access the File > Client Data Management Utility in Accounting CS when the local machine's path to the SQL server data location does not match the server machine's path to the SQL server data location, or when you do not have full permissions set up to access the SQL server data location. (In either case, we recommend that you notify your certified IT professional with SQL knowledge and advise them of the issue.)

Follow these steps for each workstation if you receive a message that indicates an issue with the path to the SQL server data location, or if your IT administrator makes significant changes to your SQL server (for example, an installation of a new SQL instance). This procedure shows you how to add an alternate temporary path in the NetworkInstallation.ini file that will be used instead of the default SQL server data location when you launch the application.

Note: Be sure that you are able to view file extensions in Windows Explorer prior to completing the following steps.

  1. Close the application.
  2. Add a new subfolder in the WINCSI folder, such as \\SERVER\WINCSI\ClientBackup (where \\SERVER represents the location of your WINCSI folder).
  3. In Notepad or a similar text editor, open the NetworkInstallation.ini file (not the NetworkInstallation.ini.readme file) for Accounting CS found at \\SERVER\WINCSI\Accounting CS (where \\SERVER represents the location of your WINCSI folder).
  4. Enter the following line in the [appSettings] section of the file, using the following format and the path you created in step 2 after the equal sign.

    ClientBackupRestoreWorkingPath=\\SERVER\WINCSI\ClientBackup

    When you add the alternate path in the NetworkInstallation.ini file, be sure that you are referencing the UNC (universal naming convention) path and not a path for a mapped drive, which often varies across different computers.

    Show me.

    networkinstallation.ini text

  5. Save and close the NetworkInstallation.ini file.
  6. Reopen the application and choose File > Client Data Management Utility.

    Notes

    • Before restoring client data, verify that your SQL instance is the same version that was used to create the backup.
    • In some circumstances with restrictive network permissions (for example, when integrating with other applications or reading/writing files from/to your local and network drives), you may need to run the application as an administrator (by right-clicking the Accounting CS icon, choosing Properties, and marking the Run this program as an administrator checkbox in the Compatibility tab).

Permissions

There are two users who need full permissions:

  • The user making the backup. In most situations, this should not need any changes if you are using a folder in the WINCSI folder because the user already has full control.
  • The user account that is running the SQL server service. Use the following procedure to find the account and set the permissions for the user to log on to the SQL server.
    1. Select Start > Control Panel > Administrative Tools, and then select Services.
    2. Right-click the SQL Server service and select Properties.
    3. Select the Log On tab to see the user account that is displayed. For SQL 2014 and higher, a user with the instance name is created (e.g., Service\MSSQL$SQL2014, where my instance name is SQL2014.)
    4. On the Security tab of the folder, provide full control for the user account.
    5. On the Sharing tab, select the Advanced Sharing button, and then the Permissions button. Set the permissions to enable access to the shared drive or folder.

Note: The SQL instance should be configured so that the CreativeSolutionsPracticeCsDatabaseOwner user has the sysadmin role.

Error logs

Error logs can be helpful in figuring out what the cause of the problem is. You can find the error logs are in C:\users\{windows login}\appdata\local\Creative Solutions\Accounting CS\log.txt.

  • An error that includes the words "Unable to determine local path to server file" most likely means that the path doesn't exist, although it may also be a permissions issue:

    CS.Accounting.Schema.BackupRestoreDataErrorsException: map FS1\CREATIVESOLUTION, \\FS1\W:\BackupRestoreTempPath\dummy_e8892f37b57949a99a011176673cf6fd.junk ---> System.InvalidOperationException: Unable to determine local path to server file: \\FS1\W:\BackupRestoreTempPath\dummy_e8892f37b57949a99a011176673cf6fd.junk at CreativeSolutions.Common.DataAccess.SqlServer.SqlServerAccessProvider.MapFileServerToLocalPath(String serverName, String filePath)

  • An error that includes the words "Access Denied" always points to a permissions issue:

    CS.Accounting.Schema.BackupRestoreDataErrorsException: map FS1\CREATIVESOLUTION, \\FS1\WinCS\AccountingCSBackup\dummy_ae4d7fa18fc8402fa353f1e956e2abd4.junk ---> System.Data.SqlClient.SqlException: Cannot open backup device '\\FS1\WinCS\AccountingCSBackup\dummy_ae4d7fa18fc8402fa353f1e956e2abd4.junk'. Operating system error 5(Access is denied.)

Error: The path to the SQL server data location ... does not exist or you do not have proper permission to it

For non-network installations: You can resolve this error message by following the path listed in the message and opening the folder. Do not change anything in this folder, just open it and give yourself permission to the folder when prompted. If Accounting CS was open when you opened the folder, make sure to close and re-open the program again.

Was this article helpful?

Thank you for the feedback!

Internal only

Error: The process has been halted due to data issues

For more information, see the Error message when backing up clients using the CDMU topic.