Network Management
Network Atlas error Connection to the Information Service has been lost and could not be established
This article describes a problem that can occur within the Network Atlas application, The following error is shown when attempting to open a map: Connection to the Information Service has been lost and could not be established.
First published date
Last published date
Overview
When attempting to open maps in the Network Atlas application the maps cannot be opened:
Upon checking SWIS V3 log - C:\ProgramData\Solarwinds\InformationService\v3.0\Orion.InformationService.log: Connection to the Information Service has been lost and could not be established.
There can be a few reasons why this issue can occur:
If you see something like:
ERROR SolarWinds.InformationService.Core.InformationService - (null) Exception caught in method Invoke
SolarWinds.InformationService.Verb.VerbExecutorException: Verb Orion.MapStudioFiles.GetMapStyle: Cannot find assembly
at SolarWinds.InformationService.Verb.VerbExecutor.EnsureCached(VerbExecutorContext verbExecContext)
NetworkAtlas log
FATAL MapEngine - Connection is in faulted state
System.ServiceModel.FaultException`1[SolarWinds.InformationService.Contract2.InfoServiceFaultContract]: Invoke failed, check fault information. (Fault Detail is equal to SolarWinds.InformationService.Contract2.InfoServiceFaultContract).
[Main Window UI thread] FATAL NetworkAtlas - UNHANDLED EXCEPTION CAUGHT ON UI THREAD.
[Main Window UI thread] FATAL NetworkAtlas - Message: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
[Main Window UI thread] FATAL NetworkAtlas - Data: System.Collections.ListDictionaryInternal
2015-12-22 16:13:10,319 [Main Window UI thread] FATAL NetworkAtlas - TargetSite: IntPtr CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
[Main Window UI thread] FATAL NetworkAtlas - StackTrace: at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)
at System.Windows.Forms.Control.DefWndProc(Message& m)
at System.Windows.Forms.AxHost.WndProc(Message& m)
at SolarWinds.MapEngine.MapEditor.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
FATAL NetworkAtlas - Source: System.Windows.Forms
Then the issue might be network atlas corruption.
However, You may also see this issue if a specific map has a query that receives a timeout from the sql server, this can be because the query cannot find specific items it is looking for and this causes the information service v3 issues, making the network atlas run into an exception and closes down the application.
ERROR SolarWinds.InformationService.Core.InformationService - NetworkAtlas|
NetworkAtlas.exe|
SolarWinds.MapEngine.WcfConnectionDependentExecutor`1+Executor.ExecutionDriver()| (null)
Exception caught in method SolarWinds.InformationService.Core.InformationService.RunQuery
System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired.
The timeout period elapsed prior to completion of the operation or the server is not
responding.
---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
Product section
Cause
- SolarWinds Information Service is in an inconsistent state
Resolution
For Corruption
- Click Start > Control Panel > Programs and Features
- Click SolarWinds Orion Network Atlas, and then click Repair.
- Click SolarWinds Information Service, and then click Repair.
- Verify that the issue is cleared and that maps can again be viewed in the Network Atlas.
For SQL Query timeout similar to the second query
- Try to Remove all objects on the map and re-add them.
- The above may help for example, if we have orphaned topology data from actual data in the database.
Further debugging
If you need to debug this further, complete the following steps.- Open LogAdjuster on your Primary Polling Engine. (See Adjust logging levels with the Orion Log Adjuster.)
- Locate SolarWinds Information Service Section all to DEBUG.
- Increase log file size to 50 MB and 25 Files and click Apply.
-
On your own local client Network atlas (NA) machine, go to:
VOLUME:\Program Files (x86)\SolarWinds\Orion\Network Atlas\NetworkAtlas.exe.config- Open it and locate <level value="INFO" /> at the bottom of the file.
- Change it to <level value="DEBUG" />. Save it.
- Open NA on your client. Connect to the primary poller, get the error. Wait few mins. Close Network Atlas.
- Go to Primary Polling Engine. Copy and ZIP all logs here: C:\ProgramData\SolarWinds\InformationService\v3.0
- Open LogAdjuster and press the reset all to default button. Click Apply.
- Go back to the Network Atlas client.
- Gather and ZIP the logs from ${ProgramData}\SolarWinds\NetworkAtlas\NetworkAtlas.log (any network atlas.log files).
- Inspect the Primary Polling Engine SWIS V3 logs and the client's NA client logs.
- If you are contacting SolarWinds Support, please also provide full diagnostics alongside both files. (See Tips and Tricks on opening a Support Ticket with SolarWinds and How to gather and send a diagnostics file to SolarWinds Support.)