Reporting Services and Sharepoint

In case you missed it in the setup Help file (I did) and you installed SQL Server Reporting Services on a virtual directory that's under Windows Sharepoint Services - there are some manual things to adjust for it to work:

1) Make sure your Default Web Site is up and running. Mine was Stopped (since it's the SPS site and I wasn't using it) and I got rather vague “Your IIS isn't configured properly“ messages during setup, which proceeded to install only the development components on my computer and not the ReportServer.

2) As the setup will conveniently tell us, we need to manually activate the services after installation. Piece of cake. Just run this (one line):
rsactivate.exe c:\program files\microsoft sql server\mssql\reporting services\reportingserver\RSReportServer.config

3) If you're getting very minimal “404 Not Found” errors when trying to access the /Reports or /ReportServer virtual directories, it's because Sharepoint, by default, blocks access to all paths it doesn't know.
So just run this to tell Sharepoint to exclude these VDirs from the paths it cares about:
STSADM.EXE -o addpath -url http://localhost/ReportServer -type exclusion
STSADM.EXE -o addpath -url
http://localhost/Reports -type exclusion

4) Right, now we're not getting 404's, we're just getting a nicer interface telling us that Reporting Services requires Session State to be enabled. At this point we'll probably scratch our heads in puzzlement, since it most definitely IS enabled in the IIS Manager, both for the Reports/ReportServer vdirs and for the root.
Again, the problem lies with the Sharepoint. The sharepoint root's web.config file contains an <HttpModules> tag containing, by default, a commented-out SessionState module. We'll re-enable that and also look for the <pages> tag a bit after than and set “enableSessionState” to “true”.

That's it, so far. All credit to http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/htm/gs_installingrs_v1_9fdy.asp

4 Comments

Comments have been disabled for this content.