Installed NPM 12 today and found I am only able to make one edit to any alert before the 'Manage Alert's > Alert Manager' display area goes into a refresh loop for about ninety seconds to three minutes and am unable to manage any of the alerts. The 'Action Manager' tab does not exhibit this behavior. Setting a different value on the 'Group By' dropdown seems to shorten the amount of time on the refreshes. We've also found using the search field before making any edits seems to prevent the refreshes from occurring.
How I reproduced it:
1.) Click Settings>Manage Alerts
2.) Select the first alert I see and click the 'Edit Alert' button.
3.) When the Alert wizard finishes loading, click the 'Cancel' button.
4.) Sit back and watch the refreshes fly.
What we did to try and fix it:
Any thoughts or suggestions would be appreciated.
Solved! Go to Solution.
I have the same problem. I can only edit one alert as soon as I save the alert it goes into a refresh loop and I have to kill that tap and open the "Alert Management" page in a new tab.
The problem was with my browser. I believe I cleared all the cache in my browser. Even though I’m not using IE, I also cleared the cache in IE as well. Now it works.
I hope this helps.
425-673-5987 EXT: 302 (WA Office)
919-683-2413 EXT: 3025 (WA Office)
I am having the same problem. I have tried flushing the cache, logging out and back in, and rebooting my desktop.
I also restarted Solarwinds itself.
I see the CPU on my desktop spiking.
This happens with both IE 11 and Firefox. (We don't have Chrome.)
While reviewing the release notes for NPM 12.0.1 I found this line among the fixes for Orion Platform 2016.2
1045304, 1015785 The Orion Web Console does not hang when managing alerts or alert maintenance.
I am therefore going to download and upgrade our dev system to 12.0.1 with associated updates. If this helps I'll do the same in our production system.
We are on 12.0.1 and still have the issue.
Frustrating trying to edit multiple alerts as I keep having close down and go back in each time.
We are also still having the problem.
I've found that, if using IE, you can kill the one IE process that is using excessive CPU and it will restart the window and not require a complete shut down of your browser.
If you use Firefox I don't know if you can do this.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.