Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > After integrating with Virtualization Manager, storage data is missing in the Orion Web Console

After integrating with Virtualization Manager, storage data is missing in the Orion Web Console

Table of contents
No headers
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 1,833 Votes: 0 Revisions: 8

All storage data is missing in the Orion Web Console after integration with Virtualization Manager. No datastores and historical statistics are available, and charts display the message: No Data.

Before you begin:
Before you proceed with the resolution, confirm that you experience this exact issue by performing the following steps:


  1. Run the following SQL query against the Orion database: SELECT * FROM Engines
  2. In the IP column, you should see the IP addressess assigned to each poller. If this IP address is not reachable from Virtualization Manager, it means that Virtualization Manager cannot send the data to the Orion database.


VMan master.log
2016-03-22 11:52:51,638 [pool-20-thread-1] ERROR com.solarwinds.vman.orion.collector.JobResultDispatcher:138 - sending results to VIM failed connect timed out 


To resolve this issue, perform the following procedure:


Option 1:

  1. Create a backup of the SolarWinds.VIM.BusinessLayer.dll.config file. This file is located in the VIM installation directory. By default, the installation directory is C:\Program Files (x86)\SolarWinds\Orion\VIM.
  2. In the original SolarWinds.VIM.BusinessLayer.dll.config file, locate a line that contains the following text: <add key="SyncWizardResolvePollerByHostname" value="false"/>
  3. Modify the value to "true", and then save the changes.
  4. In the Orion Service Manager, restart all Orion services.
  5. In the Orion Web Console, go to Settings > Virtualization Settings, and run the synchronization wizard again.


Option 2:

1) In the adapter settings with ip, select IPv4 Properties, there open Advanced settings. Uncheck the “Automatic metric” option and set Interface metric to 1 and save the changes


Once you do that, wait a moment, then check Engines table to see if the table contains correct IP, if it does, re-run the synchronization wizard, that should update IP that VMan is using to send data to


Additionally, it may also be necessary to modify the /etc/hosts file in the Virtualization Manager appliance to make sure that it can resolve the host name of the Orion server:

  1. Open the /etc/hosts file in a text editor.
  2. Add the following entry to the file: <IP_Address> <Orion_Server>
    where IP_Address is the IP address of your Orion server, and Orion_Server is the host name of the Orion Server.

After performing these procedures, storage data from Virtualization Manager should be available in the Orion Web Console.

Last modified