Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Storage Resource Monitor (SRM) > SRM - Knowledgebase Articles > Storage Resource Monitor is able to connect to the device but no compatible arrays were found

Storage Resource Monitor is able to connect to the device but no compatible arrays were found

Table of contents

Updated September 12th, 2016


Storage Resource Monitor was able to connect to the device but no compatible arrays were found.


All SRM versions


This issue can be triggered by any of the following issues:

  • An incorrect storage array type was chosen.
  • The device was unavailable during discovery, or the SMI-S provider itself could be unavailable. To test this you can use either the built-in Solarwinds CIM Browser tool from the Orion server: C:\Program Files (x86)\SolarWinds\Orion\SRM, or you can use the TestSMIProvider.bat file to ensure connectivity.
  • The provider is installed, but is not configured correctly to scan any devices. For more information on configuring your array and provider, see Add Arrays to SRM.
  • An unsupported version of the provider is being used. 
  • Find out if your storage array has a SMI-S provider built into the array itself (some more recent storage arrays can detect this) or if the SMI-S provider is installed as a third party service on a server somewhere. For EMC, for example, it commonly uses a service called ECOM. Make sure ECOM is turned on and the service has not died. Sometimes a common issue is that the ECOM service can start and then stop right away. Make sure the ECOM service starts and stays running.
  • Licensing can also cause this behavior. Check to ensure your license is large enough to accommodate another discovery. If necessary you can try unseating your license and reseating it to make sure the Orion module is calculating your License correctly and allows you to add an array.
Last modified