Problem with CRM 4.0 + Reporting Services RRS feed

  • Question

  • Hi,


    we've got a problem with using CRM-Reports with MS CRM 4.0. The scenario:

    - A CRM Server (let's call it CRMSERVER with CRM 4.0 + CRM 4.0 Email Router on a Windows Server 2003 R2 Ent. SP2 x86)

    - A DB+Reporting Services+Mail Server (let's call it SQLSERVER with SQL Server 2005 SP2 Ent. + 9.0.3159 Patch, Exchange 2007 SP1 Ent. + CRM 4.0 Reporting Services Dataconnector on a Windows Server 2003 R2 Ent. SP2 x64)


    Everything is working fine except reporting. What happens is that on every report that I'm trying to create on CRMSERVER (via web-interface from a workstation) in the eventlog appears the following:


    Ereignistyp: Fehler
    Ereignisquelle: MSCRMReporting
    Ereigniskategorie: Keine
    Ereigniskennung: 19968
    Datum:  09.04.2008
    Zeit:  16:33:22
    Benutzer:  Nicht zutreffend
    Computer: CRMSERVER

    Web service request ListExtensions to Report Server
    http://SQLSERVER/ReportServer/ReportService2005.asmx failed. Error: Fehler bei der Anforderung mit HTTP-Status 401: Unauthorized.

    Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter http://go.microsoft.com/fwlink/events.asp.

    and a bit later the following


    Ereignistyp: Warnung
    Ereignisquelle: ASP.NET 2.0.50727.0
    Ereigniskategorie: Webereignis
    Ereigniskennung: 1309
    Datum:  09.04.2008
    Zeit:  16:33:22
    Benutzer:  Nicht zutreffend
    Computer: CRMSERVER
    Ereigniscode: 3005
    Ereignismeldung: Es ist eine unbehandelte Ausnahme aufgetreten.
    Ereigniszeit: 09.04.2008 16:33:22
    Ereigniszeit (UTC): 09.04.2008 14:33:22
    Ereignis-ID: 3a1404b886bb4897ad6f97114151d704
    Ereignissequenz: 23
    Vorkommen: 1
    Ereignisdetailcode: 0
        Anwendungsdomäne: /LM/W3SVC/1/ROOT-1-128522251694660581
        Vertrauensebene: Full
        Virtueller Anwendungspfad: /
        Anwendungspfad: c:\inetpub\wwwroot\
        Computername: CRMSERVER
        Prozess-ID: 2912
        Prozessname: w3wp.exe
        Ausnahmetyp: WebException
        Ausnahmemeldung: Fehler bei der Anforderung mit HTTP-Status 401: Unauthorized.
        Anforderungspfad: /ORG/CRMReports/rsviewer/reportviewer.aspx
        Benutzerhostadresse: xxx.xxx.xxx.xxx 
        Benutzer: DOMAIN\User 
        Ist authentifiziert: True
        Authentifizierungstyp: Negotiate
        Threadkontoname: NT-AUTORITÄT\NETZWERKDIENST
        Thread-ID: 1
        Threadkontoname: NT-AUTORITÄT\NETZWERKDIENST
        Identitätswechsel für: False
        Stapelüberwachung:    bei System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
       bei System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
       bei Microsoft.Crm.ReportingServices2005.ReportingService2005.ListExtensions(ExtensionTypeEnum ExtensionType)
       bei Microsoft.Crm.Reporting.ReportServer.IsDataExtensionInstalled(String extensionName)
    Details des benutzerdefinierten Ereignisses:

    Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter http://go.microsoft.com/fwlink/events.asp.


    On the SQLSERVER I've looked into the folder \Windows\system32\LogFiles\W3SVC1 and so I see


    2008-04-09 14:33:22 W3SVC1 xxx.xxx.xxx.xxx POST /ReportServer/ReportService2005.asmx - 80 - xxx.xxx.xxx.xxx Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.1433) 401 2 2148074254
    2008-04-09 14:33:22 W3SVC1 xxx.xxx.xxx.xxx POST /ReportServer/ReportService2005.asmx - 80 DOMAIN\CRMSERVER$ xxx.xxx.xxx.xxx Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.1433) 401 5 0

    So I've tried to add DOMAIN\CRMSERVER$ with the Content-Manager and System-Administrator rights on the reporting services, but without any success.


    How is authentication in CRM working? Please help!




    Wednesday, April 9, 2008 2:47 PM


All replies


    Hi Imran,


    thanks for the info. I've not been able to solve the problem with the DiagTool. By searching in the support-db I've also followed the path of Kerberos-delegation-sign-in etc. but without any success. But now I've seen another problem:

    After restarting the IIS on SQLSERVER I get an ASP.NET access error on the first try of creating a report:


    Ereignistyp: Informationen
    ASP.NET 2.0.50727.0
    Ereigniskategorie: Webereignis
    Ereigniskennung: 1314
    Datum:  10.04.2008
    Zeit:  11:56:02
    Benutzer:  Nicht zutreffend
    Computer: SQLSERVER
    Ereigniscode: 4011
    Ereignismeldung: Es ist eine unbehandelte Zugriffsausnahme aufgetreten.
    Ereigniszeit: 10.04.2008 11:56:02
    Ereigniszeit (UTC): 10.04.2008 09:56:02
    Ereignis-ID: fe12d4fb487f47daafe72ba7c4dfa0af
    Ereignissequenz: 2
    Vorkommen: 1
    Ereignisdetailcode: 0
        Anwendungsdomäne: /LM/W3SVC/1/Root/ReportServer-1-128522949553162870
        Vertrauensebene: RosettaSrv
        Virtueller Anwendungspfad: /ReportServer
        Anwendungspfad: D:\Programme\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\
        Computername: SQLSERVER
        Prozess-ID: 932
        Prozessname: w3wp.exe
        Anforderungspfad: /ReportServer/ReportService2005.asmx
        Benutzerhostadresse: xxx.xxx.xxx.xxx (IP of CRMSERVER) 
        Ist authentifiziert: False
        Threadkontoname: NT-AUTORITÄT\NETZWERKDIENST
    Details des benutzerdefinierten Ereignisses:

    Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter http://go.microsoft.com/fwlink/events.asp.

    With ASP.NET event-id 4011 I've found some articles describing an ASP.NET 2.0 bug from mid 2007, but I've already .NET 2.0 SP1 running. So has anybody an idea?


    Thanks in advance,


    Thursday, April 10, 2008 10:15 AM
  • see my blog post for kerbose settings , its updated document.







    Thursday, April 10, 2008 1:13 PM
  • Hi,


    Enabling the kerberos delegation is not the right solution. If you do this, you even don't need to install the SRS data connector :-)


    I have had the same problem. Maybe you also have installed the CRM database on a named instance of SQL server instead of the default instance and the reporting services db is also on this named instance.


    This microsoft kb describe this problematic http://support.microsoft.com/kb/947060/en-us and the solution which consist of installing SRS data connector via command line and config file to specify the named instance of SQL server reporting services


    Hope it can help others


    Tuesday, September 16, 2008 7:21 AM
  • Klaus - I have exactly the same issue, includinfg the second message after we redeplyed an CRM database to a new server separte from the SQL default instance which houses teh SRS and a separate instance which houses the CRM databases. Reports run fine on the CRM server but everywhere else we get the same errors you are experiencinfg.


    How did you fix the problems?




    Saturday, September 20, 2008 3:59 PM

    I've got the same issue too. See http://groups.google.dk/group/microsoft.public.crm.developer/browse_thread/thread/e3f5cda26e7bbb79/d86af33be0779cfc?hl=da&lnk=gst&q=connector#d86af33be0779cfc


    I know it can be solved by enabling kerberos authentication, but I would rather solve it by installing the SRS Connector. Any help will be appreciated.



    Sunday, September 21, 2008 9:06 PM
  • Hi Imran, I viewed webpage http://microsoftcrm3.blogspot.com/2008/02/kerberos-ms-crm.html ,

    Topic: Kerberos MS CRM, Date: Wednesday, February 27, 2008.

    Viewing the document: rssetuptfd_v2.docx, I noticed I am using -

    Configuration 4: Separate Servers (Reporting Services, Microsoft SQL Server, and Microsoft Dynamics CRM on separate servers). For Data Source I enabled - Prompted Credentials, Use as Windows credentials when connecting to the data source.

    When users run SQL Report from SSRS report manager, they are prompted to enter username and password for every report. They are only able to view the data or info from the CRM Business Unit that they belong to in CRM, so crm security is working ok for SQL Reports (SQL reports - inhouse custom developed SQL reports - not CRM reports). Although it works as expected, I would like to implement Windows Authentication since it would allow users to run SQL reports without having to enter their domain logon credentials every time. I know kerberos might be the fix as your document (rssetptfd_v2.docx) explains, but has anyone successfully implemented it with Configuration 4: Separate Servers.

    Saturday, May 28, 2011 12:46 PM