Warning: file_get_contents(/data/phpspider/zhask/data//catemap/1/angular/26.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181
Performance 远程调试时无法使用诊断工具_Performance_Visual Studio 2015_Remote Debugging_Diagnostics - Fatal编程技术网

Performance 远程调试时无法使用诊断工具

Performance 远程调试时无法使用诊断工具,performance,visual-studio-2015,remote-debugging,diagnostics,Performance,Visual Studio 2015,Remote Debugging,Diagnostics,我面临一个问题,在远程调试期间无法使用诊断工具。如果我在本地机器上启动程序,一切正常 在确保我的域用户具有目标计算机上的调试权限(在远程调试工具中配置)后,我将Visual Studio连接到远程计算机上正在运行的进程。然后,我切换到diagnostics(诊断)窗口,却收到一条错误消息 在搜索web后,我找到了一种获得详细输出的方法,得到了以下结果: Debug --- Diagnostics Hub Components Loader --- Component 44d04ed9-f786

我面临一个问题,在远程调试期间无法使用诊断工具。如果我在本地机器上启动程序,一切正常

在确保我的域用户具有目标计算机上的调试权限(在远程调试工具中配置)后,我将Visual Studio连接到远程计算机上正在运行的进程。然后,我切换到diagnostics(诊断)窗口,却收到一条错误消息

在搜索web后,我找到了一种获得详细输出的方法,得到了以下结果:

Debug --- Diagnostics Hub Components Loader --- Component 44d04ed9-f786-458c-93a9-7207a3cc52e1 (Microsoft.DiagnosticsHub.Components.LazyCollectorFactory) has been loaded.
Debug --- Diagnostics Hub Components Loader --- Component 28b3f966-03cc-4632-ae04-0861ef17555a (Microsoft.DiagnosticsHub.Components.LazyCollectorFactory) has been loaded.
Debug --- Diagnostics Hub Components Loader --- Component 113e964e-152f-45e7-b70e-1e5482802d0c (Microsoft.DiagnosticsHub.Diagnostics.OutputWindowLogger) has been loaded.
Debug --- Diagnostics Hub Components Loader --- Component 72089e7a-a3c8-4652-9817-f33c8149affc (Microsoft.DiagnosticsHub.Components.LazyCollectorFactory) has been loaded.
Debug --- Diagnostics Hub Components Loader --- Component 42d07b97-c049-403e-bd24-6c55fb096d1a (Microsoft.DiagnosticsHub.VisualStudio.Targets.ExecutableTargetProviderFactory) has been loaded.
Debug --- Diagnostics Hub Components Loader --- Component 34c0b0b0-0658-4dd3-a677-81108d433d8d (Microsoft.DiagnosticsHub.VisualStudio.Targets.ProcessTargetProviderFactory) has been loaded.
Debug --- Diagnostics Hub Components Loader --- Component 52827652-539a-4099-b829-38cba3641110 (Microsoft.DiagnosticsHub.VisualStudio.Targets.AspNetWebsiteTargetProviderFactory) has been loaded.
Debug --- Diagnostics Hub Components Loader --- Component 283ff32f-bc50-467c-a318-ee7015338ac0 (Microsoft.DiagnosticsHub.VisualStudio.Targets.VisualStudioProjectTargetProviderFactory) has been loaded.
Debug --- Diagnostics Hub Components Loader --- Component 572daee0-945b-41d7-8d79-5cbf5a114372 (Microsoft.DiagnosticsHub.Components.LazyToolFactory) has been loaded.
Debug --- Diagnostics Hub Components Loader --- Component 7f65b00f-b8e3-494d-a7b7-51f13cc2011a (Microsoft.DiagnosticsHub.Components.LazyToolFactory) has been loaded.
Debug --- Diagnostics Hub Components Loader --- Component 962a0ef2-9fae-4c82-98b4-b1406b977de3 (Microsoft.DiagnosticsHub.Components.LazyToolFactory) has been loaded.
Debug --- Diagnostics Hub Components Loader --- Component 33041a6b-f1dc-4894-86a9-14e3af8299c2 (Microsoft.DiagnosticsHub.Components.LazyToolFactory) has been loaded.
Debug --- Diagnostics Hub Components Loader --- Component 1160defd-0dd3-4a25-a57b-aeff03e17354 (Microsoft.DiagnosticsHub.Components.LazyToolFactory) has been loaded.
Debug --- Diagnostics Hub Components Loader --- Component 013914d7-d262-4da2-8fa4-ba8b4e328a1e (Microsoft.DiagnosticsHub.Components.LazyToolFactory) has been loaded.
Debug --- Diagnostics Hub Components Loader --- Component dbd5eb76-7ff8-4e5a-a9b8-21b007462c7f (Microsoft.DiagnosticsHub.Components.LazyToolFactory) has been loaded.
Debug --- Diagnostics Hub Components Loader --- Component 92d8d397-d96b-442e-b891-229b833e8797 (Microsoft.DiagnosticsHub.Components.LazyToolFactory) has been loaded.
Debug --- Diagnostics Hub Components Loader --- Component 051c002f-2430-4d7a-a545-28294e888186 (Microsoft.DiagnosticsHub.Components.LazyToolFactory) has been loaded.
Debug --- Diagnostics Hub Components Loader --- Component 96dcf139-9a62-4adf-b9fa-7aec44c0b9cc (Microsoft.DiagnosticsHub.Components.LazyToolFactory) has been loaded.
Debug --- Diagnostics Hub Components Loader --- Component 96f1f3e8-f762-4cd2-8ed9-68ec25c2c722 (Microsoft.DiagnosticsHub.Components.LazyToolFactory) has been loaded.
Debug --- Diagnostics Hub Components Loader --- Plug-ins have been loaded.
Debug --- Service Microsoft.DiagnosticsHub.IDocumentsService implementation --- New document was created 'C:\Users\steffen\AppData\Local\Temp\Bericht20150909-1642.diagsession'
Debug --- ApplicationPathService --- Hub application path is 'E:\Programme\Visual Studio\Common7\IDE\CommonExtensions\Platform\DiagnosticsHub'
Debug --- Scripted Control (PerformanceDebuggerSwimLanesView.manifest.json) --- Initializing the ScriptedControl with manifest file 'E:\Programme\Visual Studio\Common7\IDE\CommonExtensions\Platform\DiagnosticsHub\WebViews\PerformanceDebuggerSwimLanesView.manifest.json'. Base directory 'E:\Programme\Visual Studio\Common7\IDE\CommonExtensions'
Debug --- Scripted Control (PerformanceDebuggerSwimLanesView.manifest.json) --- Menu command service is provided for manifest 'E:\Programme\Visual Studio\Common7\IDE\CommonExtensions\Platform\DiagnosticsHub\WebViews\PerformanceDebuggerSwimLanesView.manifest.json'.
Debug --- Scripted Control (PerformanceDebuggerSwimLanesView.manifest.json) --- Creating UIElement for E:\Programme\Visual Studio\Common7\IDE\CommonExtensions\Platform\DiagnosticsHub\WebViews\PerformanceDebuggerSwimLanesView.manifest.json.
Debug --- EventAggregator --- Event Aggregator doesn't have registered managed handlers for event type 'DiagnosticsHub.EventAggregator.DetailsViewSelectionChangedEvent'
Debug --- DiagnosticsHubPackage --- Visual Studio asks service 'Microsoft.DiagnosticsHub.VisualStudio.SDK.SVsDiagnosticsHubService'
Debug --- DiagnosticsHubPackage --- Creating service 'Microsoft.DiagnosticsHub.VisualStudio.SDK.SVsDiagnosticsHubService'.
Debug --- Session ('02e7a183-8bf4-420d-8101-d6850e19f723') --- Changing state from 'Unknown' to 'Created'.
Debug --- Document ('C:\Users\steffen\AppData\Local\Temp\Bericht20150909-1642.diagsession') --- Changing document state from 'New' to ActiveSession.
Debug --- Session ('02e7a183-8bf4-420d-8101-d6850e19f723') --- State has been changed to 'Created'.
Debug --- SessionsService --- New session has been created for document 'C:\Users\steffen\AppData\Local\Temp\Bericht20150909-1642.diagsession'
Debug --- SessionTargetsService --- New target added PerfDebuggerTarget.
Debug --- Session ('02e7a183-8bf4-420d-8101-d6850e19f723') --- Changing state from 'Created' to 'InitializePerformanceDebugger'.
Debug --- Session ('02e7a183-8bf4-420d-8101-d6850e19f723') --- State has been changed to 'InitializePerformanceDebugger'.
Debug --- Session ('02e7a183-8bf4-420d-8101-d6850e19f723') --- Collectors count: 1.
Debug --- Session ('02e7a183-8bf4-420d-8101-d6850e19f723') --- Changing state from 'InitializePerformanceDebugger' to 'PerformanceDebuggerInitialized'.
Debug --- Session ('02e7a183-8bf4-420d-8101-d6850e19f723') --- State has been changed to 'PerformanceDebuggerInitialized'.
Das System kann die angegebene Datei nicht finden. (Ausnahme von HRESULT: 0x80070002)
Debug --- Session ('02e7a183-8bf4-420d-8101-d6850e19f723') --- Changing state from 'PerformanceDebuggerInitialized' to 'CollectionTerminating'.
Debug --- Session ('02e7a183-8bf4-420d-8101-d6850e19f723') --- State has been changed to 'CollectionTerminating'.
Debug --- Session ('02e7a183-8bf4-420d-8101-d6850e19f723') --- Changing state from 'CollectionTerminating' to 'CollectionTerminated'.
Error --- Session ('02e7a183-8bf4-420d-8101-d6850e19f723') --- 
堆栈跟踪:

System.Exception: Error code: 0x80070002
       bei System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       bei Microsoft.DiagnosticsHub.VisualStudio.Collectors.CollectorService.StandardClientCollector.<CleanUpCollectionSession>d__29.MoveNext()
    --- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
       bei System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       bei Microsoft.DiagnosticsHub.VisualStudio.Collectors.CollectorService.StandardClientCollector.<Failed>d__17.MoveNext()
    --- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
       bei System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       bei Microsoft.DiagnosticsHub.VisualStudio.Runtime.PerformanceDebuggerSession.<TerminateCollectionAsync>d__38.MoveNext()
    Debug --- Document ('C:\Users\steffen\AppData\Local\Temp\Bericht20150909-1642.diagsession') --- Changing document state from 'ActiveSession' to Failed.
    Debug --- SessionsService --- Closing session for document C:\Users\steffen\AppData\Local\Temp\Bericht20150909-1642.diagsession
    Debug --- SessionsService --- Session for document C:\Users\steffen\AppData\Local\Temp\Bericht20150909-1642.diagsession was closed
System.Exception:错误代码:0x80070002
bei System.Runtime.CompilerServices.TaskWaiter.ThrowForNonSuccess(任务任务)
bei System.Runtime.CompilerServices.TaskWaiter.HandleNonSuccessAndDebuggerNotification(任务)
bei Microsoft.DiagnosticsHub.VisualStudio.Collectors.CollectorService.StandardClientCollector.d_u29.MoveNext()
---这是一个非常有趣的故事---
bei System.Runtime.CompilerServices.TaskWaiter.ThrowForNonSuccess(任务任务)
bei System.Runtime.CompilerServices.TaskWaiter.HandleNonSuccessAndDebuggerNotification(任务)
bei Microsoft.DiagnosticsHub.VisualStudio.Collectors.CollectorService.StandardClientCollector.d_u17.MoveNext()
---这是一个非常有趣的故事---
bei System.Runtime.CompilerServices.TaskWaiter.ThrowForNonSuccess(任务任务)
bei System.Runtime.CompilerServices.TaskWaiter.HandleNonSuccessAndDebuggerNotification(任务)
bei Microsoft.DiagnosticsHub.VisualStudio.Runtime.PerformancedBuggerSession.d_u38.MoveNext()
调试---文档('C:\Users\steffen\AppData\Local\Temp\Bericht20150909-1642.diagsession')---将文档状态从“ActiveSession”更改为失败。
调试---会话服务---关闭文档C:\Users\steffen\AppData\Local\Temp\Bericht20150909-1642.diagsession的会话
调试---会话服务---文档C:\Users\steffen\AppData\Local\Temp\Bericht20150909-1642的会话已关闭
该错误提到一个找不到的文件(Das系统kann die angegebene Datei nicht finden.(Ausnahme von HRESULT:0x80070002)),但没有提到哪个文件找不到

我在SO或网络上找不到任何有用的东西。我找到的最接近的东西是,但是这里没有崩溃,我只是在output/diaghub窗口中得到了异常,就是这样

编辑

感谢Thomas,我找到了4个丢失的文件和一个我不确定的文件

  • 前两个文件是我的项目中的两个.cs文件。它试图在我的机器上找到这两个文件,但路径来自buildserver。不确定那里发生了什么,但我怀疑这是问题所在
  • Applicationinsights.config-应位于我的启动项目的.csproj文件夹中,但报告为“找不到名称”可以忽略。它属于基于Azure的服务
  • Microsoft.CodeAnalysis.CSharp.ExpressionEvaluator.ExpressionCompiler.dll-应位于
    Common7\IDE\CommonExtensions\Microsoft\Roslyn\ExpressionEvaluators
    中,但报告为“找不到名称”。复制它并不能解决问题
  • 我不确定的是:
    C:\Windows\SysWOW64\api-ms-win-core-fibers-l1-1.DLL
    。第一次文件名是[…]fibers-l1-2-1.dll,第二次文件名是[…]fibers-l1-1.dll。没有出现在我的第3次和第4次跑步中
  • 在我的第一次、第三次和第四次运行时出现了另一个文件(之前忽略了它,因为它在第二次运行时没有出现):MSCORDBI_MACX86,应该位于
    C:\Users\steffen\AppData\Local\Microsoft\SilverlightDebuggingConfig1.0\MSCORDBI_MACX86.dll中

对于丢失的文件,您能试试吗?嗯,这给了我一个很长的未找到文件列表。我想大部分都是经过一些探索后发现的。我尝试了一些技巧,比如附加4次,重新启动VisualStudio,附加6次并分析两个日志,过滤附件数量并搜索常见条目。我没有在每个日志中找到任何文件。该列表应按需要的探测量排序。通常情况下,未找到的一个之前需要进行最多的探测。对不起,没用。嗯,好像我以前犯过错误。也许我算错了。我又做了同样的事情(我自己都不敢相信),发现了多个常见条目。最突出的是
表达式计算器\Microsoft.codealysis.CSharp.ExpressionEvaluator.ExpressionCompiler.dll
,编辑我的问题。@Thomas不是搜索所有内容,而是Windows搜索在
\Visual Studio\Common7\IDE\PrivateSassemblies
中找到的。