Network Management

Configuration Wizard fails with an error because the database is read-only in the SolarWinds Platform

The article discusses and provides steps on how to address the Configuration Wizard error involving the SolarWinds Platform Database being read-only.

First published date

10/30/2018 11:34 PM

Last published date

5/6/2025 3:34 PM

Overview

Configuration Wizard fails with the following message:

Completing the Configuration Wizard
The configuration wizard has failed
Database configuration failed:
Error while executing script - Failed to update database "NetperfMon" because the database is read-only.

 

The operation cannot be performed on the database "NetperfMon" because it is involved in a database mirroring session or an availability group. Some operations are not allowed on a database that is participating in a database mirroring session or in an availability group.

 

 

 

Product section

Orion Platform

Cause

The SolarWinds DB is hosted on the SQL Server Availability Group. The primary replica makes the primary databases available for read-write connections from clients. The Primary image sends transaction log records of each primary database to every secondary database. Every secondary replica caches the transaction log records (hardens the log) and then applies them to its corresponding secondary database.

You may also check if the database is clustered. If yes, work with your DBA in checking the SolarWinds database that is failing is set to the correct cluster (Primary or Secondary). 

Resolution

Resolution 1

  • Configure Readable Access on an Availability Replica (SQL Server)

To configure access on an availability replica

  1. In Object Explorer, connect to the server instance that hosts the primary replica, and expand the server tree.

  2. Expand the Always On High Availability node and the Availability Groups node.

  3. Click the availability group whose replica you want to change.

  4. Right-click the availability replica, and click Properties.

  5. In the Availability Replica Properties dialog box, you can change the connection access for the primary role and for the secondary role, as follows:

    • For the secondary role, select a new value from the Readable secondary drop list, as follows:

      Yes
      All connections are allowed to secondary databases of this replica, but only for reading access. The secondary database(s) are all available for reading access.

      Read-intent only
      Only read-only connections are allowed to secondary databases of this replica. The secondary database(s) are all available for reading access.

      No
      No user connections are allowed to secondary databases of this replica. They are not available for reading access. This is the default setting.

    • For the primary role, select a new value from the Connections in the primary role drop list, as follows:

      Allow all connections
      All connections are allowed to the databases in the primary replica. This is the default setting.

      Allow read/write connections
      When the Application Intent property is set to ReadWrite or the Application Intent connection property is not set, the connection is allowed. Connections, where the Application Intent connection property is set to ReadOnly, are not allowed. This can help prevent customers from connecting a read-intent workload to the primary replica by mistake. For more information about Application Intent connection property, see Using Connection String Keywords with SQL Server Native Client.


Once done, check if you are able to alter or truncate the tables in the DB using the SQL Studio. 

You may need to reboot the nodes required after these changes. 

 

Resolution 2

  • Perform a failover on the SolarWinds Database.

a. Kindly ask the customer to work with their DBA.
b. Access the MSSQL SQL Server.
c. Locate the High Availability Groups and check if the SolarWinds database is on the correct cluster.
d. If not, perform a failover to the correct cluster.
e. Once you re-run the Configuration Wizard it will now complete with no errors.

Resolution 3

 
  • SQL Server Address in the Configuration Wizard.
    a. Kindly make sure that the SQL Server is pointing to the correct IP Address. If not, change the SQL Server address to the listener IP Address of the database cluster in the Configuration Wizard and make sure to complete it with no errors.
    b. Once completed, the server will now be up and running.