August 9, 2012 at 7:17 am
Whenever I change anything with the configuration of a report project in visual studio something totally random and stupid occurs.
I have a project in Visual Studio with a shared data source and about a dozen reports that reference that data source. The reports all work and have been deployed to the reporting server. All is good.
In the configuration manager, I added the "development" configuration so I can deploy the reports into a different folder. Reports work, they deploy successfully into the development folder on the reporting server. I changed the data source in Reporting Services to point to the development database and everything works. All is good.
I open the project today in Visual Studio and add a new report. I changed login and database on the shared data source to look at the development database. Tested the connection, all is good. I create a new report, create the data source on the report to look at the shared data source, write the queries, put a table on the report, and press the "Preview" tab and get this error:
An error has occurred during report processing.
Cannot create a connection to data source 'WPP'.
You have specified integrated security or credentials in the connection string for the data source, but the data source is configured to use a different credential type. To use the values in the connection string, you must configure the unattended report processing account for the report server."
I've seen this stupid error before and usually deleting and recreating the shared data source resolves the issue (since the Visual Studio interface doesn't always modify the source files correctly). That didn't work in this case. I deleted and recreated the shared data source and the data source on the report but still get the error. All of the other reports (that have not been modified) are also getting the error.
The only change I did to the data source was to change the database. It uses SQL authentication and the account has access to both databases.
Has anyone else encountered this joyous experience?
...
August 9, 2012 at 7:26 am
Forget it - found the error. It's an issue with Visual Source Safe.
VS creates a \bin\debug\ folder in the local project folder. It looks like it copies the files to that folder then executes the files that were modified from there (in this case, the WPP.rds file). Because I am using Source Safe, those files are read-only by default. So Visual Studio copies my modified file to that folder, then Source Safe locks them, then Visual Studio can't use them. Nice.
I created a script to delete everything in the bin\debug folder. That doesn't get rid of my changes and it allows everything to run.
...
August 9, 2012 at 10:17 am
Cool, glad you found the solution - and thanks for posting it. 🙂
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply