Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Storage Resource Monitor (SRM) > SRM - Knowledgebase Articles > Integration failure with the SRM Orion and SRM Profiler modules

Integration failure with the SRM Orion and SRM Profiler modules

Overview

When integrating SRM Profiler Module and SRM Orion Module, the connection test is successful yet the integration fails. The following error message is received:

Cannot establish communications between Storage Resource Monitor and Storage Profile. See logs for more information.

Environment

All SRM versions

Resolution

Resolve the DNS name for the server hosting the SRM Orion Module from the server hosting the SRM Profiler Module. Update the host file as well on the SRM Profiler Module, mapping the SRM Orion Module server host name with its assigned IP address.

 

Also make sure to use the built in 'admin' account and don't  use a AD/LDAP account. 

 

The Orion Server expects to try to contact the Profiler/STM server using the built in 'admin' account using HTTPS and port 8443 using JSWIS (Java based SolarWinds Information Service as its methodology to connect back to the STM/Profiler server.

 

admin_integration.png

Last modified

Tags

Classifications

Public