Check your data source connections via the datasource settings of the report.
Main Topics
Browse All TopicsThis problem began following a server change from a box running sql server 2000 to a different box running sql server 2005. the server is running Server 2003 sp2. I have tried several suggestions that have not corrected the problem. these include the following:
1. Using the surface area configuration tool, i checked to make sure that remote connections are allowed. 2. Changed the remote setting from allowing TCP/IP only to TCP/IP and Named Pipes. 3. Turned the browser service on. 4. Restarted the Server.
The Error that comes up is as follows:
An error occurred during local report processing. Cannot create a connection to data source 'ds_nameofds'. An error has occured while establishing a connection to the server. Whne connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections(provider: Named Pipes Provider, error40 - could not open connection to SQL Server)
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I have been into the datasource directly on report. I needed to go there to modify the connection string since the server name had changed. The connection test works fine with the user/password. Just to make sure, I put in a bad password, and recieved a different error that was specifically a credential related error.
The SSRS report is located on a different computer ... in fact I am atempting to connection from my xp pro development computer, and it is from there that the error is occuring. I typically develop these reports on my machine and deploy them. Preview mode will produce the error. The same error occurs when i try to refresh the dataset data.
The "Upgrade" was actually a completely fresh install of SQL Server 2005. The databases were moved onto the new server. There are numerous databases on the server. Since the move, successful connections have been made from various applications and web servers. As far as I know, this is the only connection problem with the move.
If you are only having an issue with one report and the dataset is connection to the same datasource that other reports use then this will not be a firewall issue.
I would guess it's either corruption in the report or there is just something wrong in the data source setup.
Another idea that you may or may not have tried is to just shut the project down and re-open it.
When I develop reports, I'm often connecting through a VPN, if that gets disconnected, I have to at least close the report and re-open but often I have to shut the whole project down and re-open to get that connection with the datasource going again.
Failing that try the following;
Create another datasource that points to the same database,
Create another report
Create a dataset that does a very simple query against the new data source.
If that doesn't work you probably have permission issues.
If it does work, change the datasource of that dataset to your problem datasource,
If that works, go into the problem report and change the dataset to use the alternate datasource.
If that doesn't work I'd suggest there is something wrong with the query or the report is corrupt and will need to be recreated (you can cut and paste most stuff - it's not as bad as it sounds)
If it does work then the other datasource is corrupt, delete it and recreate it.
Cheers
Chris
Business Accounts
Answer for Membership
by: dsackerPosted on 2008-02-29 at 07:00:05ID: 21013753
Unfortunately, this error occurs for a number of reasons, and you'll get the same error message. Please check that SQL Server is set as an exception in the firewall. That seems to be one of the top reasons this can happen.