I can't make a new map. Not sure what to tell my boss on this latest feature.
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.
Similar thing happened to me. After the 11.5 upgrade, and the installation of Atlas 1.13.0.473....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.
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.
Since NPM 11.5 I get this too. Sometimes Atlas crashes and when it does it creates duplicate maps.
Same here. So man many bugs in this release..
I just got off the phone with NPM support. They are aware of the problem. Will know more Monday.
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!
I'm not guaranteeing it will fix it, but have you tried applying to 11.5.0 HotFix 1?
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.
So does this break the existing maps? We use a Network Atlas map on our main dashboard screen, so this is very worrisome. We are planning our upgrades in June, so hopefully there is a fix by then or I might just upgrade to 11.1 until its fixed.
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.
Existing maps are fine, and the crashing doesn't break them. It's just that the crash creates a duplicate - often the crash is when you are saving data.
Hi,
Might be a silly question, but has everyone updated their Network Atlas installation, if running it from client machines?
Yes this behavior occurs with the newest Network Atlas v1.13. If I use the previous version v1.12, I can edit maps normally with their existing nodes/interfaces and also change the backgrounds. However, the Orion Objects do not populate so I can't add anything new.
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.
For me, I had to upgrade Network Atlas after I upgraded to 11.5. Once I did that, I've had no issues.
I have found no issues in it
Support provided me with a buddy drop which appears to have resolved the issue. I replaced the file in my server and client's Network Atlas directory and I am saving maps without crashing!
We have had the same issue and to be honest it is serious enough for me to be suggesting we start looking at alternatives. The maps are a key facility for us for helpdesk and network management, and the lack of development and now serious failures are a real problem.
SCOM and SA Vision is an alternative but the SAV NOC views are unreliable in previous versions. They crashed constantly. SolarWinds is much more robust for NOC Views.
But, SolarWinds lacks in so many functional monitoring areas that we cannot abandon SCOM for years to come.
SCOM wins for monitoring.
SolarWinds wins for a fast robust UI.
But a fast web UI doesn't give me AlwaysOn or Log shipping monitoring.
SolarWinds is a masterful sales persons dream. But once you get under the hood there's too much lacking.
I'm conflicted a bit from the same concepts; solarwinds UI beats SCOM enough that people want to use it but there are such limitations built in that it becomes an issue. Like: why do I end up having to do rest-apis just to get around the total lack of integration between Orion and service-now, for example?
Lack of integration with a third party isn't something I would chastise them for.
What help desk software truly integrates with any monitoring tool? Even Microsoft Service Manager barely integrates with SCOM out of the box. Sure you get a connector to see your servers but that's it on day one.
It is an age old argument, what tool to use.
Based on experience of using both SCOM and SW in huge shops, if you want reliable out of the box monitoring and alerting, SCOM is the only answer. I'm still running SCOM 2007 environments that do things SolarWinds can never do effectively.
If your goal is to give a team a birds eye view of UP/DOWN status of your servers with reliable disk space and cpu monitoring and you do not care about solid SQL, IIS, .NET, Cluster, SQL 2012 AlwaysOn, mirroring or log shipping monitoring then SolarWinds is great.
I am having this problem with the nodes not populating. Any idea on that.
Just a note, we fixed the map save / duplicate map error by upgrading Solar Winds to the following:
Orion Platform 2015.1.1, QoE 2.0, NCM 7.3.2, NPM 11.5.1
After upgrading, be sure to uninstall Network Atlas from each client PC and re-install using the download link in the web GUI, which should be Network Atlas version 1.13.0.448.
I know this is an old post but we have had similar issues recently after upgrading to Orion Platform 2017.1.1 SP1, NCM 7.6, NPM 12.1, QoE 2.3, NTA 4.2.2, VIM 7.0.0, NetPath 1.1.0.
Each time I opened Network Atlas (version 1.16.0.39) and tried to edit icon images the software would crash and create duplicate map files, both client and server side. Uninstalled and re-installed Network Atlas to no avail.
In the file C:\ProgramData\SolarWinds\NetworkAtlas\NetworkAtlas.log I noticed error messages relating to an invalid icon file:
2017-05-31 12:13:54,966 [Main Window UI thread] FATAL NetworkAtlas - Message: File C:\Program Files (x86)\SolarWinds\Network Atlas\Maps\NetObjects\Custom Icons\Common\Thumbs.db is not a valid icon.
Deleted the thumbs.db file, restarted Network Atlas and everything started working.
