We're using SharePoint integrated Reporting Services.
We have a daily event that triggers eight SSRS subscriptions that write files to various shared folders after our ETL completes.
Randomly, every 5-10 days these subscriptions fail with the message:
"An impersonation error occurred using the security context of the current user. ---> System.Runtime.InteropServices.COMException: The referenced account is currently locked out and may not be logged on to."
This message is misleading as the account is not locked out. The resolution is just to re-trigger the event. The reports run fine and are saved successfully. If it happens to occur on a weekend, nothing is done and the reports just run fine the next day. Nothing is done to change the account.
The eight reports are either all successful or they all fail, there is never a combination of some success and some fails.
Any ideas what would make an account seem locked out when it's not? Is there some way to find out more information on what's going on?
Here are the relevant logs for one of the reports:
--These are the log entries when the report fails
w3wp!schedule!126!05/05/2016-05:39:29:: i INFO: Handling Event TimedSubscription with data 51740b52-5115-4452-ac2a-bb593a2959c7.
w3wp!schedule!126!05/05/2016-05:39:29:: i INFO: Creating Time based subscription notification for subscription: 51740b52-5115-4452-ac2a-bb593a2959c7
w3wp!schedule!67!05/05/2016-05:39:29:: i INFO: Handling Event DataDrivenSubscription with data 51740B52-5115-4452-AC2A-BB593A2959C7.
w3wp!library!21!05/05/2016-05:39:29:: i INFO: Handling data-driven subscription 51740b52-5115-4452-ac2a-bb593a2959c7 to report https://go.mydomain.com/sites/bi/Reports/My report Name.rdl, owner: mydomain\ownername, delivery extension: Report Server FileShare.
w3wp!library!98!05/05/2016-05:39:29:: i INFO: Initializing EnableExecutionLogging to 'True' as specified in Server system properties.
w3wp!notification!98!05/05/2016-05:39:46:: i INFO: Handling subscription 51740b52-5115-4452-ac2a-bb593a2959c7 to report My report Name.rdl, owner: mydomain\ownername, delivery extension: Report Server FileShare.
w3wp!library!98!05/05/2016-05:39:46:: i INFO: RenderForNewSession('https://go.mydomain.com/sites/bi/Reports/My report Name.rdl')
w3wp!library!98!05/05/2016-05:39:53:: i INFO: Initializing EnableExecutionLogging to 'True' as specified in Server system properties.
w3wp!library!98!05/05/2016-05:39:53:: e ERROR: Throwing Microsoft.ReportingServices.FileShareDeliveryProvider.FileShareProvider+NetworkErrorException: An impersonation error occurred using the security context of the current user., Microsoft.ReportingServices.FileShareDeliveryProvider.FileShareProvider+NetworkErrorException: An impersonation error occurred using the security context of the current user. ---> System.Runtime.InteropServices.COMException: The referenced account is currently locked out and may not be logged on to. (Exception from HRESULT: 0x80070775)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at Microsoft.ReportingServices.FileShareDeliveryProvider.FileShareProvider.GetImpersonationToken(String userName, String domain, String userPwd)
--- End of inner exception stack trace ---;
w3wp!subscription!98!05/05/2016-05:39:53:: e ERROR: Failure writing file \\server\path$\path\path2\My report Name Export.xlsx : Microsoft.ReportingServices.FileShareDeliveryProvider.FileShareProvider+NetworkErrorException: An impersonation error occurred using the security context of the current user. ---> System.Runtime.InteropServices.COMException: The referenced account is currently locked out and may not be logged on to. (Exception from HRESULT: 0x80070775)
w3wp!subscription!98!05/05/2016-05:39:53:: i INFO: Error writing file My report Name Export.xlsx to path \\server\path$\path\path2
w3wp!notification!98!05/05/2016-05:39:53:: e ERROR: Error occurred processing subscription 51740b52-5115-4452-ac2a-bb593a2959c7: Failure writing file \\server\path$\path\path2\My report Name Export.xlsx : An impersonation error occurred using the security context of the current user.
--And Later on when the event is triggered again and the report is successful...
w3wp!schedule!4a!05/05/2016-08:33:04:: i INFO: Handling Event TimedSubscription with data 51740b52-5115-4452-ac2a-bb593a2959c7.
w3wp!schedule!4a!05/05/2016-08:33:04:: i INFO: Creating Time based subscription notification for subscription: 51740b52-5115-4452-ac2a-bb593a2959c7
w3wp!schedule!126!05/05/2016-08:33:04:: i INFO: Handling Event DataDrivenSubscription with data 51740B52-5115-4452-AC2A-BB593A2959C7.
w3wp!library!4d!05/05/2016-08:33:04:: i INFO: Handling data-driven subscription 51740b52-5115-4452-ac2a-bb593a2959c7 to report https://go.mydomain.com/sites/bi/Reports/My report Name.rdl, owner: mydomain\ownername, delivery extension: Report Server FileShare.
w3wp!notification!ca!05/05/2016-08:33:25:: i INFO: Handling subscription 51740b52-5115-4452-ac2a-bb593a2959c7 to report My report Name.rdl, owner: mydomain\ownername, delivery extension: Report Server FileShare.
w3wp!library!ca!05/05/2016-08:33:25:: i INFO: RenderForNewSession('https://go.mydomain.com/sites/bi/Reports/My report Name.rdl')
w3wp!library!ca!05/05/2016-08:33:27:: i INFO: Initializing EnableExecutionLogging to 'True' as specified in Server system properties.
w3wp!notification!ca!05/05/2016-08:33:27:: i INFO: Notification 3361bf99-a2ce-4013-94eb-f33a4739fee4 completed. Success: True, Status: The file "My report Name Export.xlsx" has been saved to the "\\server\path$\path\path2" file share., DeliveryExtension: Report Server FileShare, Report: My report Name.rdl, Attempt 0