locked
Build Agent goes offline after closing run cmd window RRS feed

  • Question

  • I set up a vNext build agent in windows 10 machine. also while configuring the agent i did "Yes" for 'run as service' , but still when i close the run cmd the build agent goes offline. i tried checking in the local services, but even when the run cmd window is running, i dont see any services related to buildagent.
    Tuesday, July 2, 2019 7:06 PM

All replies

  • Hi ravi.gujja,

    Thanks for your feedback.

    According to your issue, there are some problems in your process of installing the agent.
    Please check if you have successfully deployed the agent first,generally it will display the succeed messages from the console.
    If not, try this:

    #Remove and re-configure an agent  

    If the issue still persists,try to deploy a new agent  or reproduce the issue on other machines to check if it have the same issue.

    If there's any concern, please feel free to let me know.

    Best Regards,

    Perry



    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com




    Wednesday, July 3, 2019 9:45 AM
  • Hi ravi.gujja,

    Do you have any updates? If this issue not solved, please feel free to let us know. If my reply is helpful to solve your issue, please consider marking as an answer so that can help other community members search similar problems.

    >>Note: Since your problem is about TFS, l suggest that you could redirect your issue to Stack Overflow or Developer Community because the TFS forum has been locked and the discussion for TFS has moved. Thanks for your understanding.

    Best Regards,

    Perry


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com







    Wednesday, July 10, 2019 7:12 AM