This is the Debug Info from DevErrors=On. The problem occurs when any user
(except when on server itself) accesses Reports or System Settings.
Any information on how to sort this much appreciated.
Server Error in '/' Application.
--------------------------------------------------------------------------------
The request failed with HTTP status 401: Unauthorized.
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.Net.WebException: The request failed with HTTP
status 401: Unauthorized.
Source Error:
The source code that generated this unhandled exception can only be shown
when compiled in debug mode. To enable this, please follow one of the below
steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the
error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>
Note that this second technique will cause all files within a given
application to be compiled in debug mode. The first technique will cause only
that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a
memory/performance overhead. You should make sure that an application has
debugging disabled before deploying into production scenario.
Stack Trace:
[WebException: The request failed with HTTP status 401: Unauthorized.]
System.Web.Services.Protocols.SoapHttpClientProtoc ol.ReadResponse(SoapClientMessage
message, WebResponse response, Stream responseStream, Boolean asyncCall) +1296
System.Web.Services.Protocols.SoapHttpClientProtoc ol.Invoke(String
methodName, Object[] parameters) +218
Microsoft.Crm.ReportingServices.ReportingService.L istChildren(String
Item, Boolean Recursive) +80
Microsoft.Crm.Application.Controls.ReportsGridData Provider.GetReports(Int32&
numReports) +738
Microsoft.Crm.Application.Controls.ReportsGridData Provider.Execute() +29
Microsoft.Crm.Application.Controls.AppGridUIProvid er.Render(HtmlTextWriter
output) +229
Microsoft.Crm.Application.Controls.ReportsGridUIPr ovider.Render(HtmlTextWriter output) +8
Microsoft.Crm.Application.Components.UI.DataGrid.R enderData(HtmlTextWriter
output) +531
Microsoft.Crm.Application.Components.UI.DataGrid.R enderInnerHtml(HtmlTextWriter output) +471
Microsoft.Crm.Application.Components.UI.DataGrid.R ender(HtmlTextWriter
output) +125
Microsoft.Crm.Application.Controls.AppGrid.Render( HtmlTextWriter writer)
+127
System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +243
_ASP.home_reports_aspx.__Render__control1(HtmlText Writer __output,
Control parameterContainer) +420
System.Web.UI.Control.RenderChildren(HtmlTextWrite r writer) +27
System.Web.UI.Control.Render(HtmlTextWriter writer) +7
System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +243
System.Web.UI.Page.ProcessRequestMain() +1926
Hi Eve
What makes you so certain it's not Kerberos?
We had all sorts of hassles setting up Reporting Services - from what you've
got I'd start looking at the following:
1) Has the CRM application pool user been set up to publish reports? If
it's not a user, then has the local machine been set up to publish reports?
2) Is Kerberos logging turned on? If so, is it reporting any errors in the
event log? If so, and the SPNs and delegation are set up correctly, then you
may want to check which user is appearing in the error messages. Even if
Kerberos is working correctly, the Kerberos logging may help you to track
down the source of the problem.
3) What are your application pool users for CRM and for RS? if they're not
the local machine account, have the SPNs been set up?
4) Does reporting services work on its own? i.e. if you go directly to the
RS URL, can you run the reports? Or do you get 401 errors there too? If you
do, start checking the IIS settings on the RS site. I'm assuming at this
point that Reporting Services has been initialised and is running properly.
That's not much help, I expect; there are a lot of things that can go wrong
with Reporting Services. The general rule we found when setting up Reporting
Services for CRM was "don't make any mistakes". Changing various aspects of
the setup meant we had a lot of re-fixing to do.
Regards,
Ieuan
