Installation of Devicelock Enterprise Server interrupted returning ‘Access denied (5)’ error. This happens after pressing the ‘Next’ button after configuring the ‘Log on as’ and ‘Connection settings’ parameters.
In case DeviceLock Enterprise Server is installed and an administrator is performing the server upgrade, the error indicates that the installation process is performed on behalf of a user account that does not have full administrative access to DeviceLock Enterprise Server. Lack of privileges makes it impossible for the installation wizard to install the server’s service and apply configuration changes. The error may also be caused by the lack of local administrative privileges of the account used to install DeviceLock Enterprise Server on the computer where DeviceLock Enterprise Server is being installed (for both initial installation and the upgrade).
1. Start the installation under the user account used for the initial installation of the DeviceLock Enterprise Server. If it does not help, or the initial user account no longer exists, proceed to step 2
2. Run ‘Registry Editor’ under an account with local administrative privileges, then:
a. Delete the [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DLServer] key
b. Take ownership of the [HKEY_LOCAL_MACHINE\SOFTWARE\SmartLine Vision\DeviceLockEnterpriseServer] key ([HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SmartLine Vision\DeviceLockEnterpriseServer] on 64-bit OS)
c. Reboot the computer
d. Delete the [HKEY_LOCAL_MACHINE\SOFTWARE\SmartLine Vision\DeviceLockEnterpriseServer] key ([HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SmartLine Vision\DeviceLockEnterpriseServer] on 64-bit OS)
e. Restart the installation of DeviceLock Enterprise Server
3. Make sure that the account you are using for installation does have local administrative privileges. You can try try to install any other software on this computer under the current user account.
4. If you have Kaspersky Antivirus software installed on the system, make sure its components' services are disabled using 'Services.msc' snap-in or uninstalled. A reboot may require for the changes to take effect.