by Admin
30. June 2009 09:30
SQL Server Reporting Error - rsInvalidDataSourceCredentialSetting
The current action cannot be completed because the user data source credentials that are required to
execute this report are not stored in the report server database. (rsInvalidDataSourceCredentialSetting).
I loaded up an old SQL Server Reporting project, compiled and deployed. When I tried to run the report, I
got the above mentioned error. The error made perfect sense. This was old project, and somebody saved
the project with data source point to a database that did not exist anymore. So I opened the project file
and changed the datasource settings to point to my current data base. The following screen shots where you
can change data source that will be used for the reports.
I deployed the reports again and I kept getting the same error. To debug the issue I wanted to take a look
at what data source the report is pointing to. So I browsed to the datasource folder in browser. I was
surprised that it was still pointing to old values. First thing that came to my mind was "something is
overriding" by datasource. So I went back to outout window in Visual Studio for deployment process. There was
something in the messages that I seem to have ignored and thought that it may not be important.
Warning : Cannot deploy data source MyReportsData to the server because it already exists and
OverwriteDataSources is not specified.
Well, there was the answer to my problem. When I initially deployed the reports, it got deployed with
old settings and after I fixed my datasource, deployment did not update the configuration in
deployment database. So I changed the setting for OverwriteDataSources to True in
Deployment section of the project. Redployed the project and everything was happy again.
While researching this issue, i noticed that some people suggested changing the configuration of Reporting
service etc. to use some super account that has access to all datasources. Well, I would not do that because
now you are putting security of your reporting application at risk. There are other solutions
available to the problems.
Subscribe