Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Request Failed with HTTP status 403 - Organizational settings

848 views
Skip to first unread message

S Graves

unread,
Aug 21, 2007, 11:14:03 AM8/21/07
to
When I'm on the server as admin and I go into settings>Organizational
settings>System Settings, I get the error and stack trace (at least the part
I can get to) below:

Server Error in '/' application.
The request failed to load with HTTP status 403: Forbidden

Description: An unhandeled exception occurred during the execution of the
current web request. Please review the stack trace for more information...

Exception Details: System.Net.WebException: The request failed with HTTP
status 403: Forbidden.

Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location exception can be
identified using the exception stack trace below.

Stack Trace:
[Web Exception: The request failed with HTTp status 403: Forbidden.]
System.web.services.protocols.SoapHttpClientProtocol.ReadRespose
(SoapClientMessage message, WebResponse response, StreamResponse response.
Boolean asyn...
System.web.services.protocols.SoapHttpClientProtocol.Invoke (String
methodName, Object[] parameters) +218
Microsoft.Crm.ReportingServices.ReportingService.ListChildren (StringItem,
Boolean Recursive) +80
Microsoft.Crm.Web.Tools.SystemSettings.SystemSettingsPage.ConfigureCategoryList () +329
Microsoft.Crm.Web.Tools.SystemSettings.SystemSettingsPage.ConfigurePage ()
+7718
Microsoft.Crm.Application.Controls.AppPage.OnPreRender (Event Args e) +20
System.Web.UI.Control.PreRenderRecursiveInternal () +62
System.Web.UI.Page.ProcessRequestMain () +1499

I've double checked the IIS settings and are all running on ASP 1.1 and not
2.0.
We are running Windows Server 2003 and SQL 2005.
I was able to get into Organizational Settings at one time and I'm not sure
exactly when/what caused the change.

Has anyone else seen this error?
-Sandy

Paal

unread,
Sep 14, 2007, 4:16:00 AM9/14/07
to
Hi,

Yes I have the same problem. Can't say when it occurred but get the exact
same error saying "The request failed with HTTP status 403: Forbidden". I
think it's some security settings who are wrong in the IIS. I will look into
it further and if I find a solution i'll post it here.

Cheers
Paal

Paal

unread,
Sep 14, 2007, 7:36:03 AM9/14/07
to
I just want to add that I now have run a trace using the crm tools and i've
found the following in the log:

[2007-08-30 14:06:51.734] Process:w3wp |Thread:0236 |Category: Unmanaged.Sql
|User: PlatformUser |Level: Verbose |
COLEDataAccess::ExecuteParameterizedQuery File:
c:\bt\876\src\platform\include\omcommon\dataaccess.inl Line: 820
>!! select systemuser.OrganizationId as 'organizationid',systemuser.OrganizationIdName as 'organizationidname',systemuser.OrganizationIdDsc as 'organizationiddsc' from SystemUser as systemuser where systemuser.DeletionStateCode in (0) and (systemuser.SystemUserId = ?)!!{5DE59A1F-6E09-421D-AD71-E83628CD47DE}!!
[2007-08-30 14:06:51.750] Process:w3wp |Thread:0236 |Category:
Unmanaged.Platform |User: PlatformUser |Level: Error |
InternalCrmSetErrorInfo File: c:\bt\876\src\platform\include\util\icrmerror.h
Line: 362

There are more errors also, but as a start anyone have a clue how to solve
this? I can also add that I get a error when I try this link:
http://<servername>/Reports "The underlying connection was closed: Unable to
connect to the remote server."

Anyone have a clue?

Paal

unread,
Sep 14, 2007, 9:20:04 AM9/14/07
to
I have now found a solution to the problem. The two problem I mention was
related and when one of the problem got solved I know see the other also
work. Ok, solution is this:

- Open IIS manager
- Right click ReportServer
- Click Configuration
- Under the Wildcard application maps there should be one listing. In my
case that was missing so..
- Click Insert and add the following path and verify that the file exists:
c:\windows\microsoft.net\framework\v1.1.4322\aspnet_isapi.dll
- Restart webserver and try again. In my case it worked.

I hope this can help other who might get the same problem.

Cheers
Paal

0 new messages