• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 715
  • Last Modified:

Reporting services error - cannot create a connection to datasource

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:
rs-Error.JPG
0
skaleem1
Asked:
skaleem1
  • 5
  • 2
1 Solution
 
robertg34Commented:
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.  
0
 
skaleem1Author Commented:
Redeployment did not help. Can you tell me how to re-enter stored credentials in the datasource from the reporting services web page interface.
0
 
robertg34Commented:
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.  
 
0
Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

 
skaleem1Author Commented:
I tried editing the datasource from BI and found out that I am using Windows Authentication -so no credentials required. Any clues?
0
 
skaleem1Author Commented:
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.
0
 
skaleem1Author Commented:
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"

Thanks
0
 
skaleem1Author Commented:
Thanks for your help, but pls try to elaborate a little more for novices like me
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now