Actually I already encountered the network atlas crashing issue on NPM 11.0 whenever I used the NPM server. So in order to modify or create a new map, I'm using the workstation instead since the Network Atlas can be used and install there.
I'm able to get in now without the crash on a different host. I have very extensive maps on 60 inch screens in 4 continents across the world so this is very high profile for us - when its down EVERYONE KNOWS.
So far, all is OK. I have added QOE summary stats to my dashboards and they are very nice.
SolarWinds support is awesome so far for me.
Similar thing happened to me. After the 11.5 upgrade, and the installation of Atlas 18.104.22.1683....any time I make a change to a map and hit the save button, the Atlas application throws an error and completely crashes. 80% of the time, it still updates the map the way I wanted it to, but it creates a duplicate map in the "Maps" tree. If I delete the wrong one, it breaks the hyperlinks in my map....I hope they fix this soon. I use Atlas daily.
Having the same exact problem with my NPM 11.5. I've had a case opened since I upgraded. We've tried various things to no avail. Apparently it's been moved to their "back-end" team. Hopefully they will find something soon, it's been a pain to update any maps!
Where do we find this hotfix? Can you provide a link to the hotfix release notes?
I've looked in my customer portal but I do not see any hotfixes for NPM 11.5
I'm not having a problem with NetworkAtlas crashing, but I have had some system instability and hanging/timeouts after the 11.5 upgrade. Logs indicated that the longest running queries were related to NetworkAtlas. Removing all map resources from all views seems to have stabilized the system.
Just a reminder (to you and everyone else) that WE (as customers) also have a stake in managing support calls. My experience in 10 years of being a Solarwinds customer has been that I get good support response if:
From here on out, I call support once a day and ask for a status on the ticket. Just once. I know it's hard and I know that you need help asap. My experience is that they staff is honestly working on it, but some answers take time. Calling once a day and getting status (again, being respectful) is your fastest way to get solid, positive attention on your case.
Leon, I have always been respectful. I have only sent one email per day asking for status, and/or assistance to check something. No reply for several days now. And yes I know how to open a ticket, collect diags and use leapfile. If you work at SW, feel free to pull up all my support requests.
Having a nonfunctioning system for over 30 days is NOT acceptable as a customer, and the lack of response adds insult to the injury.
Good to hear, and I wasn't trying to imply that you weren't being respectful.
I would definitely shift from emailing once a day to calling once a day. And you are 100% right, 30 days in the hole is unacceptable.
It's aways been kludgy. Now it's unusable.
I don't mean to always be a whiner here but I'm not happy paying so much money yearly for half baked beta'esque products.
Obviously this is not the normal behavior. I can promise you network atlas is alive and well in 11.5.
Your best bet is to open a ticket with support and let them help you though it.
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.