Forum Discussion
Karel_Kral
Sep 05, 2023Copper Contributor
VssUnauthorizedException: VS30063: You are not authorized to access... in web service application
In my service application, I am calling Azure DevOps server using https://learn.microsoft.com/en-us/azure/devops/integrate/concepts/dotnet-client-libraries?view=azure-devops for .Net. This applicatio...
AntonVasserman
May 29, 2024Former Employee
Hi Karel,
We've had a similar issue, for use what fixed it was to re-create the client on exception.
We figured out that the client's token/authentication expires after a certain time, so re-creating the client with a new token should be the solution.
We just wrapped the client with a proxy to re-create it on failures.
Hope this helps you as well!
We've had a similar issue, for use what fixed it was to re-create the client on exception.
We figured out that the client's token/authentication expires after a certain time, so re-creating the client with a new token should be the solution.
We just wrapped the client with a proxy to re-create it on failures.
Hope this helps you as well!
Karel_Kral
May 29, 2024Copper Contributor
Hi Anton, thanks for confirming the issue. I have created a watchdog that checks AzDevOps availability and in the case of problems, restarts the application.
After watching the watchdog results, I think that the root cause of the issue is on the server side. The application works ok for 3 months, after that, one day two failures happened.
Your solution is also good, thanks for sharing.
After watching the watchdog results, I think that the root cause of the issue is on the server side. The application works ok for 3 months, after that, one day two failures happened.
Your solution is also good, thanks for sharing.