Hello! When we run the reports on the
development environment from an ASP.NET project, the report works fine. Once the .NET project is copied over to the production
server, we get:
Server Error in '/' 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>
The Developer software has been installed on the production server as well.
Bubberz
Member
488 Points
198 Posts
Crystal Reports XI production server error: Server Error in '/' Application
May 15, 2006 03:04 PM|LINK
Server Error in '/' 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>
The Developer software has been installed on the production server as well.
Thanks!