Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Cryptic error when attempting to publish symbols to on-premises TFS
See original GitHub issueRequired Information
Type: Bug Enter Task Name: Index Sources & Publish Symbols
Environment
-
Server - TFS on-premises?
- If using TFS on-premises, provide the version: 17.143.28912.1
-
Agent - Private
- If using private agent, provide the OS of the machine running the agent and the agent version:
| Capability name | Capability value |
|---|---|
| Agent.OS | Windows_NT |
| Agent.OSVersion | 10.0.14393 |
| Agent.Version | 2.131.0 |
Issue Description
Running the task results in the described error. Looking at the task code, the following execution flow emerges:
- The code reaches https://github.com/microsoft/azure-pipelines-tasks/blob/c5de8d6beb30280eae54e6f0c2a17bb59ad98d92/Tasks/PublishSymbolsV2/PublishSymbols.ps1#L175-L177 and discovers that there is no account name, no PAT and Aad is not used.
- So, the code executes https://github.com/microsoft/azure-pipelines-tasks/blob/c5de8d6beb30280eae54e6f0c2a17bb59ad98d92/Tasks/PublishSymbolsV2/PublishSymbols.ps1#L19-L20, sending an unauthenticated request to the on-premises Azure DevOps server.
This is strange. I would expect it at least to pass -UseDefaultCredentials. As it is now, the request is aborted, which is totally expected.
In effect, it makes it impossible to publish symbols to the on premises Azure DevOps server.
Task logs
Error logs
TF400813: Resource not available for anonymous access. Client authentication required. - Azure DevOps Server
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:20 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I do not have the reopen button. It is to create it from scratch. I would not bother, they seem to ignore our issues anyway…
Is there any progress on this bug? Should I open a Microsoft Support case to attract attention? Or maybe spam my entire organisation begging for developers to upvote this issue? Can the poor folks stuck with on-prem get some loving finally?