Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Patch Manager > Unable to connect to the EminentWare Application Server

Unable to connect to the EminentWare Application Server

Created by Seamus.Enright, last modified by MindTouch on Jun 23, 2016

Views: 90 Votes: 0 Revisions: 10

Overview

This article describes the issue when you receive the following error: 

Sorry, we are unable to connect to the EminentWare Server. Verify that the connection information for the EminentWare Server is correct and the EminetWare Data Grid Service is started
Details: Unable to retrieve the device id for this server and cannot retrieve the certificate
DataPortal_Insert method call failed
DataPortal.Update failed

error2.png

 

You may also get the following error:

Source: Csla
Exception occurred at 12/05/2016 12:36:27: Unable to validate the session (6045c7e1-26f3-46ca-a2ad-40203300f44d) for user with textual sid (S-1-5-21-209280318-2008417505-470089971-1818340) at IP Address (35.53.49.188)
The session may have timed out. Use the reconnect action to re-establish a session.
DataPortal_Execute method call failed
DataPortal.Update failed

Environment

Patch Manager 2.1.1.2005-SR2 and earlier

Resolution

If this is happening from the server console immediately after installation:
  • Verify if EminentWare DataGrid Service is running
  • Verify if the Remote SQL database service is running
  • Verify if you are logged onto the server with the local Administrator account, or with a domain account that is already a member of the Administrators group on that machine.
 
If this is happening from a remote console:
  • Verify if the EminentWare DataGrid Service is running on the Patch Manager (Extension Pack) server and that you can connect from the console installed on the server.
  • Verify if the host firewall on the Patch Manager server is not blocking inbound access on port 4092, which is how the console connects to the server. The installer automatically creates and enables a rule in the Windows Firewall for this capability, but if you’re using a third-party host firewall, or you have Group Policies imposing configuration rules on the Windows Firewall, the configuration made by the installer may not be functional.
  • Verify if the hostname of the Patch Manager server is correct in the console logon dialog, and that your local machine is properly resolving the IP Address of the server hostname.
  • If the console and server are on different networks, verify if there's any intervening proxy servers, web appliances, or other network devices that are not blocking port 4092.
  • If the console can make the connection, the very first thing it does is download an authentication certificate from the server. Do not refuse this certificate.
  • By default, to connect a console session, it requires that the login being used has Administrator rights on the Patch Manager server. For non-admin accounts, you need to configure Security Roles from the server-side console to grant access to those that are non-admin accounts.
  • The basic issue that seems to exist is that the console cannot connect to the server to initiate any of the console initiation activities such as downloading the certificate, authenticating your login, or validating security role membership – these two most likely cause the service to fail to run or some network interference is blocking access on port 4092.

 

Last modified
01:20, 23 Jun 2016

Tags

Classifications

Public