| T O P I C R E V I E W |
| Keith Henkel |
Posted - 07/25/2005 : 10:29:30
I'm getting this message when I try to access the main login page. This is a first time install on WS2003.
Debugging is not supported under current trust level settings.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.HttpException: Debugging is not supported under current trust level settings.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[HttpException (0x80004005): Debugging is not supported under current trust level settings.]
System.Web.UI.TemplateParser.HandlePostParse() +182
System.Web.UI.TemplateParser.Parse() +200
System.Web.UI.TemplateParser.GetParserCacheItemThroughCompilation() +74
System.Web.UI.TemplateParser.GetParserCacheItemInternal(Boolean fCreateIfNotFound) +189
System.Web.UI.TemplateParser.GetParserCacheItemWithNewConfigPath() +125
System.Web.UI.TemplateParser.GetParserCacheItem() +87
System.Web.UI.ApplicationFileParser.GetCompiledApplicationType(String inputFile, HttpContext context, ApplicationFileParser& parser) +171
System.Web.HttpApplicationFactory.CompileApplication(HttpContext context) +43
System.Web.HttpApplicationFactory.Init(HttpContext context) +485
System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context) +170
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +414
|
| 7 L A T E S T R E P L I E S (Newest First) |
| admin |
Posted - 01/04/2006 : 23:43:06
chuckdobbs,
The server would not say what the problem was. It would just say "unhandled exception was generated during the execution".
You can normally see what the real problem is by changing the
Web.config to this:
<customErrors mode="Off" /> |
| chuckdobbs |
Posted - 12/29/2005 : 17:18:54
What was the resolution of your problem? I'm seeing the same. It appears to be related to the web.config file in the wwwroot/ dir. ReportPortal doesn't want one there but SPS does. ??? Did you figure this out?
Thanks
cd |
| admin |
Posted - 08/04/2005 : 22:59:39
Did you check if there is an entry in the event log? |
| Keith Henkel |
Posted - 07/31/2005 : 08:24:57
quote:
Originally posted by igorkrupitsky
Please try this:
http://wss.collutions.com/Lists/FAQ/DispForm.aspx?ID=139
OK. I tried that. I got another error which pointed me to another post on this forum for the session state problem. Here's what I've added to web.cofig in \reportportal
<trust level="Full" originUrl="" />
<pages enableSessionState="true" enableViewState="true"
Now I'm getting this error:
Server Error in '/ReportPortal' 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, 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 "RemoteOnly". To enable the details to be viewable on remote machines, please 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" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
|
| admin |
Posted - 07/27/2005 : 22:48:00
Please try this:
http://wss.collutions.com/Lists/FAQ/DispForm.aspx?ID=139
|
| Keith Henkel |
Posted - 07/26/2005 : 06:46:28
quote:
Originally posted by igorkrupitsky
Please try steps needed for Windows Server 2003 as described here:
http://www.reportportal.com/FAQ.asp
OK. I enabled parent paths, isapi, and asp. I'm still getting the same error. SharePoint Server is also installed. Thanks for your help. |
| admin |
Posted - 07/25/2005 : 21:06:01
Please try steps needed for Windows Server 2003 as described here:
http://www.reportportal.com/FAQ.asp |
Report Portal
