Wednesday, March 21, 2012

Getting rsOperationNotSupported when running report

I had started a project with SQL Server 2005 Express and quickly realized that it would not let me access DB's on other servers so I removed Express and Installed Workgroup Edition. When I try to run reports I still get "rsOperationNotSupported" when connecting to the remote database.

What gives? Do I need to move up to Std Edition for this?

In what way did SQL Server 2005 Express "not let you access DB's on other servers"? Have you tried setting up linked servers?

and even without that, what issues did you experience ... even if you are talking about "Mgmt Studio Express" or something rather than SQL Server Express? (I do this for most of my working day, and on one machine I definitely have SQL Server Express talking to many servers, on another I definitely have Mgmt Studio Express talking to many servers)

To answer your current question, though, ten to one the instance id for your new installation is incorrectly specified in the rs configuration somehow -- it's still pointing to the old instance.

>L<

|||

After talking to MS Support, was told that Workgroup Edidtion does not support remote data sources but Std Edition does. Will remove Workgroup and see if installing Std does the trick.

|||

Hey Tom, thanks in advance for clarifying this... is this something specific about *hosting RS* on each edition? Because I definitely access remote data from Express all the time -- I have never tried Workgroup. I must be doing something different from what you mean...

OTOH, it's true that I generally set up the remote sources as linked servers, and have one local SQL Server database "hosting" the calls for reports. This is because typically there are a lot of different datasources for each report, and I find it more convenient to have a local database caching some data, drawing other data live, but coordinating the whole thing without the reports' knowing where the data comes from.

Funny. I never would have realized that there were additional benefits re editions <s>.

>L<

|||

Found out what was going on. First SQL Server 2005 Std Edition is required if the datasource your accessing is on another server. Installed an instance of SQL Server 2005 Standard and everything worked (that is after I installed SP2).

On a related note for those insterested, I was also trying to get an instance of Reporting Services 2000 on a SQL Server 2000 Std Edition to work that I already had a license for on another server which was running Windows Server 2003. Reporting Services for SQL Server 2000 which apparently requires ASP 1.1. I had recently updated the server to run SharePoint Services v3 which requires ASP 2.0 or higher. Needless to say, they can't play together well. FYI.

Thanks to the feedback. I started me thinking in the right direction.

sql

No comments:

Post a Comment