When I run a Report using a Windows file subscription, I get this error: Failure writing file \\PGDT\Users\Patrick\Documents\Microsoft Press\Rs2008sbs\Workspace\Pacific Reseller Sales Margin Analysis Linked.pdf : An impersonation error occurred using the security context of the current user. As I am using my own id in the subscription and it owns the target shared folder, I do not see how I can get an impersonation error. I am sure the user id (PGDT\Patrick) and password are correct in the subscription. I am also pretty sure the target shared folder name is correct and I have checked it by pasting it into Explorer. The folder shows as expected. What could the problem be? Unattended Execution Account? PG A bit of experimentation by trial and error often helps get round problems.

Hi Pagtrick.Grant01, Thanks for the question. What’s the service account in your Reporting Services Configuration Manager? If it is one built-in account, please try to change to your domain account id. Thanks, Sharp Wang Please remember to mark the replies as answers if they help you and unmark them if they provide no help.

Hi Sharp Wang Thanks for the suggestion. I re-ran the windows fileshare subscription and got the same impersonation error message. I tried again after making the changes below suggested on another thread and got the same impersonation error. To fix the issue, please follow these steps: 1. On Reporting Services report server, open Local Group Policy Editor by running command "gpedit.msc" 2. Go to this configuration: Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment\ 3. Double-click "Allow log on locally" 4. Now, add the user(the user to access the file shard) to the list. This did seem to be an avenue worth exploring. PG A bit of experimentation by trial and error often helps get round problems.

Hi Sharp Wang Thanks for the suggestion. I re-ran the windows fileshare subscription and got the same impersonation error message. I tried again after making the changes below suggested on another thread and got the same impersonation error. To fix the issue, please follow these steps: 1. On Reporting Services report server, open Local Group Policy Editor by running command "gpedit.msc" 2. Go to this configuration: Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment\ 3. Double-click "Allow log on locally" 4. Now, add the user(the user to access the file shard) to the list. This did seem to be an avenue worth exploring. PG A bit of experimentation by trial and error often helps get round problems. Hadyou changed the services account to one domain account before you re-run the subscription? Thanks, Sharp Wang Please remember to mark the replies as answers if they help you and unmark them if they provide no help.

It looks there are 2 issues. First one being unattended exection account which will be solved with adding a user account and giving account policies "Allow Log On Locally" and the second issue could be with the permissions. Can you make sure the shared directory has access to the reporting services user account.Thank You, Sudhakar

Hi Sudhaker There might well be two or even more issues. There can be potentially at least four accounts permissions to consider. I am sure Unattended Execution account is one because it is needed to run the subscription. I have set up the Unattended Execution Account with my domain user id. Although this user id has most permissions anyone may ever want, I get the error below when trying to edit or view the subscription details. I also get it when running reports: The report server has encountered a configuration error. Logon failed for the unattended execution account. (rsServerConfigurationError) Get Online Help Log on failed. Ensure the user name and password are correct. (rsLogonFailed) Get Online Help Could not load file or assembly 'BCMLogon, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417) Required permissions cannot be acquired. What permissions does the domain account for Unattended Execution Account need? It has System Admin in Report Server Manager and on the PC. It has read permissions on the database used for reporting and read/write on the target directory. It also has permssisions to log on locally in Group Policy. What do you mean by the Reporting Services User Account? Is the account used to run Reporting Services (currently Network Services), the account to run the SQL Agent that triggers the job (currently Network Service), the Unattended Execution Account (currently my user id with a lot of permissions) or the account set up in the subscription (also currently my user id.) I think the main problem here is I cannot find anywhere in the Microsoft Documentation which makes it clear which accounts need what permissions to get unattended execution to work...that must be the key to getting this to work. PG A bit of experimentation by trial and error often helps get round problems.

Yes I changed the service account before re-running subscription. Then I changed it back to Network Service as it had no effect.PG A bit of experimentation by trial and error often helps get round problems.

Hi, Are you able to create subscriptions for the report with other like EMAIL and try. This still looks like unattended execution account issue. As far as i know this is not the issue with polciy this looks like user authentication itself is failing. Thank You, Sudhakar

Hi Pagtrick.Grant01, The account must be a network account, with access to the folder you are saving the file to. In additional, the account requires rights to log on locally on the Reporting Services computer. Also pay attention to the challenge-response authentication had mentioned in this article: SSRS File Share provider in a Workgroup Thanks, Sharp Wang Please remember to mark the replies as answers if they help you and unmark them if they provide no help.

Hi Sudhakar I am unable to create subscriptions with email. I can get other emails from SQL Server usach as Job completion notifications. I had thought the problem might be caused by the Clear Text authentication my ISP (BT) uses. I have tried all the possible changes to the Report Server config file to no avail. On the Unattended Execution Issue, the behaviour is odd. If I set up an Unattended Execution Account in the Report Configuration Tool, I can navigate through folders on Report Manager - BUT when I run reports, they hang aand never complete. As far as I can tell access to the database is well and truly blocked. PG A bit of experimentation by trial and error often helps get round problems.

Hi Sharp Wang What exactly do you mean by a network Account? (I am running SQL Server on a PC with Windows 7 and most of the time it works quite well.) Does this mean it will never work on a PC? Quote: Turns out that file share delivery provider doesn’t currently support challenge-response authentication. Instead, It impersonates the user before making the connection to the underlying machine. Because of this, in a workgroup environment, the file share deliveries will not work. PG A bit of experimentation by trial and error often helps get round problems.

Hi Pagtrick.Grant01, The account must be a network account, with access to the folder you are saving the file to. In additional, the account requires rights to log on locally on the Reporting Services computer. Also pay attention to the challenge-response authentication had mentioned in this article: SSRS File Share provider in a Workgroup Thanks, Sharp Wang Please remember to mark the replies as answers if they help you and unmark them if they provide no help.

Hi Sharp Wang What exactly do you mean by a network Account? (I am running SQL Server on a PC with Windows 7 and most of the time it works quite well.) Does this mean it will never work on a PC? Quote: Turns out that file share delivery provider doesn’t currently support challenge-response authentication. Instead, It impersonates the user before making the connection to the underlying machine. Because of this, in a workgroup environment, the file share deliveries will not work. PG A bit of experimentation by trial and error often helps get round problems.

Hi Pagtrick.Grant01, Thanks for the reply. The article means that you not only need to use one domain account, but also need the pc machine join to the domain. Best Regards, Sharp Wang Please remember to mark the replies as answers if they help you and unmark them if they provide no help.

OK, looks like I will have to install the product on a server.PG A bit of experimentation by trial and error often helps get round problems.