Credentials used to run this report are not stored

Hi Colin,
I understand that you encountered the error regarding stored credentials
when you tried to create a subscription or snapshot on all of your reports.
Every data source had stored credentials with the both options "Use as
Windows Credentials" and "Impersonate the authenticated user".
If I have misunderstood, please let me know.

What is the result if you do not check "Impersonate the Authenticated
user"? It is not recommended to use this option when you create a
subscription for your report. From this article,
http://msdn.microsoft.com/en-us/library/ms160330.aspx, we can find the
following description in the section "Using Impersonation with Stored
Credentials":
"Do not use impersonation for reports that support subscriptions or that
use schedules to generate report history or refresh a report execution
snapshot."

If this issue persists, I would recommend that you first check the
following articles correspondingly to see if there is any step omitted:
Creating, Modifying, and Deleting Standard Subscriptions
http://msdn.microsoft.com/en-us/library/ms156307.aspx
Tutorial: Creating a Data-Driven Subscription
http://msdn.microsoft.com/en-us/library/ms169673.aspx

If your steps are without any problem, I recommend that you mail me
(changliw_at_microsoft_dot_com) your reporting services error log
(C:\Program Files\Microsoft SQL Server\MSSQL(.n) \Reporting
Services\LogFiles) for further research.

Hope this helps. If you have any other questions or concerns, please feel
free to let me know.


Best regards,
Charles Wang
Microsoft Online Community Support
===========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@microsoft.com.
===========================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
============================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================

Thanks for that.

I was hoping that the authenticated user, when executing the subscription,
would be the secured credentials. On the other hand, when an end-user
executes the report it would be their credentials.

One of my reports needed to know the logon of the user because it creates
records in a temporary table and needed to separate records by storing the
credentials in the records.

I have overcome this problem by supplying the credentials as a report
parameter that is passed to the datasource CLR stored procedure instead.

Thanks again.

Colin Halliday






""Charles Wang [MSFT]"" wrote in message
news:RWW7zve0IHA.1788@TK2MSFTNGHUB02.phx.gbl...
> Hi Colin,
> I understand that you encountered the error regarding stored credentials
> when you tried to create a subscription or snapshot on all of your
> reports.
> Every data source had stored credentials with the both options "Use as
> Windows Credentials" and "Impersonate the authenticated user".
> If I have misunderstood, please let me know.
>
> What is the result if you do not check "Impersonate the Authenticated
> user"? It is not recommended to use this option when you create a
> subscription for your report. From this article,
> http://msdn.microsoft.com/en-us/library/ms160330.aspx, we can find the
> following description in the section "Using Impersonation with Stored
> Credentials":
> "Do not use impersonation for reports that support subscriptions or that
> use schedules to generate report history or refresh a report execution
> snapshot."
>
> If this issue persists, I would recommend that you first check the
> following articles correspondingly to see if there is any step omitted:
> Creating, Modifying, and Deleting Standard Subscriptions
> http://msdn.microsoft.com/en-us/library/ms156307.aspx
> Tutorial: Creating a Data-Driven Subscription
> http://msdn.microsoft.com/en-us/library/ms169673.aspx
>
> If your steps are without any problem, I recommend that you mail me
> (changliw_at_microsoft_dot_com) your reporting services error log
> (C:\Program Files\Microsoft SQL Server\MSSQL(.n) \Reporting
> Services\LogFiles) for further research.
>
> Hope this helps. If you have any other questions or concerns, please feel
> free to let me know.
>
>
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ===========================================================
> Delighting our customers is our #1 priority. We welcome your
> comments and suggestions about how we can improve the
> support we provide to you. Please feel free to let my manager
> know what you think of the level of service provided. You can
> send feedback directly to my manager at: msdnmg@microsoft.com.
> ===========================================================
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscripti...ult.aspx#notif
> ications.
>
> Note: The MSDN Managed Newsgroup support offering is for
> non-urgent issues where an initial response from the community
> or a Microsoft Support Engineer within 1 business day is acceptable.
> Please note that each follow up response may take approximately
> 2 business days as the support professional working with you may
> need further investigation to reach the most efficient resolution.
> The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by
> contacting Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscripti...t/default.aspx.
> ============================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> =========================================================
>
>

Hi Colin,
Thank you for your response and let me know your solution. Congratulations!
This information has been added to Microsoft's database. Your solution will
benefit many other users, and we really value having you as a Microsoft
customer.

If you have any other questions or concerns, please do not hesitate to
contact us. It is always our pleasure to be of assistance.

Have a nice day!

Best regards,
Charles Wang
Microsoft Online Community Support
=========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@microsoft.com.
=========================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================