Network Management

CWActiveInstanceChecker - Extending expiration for active instance of ConfigWizard on machine

This article describes the issue when the Configuration Wizard hangs on some stages and does not go further or Configuration Wizard not finishing.

First published date

11/29/2018 10:48 PM

Last published date

1/3/2025 2:40 PM

Overview

  1. This article describes the issue when the Configuration Wizard hangs on some stages and does not go further.



You have followed the below KB and check this article provides basic steps to troubleshoot SolarWinds Orion Configuration Wizard related issues:

For example, if it is stuck and not moving ahead 
And when you check the logs: C:\ProgramData\Solarwinds\Logs\Orion\ConfigurationWizard.log it contains messages like this:
INFO  CwActiveInstanceChecker - Extending expiration for active instance of ConfigWizard on machine MySolarWindsSever (xxx.xxx.xxx.xxx)

ERROR DatabaseHelper - Unable to set active instance for ConfigWizard on machine MySolarWindsSever (xxx.xxx.xxx.xxx)! Reason: The transaction log for database 'SolarWindsOrionSAM' is full due to 'ACTIVE_TRANSACTION'.
System.Data.SqlClient.SqlException (0x80131904): The transaction log for database 'SolarWindsOrionSAM' is full due to 'ACTIVE_TRANSACTION'.

 

DEBUG SqlHelper - SQL: SELECT CAST((CASE WHEN SERVERPROPERTY('edition') = 'SQL Azure' THEN 1 ELSE 0 END) AS INT)
INFO  CwActiveInstanceChecker - Extending expiration for active instance of ConfigWizard on machine MY_Orion_Poller (xxx.xxx.xxx.xxx)
DEBUG SqlHelper - SQL: SELECT CAST((CASE WHEN SERVERPROPERTY('edition') = 'SQL Azure' THEN 1 ELSE 0 END) AS INT).

This means the error is due to the Configuration Wizard not being able to complete.

 

Product section

Network Performance Monitor

Cause

  • Recent Orion database migration
  • SQL Server disks under stress
  • Temp DB is filling up
  • Low Disk space on the SQL Server
  • Database Maintenance issues (Orion database maintenance never completed or have Errors)
  • Large Database
  • Poor SQL Performance
  • SQL Server not configured for correct Memory

Resolution

You can wait for the Configuration Wizard as it will take some time to complete here. 

Resolutions:

Filter Profiler Trace To Display Events From Orion Database 

Please consult your DBA ,  to run the SQL profiler and trap the queries and statements either for error debugging or to find performance issues. Limit the tracing to a specific Orion  database.

Here is the step by step instruction to filter the profiler trace to display events from a specific database.

Steps To Filter Profiler Trace For Events From Orion database

  1. From the SQL profiler trace window, go to menu Files > Properties.
  2. In the Trace Properties window, go to Events Selections tab.
  3. Select the check box Show all columns.
  4. Press the Columns Filters… button below.
  5. In the Filter pop-up window, from the left panel select Orion DatabaseName.
  6. From the right panel, under Like tree node, enter the database name and press OK.
  7. Then, press Run button to start the trace.

Now the SQL profiler trace window will capture only the configuration wizard events queries from the Orion database 
 

For other reasons 
If it is a recent database migration:
  • Check the Orion Database Size and Locating your Orion database properties and storing your DB files set to the single disk array. The disk is under pressure, creating some latency when running the Configuration Wizard. 
  • Shrink the size of the Orion Database reduced the size from 60 Gig to 30 Gig (50%)
  • Re-boot the SQL Server and manually complete the Database Maintenance; Re-run the Configuration Wizard once again by going to Start > run > All Programs > Solarwinds Orion > Configuration and Auto-Discovery > Configuration Wizard > select all 3 options. 
  • Re-boot the Orion Server and re-run the Configuration Wizard once again by going to Start > run > All Programs > Solarwinds Orion > Configuration and Auto-Discovery > Configuration Wizard > select all 3 options. 

This time the Configuration Wizard will be completed successfully. To avoid such issues in the future, see the link:




*****************************************
Additional Steps that worked on case number: 01141928

Configuration Wizard logs

CWActiveInstanceChecker - Extending expiration for active instance of ConfigWizard on machine


1. Stop all services on All APE, while the configuration wizard is running.