Issue with viewing report in SharePoint using Windows Authentication
I created a very simple report displaying some fields in my SP list. I can preview it and everything looks fine. I deployed the report to a document library in my site, then added the report viewer web part onto a page and pointed it at the report. This is what I get: An error has occurred during report processing. This data source is configured to use Windows integrated security. Windows integrated security is either disabled for this report server or your report server is using Trusted Account mode. After some searching I find that I need to adjust some settings in Central Admin. I go in and change the authentication mode from Trusted Account to Windows Authentication. I go back and refresh my page and BAM. The whole page comes up displaying "An unexpected error has occurred." If I change it back to Trusted Account the page reverts back to the previous error. Also, not sure if this is related as I'm new at this. If I just click on the report sitting in the document library I get an Unknown Error message from SP. I'm not sure if I should be able to open it directly or not. This is on MOSS 2007 using SQL 2005.
July 23rd, 2009 10:15pm

Hi Mikey52, The Reporting Services will be configured as Kerberos mode after you installed Reporting Services for SharePoint add-in. In the meantime, if you have configured the Kerberos in your environment, you will receive the error This data source is configured to use Windows integrated security. Windows integrated security is either disabled for this report server or your report server is using Trusted Account mode. To solve the issue, please configure Kerberos correctly, we had to do multiple things: 1. If there were a few duplicate SPNs on the network and we used DelegConfig to locate these. You can get "DelegConfig" from the following link: http://www.iis.net/downloads/default.aspx?tabid=34&g=6&i=1434 2. We then had to create SPNs for the SQL Server Service account and the SharePoint web servers. You can find more information on these SPNs in the following articles:a)http://support.microsoft.com/kb/319723/en-us b) http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/df979570-81f6-4586-83c6-676bb005b13e.mspx?mfr=true 3. We also had to change all of the SharePoint sites to use "Negotiate" instead of "NTLM" to do this follow these steps: a. Go to the following SharePoint menu: i. "Central Administration > Application Management" ii. Under the "Application Security" heading click "Authentication Providers"3 b. Click on the zone you wish to modify. c. Under the "IIS Authentication Settings" section select "Negotiate" instead of "NTLM". d. Click "Save" e. Repeat b-d for each zone you wish to change. If you have any more questions, please feel free to ask. Thanks, Jin ChenJin Chen - MSFT
Free Windows Admin Tool Kit Click here and download it now
July 28th, 2009 10:58am

I'm having this same issue where I'm unable to utilize Reporting Services "Windows Authentication" (run through Sharepoint). When I try, I get this error: An error has occurred during report processing. Cannot create a connection to data source 'reportdb'. For more information about this error navigate to the report server on the local server machine, or enable remote errors While the error is different than the original poster, what I'm gathering is that this can also be solved by having Kerberos properly configured in the environment. If that is true, my post is hoping that I can receive a little clearer direction on how to do that properly. The reports have no issues when run with Stored Credentials, or if I Prompt. Environment: Server A - Reporting Services 2005, Sharepoint (WSS3.0), and IIS v7.5: Windows 2008 R2 64-Bit Server B - SQL Server 2005 - Windows 2008 R2 64 Bit IIS appears to have Kerberos active. However the only other place I know to set this is in Sharepoint Central Admin. When I change the authentication from NTLM to Negotiate (Kerberos), I'm told that further configuration will be required if the Application Pool is not using 'Network Service'. I apply the change anyway, and nothing different happens in my environment. Everything still seems to work just the same. But the error remains. In fact, I am NOT using 'Network Service' for either the sharepoint or reporting services application pools. If I make that change, things stop working (can't even connect to Sharepoint). But I don't know what to do at this stage. I would appreciate any direction specific to my environment and my issue. Thanks Tim
January 11th, 2011 9:30am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics