search

jessehouwing / azure-pipelines-tfvc-tasks

Azure Pipelines tasks for Team Foundation Version Control
https://marketplace.visualstudio.com/items?itemName=jessehouwing.jessehouwing-vsts-tfvc-tasks
MIT License
28 stars 17 forks source link

Service EndPoint Error using Check Out Task #70

Closed leahymichael closed 6 years ago

leahymichael commented 6 years ago

We've been using the CheckOut / CheckIn tasks for a while now as part of our builds; this morning the CheckOut task started throwing the following error:

System.Collections.Generic.KeyNotFoundException: The service endpoint society was not found PowerShell script completed with 1 errors.

This is running against local (private) build agents. I've made sure the build agent code, and the VS Install on the build agent is current, but neither helped the error.

jessehouwing commented 6 years ago

Thus has been fixed in the latest agent version. Please upgrade your agent to 2.140

On Mon, 10 Sep 2018, 18:32 leahymichael, notifications@github.com wrote:

We've been using the CheckOut / CheckIn tasks for a while now as part of our builds; this morning the CheckOut task started throwing the following error:

System.Collections.Generic.KeyNotFoundException: The service endpoint society was not found PowerShell script completed with 1 errors.

This is running against local (private) build agents. I've made sure the build agent code, and the VS Install on the build agent is current, but neither helped the error.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jessehouwing/vsts-tfvc-tasks/issues/70, or mute the thread https://github.com/notifications/unsubscribe-auth/AD-uSw5WbYOhusu5Bxg9HGei0lB3W7rHks5uZpQpgaJpZM4WhwZc .

leahymichael commented 6 years ago

Ok thanks, I'm on 2.138.6 currently - I ran the Agent Auto-Update and didn't realize it actually failed, so looks like I'll have to manually re-deploy the agents (again - had to do that on last update as well). I will try that and hopefully that does the trick.

leahymichael commented 6 years ago

Manually updating to 2.140 agent fixed the issue. Thanks for quick response.