• State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 94 subscribers
  • Views 8741 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DGE Agent status shows "Waiting for Agent Connection"

Jaipal.Sivaiah
over 8 years ago

Hi All,
I have installed and configured D1IM 7.0.2 with DGE edition. I have configured Locally Managed windows host, but Agent status says:

"Waiting for Agent Connection"

I have opened all required ports on Agent Server. Any idea how to fix this issue?

Here is the Agent Log error:


2016-09-19 15:22:19.228 [4][INFO][InitializeAgentService(0)] Working directory: C:\Program Files\Dell\One Identity Manager Data Governance Edition\Agent Services
2016-09-19 15:22:19.228 [4][INFO][InitializeAgentService(0)] StartupOptions:
ServiceName=DGE_DEFAULT_LocalHost InstanceID=DGE_DEFAULT_LocalHost
2016-09-19 15:22:19.243 [5][INFO][StartDgeServerListenerSocket(0)] Listening for service commands on '18530'
2016-09-19 15:22:19.665 [5][WARN][Register(0)] Failed to register with DGE Server. Will keep trying.

 

Thanks,
JP

Parents
  • 0 over 8 years ago
    How did you install the Data Governance service? Did you use the Data Governance Configuration Wizard (i.e. C:\Program Files\Dell\One Identity Manager\Data Governance Configuration Wizard.exe) or did you install it manually?

    The only reasons I can think of for the Data Governance service not to start correctly running as local system are as follows:

    1. The service was deployed but not initialized (i.e. in the registry on the DGE Server you will see the following values under HKEY_LOCAL_MACHINE\SOFTWARE\Dell\Broadway\Server: "Q1IMDBConnectionString" and "QAMAuditActivityDBConnectionString" if either of those are empty, then the DGE service has not been initialized)
    2. The service was deployed and initialized, but then the service was afterwards changed to run as a different account. This means that the encrypted connection strings in the database can no longer be decrypted and therefore the DGE service will fail to start.

    The main reason for running the DGE service as an account other than Local System are if you are using Windows Authentication to your SQL Server instead of using SQL Authentication.

    So understanding how you deployed the DGE Service to begin with, in conjunction with understanding the authentication to SQL Server you are using would help.

    There are PowerShell commands available that can do the initialization of the DGE Service using the account it is running as (Initialize-QDataGovernanceServer and Initialize-QDataGovernanceActivity), but I wouldn't go that far right now.

    My recommendation is to manually Remove the Data Governance Service from the machine, and then re-deploy using the Data Governance deployment wizard. It's a quick wizard and basically installs the service, creates the activity database (or, reuses the one you specify), and initializes the service with the connection to D1IM and to the DGE activity database. If you are not using SQL authentication and must run using Windows Authentication to SQL Server, then let us know.
Reply
  • 0 over 8 years ago
    How did you install the Data Governance service? Did you use the Data Governance Configuration Wizard (i.e. C:\Program Files\Dell\One Identity Manager\Data Governance Configuration Wizard.exe) or did you install it manually?

    The only reasons I can think of for the Data Governance service not to start correctly running as local system are as follows:

    1. The service was deployed but not initialized (i.e. in the registry on the DGE Server you will see the following values under HKEY_LOCAL_MACHINE\SOFTWARE\Dell\Broadway\Server: "Q1IMDBConnectionString" and "QAMAuditActivityDBConnectionString" if either of those are empty, then the DGE service has not been initialized)
    2. The service was deployed and initialized, but then the service was afterwards changed to run as a different account. This means that the encrypted connection strings in the database can no longer be decrypted and therefore the DGE service will fail to start.

    The main reason for running the DGE service as an account other than Local System are if you are using Windows Authentication to your SQL Server instead of using SQL Authentication.

    So understanding how you deployed the DGE Service to begin with, in conjunction with understanding the authentication to SQL Server you are using would help.

    There are PowerShell commands available that can do the initialization of the DGE Service using the account it is running as (Initialize-QDataGovernanceServer and Initialize-QDataGovernanceActivity), but I wouldn't go that far right now.

    My recommendation is to manually Remove the Data Governance Service from the machine, and then re-deploy using the Data Governance deployment wizard. It's a quick wizard and basically installs the service, creates the activity database (or, reuses the one you specify), and initializes the service with the connection to D1IM and to the DGE activity database. If you are not using SQL authentication and must run using Windows Authentication to SQL Server, then let us know.
Children
No Data