can't create a subscription if data source is set to impersonate the authenticated user - by GregGalloway

Status : 


Sign in
to vote
ID 543052 Comments
Status Active Workarounds
Type Suggestion Repros 1
Opened 3/18/2010 3:30:56 PM
Duplicates 561917 Access Restriction Public


Create a report with an SSAS data source. The data source should be setup as follows:

1. Check "credentials stored securely" and enter some credentials
2. Check the "Use as Windows Credentials" checkbox
3. Check the "Impersonate the authenticated user" checkbox

Behind the scenes when running the report live, when you check the "Impersonate the authenticated user" checkbox, it appends the EffectiveUserName property to the connection string.

Now go to the subscriptions tab and click "New Subscription". You will get this error message:

Subscriptions cannot be created because the credentials used to run the report are not stored, or if a linked report, the link is no longer valid.
Sign in to post a comment.
Posted by Koen Verbeeck on 12/1/2016 at 2:12 AM
What's the status on this?
Posted by Barret Miller on 4/14/2011 at 11:06 AM
As Paul said, I believe this would solve the fundamental issue, but you guys may come up with a better way to do it:
Posted by Paul Turley on 3/17/2011 at 12:05 AM
This cmes up regularly in my consulting work on on the forum. If we were able to use an expression to to build the connection string in a shared data source, it would solve the problem.
Posted by Microsoft on 10/1/2010 at 4:39 PM
Thank you for the comment. One thing to note that the workaround on your blog post uses a hidden parameter. Please note that parameters can be supplied by any user - so if you use the workaround mentioned, control extremely well who is able to run that report, other wise you are exposing a security vulnerability in your report. This is actually why reports with dependencies on User!UserID are disable in data-driven subscriptions...

Thank you for the detailed feedback,
Posted by GregGalloway on 10/1/2010 at 10:53 AM
I ended up blogging about this scenario. There's something of a workaround described in there, but hopefully the SSRS team will address this more properly in a future release:
Posted by Microsoft on 9/30/2010 at 8:29 AM
@vk_ravikumar: Data Driven subscriptions support SSAS today. You have to store data source credentials to make the connection.
Hope this helps,
Posted by DanielBos on 9/30/2010 at 7:25 AM
Posted by vk_ravikumar on 7/12/2010 at 2:05 AM
Data-driven subscription is one of the much needed feature. Request Microsoft to provide this with SSAS as data source.
Posted by Microsoft on 6/15/2010 at 12:00 PM
Thank you for providing the additional comments, it makes the scenarios very clear.

Posted by Teo Lachev on 4/2/2010 at 12:06 PM
Further, it will be nice if data-driven subscriptions support the same feature, that is an expression-based connection string so EffectiveUserName can be used by appending the user logon from the profiler store to the data source connection string.

This will be probably more difficult to implement than regular subscriptions but it will be a great addition for users targetting Analysis Services.
Posted by Microsoft on 3/26/2010 at 7:36 AM
Thank you for filing this issue. It is not something we will add as a bug fix. We will consider it as a feature request for a future release.

Posted by Teo Lachev on 3/18/2010 at 6:38 PM
Yes, this should be allowed to facilitate regular subscriptions with SSAS. Regular subscriptions allow using User!UserID on the report. I don't see why this is not allowed in the connection string.