Database permission error in the Configuration Wizard for SolarWinds Platform products

11/29/2018 10:48 PM

5/28/2025 1:35 AM

C:\ProgramData\SolarWinds\Logs\Orion\ConfigurationWizard.log

ERROR SceneContainer - SceneContainer:bntNext_Click: System.Data.SqlClient.SqlException (0x80131904): VIEW SERVER STATE permission was denied on object 'server', database 'master'.

 

Orion Platform

The Configuration Wizard reports this error because the SQL account assigned to your installation does not have required permissions to access your database. You must create a new SQL account with required permissions for your installation.

Here are guidelines for database roles and permissions required for SolarWinds Platform modules:

• If you are creating a new database, the user account must be a member of the dbcreator server role. The sysadmin role and the SA user account are always members of dbcreator.
• If using an existing database, the user account needs only to be in the db_owner database role for the existing database.
• If creating a new SQL account for use with SolarWinds NPM, the user account must be a member of the securityadmin server role. Note: The sysadmin role and the SA user account are always members of securityadmin.
• If using an existing SQL account, the user account needs only to be in the db_owner database role for the database.

The Orion Platform system requirements also contain details about server roles and permissions. See also Why do I need SQL SA level account credentials for Configuration Wizard. 

To create a new SQL account, you must have:

• Microsoft SQL Server Management Studio installed on the SQL Server hosting your database.
• An account that is a member of the following SQL Server roles required to install SolarWinds Platform products
  • dbcreator
  • public
  • securityadmin

1. Using an account with required server-level roles (see above), log into SQL Server Management Studio on the SQL Server hosting your Orion database.
2. Click + to expand Security > Logins.
3. Delete all existing SolarWinds Platform database accounts (You must be logged in as the SA user. Do not delete the SA user).
4. Create a new user.
5. Right-click Logins, and then select New Login.
6. Click General in the Select a page pane on the left.
7. Enter a Login name.
8. Select SQL Server authentication, enter and confirm an appropriate password. 
9. Clear the Enforce Password Policy selection.
10. In the Default database field, select your database. The default database is SolarWindsOrion
11. Click Server Roles in the Select a page pane on the left.
12. Select public and sysadmin.
13. Click User Mapping in the Select a page pane on the left and select your Orion database.
14. In the corresponding Default Schema field, click Browse (...), enter dbo. 
15. Click Check Names, click OK. 
16. On the login - New Window click OK.

To verify the new user, click + to expand Databases > OrionDatabaseName > Security > Users.. Your newly created user should display in the Users list.
 

If your newly created user does not display in the Users list, the account you used to initially log in to the SQL Server Management Studio does not have permission to create database accounts.

Note: If you prefer to use SQL command instead of GUI (Graphical User Interface). Please refer to Command
 

--Scripts are not supported under any SolarWinds support program or service. Scripts are 
--provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties 
--including, without limitation, any implied warranties of merchantability or of fitness for a 
--particular purpose. The risk arising out of the use or performance of the scripts and 
--documentation stays with you. In no event shall SolarWinds or anyone else involved in the
--creation, production, or delivery of the scripts be liable for any damages whatsoever 
--(including, without limitation, damages for loss of business profits, business interruption, loss 
--of business information, or other pecuniary loss) arising out of the use of or inability to use 
--the scripts or documentation.


GRANT VIEW SERVER STATE <username>