azure-pipelines-agent: KERNELBASE.dll exception with missing method exception VssEnvironment.EnumerateVssPaths()
Have you try trouble shooting doc?
Yes.
Agent version and platform
- v2.114.0
- v2.115.0
- v2.116.1
Platform:
- Windows Server 2016
- VS2015 Professional (Update 3)
VSTS type and version
VisualStudio.com
What’s not working?
tf.exe
in the vstsom
folder from the installed local agent.
See following when i try to run tf.exe manually:
Event log entry:
Faulting application name: TF.exe, version: 15.108.25929.0, time stamp: 0x583e1c41 Faulting module name: KERNELBASE.dll, version: 10.0.14393.1066, time stamp: 0x58d9f07f Exception code: 0xe0434352 Fault offset: 0x000da932 Faulting process id: 0x19f0 Faulting application start time: 0x01d2c7384050cee8 Faulting application path: C:\Users\Administrator\agent\externals\vstsom\TF.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: 6095e440-f263-4213-8901-0bbc0b167ef5 Faulting package full name: Faulting package-relative application ID:
What have i tried?
- Checked for corruption on server level.
- Repaired VS2015.
- Redownloaded and configured the agent.
- Checked permissions.
- Tried it as a different Windows user.
- Checked ‘Turn on DEP for essential Windows programs and services only’
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 50 (24 by maintainers)
Commits related to this issue
- Merge pull request #956 from alepauly/users/alpauly/151cherrypicks Bring forward commits from 151 versions — committed to prebansa/azure-pipelines-agent by alepauly 5 years ago
it’s in the GAC. 😄
Also note that we worked with the biz talk team to fix this for their next update.
@TingluoHuang Great! Glad we identified the program.
@ericsciple Shouldn’t the .NET versioning info on How to: Determine Which .NET Framework Versions Are Installed still be addressed because it corresponds with Win 10 like you mentioned?
Removing
Microsoft.VisualStudio.Services.Common
from the GAC did the trick. Pfew, thanks a lot for your assistance guys.Still curious what installer put that file in the GAC. It cerainly wasn’t me. This machine is brand new and i did nothing with the GAC yet.
… Of course, as soon as I claim to be out of ideas publicly, I have an idea. 🐑
@erwinkramer can you, from a Developer Command Prompt, run the following command?
gacutil /l | findstr /I Microsoft.VisualStudio.*
… and share the output. I’m wondering if the GAC isn’t out enemy here. Perhaps there’s a GAC version of the assembly that’s being loaded that’s actually older than the version shipped with the Agent. It’s worth a try!