Error with Orion Configuration Wizard after Cirrus -> Orion NCM upgrade

So, after installing ORION NCM, the Configuration WIzard starts. It fails with this error however:

An error occured configuring Orion Network Configuration Manager DataBase [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user ' '. The user is not associated with a trusted SQL Server connection.. Please check the ConfigurationWizard.log for details.

ConfigurationWizard.log helpfully contains the exact same error message.

Any idea what I did wrong? This was working great with Cirrus.... was hoping for a smooth upgrade.

BTW, I tried the advice in this thread: but did not help.

Thanks.

Find more posts tagged with

configuration_wizard

problem

orion

ncm

upgrade

Accepted answers

All comments

rsprim

You didn't do anything wrong. I believe this is a bug in the software but here's what fixed it for me. I learned this after talking with support.

Open Regedit and go to HKEY_LOCAL_MACHINE/SOFTWARE/SolarWinds.net/ConfigurationWizard/ConfiguredModules and create a string value named "1" (no quotes) with Value data of True. Then rerun the NCM Configuration Wizard and see if you can now select the database server and local SQL account. If all the registry folders are not created on your system then create new "KEYs" in order to create them.

Another thing to be aware of is that apparently the SP1 update automatically runs after the initial install (I haven't found this documented anywhere) so there is no need to run it again. After that run the bundled integration module and once that is completed re-run the SP2 patch if you already had Orion SP2 running prior to the NCM upgrade.

As mentioned in a previous post, you can verify your upgraded to SP1 by looking in the registry at key: HKEY_LOCAL_MACHINE/SOFTWARE/SolarWinds.net/Configuration Manager/ProductDisplayName.

I work in a government environment and we have successfully been able to enable the NCM website for SSL and permit CAC login to the NCM website utilizing port 4443 since our Orion site already uses 443. My understanding is we'll be able to do something similiar using Orion v9.1 but we haven't upgraded to that yet since there is a known issue with the rollup of worst status in child maps to Parent maps. In case your wondering, I do not have local accounts created in NCM either which is currently not the case in Orion (or so I'm told).

Rob

therealgt

Thanks Rob, I'll give this a shot!

therealgt

Hey Rob, that worked out OK, but then I got a message saying that I needed to enable Mixed Mode Authentication on my SQL database.. Since I'm using SQL Express 2005 that shipped with Cirrus, I had to use the instructions found here : http://support.microsoft.com/kb/319930 to enable mixed mode authentication.. After that, I was good. Just had to make sure I used a "strong password" when creating the new DB user for Orion - "password" won't cut it anymore.

Anyhow, everything appears to be working now, We'll know soon.

Thanks again.