求助:asp程序在godaddy win主机的错误解决方法?

xiaofp80

求助:asp程序在godaddy win主机的错误解决方法?
上传国内主机可用的asp程序到godaddy win主机,显示500错误,通过创建web.config文件,就显示下面错误,请版主帮助看一下是什么问题?

An error occurred on the server when processing the URL. Please contact the system administrator.
If you are the system administrator please click here to find out more about this error.

add.c

错误提示要求你联系GoDaddy官方

xiaofp80

备注:
点击:here 就进去这个网址:http://learn.iis.net/page.aspx/559/running-classic-asp-applications-on-iis-70-and-iis-75/

tnnd

把你的浏览器改为显示全部信息。

好像贴不了图啊

xiaofp80

/?
跟这个有关吗?

tnnd

你现在看不到详细的错误信息，这样就可以看到了。

tnnd

知道哪里出问题了，才能解决问题嘛，呵呵。

xiaofp80

就显示上面的错误信息啊!!!
An error occurred on the server when processing the URL. Please contact the system administrator.
If you are the system administrator please click here to find out more about this error.

网址:http://www.gdlianfa.com/gk863

add.c

联系官方检查哦
联系GoDaddy客服发ticket教程

xiaofp80

看不懂,也不知道怎么解决???下面是联系官方后得到的回复:

Our support staff has responded to your request, details of which are described below:

Discussion Notes
Support Staff Response
Dear feipeng xiao,

Thank you for contacting Online Support.

It sounds like you may need to temporarily enable detailed error reporting in order to troubleshoot this issue.


By default, our Windows hosting servers display a generic error when any .NET application generates an exception. The error message resembles the following:



Server Error in '/mytestapp' Application.

Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed.

Details: To enable the details of this specific error message to be viewable on the local server machine, create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "RemoteOnly". To enable the details to be viewable on remote machines, set "mode" to "Off".
<!-- Web.Config Configuration File -->

<configuration>
  <system.web>
    <customErrors mode="RemoteOnly"/>
  </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->

<configuration>
  <system.web>
    <customErrors mode="On"default Redirect="mycustompage.htm"/>
  </system.web>
</configuration>



We have set the default behavior for the hosting server this way for security reasons. When displaying a custom error message, it is possible for a malicious user to obtain sensitive information from the message. This is why we recommend you use this feature sparingly and only when troubleshooting. Additionally, be sure to re-enable the generic error message once you are finished debugging any problem.



To view the detailed error messages remotely, modify the following tag in the web.config file in the root of your application folder. If the tag does not exist, you can add it within the <configuration> and <system.web> tags:



<customErrors mode="Off"/>


To specify a custom error page to display, instead of the more detailed error message, add the following tag:



<customErrors mode="On" defaultRedirect =”~/MyErrorPage.aspx”/>
where MyErrorPage.aspx is the name of your error page.






Mode Values:


There are several possible Mode values.





RemoteOnly:

Only users logged on to the console of the server can view the detailed error messages. Remote users will see the generic error page unless the defaultRedirect is defined, in which case the custom page is displayed.

On:

No detailed error messages are shown. The custom error page will be used if it was specified in the defaultRedirect.

Off:

Detailed error messages are shown for remote and local users. Use this value to set the value of mode.



The defaultRedirect value is used to specify the error page to use when a .NET error is encountered. This URL is relative to the location of your web.config file, or if a tilde is used, is relative to the root of your application (for example: ~/MyErrorPage.aspx).



Please let us know if we can help you in any other way.

Sincerely,
Stephen P.
Online Support Team