You don't have to use RDP, simply by turning off custom error in Web.Config will do. But make sure you are adding that in the root Web.Config, that will do the trick.
Just be aware that there are multiple web.configs in a typical project.. make sure you are adding this in the root web.config (where your Global.asax is) and NOT in Views folder.
发布评论
评论(2)
对于 500 个错误,一种好方法是打开诊断并查看日志 - 应用程序事件日志和失败的请求日志可能会有所帮助。这是关于此的一篇文章 - http://oakleafblog .blogspot.com/2010/11/adding-trace-event-counter-and-error.html
正如 Igorek 所说,您还可以使用 RDP(远程桌面)来登录并检查应用程序 - 这是关于此的一篇很好的博客文章 - https://blogs.msdn.com/b/jimoneil/archive/2011/04/11/500-and-other-errors-in-azure-deployments.aspx
我的猜测是您可能缺少已部署包中的一个或多个程序集
For 500 errors, one good way is to turn diagnostics on and to look at the logs - both the application event logs and the failed request logs might help. Here's one post about this - http://oakleafblog.blogspot.com/2010/11/adding-trace-event-counter-and-error.html
As Igorek has said, you can also use RDP (remote desktop) to log in and to check the app - here's a good blog post about this - https://blogs.msdn.com/b/jimoneil/archive/2011/04/11/500-and-other-errors-in-azure-deployments.aspx
My guess is that you might be missing one or more Assemblies from the deployed package
您不必使用 RDP,只需关闭 Web.Config 中的自定义错误即可。但请确保将其添加到根 Web.Config 中,这样就可以解决问题。
这是我的一个例子:
请注意,典型项目中有多个 web.config。确保您将其添加到根
web.config
中(您的Global.config 所在的位置)。 asax
是),而不是在Views
文件夹中。You don't have to use RDP, simply by turning off custom error in Web.Config will do. But make sure you are adding that in the root Web.Config, that will do the trick.
Here is an example of mine:
Just be aware that there are multiple web.configs in a typical project.. make sure you are adding this in the root
web.config
(where yourGlobal.asax
is) and NOT inViews
folder.