ssrs unattended account interferes with development

Question

hi we run 2014 enterprise. we develop on tfs (via vs 2017) where there are a number of "business area" folders in our dev branch. Each folder has a different reporting solution. Very often i like to set up a mini environment locally (new db usually) to get development going outside the main stream. Very often i start with a similar report as a starting place for a new report.

i usually switch connection(s) over to "embedded" (moving away from the shared ds) but more often than not find that when i start opening the data sets there is an initial error saying there was a problem connecting to the data source. today i looked at the details and saw the explanation you see at the bottom of this post. i looked at my local ssrs service and while i did update the pswd etc while in there i noticed it wasnt started so i'm assuming the "unattended account" has nothing to do with that.

most of the time when this starts happening , i switch gears and copy what i've developed so far over to a repo folder i have that is outside of tfs. and am able to continue developing and previewing there. eventually i copy what i did in the external folder back over to tfs.

does anyone know how i can avoid that annoying step of going outside of tfs when the connection issue raises its ugly head?

i have to double check but i believe when i first change the data source to embedded (still in tfs) and build the conn string, i get an opportunity to test the connection and it always works.

--the detail error
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.

Answer 1

Hi @db042190 ,
What method do you use for authentication?
If we configure the data source to use Windows integrated security, we will not be able to use SQL Server authentication in the connection. Please just use the following connection string: Data Source=servername;Initial Catalog=databasename
If you want to use SQL Server authentication, please follow these steps:

• Set the connection string to be: Data Source=servername;Initial Catalog=databasename
• Check "Credentials stored securely in the report server", and type the UID and PWD in the username and password textbox.

Your error message looks like it forgot your password,if it is an embedded data source> right click on the data source and go to Properties> Credentials to view the data source.
Hope this helps.
Best Regards,
Joy

---

If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.