Orion Database issue, new install

I nave an existing install of Orion, 7.5, I moved the database to a windows 2000 server running SQL 2000 SP4. Installed 8.5.1 on a new server and ran through the configuration wizard, pointed to the server, it ran through everything OK, setup SolarWindsNPM as the user then when it finished and tried to bring up Orion, I got an error,

Connection = Provider=SQLOLEDB.1;User ID='SolarWindsNPM';Password='*********';Persist Security Info=False;Initial Catalog=NetPerfMon;Data Source=XCHMON\SOLARWINDS;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=SolarWinds;Use Encryption for Data=FALSE;Tag with column collation when possible=False

I tried to rerun the wizard and cant connect using SolarWindsNPM as the user, but can as SA after resetting the password under the SQL manager. I can connect using the Solarwinds SQL manager. I am not sure where the problem is.

Edit; Applying SP2 update I came across an error during the configuring Orion Network Performance Monitor

CustomPropertyEditor

Run-Time error '91':

Object variable or With block variable not set

I click OK and it continued the configuring Orion Wizard.

Find more posts tagged with

Accepted answers

All comments

mark_wiggans

I nave an existing install of Orion, 7.5,
I moved the database to a windows 2000 server running SQL 2000 SP4.
Installed 8.5.1 on a new server and ran through the configuration wizard, pointed to the server, it ran through everything OK, setup SolarWindsNPM as the user then when it finished and tried to bring up Orion, I got an error,
Connection = Provider=SQLOLEDB.1;User ID='SolarWindsNPM';Password='*********';Persist Security Info=False;Initial Catalog=NetPerfMon;Data Source=XCHMON\SOLARWINDS;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=SolarWinds;Use Encryption for Data=FALSE;Tag with column collation when possible=False

Login fails.

I tried to rerun the wizard and cant connect using SolarWindsNPM as the user, but can as SA after resetting the password under the SQL manager. I can connect using the Solarwinds SQL manager. I am not sure where the problem is.

Edit; Applying SP2 update I came across an error during the configuring Orion Network Performance Monitor
CustomPropertyEditor
Run-Time error '91':
Object variable or With block variable not set

I click OK and it continued the configuring Orion Wizard.

It looks like the new server does not have the required permissions to the existing SQL DB.
The normal way to migrate the DB to a new server is to backup the existing DB.
Then install SQL on the new server & do a restore of the backup.
Then install Orion & point it to this restored DB.
It must have the required permissions in the account used to access the DB. (DBA/SA rights to modify the DB).

Which OS do you have 8.5.1 installed on & where does this Run time error 91 appear?

chris.conway

Could be wrong, but I think you need to get the 7.5 install up to 7.8.5 first before the upgrade will work correctly

ACDII

I followed the move PDF to the letter to a new server. The server running SQL is 2000 SP4, the new server that Orion is installed on is 2003x64. I am not upgrading Orion, I am doing a fresh install but using the old database. Could it be that the SolarWindsNPM user has a different password from the old Orion, and I need to match it? How can I change the password for SolarWindsNPM in SQL?

mark_wiggans

I am doing a fresh install but using the old database. Could it be that the SolarWindsNPM user has a different password from the old Orion, and I need to match it? How can I change the password for SolarWindsNPM in SQL?

Use the Configuration Wizard to setup the password.

ACDII

I found something interesting, not sure what it relates to though. I compared the database users on the running Orion server to the backup server that will be running the new Orion database. The users have no login name on the new database. Could that be the problem?

EDIT: Finally I got it working. I drilled through all the fields in the Enterprise manager and found the SolarWindsNPM user that was giving me the trouble. It looks like that user was there from the older version when I moved the database since I didnt need to add it when I ran the configuration wizard. I removed the user and reran the wizard and now I was able to connect!