Reporting Services Error

Question

Reporting Services Error

Karthika Raman

SSCrazy

Points: 2520
More actions
May 20, 2008 at 1:30 pm

#185811

The datasource is a shared datasource that is used by other reports and works fine. The datasource is accessed using stored credentials.
I get the error with one report:
Error processing report. Query execution failed for dataset 'dataset'
The report uses a stored procedure and and runs fine through the report builder but fails with the above error in reporting services
Any help is appreciated
KR

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

Ben Sullins-437405 SSCertifiable Points: 5397 More actions · Answer 1

Is that the only message you received? Usually when I see that there is also something like 'Stored procedure doesn't exit or is not found...'

Cheers,

Ben Sullins
bensullins.com
Beer is my primary key...

Karthika Raman SSCrazy Points: 2520 More actions · Answer 2

Yes,

Here is the exact copied error:

An error has occurred during report processing.

Query execution failed for data set 'dataset'.

For more information about this error navigate to the report server on the local server machine, or enable remote errors

The remote errors option is enabled, but all I get is this.

Thanks

Karthika

Ben Sullins-437405 SSCertifiable Points: 5397 More actions · Answer 3

Hmm...is it an option to run the report from the report server itself? When you enabled remote errors did you restart the SQL Reporting Services Service as well as IIS (World Wide Web Publishing Service)?

If you can get to the report server to run the report there you should see a more descriptive error message that can help you troubleshoot...

Cheers,

Ben Sullins
bensullins.com
Beer is my primary key...

Karthika Raman SSCrazy Points: 2520 More actions · Answer 4

I am not sure what you mean by run the report on the server - do you mean using visual studio?

Also, I am assuming the services were restarted since the option was enabled when I looked.

Thanks

KR

Ben Sullins-437405 SSCertifiable Points: 5397 More actions · Answer 5

I mean log into the report server itself and go to the Report Manager and run the report. This is where you'll see the more descript errors. Also, If it's possible I would recommend restarting those services to make sure the remote errors enable option has been applied.

Cheers,

Ben Sullins
bensullins.com
Beer is my primary key...

Karthika Raman SSCrazy Points: 2520 More actions · Answer 6

This error is through the report manager.

I cannot restart the services now, since people are using it currently. Will have to do it at a scheduled time if there is no other way to solve it.

Thanks

KR

Ben Sullins-437405 SSCertifiable Points: 5397 More actions · Answer 7

You're not understanding my suggestion...

Use 'Remote Desktop' or whatever app you have to remotely login to servers and login to the report server itself. If you don't have that setup walk over to the server itself and phsyically log into the report server.

Once logged into the report server open up the Report Manager (on the report server) and browse to the report. From there you should get more detailed error reporting that will help you troubleshoot the problem with the data set...

Good Luck!

Cheers,

Ben Sullins
bensullins.com
Beer is my primary key...

Karthika Raman SSCrazy Points: 2520 More actions · Answer 8

Thanks for the clarification!

That helped. The full error is :

An error has occurred during report processing.

Query execution failed for data set 'dataset'.

Must declare the scalar variable "@GroupNumber".

I did some more research on this and found that it is due to incorrect mapping of report parameters to the stored procedure parameters. If that is the case then would the error not appear when the report is run through the report builder in visual studio?

Anyway, I have passed the info on to the developer to check the mapping on the report and redeploy the report and see.

Thanks

KR