Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Network Atlas Hangs trying to load a map "Operation in progress, waiting for a connection"

I just recently completed my upgrade to NPM 12 and SAM 6.2.4, and now I am having issues getting into my Network Atlas. When I try to load up a map I made, it hangs with a status message "Operation in progress, waiting for a connection". Before the upgrade, it worked fine.

When I originally created my own map, I added a couple of nodes, plus two application monitors to represent a VPN tunnel. I suspect the problem is that something isn't working correctly connecting to that app monitor for that VPN tunnel. Before I try to connect my maps, if I just browse the objects that are in it, they show up under "Unknown Objects", and then below that, two entries for the app monitors:

The application monitors still exist in Orion, and the both of the application and node ID's are still the same. I can browse to them and they appear to be polling just fine.

In the Network Atlas, however, I cannot seem to be able to delete them. As soon as I right click on the Map and select "Open", it just hangs. I suppose I could easily recreate those two connections if need be. Or, just figure out how to get them to reconnect.

Any thoughts on how I can fix this map?

Thanks!

Find more posts tagged with

Accepted answers

FormerMember

Turns out the issue was with a handful of Netflow virtual interfaces that were somehow misconfigured. I called support, and they found in the logs that when the Atlas was trying to run, it would eventually hang on a number of virtual interfaces that were set to a polling interval of zero, which is apparently bad. I removed the virtual interfaces and the Atlas stopped hanging.

All comments

mschwarz

I'm having the same issue however it started prior to my version 12 upgrade and continues after the upgrade. I created a new map and it started having the issue when trying to add Nexus nodes onto it.

rstewart1

Having the same issue after upgrading to NPM 12 on one map with IP SLA.

Solved by deleting the map and recreating it. It was only one map with IP SLA nodes.

mschwarz

Okay my issue with Network Atlas on 11.x was that some nodes were not showing the interface tab so that I could not create logical maps with proper interfaces. That issue continued on after the upgrade to 12. Re-installing Network Atlas corrected the Interfaces not showing problem however I then encountered the "Operation In Progress" message. After a couple of hours with support, we found that certain nodes were causing the issue.

My problem was solved after deleting them from NPM and re-adding them back. I could then open the impacted map and add the nodes back.

To find the nodes causing my grief I only had to select the + to expand the node in Network Atlas to cause the message. Had to use Task Manager to kill Network Atlas each time the message came up.

ccorbin123

Getting the same error message, started after upgrade to 1.15 to 1.15.0.287 - even when creating a new map - everything is fine until I change the "Connection Display Options" from Don't show additional info to Show Link Utilization.

I wonders if the maps you are trying to open have that option selected as well.

extraman

Similar issues here, opened a ticket with SolarWinds, no solution until now.

FormerMember

sgtp

The fix for me was, strangely enough, to delete the contents of the log file. weird.

worto03

Hi,

What was the name of the log file you deleted? I'm getting this issue and that sounds like something to quickly try before I log a ticket.

thanks,

worto.

sgtp

I'm not at my desk so I don't know it off the top of my head, but it was in %programdata%/solarwinds/atlas/ or solarwinds/logs/atlas or somewhere there abouts. I didn't delete the log file, just the contents. Not sure if it makes a difference but just wanted to clarify.