question

nofilasad-8802 avatar image
0 Votes"
nofilasad-8802 asked lextm commented

DebugDiag2 Analysis - An error occurred while generating the analysis report

Hi,
I am getting the following error while analysing the dump files for a high CPU usage Exception:

Type: COMException Message:
Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED)) StackTrace:
at DebugDiag.DbgLib.DbgControlClass_Legacy.OpenDump(String DumpPath, String SymbolPath, String ImagePath, Object pProgress)
at DebugDiag.DotNet.NetDbgObj.OpenDump(String dumpPath, String symbolPath, String imagePath, Object pProgress, Boolean throwOnBitnessMismatch, Boolean loadClrRuntime, Boolean loadClrHeap)
at DebugDiag.DotNet.NetDbgObj.GetDumpFileType(String dumpFile, String symbolPath)
at DebugDiag.DotNet.NetAnalyzer.AddDumpFile(String dumpFile, String symbolPath)
at DebugDiag.DotNet.NetAnalyzer.AddDumpFiles(List`1 dumpFiles, String symbolPath)
at DebugDiag.Analysis.AnalyzerClient.RunAnalysisAsyncInternal(NetProgress progress, String symbolPath, String imagePath, List`1 dumpFiles, List`1 analysisRules, String reportFileDirectoryOrFullPath, Boolean IncludeSourceAndLineInformationInAnalysisReports, Boolean SetContextOnCrashDumps, Boolean DoHangAnalysisOnCrashDumps, Boolean IncludeHttpHeadersInClientConns, SynchronizationContext synchContext, Boolean ExcludeIdenticalStacks, Boolean IncludeInstructionPointerInAnalysisReports)

dotnet-aspnet-core-general
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

No surprise. DebugDiag is not a tool covered by Microsoft support contracts, and provided as it is, and it won't work for all dump files. You need to use VS or WinDbg to analyze the dump manually, or open a support case via http://support.microsoft.com and ask for help.

0 Votes 0 ·

0 Answers