Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Network Performance Monitor (NPM) > Configuration Wizard cannot use the special principal SA account

Configuration Wizard cannot use the special principal SA account

Created by Harry Griffiths, last modified by MindTouch on Jun 23, 2016

Views: 145 Votes: 1 Revisions: 7

Overview

 

The following errors about the SA account appears 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)

Environment

NPM 11.5.2

Cause 

There are SQL permission issues.

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 sw database, use SA for example.
  2. 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 Security tab and under Server Authentication, select SQL Server and Windows Authentication Mode.
  3. 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.

 

Last modified
21:55, 22 Jun 2016

Tags

Classifications

Public