Reporting services error - cannot create a connection to datasource

Posted on 2010-08-16
Last Modified: 2012-05-10
I have developed few reports and have provideed the browser level access to few users. Everything was working fine until few hours ago. Suddenly, after I deployed the reports after adding new reports and modifying few existing reports, all my users are getting the error shown in the screen shot file below. What has changed and how to fix this:
Question by:skaleem1
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 2

Expert Comment

ID: 33450333
Redeploy your datasource and the error should clear.  If you are using stored credentials in the datasource, you may have to re-enter those from the reporting services web page interface.  

Author Comment

ID: 33451013
Redeployment did not help. Can you tell me how to re-enter stored credentials in the datasource from the reporting services web page interface.

Accepted Solution

robertg34 earned 500 total points
ID: 33451052
If you don't see your data sources, there should be a link to show 'all' on the main report page.  Click that and look for your data source, click the data source and choose properties.  Within that will be the options to store your credentials.  That is if the credentials were stored in the first place.  That's a known issue a lot of folks have.  
Get Actionable Data from Your Monitoring Solution

Your communication platform is only as good as the relevance of the information you send. Ensure your alerts get to the right people every time with actionable responses. Create escalation rules that ensure everyone follows the process and nothing is left to chance.


Author Comment

ID: 33454504
I tried editing the datasource from BI and found out that I am using Windows Authentication -so no credentials required. Any clues?

Author Comment

ID: 33454546
another thing to notice, I can access it locally from the report server as well as from my laptop computer using the web app. that calls the report link. But non of the other users can access the report.

Author Comment

ID: 33457739
Here is how it was resolved-as you pointed out in your answer. I am adding a detailed walk through so that anyone going through this issue does not waste time that way I did :-)
Step 1: Add a New Report User - Go to SQL Server Management Studio- Connect to the Database Server -Database Engine- Expand the Security folder - right click on Logins Folder - Select New Login and add a new User called ReportUser. Login - New dialog box opens - Enter a new login name (say) ReportUser, select SQL Server Authentication and provide password. In the left pane, select User Mapping link and check the database(s) you want to provide the access in the upper right pane and the data role membership in the lower right plane and click OK.

Step 2- Update the Data Source: From SQL Server BI Development Studio, go to the report.rdl file Data view, click on the eclipse on the right of the Dataset- Dataset dialog box opens-on the Query tab click on the eclipse on the right of the data source selected in the dropdown list-Data Source Dialog box opens up-in my case "Use shared data source reference" is checked as I am using the shared data source- click on the Edit button located on the RHS of the data source reference selected in the dropdown list - Shared Data Source dialog box opens up - in the General tab, click on the edit button located on the right hand side of the Connection String text box- Connection Properties dialog box opens up - change the "Use Windows Authentication" option to "Use SQL Server Authentication", provide the user name and password and check the "Save my password" checkbox. Click on the Test Connection button on the bottom of the dialog box to make sure that the connection succeeds and click OK-OK-OK-OK.

Step 3: Set OverWriteDataSources property to true (in case we are deploying within the same environment) From SQL Server BI Development Studio, go to the Solutions Explorer, right click the Reports project and select properties - Properties page opens - In the right pane, make sure that OverWriteDataSources property is set to true.

This will resolve the above error and all users will be able to access the reports through a single user we just created named "Reports User"


Author Closing Comment

ID: 33457769
Thanks for your help, but pls try to elaborate a little more for novices like me

Featured Post

Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I have a large data set and a SSIS package. How can I load this file in multi threading?
A Stored Procedure in Microsoft SQL Server is a powerful feature that it can be used to execute the Data Manipulation Language (DML) or Data Definition Language (DDL). Depending on business requirements, a single Stored Procedure can return differe…
Familiarize people with the process of retrieving data from SQL Server using an Access pass-thru query. Microsoft Access is a very powerful client/server development tool. One of the ways that you can retrieve data from a SQL Server is by using a pa…
Via a live example, show how to setup several different housekeeping processes for a SQL Server.

696 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question