This issue took me sometime to fix it.
Situation
On a working CRM 3.0 implementation and if you install Sharepoint Services 2.0 on top of it then, SQL Reporting (SRS) would stop working. If you uninstall the sharepoint everything works again.
Problem
The problem is when you configure the virtual directories, the Reporting Services Configuration tool adds them to the SharePoint list of exclusions. Note that a Report Server application pool is created by default for the Reporting Services virtual directories.
One more possibility is the port number used for SQL Reporting is taken over by Sharepoint. To know more in detail about this, read blog entry http://gustafwesterlund.blogspot.com/2007/04/messing-up-sql-rs.html by Gustaf Westerlund.
Solution
Solution provided by Gustaf didn’t worked in my case. After digging into Microsoft MSDN site. I got the solution:
Using a dedicated application pool can help avoid conflict with existing Web applications.
Read Microsoft link for more info: http://msdn2.microsoft.com/en-us/library/ms159697.aspx
If you install SharePoint Services after Reporting Services is already installed and configured, your Reporting Services installation will be unusable until you perform the following steps:
1. Start the Reporting Services Configuration tool.
STSADM.EXE -o addpath -url http://localhost/ReportServer -type exclusion
and
STSADM.EXE -o addpath -url http://localhost/Reports -type exclusion
By default, the Stsadm.exe file is located in C:\Program Files\Common Files\Microsoft Shared\Web server extensions\60\bin
WOW!! Sharepoint and SQL Reporting both works. Now on to step 2 (check out if you need it).
2. Configure the Report Server virtual directories.
Check out this link to configure the directories: http://msdn2.microsoft.com/en-us/library/ms155921.aspx
Enjoy sharepoint and reporting.
Piyush
July 31, 2007 at 2:28 pm
[...] Thanks Piyush. [...]