EQATEC Profiler - 远程服务器返回错误：(404) 未找到
我正在尝试使用 EQATEC Profiler 来分析我的 ASP.Net 应用程序。我按照此处列出的说明进行操作。它第一次工作，但从那以后，当我运行我的应用程序时，我没有收到“已启动配置文件的应用程序”消息。然后，当我单击“拍摄快照”按钮时，我收到以下信息：
“拍摄快照...失败：远程服务器返回错误：(404) 未找到。”
为什么找不到我的应用程序？
I'm trying to use EQATEC Profiler to profile my ASP.Net app. I followed the instructions listed here. It worked the first time, but every since then, when I run my app, I don't get a "Profiled app started" message. Then when I click on the "Take snapshot" button, I get the following:
"Taking snapshot ...failed: The remote server returned an error: (404) Not Found."
Why can't it find my app?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
如果分析的应用程序遇到错误，它会将这些错误记录到 profiler.log 文件中。默认情况下，您将在 C:\Windows\Temp\EQATECProfilerLogs 中找到它。尝试看看它是否包含一些线索。您还可以尝试在应用程序选项中启用“完整日志记录”，这至少会向日志输出一些内容。
当与分析器对话时，分析的应用程序实际上是“服务器”；是分析器连接到应用程序，而不是相反。在您的情况下，旧应用程序似乎已停止侦听（否则探查器的连接尝试将仅由旧应用程序提供服务），但新应用程序尚未（不能？）开始侦听。
但这看起来很奇怪，所以我最好的建议是检查日志文件。例如，它将显示应用程序是否无法启动其控制服务器，如果是，为什么不启动。
If a profiled app encounters errors it will log these to the profiler.log file. By default you will find this in C:\Windows\Temp\EQATECProfilerLogs. Try to see if it holds some clues. You can also try to enable "Full logging" in the app options, which will at least output something to the log.
A profiled app is actually the "server" when talking to the profiler; it is the profiler that connects to the app, not the other way around. In your case it seems that the old app has stopped listening (otherwise the profiler's attempt to connect would simply be served by the old app), but the new app has not (could not?) started listening.
It seems strange, though, so my best suggestion is to examine the log-file. It will e.g. show if the app could not start its control-server and if so, why not.
1) 尝试重建（在 Equatec 中）您的应用程序。确保在构建时在应用程序选项中启用“启用运行时控制”。
1a) 尝试更改用于运行时控制的端口。
2) 通过 Equatec 运行您的应用程序
3）检查您是否有任何有趣的防火墙设置或类似内容。某些防火墙将 Equatec 通信视为要阻止的流量。
4。如果一切都失败了，只需正常关闭您的应用程序即可。即使拍摄快照失败，应用程序关闭后您仍然可以看到配置文件。
1) Try rebuilding (in Equatec) your application. Make sure "enable runtime control" is enabled in the application options when you build.
1a) Try changing the port being used for runtime control.
2) Run your application through Equatec
3) Check if you have anything funny for firewall settings or similar. Some firewalls treat Equatec communication as traffic to be blocked.
4. If all else fails, just close your application normally. Even if taking snapshots fails, you can still see the profile once your application is closed.
我想我应该提供这方面的更新。下载最新版本后，该错误得到解决。
Guess I should provide an update on this. The error was resolved once I downloaded the latest version.