Just did the APM 2.0 install - important tip...don't run the upgrade directly from within a remote desktop connection.. as the release notes say:
If you are installing Application Performance Monitor through a terminal server session, use the Add or Remove Programs utility on you server (Start > Control Panel > Add or Remove Programs) to run the Application Performance Monitor installer.
In this case, I can confirm (blush) that NOT RTFM-ing that part of the release notes gave me considerable grief.. the install appeared to go find, but when you went to access Orion you'd get a APM cannot connect to engine error message.
Otherwise, it went fine!!
Don
I got the same problem installing it via RDP and following the instructions to use Add/Remove programs :( going to log a support ticket now
Don331:In this case, I can confirm (blush) that NOT RTFM-ing that part of the release notes gave me considerable grief.
In this case, I can confirm (blush) that NOT RTFM-ing that part of the release notes gave me considerable grief.
Stephensa,
Ouch!
Hmmm.. the other thing I did (before I ran the instructions...) was I un-installed APM 2.0, then re-ran Orion configuration (all options).. then I re-installed APM using Add/Remove programs. Worked fine since.....
I'd be interested to know what support finds out.
The issue isn't Remote Desktop, it is Windows Terminal Server. If you will go to Start | Administrative Tools | Terminal Services Configuration, select Server Settings and look for the Licensing setting. It probably says "Remote Desktop for Administration". In this case, you won't need to run the installer via Add/Remove Programs. If your server is running as a Terminal Server, you'll see "Per Device" or "Per User" under licensing.
Terminal Server requires running installer in a "special" way. This does not apply for Remote Desktop for Administration. For more information see http://msdn.microsoft.com/en-us/library/ms811523.aspx
From the problems other users have hit, I'm guessing you are having a licensing issue. Check your event logs to see if you are getting a licensing error from the Orion Module Engine.
For those that have uninstalled and then reinstalled, this is what is fixing your problem. We are still trying to dtermine why certain users are having this issue. We have not been able to duplciate this issue here.
Don331, that did the trick !!!
We uninstalled and reinstalled APM via add/remove programs and all working now, and a small update to the schema for some custom properites we use.
Josh,
Thanx for the info.
I did check through the event logs, and I do see this error:
SolarWinds.APM.BusinessLayer:A license check failed. License does not match install type.
Which went away after I uninstalled and reinstalled the product.
Hi Josh
Exactly the same for me, we had the license error and when we uninstalled 2.0 after the upgrade and then reinstalled the problem went away. If it helps we are running APM500 on Orion SLX 9.0 SP2.