azure-pipelines-tasks: PublishSymbols fails after Windows Update

Required Information

Question, Bug, or Feature?: Bug Enter Task Name: PublishSymbols

Environment

  • Azure DevOps Server (on-premises) Version Dev17.M153.5
  • private Agent
    • on Windows Server 2019 Version 1809
    • agent version 2.170.0
    • 5 agents are identically configured to the same pool

Issue Description

The builds using PublishSymbols task were running fine until installation Windows updates. Now the step fails with Encountered Win32 error '203' from method 'SymEnumSourceFiles'.

  • We are using V1 and V2 of Publish symbols.
  • Last successful run around 5th august.
  • Windows updates installed on 13th august: KB4570505, KB4565349, KB4566424

Similar issues exist but already closed without helpful information:

  • #9139 => x64 version on x64 Windows is installed
  • #13439 => self-closed after downgrade to Win2016

Please note, the waning on dbghelp.dll is very confusing because expected and actual path are identical!

Task logs

1_Initialize Job.txt 14_Publish symbols.txt

Error logs

##[warning]Library dbghelp.dll is already loaded from an unexpected path. Expected 'C:\build\_work\_tasks\PublishSymbols_0675668a-7bba-4ccb-901d-5ad6554ca653\2.0.16\dbghelp.dll'. Actual 'C:\build\_work\_tasks\PublishSymbols_0675668a-7bba-4ccb-901d-5ad6554ca653\2.0.16\dbghelp.dll'.
##[error]Encountered Win32 error '203' from method 'SymEnumSourceFiles'.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 15 (2 by maintainers)

Most upvoted comments

I spend some serious time on this issue as well. After failing to uninstall any of the mentioned KB (KB4570505, KB4565349, KB4566424) updates via wusa and experimenting with several versions of the task, I was eventually able to fix the problem by removing McAfee antivirus from the affected server. It has since been replaced with a competitors product but unfortunately I’m not allowed to share the name of the product here due to company policies.