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) > Database configuration fails with invalid object name errors

Database configuration fails with invalid object name errors

Created by Aileen de Lara_ret, last modified by Rodim Suarez on Feb 08, 2017

Views: 1,144 Votes: 1 Revisions: 8


This article provides brief information and steps to resolve database configuration failures with invalid object name errors. 


All Orion Core products


I. Review the Configuration Wizard log for more specific errors:

  1. Create a SolarWinds Diagnostics archive, as shown in the following steps:
    1. Click Start > All Programs > SolarWinds Orion > Documentation and Support > Orion Diagnostics.
    2. Click Start.
    3. Designate an appropriate location, and then click Save.
  2. Right-click the diagnostics archive, and then click Extract all.
  3. Complete the Extraction Wizard
  4. In the extracted archive, browse to LogFiles\Orion, and then open ConfigurationWizard.log.
  5. If the following line, or similar, is in the ConfigurationWizard.log, your SQL Server may be installed with an incompatible locale identifier (LCID):
    ERROR ConfigurationProgressScene - Installing NPM Update Descriptor package ....Failed!
    System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
    ---> System.Data.SqlClient.SqlException: A .NET Framework error occurred during execution of user-defined routine or aggregate "NPM_CreateStatisticsProperties":
    System.Data.SqlClient.SqlException: The locale identifier (LCID) 17417 is not supported by SQL Server.


You can also find the logs:




II. Reinstall your SQL Server, recreating your SolarWinds database instance using the English (United States) locale. By default, a full reinstall is required due to the fact that SQL Server, unless otherwise directed, inherits the locale of the host operating system.



Last modified
17:25, 8 Feb 2017