No VMs are running on this connection

After downloading, installing & configuring the tool, I have these issues:

  1. I do not see all the esx hosts:  there are three but I only see one.
  2. I do not see all the datastores connected to the vCenter.
  3. Of the datastores I do see, no VMs are listed for any of them.  (If this were true I wouldn't have time to write this!) 

I have the software installed on a different server from the VMware vCenter server, but the server name and credentials were validated within the SRTM application.  All the statuses from the hosts show unknown.  Now, the server I have the software installed on is itself a VM.  Will this affect the software?

Thanks for your time & let me know if there's any more information you need.

  • We won't show an ESX host if it doesn't have datastores and we display a list of Host to data store connections not a list of datastores. Also if the data stores are not actively connected we may not show them.

    You can set the logging level to verbose and restart the app then after it runs for some time you can send us the logs and we can take a look at them.
  • I am having a similar issue.  I am running SRTM on my (physical) system and it states "No VM's are Running on this Connection."

    I am running an older version of vCenter:  12/12/2011 10:25:26 [11] INFO  VMDataProvider VirtualCenter

    The last line in my log states:  12/12/2011 10:27:26 [11] INFO  VMDataProvider Getting performance for 32 connected vms yet no performance metrics are displayed for the VMs

  • Can you send us log files so we could look at the issue? To capture the logs, please follow the steps below:

    1) go to settings and turn VERBOSE logging on

    2) reproduce the issue

    3) stop the application

    4) locate the log in c:\programdata\solarwinds\SRTM (C:\documents and settings\all users\application data\solarwinds\SRTM on older systems)

    You can use private message on thwack to send me the log file.

  • You can use private message on thwack to send me the log file.

    It doesn't seem to allow me to send a PM; the forum states my forum participation is too low to send you something.  I am assuming the "send e-mail" link in your profile is private messaging? 

    Doesn't matter.. I attached it to this reply since it doesn't have anything in it to compromise me.

    Thank you for your time!

  • jbencivengo,

    Michal and I have your logs and are looking at them. We should be able to get back to you on this forum in the next couple of days.




  • Thanks for your reply, sorry it took so long for me to get back to you.

    RE #1:  For a sanity check, I reviewed the hosts->datastore config from vSphere and there are more datastores shown being connected to an ESX host in vSphere than in RTSM.

    RE #2: The datastores I'm looking for are all actively connected and running VMs.

    RE #3: Attached is the logfile; after running in verbose mode for 1/2 hour (or so) the logfile is 504KB.

    Looking forward to any assistance!


  • Michelle,

    I also had the problem where only a few datastores were showing up.  I went into SRTM settings and I set both:

    "Show connections with worst response time" and "Show busiest VMs on a connection" from the default of "5" to "All" and now I see all my hosts and datastores.

    This didn't solve the No connected VMs issue though.  I also noticed you and I are both on vSphere 4.0.0.x.  I wonder if that may have something to do with it...


  • We will have more information coming later but for now we do know there is an issue with vSphere 4.0. It is not providing all the values we are expecting.

    More to come.



  • John, that worked for me as well.  I also have the problem of 'No connected VM's' and am also running vSphere 4.0 U2.  Also, regardless of what I set the limits to be for Warning and Error for response time, I don't see anything flagged the way I thought it would be.



  • All,

    Please see the following thread for information on this problem:

    Storage Response Time Monitor - missing VMs

    The crux of the issue is that some combinations of vSphere and ESX are not returning some of the metrics we need to provide IOPs for the VMs. We are not showing VMs for which we have no IOPs value. We are making an update to show those VMs and make it clear when IOPs are not available. We hope to have it available very soon. See the above link for best information on vSphere/ESX combinations.