Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > 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 Server certificate ONLY from the Trusted root certificate store on 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