locked
Troubleshooting Deployment Agent - Deployment Agent has not yet reported a heart beat. RRS feed

  • Question

  • We are new to Release Management and are running into a problem getting a deployment agent to work.  We have installed 2013 RM Server Update 4, RM Client Update 4, and Deployment Agent Update 4.  The Deployment agent has been installed on two servers - one is a Windows 2008 R2 server and the other is a Windows 2012 server.  All servers in our environment are in the same domain.  We are able to install and run configuration of the deployment agent on both the 2008 and 2012 server, and we are able to run deployments to the 2008 R2 server.  However, in the RM Client, the 2012 server shows a "Deployer Status" of Offline and an error stating "Deployment Agent has not yet reported a heart beat.  Please wait for some time and then try refreshing."  We have waited and the status does not change.  When we try to deploy to the server, the deployment fails and we get the message "the selected server is currently unavailable."  We've verified that port 1000 is open across the machines and we're not seeing anything in the event logs that indicates an error.  On the RM Server machine, we see posts to RM services that appear to be coming from the deployment agent machine so the channel of communication appears to be open.  We can't seem to figure out why we are getting this heartbeat error.  We are new to all of this - does anyone have any ideas for additional troubleshooting?

    Thanks in advance -


    Friday, March 27, 2015 9:01 PM

Answers

  • Hi Matt,

    Thanks for your reply. 

    There’s no value for IP Address and Version in  your screenshot, so it seems this deployment agent’s version and machine IP both not be identified in your RM Client, try to provide the full deployment agent machine name in DNS Name textbox, then Save & Close this server, and click Refresh button under Servers tab. 

    Please launch this “issue” agent’s Deployment Agent console, click About button to view it’s version manually. Ensure the version is 12.0.31101.0 Update 4.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Wednesday, April 1, 2015 8:41 AM
    Moderator

All replies

  • Hi Matt, 

    Thanks for your post.

    On your Windows 2012 Server, please manually access your http://servername:1000/ReleaseManagement in IE, ensure it can be accessed successfully. Then launch your Configure Microsoft Deployment Agent 2013 console, provide the required  account and RM Server URL(http://servername:1000/), then click Apply settings button, after applied correctly, recheck this deployment agent’s status in RM Client.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, March 30, 2015 5:56 AM
    Moderator
  • I have a Behind the Scenes of the RM Deployment Agent blog post that might be worth working through.

    Cheers - Graham


    Blog: http://pleasereleaseme.net   LinkedIn:

    Monday, March 30, 2015 9:37 AM
  • John-

    I am able to connect to the http://servername:1000/ReleaseManagement URL with no problems from the deployment target machine.  I have updated the deployment agent settings, applied settings, restarted all machines, etc. and the RM Client still shows that the deployer status of the target machine is Offline and the error is "Deployment Agent has not yet reported a heartbeat."

    Matt

    Monday, March 30, 2015 2:00 PM
  • Thanks for the link.  I have bookmarked it for future use.  Unfortunately, right now it didn't have anything to help me get the deployment agent and RM Server talking.

    Matt

    Monday, March 30, 2015 2:01 PM
  • Hi Matt,  

    Thanks for your reply.

    Try delete that Windows 2012 server from Servers tab in RM Client, then re-add it back to Servers and check result.

    If re-add server cannot resolve it, please open this Windows 2012 server from RM Client, and share the screenshot here.  


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, March 31, 2015 1:57 AM
    Moderator
  • Hi-

    Deleting and adding the server back did not fix the problem.  Below is a screen shot of the server from the RM Client.  Here is a link to the same image if you have trouble viewing it in the post:

    https://drive.google.com/file/d/0BwcijJMw1CdEeE5hYlFrUUcyWFE/view?usp=sharing


    • Edited by Matt Pelham Tuesday, March 31, 2015 1:06 PM Added link to image because it was difficult to see when embedded in post
    Tuesday, March 31, 2015 1:04 PM
  • Hi Matt,

    Thanks for your reply. 

    There’s no value for IP Address and Version in  your screenshot, so it seems this deployment agent’s version and machine IP both not be identified in your RM Client, try to provide the full deployment agent machine name in DNS Name textbox, then Save & Close this server, and click Refresh button under Servers tab. 

    Please launch this “issue” agent’s Deployment Agent console, click About button to view it’s version manually. Ensure the version is 12.0.31101.0 Update 4.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Wednesday, April 1, 2015 8:41 AM
    Moderator
  • Using the FQDN of the machine cleared up the problems and we are now able to run deployments to the server.  Is there an issue with using DNS names for machines in the RM Client?  We tend to set up internal DNS names for our servers and use those rather than directly referencing machine names.
    Thursday, April 2, 2015 12:51 PM
  • Hi Matt, 

    Thanks for your reply.

    We usually use machine name and DNS name in RM Client connect to the Deployment Agent, and that works fine. But for this specific ‘issue’ agent, we should use the FQDN provide in RM Client to connect it.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Friday, April 3, 2015 2:06 AM
    Moderator