Finish


 

If there are no errors, press the Finish button to apply changes and close the wizard.

 

If some parameters on the previous wizard's page were specified incorrectly, you may see one of these errors:

 

- [2] The system cannot find the file specified - you've configured DeviceLock Enterprise Server to store binary data on the disk but the path specified in Store path is incorrect. If you've specified the shared network resource then it is possible that this network resource is not accessible.

 

- Failed to verify store path. [5] Access is denied - the path specified in the Store path parameter is correct, but the user account used to run the DeviceLock Enterprise Server service doesn't have full access to files by this path. 

 

- CREATE DATABASE permission denied in database 'name' - the user's account (login) used to connect to SQL Server doesn't have enough privileges to create the database. The login should have at least the dbcreator Server role (see Server Roles in Login Properties of Microsoft SQL Server Management Studio).

 

- The server principal "user_name" is not able to access the database "name" under the current security context - the user's account (login) used to connect to SQL Server doesn't have access to the existing database. The login should be mapped to this database (see User Mapping in Login Properties of Microsoft SQL Server Management Studio).

 

- SELECT permission denied on object 'name', database 'name', schema 'name' - the user's account (login) used to connect to SQL Server doesn't have read/write access to the existing database. The login should have at least db_datareader and db_datawriter Database roles (see User Mapping in Login Properties of Microsoft SQL Server Management Studio).

 

- Invalid object name 'name' - the database specified in the Database name parameter already exists in this SQL Server but has an incorrect format. It happens when you are trying to use the database that was not created by DeviceLock Enterprise Server or if the database was corrupted.

 

- DeviceLock Database has an old format, you should upgrade the database - the database specified in the Database name parameter already exists but is outdated.

 

- DeviceLock Database has a format that is not supported by the current server version - the database specified in the Database name parameter already exists but it was created by the more recent version of DeviceLock Enterprise Server. You should either use the latest version of DeviceLock Enterprise Server or use another database (or create a new one).

 

Also, some of the SQL Server connection errors described in Test Connection may be displayed here as well. 

 

Use the Back button to return to the previous page and make necessary changes.