ssrs migration from 2005 to 2008. Execution account error.

Posted on 2013-11-13
Medium Priority
Last Modified: 2013-11-14

We have migrated about 300 rdl files from SSRS 2005 to SSRS 2008 .For each RDL file had its own seperate Dynamic datasource with datasource credentials in SSRS 2005 but after migration on SSRS 2008 all rdl files lost their datasource credentials.
So if we run rdl file in report manager it shows following error :
"The report server has encountered a configuration error. Logon failed for the unattended execution account. (rsServerConfigurationError) Log on failed. Ensure the user name and password are correct. (rsLogonFailed) Logon failure: unknown user name or bad password " .

To avoid error we need to go for each rdl file and save datasource credentials manually, but its not feasible for us as we have about 300 rdl file needs to manuaaly update .

Is there any another way to add execution account credentials for all reports ?

Error :
report error
Manual update need for each report  :
manual setting
Question by:vikasbapat
  • 2

Accepted Solution

FriedTyGuy earned 1500 total points
ID: 39645438
Just a suggestion for future development, use shared data sources whereby the data source is saved on the reports server.  This way in instances such as this, you only need to update a couple data sources.  For our recent upgrade from SharePoint 2007 and 2005 SSRS to SharePoint 2013 integrated 2012 SSRS I pulled all our reports into a single VS2012 solution and with multiple projects based on report types (we had to do this as the old .rdl files wouldn't work on 2012 SSRS).  Each project had anywhere from 10-15 to over 50 reports.  The magic in this though is I could set the properties for each project (location, data sources, etc) and then do a mass deploy to our reports server.  Any new reports that are created are managed through the single solution so that for our next upgrade if Microsoft wants to throw another curve at us we'll be able to convert the entire solution and then after updating the project properties mass deploy it to our new environment.

It may sound like a lot of work initially, but it's much easier to maintain.  Also, it's not like you have to recreate all the reports as you can just copy the xml of the old report into blank reports in your VS solution/projects.

As far as manually changing all your individual data source credentials, I wish I could offer an easier solution.  I can only suggest using shared data sources in future to make these types of issues easier to maintain in the future.

Author Comment

ID: 39647074
I appreciate your reply .
But we have multiple  databases in our application and DB name should be dynamically passed as parameter to report.
So the Connection string should be dynamic mentioned as expression in datasource.
Can we Write Dynamic connection string in shared data source ? we have tried this in SSRS 2008 , but it doesn't allow to create dynamic connection string for shared database.

Expert Comment

ID: 39647593
I see your dilemma, if you have access to the data base server you could take a look into this:


Another, extremely painful option, as mentioned in the link is to deploy a report for each data base, but having over 300 reports; doesn't seem like an option.

You could also consider:


Featured Post

Train for your Pen Testing Engineer Certification

Enroll today in this bundle of courses to gain experience in the logistics of pen testing, Linux fundamentals, vulnerability assessments, detecting live systems, and more! This series, valued at $3,000, is free for Premium members, Team Accounts, and Qualified Experts.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

In part one, we reviewed the prerequisites required for installing SQL Server vNext. In this part we will explore how to install Microsoft's SQL Server on Ubuntu 16.04.
It is possible to export the data of a SQL Table in SSMS and generate INSERT statements. It's neatly tucked away in the generate scripts option of a database.
Via a live example, show how to extract information from SQL Server on Database, Connection and Server properties
Via a live example, show how to extract insert data into a SQL Server database table using the Import/Export option and Bulk Insert.

588 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