Integrate WSS 3.0 and Reporting Services with Kerberos - Help Need
Hi,
For last 2 days, I'm struggling to integrate WSS 3.0 with SP1 with SQL Server 2005 Reporting Services with SP2 with Kerberose authentication.
And finally I'm stuck

At the moment I've got 2 issues, one is when "Set defaults" on Central Administration site, second is when I'm trying to browse the reporting server for report – using Report Viewer webpart configuration (when selecting "Report").
Before I will go futher with errors message, here is my configuration:
WSS 3.0 with SP1 and Reporting Services Add-in:
Computer: SharePoint02 | SharePoint02.led.local
Portal url: http://sharepoint02 | http://sharepoint02.led.local
Admin url: http://sharepointadmin02 | http://sharepointadmin02.led.local
Portal App Pool: LED\SPContentPool
Admin App Pool: LED\SPConfigAcct
SQL Server 2005 with SP2, Reporting Services with SP2, WSS 3.0 with SP1 Front End:
Computer: SharePointDB | SharePointDB.led.local
Front End Portal url: http://sharepointdb | http://sharepointdb.led.local
URL to reporting services: http://sharepointdb/SPSReportServer | http://sharepointdb.led.local/SPSReportServer
Front End App Pool: LED\SPContentPool
Reporting Services App Pool: LED\SPConfigAcct
Report Server Service Account: LED\SPConfigAcct
SQL Server Account: LED\SPConfigAcct
I know I should have separate account.
Service Principals (SPContentPool):
Registered ServicePrincipalNames for CN=SPContentPool,CN=Users,DC=LED,DC=LOCAL:
HTTP/sharepoint02
HTTP/sharepoint02.led.local
Service Principals (SPConfigAcct):
Registered ServicePrincipalNames for CN=SPConfigAcct,CN=Users,DC=LED,DC=LOCAL:
HTTP/sharepointdb
HTTP/sharepointdb.led.local
MSSQLSrv/sharepointdb.led.local:1433
HTTP/sharepointadmin02.led.local
HTTP/sharepointadmin02
Reporting add-in is activated, I'm able to specify the report server (http://sharepointdb.led.local/SPSReportServer) and to grant permission.
1) FIRST ISSUE
However when I'm trying to set the defaults for Reporting Services from Central administration I'm getting following error:
The target location you specified is not supported by the report server. A report definition (.rdl), report model (.smdl), resource, or shared data source (.rsds) file must be located within a library or a folder within it. ---> The target location you specified is not supported by the report server. A report definition (.rdl), report model (.smdl), resource, or shared data source (.rsds) file must be located within a library or a folder within it.
Reporting Server error message is:
w3wp!library!1!03/12/2008-12:15:23:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ContainerTypeNotSupportedException: The target location you specified is not supported by the report server. A report definition (.rdl), report model (.smdl), resource, or shared data source (.rsds) file must be located within a library or a folder within it., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.ContainerTypeNotSupportedException: The target location you specified is not supported by the report server. A report definition (.rdl), report model (.smdl), resource, or shared data source (.rsds) file must be located within a library or a folder within it.
w3wp!library!1!03/12/2008-12:15:39:: Call to GetDataSourceContentsAction(http://sharepoint02.led.local/lrs/Reports/SHAREPOINTDB.rsds).
w3wp!library!5!03/12/2008-12:15:49:: Call to GetDataSourceContentsAction(http://sharepoint02.led.local/lrs/Reports/SHAREPOINTDB.rsds).
w3wp!library!1!03/12/2008-12:15:52:: Call to GetDataSourceContentsAction(http://sharepoint02.led.local/lrs/Reports/SHAREPOINTDB.rsds).
w3wp!library!1!03/12/2008-12:15:55:: Call to GetDataSourceContentsAction(http://sharepoint02.led.local/lrs/Reports/SHAREPOINTDB.rsds).
w3wp!library!1!03/12/2008-12:16:07:: Call to GetDataSourceContentsAction(http://sharepoint02.led.local/lrs/Reports/SHAREPOINTDB.rsds).
w3wp!library!1!03/12/2008-12:16:59:: Call to GetDataSourceContentsAction(http://sharepoint02.led.local/lrs/Reports/SHAREPOINTDB.rsds).
w3wp!library!1!03/12/2008-12:17:11:: Call to GetPermissionsAction(http://sharepoint02.led.local/lrs/Reports/TestSharepoint.rdl).
This error message then repeats few times, usually always after:
w3wp!library!5!03/12/2008-11:18:16:: Call to GetSystemPropertiesAction().
2) SECOND ISSUE
When the I'm trying to add Report Viewer (I'm logged as Portal administrator) and then select the report from web part settings, I'm getting:
Server was unable to process request. ---> The request failed with HTTP status 401: Unauthorized.
When I'm looking at the Event log in SharePointDB I see Anonymous login:
Event Type: Success Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 540
Date: 12/03/2008
Time: 12:13:07
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SHAREPOINTDB
Description:
Successful Network Logon:
User Name:
Domain:
Logon ID: (0x0,0x12C0209E)
Logon Type: 3
Logon Process: NtLmSsp
Authentication Package: NTLM
Workstation Name: SHAREPOINT02
Logon GUID: -
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: 10.192.65.67
Source Port: 1705
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Is there any chance to solve these issues? What did I done wrong?
I would really appreciate any help!
Cheers,
Jakub G
Answers
Hi All,
The issue was caused by alternative address mappings on Central Administration Site. During install I have installed Admin site on sharepoint02:8888 port, but because of the SPN I have created the A record in DNS sharepointadmin02 pointing to sharepoint02. On Alt address mappings I have set default URL to sharepointadmin02, then I have added sharepointadmin02.led.local as internal URL, and I have deleted sharepoint02:8888.
In IIS I have added additional URL and port for Central Administration Site (so I had sharepoint02 on port 8888 and sharepointadmin02 (host header) on port 80).
This settings was causing the issue with Set Default operation on the Central Administration site. After I had added internal URL sharepoint02:8888 pointing to sharepointadmin02 in alternative address mappings, I’ve run into the problem described here:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3004729&SiteID=1&mode=1
But I could not find a solution for it. Even reinstalling Reporting services didn’t help. Despite SPN settings I have made sharepoint02:8888 the default URL and I have deleted all sharepointadmin02 urls from Central Administration Alternative Address Mappings site.
Then the Set Defaults start to work! In Kerberos mode! Strange(?) but maybe host head in IIS is doing the proper job
So if the Set Default start to work, I’ve go back to Alternative Address Mappings and I have added internal urls pointing to sharepoint02:8888 (sharepointadmin02, sharepointadmin02.led.local).This solve the issue with Set Defaults!
Anonymous login issue was quite stupid if I can say so. It occurred that IE when looking for the addresses like sharepointrs, sharepointdb and sharepoint02 didn’t release that the URL are in Local Intranet Zone! All I need to do was to add sites to trusted sites in Local Intranet Zone.
And suddenly whole solution start to work with Kerberos authentication!
Hope this will help someone, somewhere, sometime

Cheers,
Jakub G
All Replies
Hi All,
The issue was caused by alternative address mappings on Central Administration Site. During install I have installed Admin site on sharepoint02:8888 port, but because of the SPN I have created the A record in DNS sharepointadmin02 pointing to sharepoint02. On Alt address mappings I have set default URL to sharepointadmin02, then I have added sharepointadmin02.led.local as internal URL, and I have deleted sharepoint02:8888.
In IIS I have added additional URL and port for Central Administration Site (so I had sharepoint02 on port 8888 and sharepointadmin02 (host header) on port 80).
This settings was causing the issue with Set Default operation on the Central Administration site. After I had added internal URL sharepoint02:8888 pointing to sharepointadmin02 in alternative address mappings, I’ve run into the problem described here:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3004729&SiteID=1&mode=1
But I could not find a solution for it. Even reinstalling Reporting services didn’t help. Despite SPN settings I have made sharepoint02:8888 the default URL and I have deleted all sharepointadmin02 urls from Central Administration Alternative Address Mappings site.
Then the Set Defaults start to work! In Kerberos mode! Strange(?) but maybe host head in IIS is doing the proper job
So if the Set Default start to work, I’ve go back to Alternative Address Mappings and I have added internal urls pointing to sharepoint02:8888 (sharepointadmin02, sharepointadmin02.led.local).This solve the issue with Set Defaults!
Anonymous login issue was quite stupid if I can say so. It occurred that IE when looking for the addresses like sharepointrs, sharepointdb and sharepoint02 didn’t release that the URL are in Local Intranet Zone! All I need to do was to add sites to trusted sites in Local Intranet Zone.
And suddenly whole solution start to work with Kerberos authentication!
Hope this will help someone, somewhere, sometime

Cheers,
Jakub G


