Hi Teo,
I installed SP2 yesterday on my test box, with WSS 3.0 Installed, the installation went smoothly without any problem. Then I download the feature pack of RS on WSS 3.0. I then launch WSS central management site, go to applicatoin management, then Reporting Services.
Manage Integration Setting: Reporting service is at the same box as WSS, so I put the http://abc/reportserver, then I choose Window Authentication, no complain there;
Grant Database Access, I just use default instance since all SQL server components is the at the same box of WSS;
Ten I got the error on step 3: Set Server Default, here is the error message:
An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode.
Anything I miss?
Thanks
Dong
I follow the RS Configuration tool and create new reportserver database (ReportServerWSS) and choose Sharepoint integration mode, then I go to WSS central admin again, re-configure Manaage Integration Setting, Grant Database Access and Set Server Default, all goes well.
Then I drop the RS web part again, and it asks me to "You must first select a report to display in this Web Part. Do this by opening the tool pane and specifying the path and file name of the Reporting Services report that you would like to show. Alternatively, you can connect the Web Part to another Web Part on the page that provides a document path."
So I put http://abc/reports, then target folder, however it gave error saying "The item 'http://abc/reports' cannot be found. (rsItemNotFound)".
Also if I launch http://abc/reports/Pages/Folder.aspx here is the error I got:
"The operation is not supported on a report server that is configured to run in SharePoint integrated mode. (rsOperationNotSupportedSharePointMode) Get Online Help"
Does this mean I can no longer browser through http://abc/reports/Pages/Folder.aspx?
Don
h
I also notice at the RS Configuration Tool Report Manager Virtual Directory is grayed out, it says: Report Manager is not avaliable when using SP integration.
This is not good if I can only use WSS to browse my reports, I wonder how I can still be able to browse http://abc/reports, do I have to switch back to native mode?
Thanks Teo,
So just under "Database setup" of RS configuration and change database name to "ReportServer", and connect?
Also I am wondering where is the report explorer view, how I can diplay list of report ?
I just test the switch back to native mode without any problem, but I still could not display report list in WSS under sharepoint mode, anything I miss?
One side question, does WSS 3.0 still support OWC web part?
HI DZ001,
I am also facing the similar trouble in Integrating with Reporting service with Sharepoint
In Report server configuration wizard all the options configured and turn green except Report Manager Virtual Directory got disabled
i.e. its enabled for SharePoint Integration...
My problem is I am unable to see the Report Server Content Types in Sharepoint sites?
i.e If I Go to Document Library Settings and AddFrom Existing Content type but there
I am unable to see "Report Server Content Types".........
Note:I installed and configured SharePoint Extenstions for Reporting services
Or How can I deploy the existing/legacy Reports onto SharePoint Site after integration?
How to ensure that my integration is succeded?
How to run Report Builder from Sharepoint??
Advance Thnaks
Did you install the RS Add-in for WSS? What happens when you go to http://localhost/reportserver/?
I Installed the "SharePointRS.msi"(36mb) for RS add- in for WSS!
and I can see the newly created links for Reporting Service managent in central administration-->Application management
I configured all these links Under newly Created Reporting Services also
and when I call http://localhost:8080/reportserver/
I can see following screen
-------------------------------
Thursday, November 08, 2007 1:28 PM <dir> http://ibnjdevdt:100/sites/ShareCaseTracker Tuesday, November 13, 2007 7:21 AM <dir> http://ibnjdevdt:100/sites/TestTeamSite Thursday, November 08, 2007 1:05 PM <dir> http://ibnjdevdt Monday, November 12, 2007 12:21 PM <dir> http://ibnjdevdt/personal/administrator Thursday, November 08, 2007 1:03 PM <dir> http://ibnjdevdt/ssp/admin
Microsoft SQL Server Reporting Services Version 9.00.3042.00
-------------
but when I go and see for site content types I am uable to find Report server Content types
1) How can I Create New Reports In wss?
2) How can I deploy legacy reports on to WSS sites?
if you don't see the RS content types then there is something wrong. I remember struggling quite a bit with this one and MOSS 2007 because there is a security-related step in MOSS that you need to perform to get the types to show up. The RS steps don't tell you this and I don't recall what this step was exactly. But you shouldn't have this problem if you use WSS 3.0 only. Once you enable the RS content types:
1. As you would in navitve mode by using the Report Designer or Report Builder and publish to WSS.
2. You can deploy them one by one or deploy them from VS.NET.
tlachev: if you don't see the RS content types then there is something wrong. I remember struggling quite a bit with this one and MOSS 2007 because there is a security-related step in MOSS that you need to perform to get the types to show up. The RS steps don't tell you this and I don't recall what this step was exactly. But you shouldn't have this problem if you use WSS 3.0 only. Once you enable the RS content types: 1. As you would in navitve mode by using the Report Designer or Report Builder and publish to WSS. 2. You can deploy them one by one or deploy them from VS.NET.
In your Nov. 16, 2007 response, you indicated that there was a missing MOSS security step that prevented the Report Services content types from being enabled.Though you didn't recall the step exactly, is there any additional information that you or others may provide that would help me research and discover what this step may be?
Thank you in advance for any help that you may offer.
Best regards - Mark Frederiksen
I "think" it was configuring the MOSS policy under the Application Management section in MOSS Central Administration but I could be wrong. I don't have a MOSS instance around to check. It could be also a site setting on the site itself. Sorry for the vague reply but it's been a while since I wrestled this beast. If you find what the magic setting is please post your solution here to document it.