Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Upgrading server and NPM version, issue with getting NPM running on new server

Hi All,

Just wondering if anyone has seen the following and might be able to shed a bit a light:

Database configuration failed:

• Cannot create new Table (Nodes) ExecuteNonQuery failed for Database 'SolarWindsNPM'.

So, a bit of background...

We are running a very old, unsupported version of NPM (10.7). This is also running on a server 2008 R2 box. We can't have an outage that's too long, so our plan was to install a matching version of NPM on the new server, make a copy of the DB, move it to the new server and connect. We can then practice/time the upgrade process to the latest version whilst the current live system is up and running. We would then replicate the process for real once we'd run through it without any issues, thus keeping downtime hopefully to a minimum

However, we've hit an issue really early on - we get the above error when trying to connect 10.7 to the copy of the DB. This is from the same version NPM, and NPM works if we let it create a new, blank database so I know the installation is ok. I've checked SQL sa permissions as per a few SolarWinds support articles, but without fail I always get the above error.

Any idea's?

I've opened a support call with Orion, but wondered if anyone here had seen anything similar?

Thanks!

Find more posts tagged with

Accepted answers

All comments

vinay.by

Have you tried this ?

https://support.solarwinds.com/Success_Center/Network_Performance_Monitor_(NPM)/Cannot_create_new_Table_(Accounts)_Execu…

dgsmith80

Hi mark.lewis

The error you've got does indicate an SQL permissions issue most likely, maybe you tried to use the existing database account on the new SQL Server? The server would need a local account creating matching that username, then you can tie them together otherwise the config wizard will fail.

I actually had to do something similar for a customer a while back, as they had an old unsupported NPM10.7, and the SAN Storage hosting the Application and Database crashed, and wasn't recoverable. Luckily they had a backup of the database, so they spun up 2 new machines (Application & SQL) and we got to work by first installing all the modules to the current version, and connecting them to the database.

Firstly you will need to check your SQL Database version as SQL10.7 would only support up to SQL Server 2012 and I don't know what other modules you're running which could have a similar impact.

Assuming your SQL is all Ok, the other key things you will need to do is run the Database migration script to edit the NetBios BEFORE you run the Configuration Wizard - Step 7 of this Guide: Migrate SolarWinds products to a new server with a new IP and hostname - SolarWinds Worldwide, LLC. Help and Support but here is the SQL Script to clarify:

DECLARE @oldHostname nvarchar(max)SET @oldHostname = 'Server1'DECLARE @newHostname nvarchar(max)SET @newHostname = 'Server2'UPDATE Engines SET ServerName = @newHostname WHERE ServerName = @oldHostnameUPDATE WebSettings SET SettingValue = @newHostname WHERE SettingName = 'JobSchedulerHost'UPDATE Websites SET ServerName = @newHostname WHERE ServerName = @oldHostnameUPDATE OrionServers SET HostName = @newHostname WHERE HostName = @oldHostname

Then the configuration wizard should run, connect to your database and start to sync up. Be warned your alerts will start to fire off if you didn't mute them before you took the backup, but you can jump into the new box and mute them fairly quickly.

After that then you have the big job of the upgrade process itself. My jump from NPM10.7 (along with 7 other modules) included over 20 different upgrade steps to bring it to 12.2, but as already mentioned you can check the Product Upgrade Advisor.

If you're still not sure then I'd be happy to run through an upgrade plan with you, just share some additional information on your application server and SQL Server and any additional modules.

- David Smith

Kenson - SolarWinds Authorized Partner

Training, Licenses & Professional Services

- LinkedIn

- Twitter

- Facebook