I Created a report that runs without a problem in SSBI Development studio. I deploy the report to the server, ReportViewer and I get the following error: An error occurred during client rendering. An error has occurred during report processing. Cannot create a connection to data source '<data source name>'. For more information about this error navigate to the report server on the local server machine, or enable remote errors The datasource uses the sa account to connect to the SQL server database. I have admin priviledges to ReportViewer. What could be wrong?

This might help you to fix the issue http://msdn.microsoft.com/en-us/library/ms156468.aspx

The article doesn't help because there are no connection issues. The Data Source tests susscefully on the Report Designer (BI Development Studio) and the report runs fine. I know the deployment settings are correct, because I see the report and the datasource on the report viewer. The only problem is the report runs on the designer, but won't run on the Report Viewer. I have the following permissions on the Viewer: Browser, Content Manager, My Reports, Publisher, Report Builder.

Susan, when you say "ReportViewer", I assume you mean when you launch the report with the Report Manager and select the report from the Reporting Services catalog. Right? You don't really mean that the application was developed using the ReportViewer control and it's imbedded in an application? Okay, connection issues: First, it's incredibly dangerous to use SA for any non-DBA work. Even then it's dangerous and could jeapordize data integrity and compromise security. Next, examine the properties of the deployed report. Since you can't launch it from the server catalog, using Report Manager, inspect the report Data Source and click the "Test Connection" button to make sure it's working. If it doesn't, you need to figure out why. This could be any of a dozen dozen reasons (as outlined in the article). Consider that the account must have rights on the server instance as a known login. That login must have rights to the database. Consider that when you deploy a report with a shared Data Source, the default BIDS behavior is to NOT overlay the existing cataloged shared Data Source. hth __________________________________________________________________ William Vaughn Mentor, Consultant, Trainer, MVP http://betav.com http://betav.com/blog/billva http://www.hitchhikerguides.net Hitchhikers Guide to Visual Studio and SQL Server (7th Edition) Please click the Mark as Answer button if a post solves your problem!

Susan, when you say "ReportViewer", I assume you mean when you launch the report with the Report Manager and select the report from the Reporting Services catalog. Right? Susan- Yes. I mean Report Manager when I say ReportViewer. You don't really mean that the application was developed using the ReportViewer control and it's imbedded in an application? Susan- No, the report was developed in BIDS. The Datasource was created in BIDS as well. Okay, connection issues: First, it's incredibly dangerous to use SA for any non-DBA work. Even then it's dangerous and could jeapordize data integrity and compromise security. Susan - This is just an internal DB in the development fase. I'm currently the only one accessing it. In an case, I've created another user account. Next, examine the properties of the deployed report. Since you can't launch it from the server catalog, using Report Manager, inspect the report Data Source and click the "Test Connection" button to make sure it's working. If it doesn't, you need to figure out why. This could be any of a dozen dozen reasons (as outlined in the article). Consider that the account must have rights on the server instance as a known login. That login must have rights to the database. Consider that when you deploy a report with a shared Data Source, the default BIDS behavior is to NOT overlay the existing cataloged shared Data Source. Susan- As I mentioned above the report runs successfully in BIDS. I've tested the connection and it connects successfully. So the login has the correct rights to the database. I've changed the default setting so it overlays the existing catalog in Report Manager. I changed the OverwriteDataSources setting to "True". I think the problem is on the Report Server (which I don't have access). My database resides on my local machine. I've been given the following roles to Report Manager: Browser, Content Manager, My Reports, Publisher, Report Builder

I found out the problem. The data source connects to a database that is sitting on SQL Server Express, and I believe by default SQL Express is set to not allow network connections, only local connections.