Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Patch Manager > Unable to access automation servers from the primary server console

Unable to access automation servers from the primary server console

Updated July 14, 2017


This article describes an issue where you are unable to browse and access the Patch Manager Console and the following error is found in the EWDGS logs:

2017/07/06 13:23:29:412 PID: 7104 TID:  6168 [ERROR] SMO InnerException: An exception occurred while executing a Transact-SQL statement or batch.
    at Microsoft.SqlServer.Management.Smo.SqlSmoObject.AlterImpl()
   at EminentWare.DataQueryAdapters.CMDBManager.SetAutoCloseOff()
2017/07/06 13:55:57:567 PID: 7104 TID:  4948 [ERROR] MonitoringAndSychronizationRequest::ExecuteDiagnosticsRequest(auto) to server: V1TSSPM03 failed. Message: Communication failure.
The RPC server is unavailable.
Details: dgsrpcinterface::createsession failed!
Stack Trace:    at EminentWare.Core.Client.RPC.rpcclient.createsession(String operation, String subsystem, String taskid)
   at EminentWare.DataGridServer.Executive.MonitoringAndSychronizationRequest.ExecuteDiagnosticsRequest()


  • Patch Manager 2.1.3
  • Automation server in separate domains with individual service accounts


  1. Delete the EminentWare certificates from the automation servers.
  2. Repair the automation server from Add or Remove programs.
  3. Run the Patch Manager configuration wizard to completion.
  4. Run the Patch Manager server wizard to authenticate the primary server from the automation server.
  5. Run services.msc and start the EminentWare service.


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.


Last modified