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

NCM V7 Upgrade Issue

I have stated to upgrade my NCM server from 6.1 to 7. My separate NPM server is running 10.2.1. Both of these servers use a dedicated separate SQL server for their respective databases.

As per the video instructions I upgraded the Orion NPM server first with the new web integration modules for NCM 7 and it went well with no issues. The only odd thing is that it asked me if I wanted to license NCM on that server and I said no and to continue the 30 day eval. I figured since there is only one license I should reserve licensing it on the NCM server itself. But not sure about that.

Anyway afterward I went to the NCM server to upgrade it to 7 and during the install where it validates you can connect to the Orion server it fails. Now from that NCM server I can run a browser session and connect to it just fine it just wont validate during the install script. Have turned off all firewalls just in case but since the browser works you would think the install script would as well.

Any ideas?

Find more posts tagged with

ncm_7_upgrade

Accepted answers

ElDeeBee

Verified with customer that this will occur when you have two machines that cannot establish connection via WCF.

From Microsoft WCF Community this kind of exception can be caused due to clock system not synchronized between NPM and NCM machines.

According to Microsoft the 2 servers can only have certain time difference for security reason.

www.mythos-rini.com/.../2536

Synchronizing the clocks did fix the issue for this customer.

All comments

mdiotte

Hi gfaircloth,

The NCM license does in fact live on your main Orion server in 7.0 where you installed the website and not the NCM server.

For your second issue I would validate that the Orion SWIS service is working properly on the NPM server. The easiest way to validate that is by re-running the Orion Configuration Wizard on the NPM/Orion server and choosing to reconfigure the "Services".

Hope this helps.

Matt

gfaircloth

Thanks!

OK I fixed the license issue and ran the services reconfig and it still does the same thing. So I rebooted the NPM server just to make sure everything was started cleanly, still can't upgrade the NCM server.

And I can still login to the NPM server from the NCM server with a browser using the same exact IP and username/password.

Any other ideas?

mdiotte

What specific error message are you seeing? Have you tried using the IP address vs hostname? Are you providing an account with Orion admin privileges?

gfaircloth

This is the error message I get when trying to validate the Orion server connection from the NCM server.

This is the screen previous to the error where you enter the connection information. I have always used the IP and not the hostname so its not DNS related.

And this is what you get when you try a browser on the NCM server and if you enetr the exact same credentials it works perfectly. Note the exact same IP.

This really should not be so hard I must be doing something completely wrong somewhere but have no idea where. BTW the admin account has full rights to Orion NPM and works fine in everyday use.

Thanks for looking.

mdiotte

Hi Jerry,

I can't see anything obvious you are doing wrong. The fact that you can connect via the web is good but not necessarily a factor as the validator is actually making a call to the remote Orion using our SWIS service which is listening on TCP port 17777.

It may be best to open a support case so that we can take a closer look at the log files. One log file that may have relevant information about why the connection is failing is "C:\Documents and Settings\All Users\Application Data\SolarWinds\Cirrus\Logging\PreInstaller.log"

gfaircloth

Thanks Matt, I looked into the reverse DNS that Sean had mentioned and sure enough that was fouled up on one of the servers but after fixing that it did not seem to help. I looked into the log file and definately there is an issue with the communications.

Have a good weekend

I will open up a case on Monday I guess.

Snippet from log file up to the error:

2012-01-06 17:58:55,703 [1] INFO PreInstaller.CommonHelper - Pre-Installer Started
2012-01-06 17:58:55,718 [1] INFO PreInstaller.CommonHelper - Is Core installed: False
2012-01-06 17:58:55,734 [1] INFO PreInstaller.CommonHelper - Is NCM Server installed: True
2012-01-06 17:58:55,734 [1] INFO PreInstaller.CommonHelper - NCM Server Version: 6.1
2012-01-06 17:58:55,734 [1] INFO PreInstaller.CommonHelper - NCM Server Install Dir: C:\Program Files\SolarWinds\Configuration Management\
2012-01-06 17:58:55,734 [1] INFO PreInstaller.CommonHelper - Is NCM Integration Module installed: False
2012-01-06 17:58:55,734 [1] INFO PreInstaller.CommonHelper - Is NPM Module installed: false
2012-01-06 17:58:55,750 [1] INFO PreInstaller.CommonHelper - Initiating Commercial Workflow
2012-01-06 17:58:55,765 [1] INFO PreInstaller.CommonHelper - Workflow Started
2012-01-06 17:58:55,781 [1] INFO PreInstaller.CommonHelper - Executed step CorePresent in workflow.
2012-01-06 17:58:55,781 [1] INFO PreInstaller.CommonHelper - JoinCoreSetup: Displaying join to Core question dialog
2012-01-06 17:59:44,546 [1] INFO PreInstaller.CommonHelper - Validate remote NCM integration module version started
2012-01-06 17:59:46,359 [1] ERROR SolarWinds.InformationService.Contract2.InfoServiceProxy - An error occured opening a connection to the orion communication service.
System.ServiceModel.Security.MessageSecurityException: An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail. ---> System.ServiceModel.FaultException: An error occurred when verifying security for the message.
--- End of inner exception stack trace ---

ElDeeBee

Verified with customer that this will occur when you have two machines that cannot establish connection via WCF.

From Microsoft WCF Community this kind of exception can be caused due to clock system not synchronized between NPM and NCM machines.

According to Microsoft the 2 servers can only have certain time difference for security reason.

www.mythos-rini.com/.../2536

Synchronizing the clocks did fix the issue for this customer.