2 of 2 people found this helpful
"I have a complete unusable system" At this point in the installer, nothing has changed on your existing installation. Can you clarify what you mean by "unusable system"?
You can get around this issue by uninstalling IPAM. Don't run the configuration wizard when you remove the product at this stage. Then, you would run the 12.2 installer again. On the first screen, expand "Select Additional Products" to select IPAM. This will install IPAM + upgrade your existing system all in one go, and you'll be up to date on the latest.
Seems to be based on a cookie. Log in on a different machine and you get the pop up again.
This hotfix left me with an unusable system. I have 4 open tickets now and they have been escalated to dev.
What is your case number?
The main one right now is Case # 1291329 but if you could look at 1243657 as well.
3 of 3 people found this helpful
If I might be so bold as to offer Installer Error Reports suggestions:
- It's unnecessary to indicate "we detected a problem."
- The largest text on the page should be applied to the actual problem.
- The robot overwhelms the page, indicating a problem, but no solution. In fact, no one here knows how to help a dazed robot, so we're left stunned & confused too. Although the robot IS pretty cute.
- Lose the "Close the installer" link, and replace it with the instructions necessary to diagnose, troubleshoot, and correct the problem. A link to installer logs might be useful, if those logs stated the problem, like "A duplicate version of ActiveDiagnostics version 12345 was detected. Cancel this installation of that same product and restart the process, skipping installing ActiveDiagnostics", or the equivalent.
When you get this, which installer are you running? You can get around this error by uninstalling Active Diagnostics and then running the installer again.
I resolved Case # 1291329
Alerting service was failing. I stopped alert actions. Cleared all alert instances, and the alerting service seems stable. I have resumed alerts and it is still stable.
Apparently, something in the alerts table got corrupt when the config wizard ran.
Performed the upgrade this afternoon (NPM, UDT, NTA, NCM). Installer went smoothly and probably around an hour. NPM 12.1 was the old platform and Win 2K16 server.
Unfortunately, it created havoc in my environment. My most critical ASA 5520 failover pair became unusable and started rebooting. I had to unmanage them in Orion to get them stable again (after powering off each as Orion was reporting them with dead fans and temp warnings as well as the reboots). It also caused a number of Cisco APs in my environment to become unresponsive and reported them as rebooting repeatedly. The telnet/SSH console was so unresponsive that I couldn't manage to login. Changed them to ICMP only polling and service was restored.
Also have a Citrix SD-WAN appliance with a similar symptom and reporting in Orion as rebooting every 30 minutes now. I checked the appliance and it doesn't appear to be restarting so this may be a SYSUPTIME reporting issue, although I have 4 other SD-WAN appliances on the network that aren't reporting issues...
I have a case open and awaiting feedback.... beware on upgrading your prod environment.
PS: I noticed some else reported the 0C temp reporting on their ASA. I have a 5525-X failover pair reporting the same. It is also reporting the fans are all spinning at 0 rpm. Might need to report that as well.
Can you send us your support ticket #?
Where you able to do this with only the 12.2 installer or did you have to do interim steps before it?
We've some serious problem after the upgrade from version 12.1 to 12.2.
The installation part was fine without any error but the license store is now corrupted.
We tryed to follow this thread :
However we have an error when trying to launch migration.exe /ExpireAll command , reporting that The license store is not in valid state
Anyone have this problem?
We've already opened the Case #1295467 but we're still awaiting an answer from the support service .
Thanks in advice
I'll have to watch this thread...