Do not use the Report Server add-in for SharePoint. There is no need to use it, it has only given me a headache. All you need to do when you are running the Reporting Services Configuration Tool is to add the Reports and ReportServer Virtual Directories to the SharePoint site. I know, this seems too simple right, well it works. Please keep in mind that i am using SSL and i have not tried this otherwise. When I first started research this I came across the Reporting Services Add-In for SharePoint tutorial from here. It says to setup the Report Server on the default web site in IIS under a different port. Well this didn’t work for me so I read up and others told me to create a new sub site named something like reports. So I made reports.ourwebsite.com and SharePoint was on portal.ourwebsite.com. So now I install the add-in and I think everything is good. Then we moved our web server to a different box that was not a domain controller. Well this made problems because we had the site setup for windows authentication. While on the domain controller the website only asked for the username and password, now that IIS is on a separate box it asks for the domain\username and password. That won’t work because our customers will not know the domain name. So I moved us to Basic Authentication. The issue with this is the Report Server Add-In for SharePoint will not work with Basic Authentication. Now I am stuck having to put the Report Server back to Native mode and have our customers click a link from our portal to reports. The issue now is our customers now need to double authenticate, first to portal then to reports! Then I was recommended from a co-worker to try and just add the Report Server application pools to the SharePoint site. So I tried it even though all the documentation I’ve read seemed to completely veer away from that idea. It worked!! I added my link in the page viewer web part and it is flawless. I am able to use basic authentication and have the report integrated into my SharePoint webpage. I am kind of upset because the Microsoft website steered me on the wrong path. If you look a couple of posts down you will see a picture of the integrated Report Server in SharePoint, my new setup looks exactly the same as this. If you have any questions at all please leave me a comment and I will defiantly try and help.
- Kevin C -
I’ve had a couple requests to see how the reporting service add-in for SharePoint looks like on my site. My purpose of merging the two is to allow our customers to view there current and past bug reports they had submitted to our company. I built a report to show the status of there ticket and all the notes that have been recorded on the ticket. The database that the report is quarrying is SQL and the bug tracking system we are using is TestTrack Pro. We had to convert the TestTrack Pro database to SQL from its Native database to allow for reporting. The reporting service add-in allows you to upload a report to any document library. The permissions for that report are managed by whatever permissions you define in SharePoint. Please note that the user must have sufficient permissions in the SQL database you are quarrying to allow for report viewing. The add-in also comes with a report web part which allows you to define perimeters. In my case i used the company name to allow the one report with all of our customers to be narrowed down to the specific company for report viewing on there site specific web page. If you have any questions please leave a comment.
- Kevin C -
I installed reporting services on a website when it was not setup with SSL to start. We had the security certificate so I setup report services for SSL but once I did this report manager stopped working. The error i received was this: The request failed with HTTP status 401: Unauthorized. I could still hit report server and view reports but i could not reach reports (Report Manager). After some research I found a Microsoft fix. It will require adding an entry into the registry. Well worth the time. It will not hurt anything (not that i know of anyway) to add the value. Once added I was able to get to the report manager on SSL.
http://support.microsoft.com/default.aspx?scid=kb;en-us;896861
This is the method that fixed my issue.
Follow these steps:
1. Click Start, click Run, type regedit, and then click OK.
2. In Registry Editor, locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. Right-click Lsa, point to New, and then click DWORD Value.
4. Type DisableLoopbackCheck, and then press ENTER.
5. Right-click DisableLoopbackCheck, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. Quit Registry Editor, and then restart your computer or just restart IIS
- Kevin C -
My latest project that i will be working on is to be installing and configuring SQL Reporting Services 2005 Standard Edition. I will then be making reports with already created SQL database files. It has so far taken me a week to install and configure reporting services. I originally started with trying to get reporting services to work with Sharepoint (we have Sharepoint 3.0 and MOSS 2005 installed on our 2003 Server). After deciding to try and use a database in Native mode instead of Integrated with Sharepoint I found that reporting services it self was messed up it was nothing to do with Sharepoint. Basically when i went to the reports section (http://(server-name)/reports) it would give me an error. The strange thing was that the reportserver section (http://(server-name)/reportserver) did seem to work. I uninstalled reporting services by going to “Add and Remove programs” and clicking “Change” on “SQL Server 2005.” I then picked the instance of SQL i was using and clicked “Next.” I then had the option to choose to uninstall “Reporting Services.”
When re-installing Reporting Services the “default” install instance was grayed out with “details” as an option to see why. The details said “The prerequisite check failed for a default report server installation: First time install, the SQL instance is either not selected or is not a local install.” I continued with the install and it finished successfully. I then went to Windows Updates and found that the SQL SP2 was needing to be downloaded and installed. This seemed odd to me since I had already installed SQL SP2 a week before hand. I guess since i installed Reporting Services and it had not been patched with SQL SP2 it needed to be updated (I had thought there would be a patch I wouldn’t have thought that i needed to install the whole thing again). After installing the SQL SP2 I attempted to run SQL Reporting Service Configuration Tool since there was no report from Microsoft that i needed to reboot. I got a really nasty error. So now I am thinking the program is corrupt, AGAIN! Ok so I guess I will restart the server and see if it helps or I may just need to try again (this sucks since this is a production machine and I have to send out site wide email about rebooting before doing so). After the reboot I re-opened the config tool and ~by golly~ it worked!! Thank the Lord! 
- Kevin C -
Recent Comments