Processing Aborted / Error Opening Connection

  • I have just had my first deploy of reports to our SQL 2005 Report Server :-D, and of my 5 testers 2 have no issue running any of the reports and 3 get the same error:

    An error has occurred during report processing. (rsProcessingAborted)

    Cannot create a connection to data source 'sourcename'. (rsErrorOpeningConnection)

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

    In the Report Manager they have all been given the same access level; Browser. And all are trying to run different reports. :crazy:

    Also if this helps: 1 database, 3 sources, 12 reports (6, 2 & 4). We are not using the Report Server web access but have created a separate HTML front end that lists the reports, then user clicks on the wanted report that takes them to the RS report viewer to run the report. All but 2 reports have user defined parameters. And yes it all work fine in localhost setting.....

    Any guidelines, info, random thouhgts would be helpful! Let me know if you need any further info, too!!

    Thanks in Advance, you folks rock!!!:-)

  • How is the data source security set up? are you passing your user's credentials through to the database server or are you using a single set of credentials for all of the reports to access the database?

    Giving the users the Browser right only gives them access to the report itself. You'd need to somehow deal with the way the reports connect to the database, which logins are used etc.

    does 1 Datasource work and the other 2 not? what's different between them?

    -Luke.

    To help us help you read this[/url]For better help with performance problems please read this[/url]

  • At the moment it is just their Active Directory creds for the network, I belive, our network admin has set up all that. I just control the Report Server.

  • The reports use a dataset to connect to some sort of datasource. Do the reports all use the same datasource? The datasource definition should contain the connection information. Do all of the reports use the same connection information?

    -Luke.

    To help us help you read this[/url]For better help with performance problems please read this[/url]

  • Yes, they use the same data source, with different datasets.

    SQL

    Data Source=joesqldata;Initial Catalog=dbname

    False

    False

    Integrated

    True

    P.S. Thanks for helping, Luke! May the Force always be with you!:-D

  • Thanks for posting the datasource definition. I take it that you are using SSRS 2000 because of the definition you posted. Either way it seems you are using integrated security to authenticate to the database.

    You or your network admin or DBA or whomever will need to take a look at the AD accounts and which groups/accounts have been created as logins to the SQL Server and how those users are mapped to user accounts within the database. It seems that for the user that the reports work for, that they have a different security level than the other users.

    -Luke.

    To help us help you read this[/url]For better help with performance problems please read this[/url]

  • Was afraid you where going to say that..:laugh:..the Network Admin and I were thinking on those lines the other day. It is nice to have it confirmed by some one with more exprience and to know my thought processes are on the right tract.

    But I find it a little strange that it is set up that way. I see the security side of it, but if the user is in no way directly accessing the database then why give them rights to the database to view a report?

    Thanks again for all your help, you have been awesome!!!!:-D

  • The user is directly accessing the database by the very nature of the datasource connection that you have specified. The report server is authenticating to the database using an integrated connection aka the individual user's account/permissions etc.

    If you instead create the datasource with a specific login/password be it a windows user or SQL login or which ever, then they will be authenticating with those credentials and not those of the individual users. Much of it depends on how much you want to manage security in your database and what you want your users to be able to do.

    There are a lot of options, it all depends on what works best for your particular environment.

    -Luke.

    To help us help you read this[/url]For better help with performance problems please read this[/url]

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

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