I've just updated to Visual Studio 2015 Update 1, and I'm getting the error whenever I start debugging:
Internal Diagnostics Hub Exception. See log for more details.
How do I fix this, or disable the error?
I don't know which log file I should check. In ActivityLog.xml
, the last entry is of yesterday, so that doesn't contain anything useful. Next, I know there is a logfile of MEF (Microsoft.VisualStudio.Default.err
), but that's empty. How to investigate this?
I dug into the the Visual Studio logs to understand what was happening (
C:\Users\YourUser\AppData\Roaming\Microsoft\VisualStudio\14.0\ActivityLog.xml
). In mine, the messages were something like this:And then, I realized that TypeScript support should be broken.
Just installing TypeScript for Visual Studio 2015, closing Visual Studio and then opening your project again will solve your problem. The message will disappear.
I am also having the same issue on one of my installations (an upgrade from
Update 1
versus a clean ISO install of theUpdate 2 RC
bits which works). It should be noted my installation was also missing the ScriptedHost.dll assembly which I had to manually copy over from the working system :\The file
PerformanceDebuggerSwimLanesView.html
was missing fromc:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Platform\DiagnosticsHub\WebViews\
. After I copied over the file from a coworker, the error was fixed ;)I've put the file in a gist, in case you want it.
Enabled the logging as described in other answer and saw this error:
But the file
PerformanceDebuggerSwimLanesView.manifest.json
exists inC:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Platform\DiagnosticsHub\WebViews
. Solution is to run Visual Studio as Administrator, no more Internal Diagnostics Hub Exceptions.To enable the logs for the diagnostic tools, add the following registry keys
For LogLevel you can use one of the following strings "All", "Info", "Debug", "Warning", "Error" (In your case I would use All to better see what is happening). As for LogDirectory it is a directory of your choice "C:\Logs". When your done, don't forget to delete these keys as the diagnostic tools logging is pretty system intensive.
We try to only prompt message boxes in unexpected cases (normal errors are only shown as an error in the tool window and never through a message box), so this sounds like an issue with a 3rd party app or some weird upgrade issue. You should be able to search for "Error ---" in the logs and see what the root cause is. Feel free to post the error here or PM me and I would be happy to help (Note: I work on the Diagnostic Tools team)
Feel free to also post the issue at: https://connect.microsoft.com/ Each issue that is received there gets turned into a bug and assigned to the corresponding team.
This worked for me:
Inspired by this post:
https://connect.microsoft.com/VisualStudio/feedback/details/3038181/internal-diagnostics-hub-exception