Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Network Performance Monitor (NPM) > ERROR DBConfigProcessor - Error while executing script - profile name is not valid

ERROR DBConfigProcessor - Error while executing script - profile name is not valid

Created by Juan Carlo del Rosario, last modified by MindTouch on Jun 23, 2016

Views: 30 Votes: 0 Revisions: 7

Overview

Configuration Wizard fails with the following error:

ERROR DBConfigProcessor - Error while executing script - profile name is not valid
An error was raised during trigger execution. The batch has been aborted and the user transaction, if any, has been rolled back..
 Error details: System.Data.SqlClient.SqlException (0x80131904): profile name is not valid
An error was raised during trigger execution. The batch has been aborted and the user transaction, if any, has been rolled back.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, 

at System.Data.SqlClient.SqlCommand.ExecuteScalar()
   at SolarWinds.ConfigurationWizard.Plugin.Common.DBConfigProcessor.ExecuteSqlBatch(IDbConnection connection, String sqlQuery, ConfigurationLogDelegate configLog)
ClientConnectionId:17b812c6-627b-4531-b07d-edbb1edd7df5
 Failing Sql command:

-- 
-- C:\Projects\NTA\NTAPepper\Src\Src\Config\SQL Scripts\Pre\AddNewFileGroupsToDB.sql
-- 
-- Add new files groups to existing database

DECLARE 
@dbName nvarchar(200), 
@dbScript nvarchar(max)

SET @dbName=db_name();

CREATE TABLE #NetFlowTableInfo
(
 TableName nvarchar(100) COLLATE database_default,
 

Environment

NPM v11.5.2 

Cause 

The Orion account being used to access the database does not have the proper permission/s.

Resolution

  1. Provide a sysadmin role to the Orion account from your SQL Management Studio.
    Note: This needs to be provided by your SQL administrator. 
  2. Re run the Configuration Wizard.

 

 

Last modified
22:17, 22 Jun 2016

Tags

Classifications

Public