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

How to fix Waiting for agent connection The management server is waiting for the agent to register with the server.

I have deployed One Identity Manager Data Governance Edition 8.0 and while deploying agent i could see "waiting for agent connection".

The status remains the same for long time and there is no error message.Kindly suggest the possible loop holes to fix this issue.

Thanks

  • What managed host type is it? Local Windows / Remote Windows / something else? Do you have a scanning schedule set for the agent? When you say there is no error message ... do you mean there is no error message in the DGE service log or in the agent log? Is the agent service actually running on the agent box?

  • Hi Matthew,

    Please find answers to your questions below:

    What managed host type is it? Local Windows / Remote Windows / something else? 

    1. It's a "Windows server, and i am trying to connect remote window server

    Do you have a scanning schedule set for the agent? 

    2.Yes, i defined/selected 3 paths and set the schedule as: run immediately after agent deployment (as i am deploying agent for the first time)

    When you say there is no error message ... do you mean there is no error message in the DGE service log or in the agent log? 

    No error message in agent log.

    Is the agent service actually running on the agent box?

    NO, i am deploying the agent for the first time.

    Please share more details on this. Do i need to install agent service on agent or my remote box.

    I could see the various stages of agent while deployment and i got stuck at "Waiting for agent connection"

    Please suggest me how to fix it.

    Thanks

  • I can see the agent deployment on my local machine with below error in Agent logs:

    INFO:Working directory: C:\Program Files\One Identity\One Identity Manager Data Governance Edition\Agent Services
    INFO:StartupOptions: ServiceName=DGE_UDG_LocalHost InstanceID=DGE_UDG_LocalHost
    INFO:Listening for service commands on '18530'alHost
    WARN:Failed to register with DGE Server. Will keep trying.

    Kindly suggest

    Thanks

  • I think your best bet at this point would be to log a ticket with the support department. That way, they can gather all the required information, log files, etc. Prior to creating the support ticket, I would suggest having a debug version of the agent log file along with your ticket. Here is the section of the documents regarding logs. Check the section for enabling debug logs on the agent. https://support.oneidentity.com/technical-documents/identity-manager-data-governance-edition/8.0.2/deployment-guide/22#TOPIC-1000467. Create the support ticket with the agent log after making that change (restart your agent after making the change, it isn't strictly required, but it is a good idea). Let support know about the accounts that both the agent service and DGE service are running as. Also include information from AD with regards to the Service Connection Point for the DGE service. Support should be able to help you from there.

  • Hi Matthew,

    Thanks for your suggestion.