June 11, 2014 at 1:36 am
Hi
We have reporting services job schedule on sql server.few of them send mail through reporting services subscription .All was working fine but few days back mail are not begin sent i am get below error(all though jobs are executed on sql server).
On trying to edit any subscription i get this error : 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
On inspecting reporting services log i get following error :
The current action cannot be completed. The user data source credentials do not meet the requirements to run this report or shared dataset. Either the user data source credentials are not stored in the report server database, or the user data source is configured not to require credentials but the unattended execution account is not specified.;
Error sending email. Microsoft.ReportingServices.Diagnostics.Utilities.RSException: The current action cannot be completed. The user data source credentials do not meet the requirements to run this report or shared dataset. Either the user data source credentials are not stored in the report server database, or the user data source is configured not to require credentials but the unattended execution account is not specified
library!WindowsService_33!11cc!06/02/2014-02:00:13:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InvalidDataSourceCredentialSettingException: , Microsoft.ReportingServices.Diagnostics.Utilities.InvalidDataSourceCredentialSettingException: The current action cannot be completed. The user data source credentials do not meet the requirements to run this report or shared dataset. Either the user data source credentials are not stored in the report server database, or the user data source is configured not to require credentials but the unattended execution account is not specified.;
library!WindowsService_33!11cc!06/02/2014-02:00:13:: w WARN: Microsoft.ReportingServices.Diagnostics.Utilities.InvalidDataSourceCredentialSettingException: The current action cannot be completed. The user data source credentials do not meet the requirements to run this report or shared dataset. Either the user data source credentials are not stored in the report server database, or the user data source is configured not to require credentials but the unattended execution account is not specified.
emailextension!WindowsService_33!f68!06/02/2014-02:00:13:: e ERROR: Error sending email. Microsoft.ReportingServices.Diagnostics.Utilities.RSException: The current action cannot be completed. The user data source credentials do not meet the requirements to run this report or shared dataset. Either the user data source credentials are not stored in the report server database, or the user data source is configured not to require credentials but the unattended execution account is not specified. --->
June 11, 2014 at 2:25 pm
It sounds like the password might have been changed for the user whose credentials are used for the data source. I would start by checking the data source in SSRS and ensuring the password entered there is correct.
June 26, 2014 at 1:21 am
doug.brown (6/11/2014)
It sounds like the password might have been changed for the user whose credentials are used for the data source. I would start by checking the data source in SSRS and ensuring the password entered there is correct.
Can u tell me how to proceed step by step.
I donot know anything about ssrs .
June 26, 2014 at 1:47 pm
First see what data source the report is using. In SSRS, when you have the report open go to Properties -> Data sources. Usually, you'll see a pathway to a shared data source (something like /Data Sources/Reporting DB). In the example I just used, from the Home menu you would go into the Data Sources folder and find a data source called Reporting DB. When you click on the data source, you'll see a properties screen that includes the connection credentials. If you know the current password for the user in the data source, re-enter it and click Apply.
Now try the report again and see if that fixed it. If not, the issue is probably something else.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply