Friday, August 17, 2007

 

Finally fixed the problem w/ reporting over WSS3/MOSS lists

Sorry that this took so long. Many people have reported that using the Reporting Services Extension for SharePoint Lists gives an error when used against WSS3 or MOSS 2007, the latest incarnations of SharePoint.

For a long time, I couldn't find the time to fix the problem. I did not have a developement environment with Reporting Services anymore, so setting everything up again was not something for a spare 30 minutes.

Anyway, I found the problem (I explain below). You can download a fixed reporting extension here. Note that this is a version for SQL 2005. I do not have the tools anymore to compile one for SQL 2000.

So what was the problem? The extension uses the "Display Name" of a list column as its internal name. The problem arises when two columns have the same Display Name. It turns out the all lists on WSS3/MOSS2007 have several columns named "Modified". In the new version these will show up as "Modified" and "Modified_1".

I also made sure that in the future the error messages will be more meaningful. Enjoy.


Comments:
I successfully created a report in VS studio 2005? could you post how to put this report in Sharepoint site?
Thank you,
Kim
 
The point of the extension described here is to use SharePoint lists as the data store. What you are asking is the other way around: showing reports in a SharePoint site. To do this, several solutions are available:
http://aspalliance.com/729 [article]
http://www.microsoft.com/downloads/details.aspx?FamilyID=1E53F882-0C16-4847-B331-132274AE8C84&displaylang=en [download from MS]
 
Hi teun!
I was wondering is it was possible to get a roll-up report of a particular LIST (say TASKS) from all sub sites of a collection (all based on same template) using your current ver, possibly through query-string? or do we have to extend your code.

Second, i'm able to get report working from within vs2005 (preview), but after deploying to RS, it gives an error "An error has occurred during report processing", i have given permissions etc on RS, but any other reason? seems like the report when on RS isn't being allowed to access wss list, wheras inside vs2005, it can.

Kind regards
Satish
 
@Satish:
1. No, you cannot do rollups with the extension. The reason here is that the SharePoint SOAP services don't (at least in SP2003, not sure about 2007) allow to query across lists. You may be able to implement this yourself using the provided code, though.
2. This sounds like a privileges issue. Or you haven't deployed the extension properly on the reporting server. The deployment procedure describes two places where you must place the dll and change config files. One must be done on the client running VS.NET, the other one should be done on the server running SSRS.
 
Yes of course it was just the codegroup nodes position in the config file on RS server, now it works.

Thanks,
Satish
 
This works great in Visual Studio but when I run the report on the Reporting Services Server (separate box) I get an error "An error has occurred during report processing."

When I look at the Report Server Log File I see the following entry

"w3wp!processing!1!2/28/2008-16:22:25:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'Sharepoint_Locations'., ;
Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'Sharepoint_Locations'. ---> System.Net.WebException: The request failed with HTTP status 401: Unauthorized."

Notice the HTTP 401 error

SharePoint is on a different server to Reporting Services

and the account running the reports is a domain user and is also added to the Sharepoint site with read access.

Any ideas ??

MOSS2007 Sp1 /SSRS 2005 Sp2
 
Hi Teun,
Thanks for the great blog it is really helpful. I did all the steps and after that when I tried to create a Report Project using VS 2005 Report Project wizard, it is giving me the following error.

The configuration file RSReportDesigner.config could not be loaded. The report server has encountered a configuration error.

Thanks for your help in advance.

Regards,
Kalyan Guin
 
Hi Teun,

we want to use the extension above in a cluster environment. Do you know any restrictions we have here?

br
 
I can't think of a problem with clustered installations. Keep in mind though that reporting over lists in Sharepoint is not very performnace optimized. Every query will be calling SOAP webservices downloading all of the data from one of the sharepoint servers down to the Reporting server(s). With many users viewing the same report, this is no problem (Reporting Services will cache the results). However when many users make many different queries might result in a very high load on WSS. Especially for large lists: in that case each user will download all of the data to the reporting server and perform any filters or calculations there.
 
Thanks,

I gonna tell you afterwards about the performance if you want.

br Dominik
 
Post a Comment

Links to this post:

Create a Link



<< Home

This page is powered by Blogger. Isn't yours?