Skip to content
This repository has been archived by the owner on Feb 28, 2024. It is now read-only.

Analysis report fails for .NET core memory dumps #5

Closed
puneetg1983 opened this issue Jan 7, 2021 · 1 comment
Closed

Analysis report fails for .NET core memory dumps #5

puneetg1983 opened this issue Jan 7, 2021 · 1 comment
Assignees

Comments

@puneetg1983
Copy link
Contributor

The Dump Analysis report may fail to display managed callstacks and other .net analysis information if both .NET Core and .NET Framework are loaded in the process. The analysis report may contain an error like below.

Analysis results may be incomplete because an error occurred while initializing the CLR diagnostic runtime for instance_w3wp_17740.dmp. Dump File:  instance_w3wp_17740.dmp Type:  DebugDiag.DotNet.DacNotFoundException Message:  CLR is loaded in the target, but the correct dac file cannot be found. DacFileName: mscordacwks_Amd64_Amd64_4.8.4210.00.dll. DacLocation: To fix this problem, you can copy mscordacwks.dll from the server where the dump was taken and rename it to and add the path of the folder to the Symbol server path by going to Tools-> Options and Settings For more details on this issue, please refer to this blog. The following symbol probe information may be helpful:    Created SymbolReader with SymbolPath srvf:\nofolderexistshttp://msdl.microsoft.com/download/symbols        Probe of http://msdl.microsoft.com/download/symbols/mscordacwks_Amd64_Amd64_4.8.4210.00.dll/5efa67efac1000/mscordacwks_Amd64_Amd64_4.8.4210.00.dll failed: Could not find a part of the path 'f:\nofolderexists\mscordacwks_Amd64_Amd64_4.8.4210.00.dll\5efa67efac1000'.    Probe of http://msdl.microsoft.com/download/symbols/mscordacwks_Amd64_Amd64_4.8.4210.00.dll/5efa67efac1000/mscordacwks_Amd64_Amd64_4.8.4210.00.dl_ failed: The remote server returned an error: (404) Not Found.    Probe of http://msdl.microsoft.com/download/symbols/mscordacwks_Amd64_Amd64_4.8.4210.00.dll/5efa67efac1000/file.ptr failed: The remote server returned an error: (404) Not Found.

This issue will be fixed with ANT 92.

@puneetg1983 puneetg1983 self-assigned this Jan 7, 2021
@puneetg1983
Copy link
Contributor Author

This issue is resolved as ANT92 deployment finished everywhere.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant