Post reply

Report Viewer gives an error after deploying report

  • March 27, 2007 at 2:50 pm

    #172606

     

    I have created a report on my local machine and deployed it on a server. As I am the administrator of the server, I can access the reports with servername\Reports. The report has got three data sets. Out of these three one is a Stored procedure and other two data sets have sql queries. The user selects the 'Business year' and 'sales type' from list box. This report works perfect from my local machine as well as from teh server when I am running it

     

    I have some other users who wish to access these reports. I did the following steps:

    • Created a new role and assigned it at the Data Source Folder and Reports Folder
    • I also made the user a Database user on the server.

    After doing these steps, the user can access the Reports site by servername\Reports.

    The user then can go into the Reports folder. But when the user tries to run the report, he gets an error with:

    An error has occurred during report processing. (rsProcessingAborted)

    • Query execution failed for data set 'BusinessYear'. (rsErrorExecutingCommand)

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

    Can anyone help me with this? Is htere something to do with setting up of the datasource?

     

    I have tried to search, but could not find relevant info.

     

    Any help/Pointers will be really appreciated.

     

    regards

    Joshker

  • March 28, 2007 at 4:14 pm

    #697548

    try this,

    Since I don't know your network and am not familiar with your set up, you can always try and use a SQL Server User in the datasource for the report.  You can add a SQL Server user to the datasource by way of your Reporting Services dev environment, or you can go to the report on your reportserver and click properties, then click datasources, then change it there from windows authentication a a username/password.  You can create a user in SQL server granting read-only and execute procedure rights.

     

     

Viewing 2 posts - 1 through 1 (of 1 total)

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