During the initial installation or upgrade of DA (Desktop Authority), installation fails when wizard gets to “configuring databases” and then has to roll back the changes. However the previous version (if doing an upgrade) does not completely return either.
Lack of correct SQL permissions or using an SQL SA account without sufficient privileges can contribute to this issue.
First, identify the Active Directory Windows user account that is being used for the “Desktop Authority OpsMaster Service” in Windows Services. Right-click on the service and go to the “Properties” |“Log On” tab.
While logged in with the domain\domainusername account that the OpsMaster Service is using, connect to the SQL Database that DA is using via the Microsoft SQL Server Management Studio Express console tool.
Expand Databases | Security and right-click on “Logins”. Select “New Login”.
Add the account being used for the Desktop Authority OpsMaster Service for “Login name”, or if it is already installed, right-click and go to “Properties” for this account.
Select “Server Roles” and check “sysadmin” for the Domain Admin account.
Select “User Mapping” and check “DAConfiguration” and “db_owner”.
Then place a checkmark on “DAReporting” and “db_owner”.
Click OK to accept changes.
After this process has been completed or permissions verified, run the Desktop Authority 9.x installer wizard. When prompted to choose the authentication type, select “Windows Authentication” and use the Domain Admin Service account for the Desktop Authority OpsMaster Service.
This should allow for the installation to complete successfully.
If there are any additional issues or you still cannot access the SQL databases,DAConfiguration or DAReporting, contact Quest Software Support for assistance.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center