Network Management
Configuration Wizard cannot use the special principal SA account in Orion
The SA account is restricted. The Configuration Wizard needs to use the account that owns the DB.
First published date
Last published date
Overview
The following errors about the SA account appear during Configuration Wizard:
ERROR UserAccountProcessor - Microsoft.SqlServer.Management.Smo.FailedOperationException: Create failed for User 'sa'. ---> Microsoft.SqlServer.Management.Common.ExecutionFailureException: An exception occurred while executing a Transact-SQL statement or batch. ---> System.Data.SqlClient.SqlException: Cannot use the special principal 'sa'. at Microsoft.SqlServer.Management.Common.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action, Object execObject, DataSet fillDataSet, Boolean catchException) at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType) --- End of inner exception stack trace --- at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType) at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(StringCollection sqlCommands, ExecutionTypes executionType) at Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQuery(StringCollection queries) at Microsoft.SqlServer.Management.Smo.SqlSmoObject.ExecuteNonQuery(StringCollection queries, Boolean includeDbContext) at Microsoft.SqlServer.Management.Smo.SqlSmoObject.CreateImplFinish(StringCollection createQuery, ScriptingPreferences sp) at Microsoft.SqlServer.Management.Smo.SqlSmoObject.CreateImpl() --- End of inner exception stack trace --- at Microsoft.SqlServer.Management.Smo.SqlSmoObject.CreateImpl() at SolarWinds.ConfigurationWizard.Plugin.Common.UserAccountProcessor.AddDatabaseUser(Database database, String userName, ConfigurationLogDelegate logger) 2015-11-12 13:23:16,074 [7] ERROR ConfigurationProgressScene - Can not add 'sa' user to database 'SolarWindsOrion'. See configuration log file for detail. SolarWinds.ConfigurationWizard.Common.ConfigurationException: Can not add 'sa' user to database 'SolarWindsOrion'. See configuration log file for detail. at SolarWinds.ConfigurationWizard.Plugin.Common.UserAccountProcessor.AddDatabaseUser(Database database, String userName, ConfigurationLogDelegate logger) at SolarWinds.ConfigurationWizard.Plugin.Common.UserAccountProcessor.AddUserToDatabase(IDatabaseInfo databaseInfo, SmoDbServer dbServer, ConfigurationLogDelegate logger) at SolarWinds.ConfigurationWizard.Plugin.Common.UserAccountProcessor.UpdateUserAccount(IDatabaseInfo databaseInfo, ConfigurationLogDelegate logger) at SolarWinds.ConfigurationWizard.Plugin.Orion.OrionMainPlugin.ConfigureDatabase(IOrionConfigHost host, ConfigurationProgressDelegate progress, ConfigurationLogDelegate logger) at SolarWinds.ConfigurationWizard.Plugin.Orion.OrionMainPlugin.DoConfigure(IOrionConfigHost host, IComponentInfo component, ConfigurationProgressDelegate progress, ConfigurationLogDelegate logger) at SolarWinds.ConfigurationWizard.Plugin.Common.OrionConfigPlugin.SolarWinds.ConfigurationWizard.Common.IOrionConfigPlugin.DoConfig(IOrionConfigHost host, IComponentInfo component, ConfigurationProgressDelegate progress, ConfigurationLogDelegate log) at SolarWinds.ConfigurationWizard.Host.Presentation.CommonConfiguration.ConfigurationProgressScene.DoConfigForComponent(IOrionConfigHost host, Int32 componentId)
Product section
Cause
Resolution
Resolution 1
- Verify if the SW DB has an owner.
a. Open SQL Management Studio.
b. Log in as SA or local windows administrator.
c. Right-click on the SolarWinds DB and select Properties.
d. Click on the Files page.
e. Verify that you have a DB owner for the SolarWinds database, use SA for example. - Verify the authentication mode that is set up.
a. Open SQL Management Studio.
b. Open Object Explorer.
c. Connect to your server and right-click on the server name, then select Properties.
d. Go to the Security tab and under Server Authentication, select SQL Server and Windows Authentication Mode. - Explicitly enable the SW DB account (such as SA).
a. Open SQL Management Studio.
b. Expand Security->Logins.
c. Right-click on the "sa" account, select "Properties".
d. In the list on the left, select "Status" and under "Login" on the right, make sure that "Enable" is selected. - Run the Configuration Wizard again.
Resolution 2
- Explicitly add the user as the db owner.
- Open SQL Management Studio.
- Log in as SA or local windows administrator.
- Right-click on the Solarwinds DB and select New Query
- Run the following:
-- 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. USE mydatabase exec sp_changedbowner 'sa', 'true'
- Run the Configuration Wizard Again.