Hi, App1 is calling App2 and within the server, I have no problem to call 2nd app and then show the page. But when doing the same in the client machine, I encounter this. Why?
Server Error in '/App2' 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 remotely (for security reasons). It could, however, be viewed by browsers running
on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please 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 "Off".
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.
Do it as it says...you need to make customErrors to OFF, so that we all can see the original exception and there by provide solution....with the present information at hand, we cannot troubleshoot this issue...
wmec
Contributor
6224 Points
3221 Posts
Problem to call another app
Feb 05, 2013 06:33 AM|LINK
Hi,
App1 is calling App2 and within the server, I have no problem to call 2nd app and then show the page. But when doing the same in the client machine, I encounter this. Why?
Server Error in '/App2' 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 remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please 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 "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</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="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
HuaMin Chen
ramiramilu
All-Star
95463 Points
14106 Posts
Re: Problem to call another app
Feb 05, 2013 06:36 AM|LINK
Do it as it says...you need to make customErrors to OFF, so that we all can see the original exception and there by provide solution....with the present information at hand, we cannot troubleshoot this issue...
thanks,
JumpStart
wmec
Contributor
6224 Points
3221 Posts
Re: Problem to call another app
Feb 05, 2013 07:30 AM|LINK
Thanks. The relevant project/app has been deployed to
C:\inetpub
Is it to do the change to this file
C:\inetpub\web.config
in the server?
HuaMin Chen
wmec
Contributor
6224 Points
3221 Posts
Re: Problem to call another app
Feb 06, 2013 02:03 AM|LINK
Dear all,
Any help to this?
HuaMin Chen