Network Management
Why do I need SQL 'sa' level account credentials for Configuration Wizard in Orion Platform?
In this article you will learn the process or requirements for SQL credentials during Orion Configuration wizard to connect the application with SQL server and logic behind the process .
First published date
Last published date
Overview
- Created database using same configuration wizard and failed to connect to the other database i have just created why
- Unable to switch configuration wizard to another Database or Database on another SQL Server
- Configuration Wizard not moving ahead (Multiple Polling Engine Detected ) after connecting to the Orion DB
- Ran Orion Configuration Wizard > Created Brand new database (Database-1) then created another Database using the Configuration Wizard (Database-2)
Product section
Cause
Configuration Wizard Errors such as below
ERROR SceneContainer - SceneContainer:bntNext_Click: System.Data.SqlClient.SqlException (0x80131904): VIEW SERVER STATE permission was denied on object 'server', database 'master'.
ERROR TaskAdapter - Error running task Orion.ConfigureDatabase Orion Database System.Data.SqlClient.SqlException (0x80131904): Could not find stored procedure
ERROR ColumnStoreSchemaManager - Failure during modifying schema. System.Data.SqlClient.SqlException (0x80131904): Could not find stored procedure
| Account privileges |
SolarWinds recommends that SolarWinds Orion administrators have local administrator privileges on the Orion server to ensure full functionality of local SolarWinds tools. SolarWinds Orion user accounts limited to the Orion Web Console do not require local administrator privileges. Users running the Configuration wizard must have DBO specified as the default database schema. For more details please find the details below Amazon RDS for Microsoft SQL ServerThe Microsoft SQL Server database engine uses role-based security. The master user name that you specify when you create a DB instance is a SQL Server Authentication login that is a member of the Any user who creates a database is assigned to the db_owner role for that database and has all database-level permissions The following server-level roles aren't available in Amazon RDS for SQL Server:
When using Amazon RDS for Microsoft SQL Server running Configuration Wizard please specify master username when creating the database is what you would need to use. It should be able to do everything that you'd normally need to do to create and manage databases. The limitations it does have are described at Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.
You are generally restricted to actions and roles that could alter your ability to access, monitor, or manage the instance. If possible, you may need to alter your deployments to accommodate those restrictions.
| |||
Resolution
Stage 1
In the configuration wizard 1st step, we need to use a "sa" account (recommended) the logic behind that is the "sa" account is the member of the sysadmin role, & therefore "sa" & sysadmin roles are the members of dbcreator server role by default.
In the meantime, you can also use the Windows authentication account (as far as that account is a member of the dbcreator server role).
The reason we use a high privileged account on the 1st step is so we can access the SQL server without any security issues and as mentioned the sa account is a member of the dbcreator server role by default (who have privileges to create a new database within SQL server)
Stage 2
Now in the 2nd step of Configuration Wizard, you simply select to create a new database (SolarWindsOrion) name of the Orion database. Or an existing migrated Database.
Stage # 3
Finally, in the 3rd option, you have to create a new "SQL authentication account" called "SolarWindsOrionDatabaseUser" the logic behind creating this account (it is just a public account that has read/write access to the Orion database) and nothing other than that, for day to day activities. It's not feasible from a security point of view to use the "sa" account to access the Orion database, as this account has far more privileges and therefore is not suitable in a day-to-day scenario.
I have already created an SQL account for Orion where I can use it in the Configuration Wizard?
So if you do have already 3rd option account created you can simply use that account while connecting to the SQL Database on 1st step
| Account privileges |
SolarWinds recommends that SolarWinds Orion administrators have local administrator privileges on the Orion server to ensure the full functionality of local SolarWinds tools. SolarWinds Orion user accounts limited to the Orion Web Console do not require local administrator privileges. Users running the Configuration wizard must have DBO specified as the default database schema. | |||
Common Issues:
I have created a database using the same configuration wizard and failed to connect to the other database I have just created why?
I am unable to switch my Database?
I am running an upgrade and Configuration Wizard not moving ahead (Multiple Polling Engine Detected ) after connecting to the Orion DB why?
You Ran Orion Configuration Wizard > Created Brand new database (Database-1) then created another Database using the Configuration Wizard (Database-2)
Now you wish to change the Database-2 to Database-1 and fail with an Error.
ERROR SceneContainer - SceneContainer:bntNext_Click: System.Data.SqlClient.SqlException (0x80131904): VIEW SERVER STATE permission was denied on object 'server', database 'master'.
The user does not have permission to perform this action.
Cause :
User account permission to go to the SQL Server > and check the User permissions and default database assigned to the user. (Please contact your DBA) and make sure the account does have proper permissions as explained above
Further, your DBA can change the default database as required by the application to use.
So the user can create the DB - (DB Creator Role ) but he cannot change the default database assigned to the user.
User needs more permissions to make changes into the DB - Please use Step #1 and use the sa account let the Configuration wizard create the Orion user account with appropriate permissions.
Or contact your DBA for any further changes with user permissions.
Please do consult your DBA before making any changes
Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.