August 27, 2013 at 9:53 am
So we have some reports (which I didnt develop) that work fine if I run them on the server reporting services is configured on, but if they are ran from my machine, or from any other box, they fail with the error
Cannot create a connection to data source
If I go into the reports using this data source, and click on the history tab it says - Credentials used to run this report are not stored
The data source is currenly using windows integrated security. Is the only way to get around this error to use "credentials stored securely in the reportserver" and specify an account to use?
August 27, 2013 at 1:20 pm
Another options is to prompt the user to enter credentials when the report is ran.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
August 27, 2013 at 3:28 pm
You can override the data source credentials on the report server. Go to the data sources and set the account you want to use, then in your BIDS project, in the deployment settings be sure to uncheck the "overwrite data sources" option - this will leave your working DSN int act on the report server...
Or you can use Koen's suggestion: have the user enter it each time they run a report
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
August 28, 2013 at 6:54 am
MyDoggieJessie (8/27/2013)
You can override the data source credentials on the report server. Go to the data sources and set the account you want to use, then in your BIDS project, in the deployment settings be sure to uncheck the "overwrite data sources" option - this will leave your working DSN int act on the report server...
I use this method for my development and overall it works rather well.
We had been running into a problem where our source control system didn't store the credentials (we use a SQL user) and anytime we published an update to a report, the credentials on the report server would be overwritten. Once I made this change, that problem went away. Additionally, I can change the credentials on my dev machine to point to one of our test environments without worrying about overwriting the credentials that my users are using.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply