Some kind of security issue I’m sure. The user specified in the error has all rights that I know to give.
Program Ice.Services.Lib.RunTask raised an unexpected exception with the following message: RunTask: The permissions granted to user ‘ABC\UserName’ are insufficient for performing this operation. —> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user ‘ABC\UserName’’ are insufficient for performing this operation
Did you try just deleting the excel version of the report?
The “excel” version of the file didn’t exist
Then it sounds like the issue wasn’t the user accessing it, but rather it being created from the base (i.e. PDF) version.
Can any other user run that report and style as an XLS output?
For the record, this is a BAQReport I’m building for a user. I tested Excel and Excel+Map and both of those work but neither Excel-Data Only or Excel-Data Only+Map. This is a new SSRS server for us though which is why I’m thinking a setting somewhere.
Randy when you use Excel-Data the Service Account that SSRS Runs under, the same account you configured in the SSRS Tab in Admin Console – tends to create additional .rdl files (temporary ones) in the same folder where the Report Style is pointing to… I assume if that Service Account doesnt have the right R/W Permissions it simply can’t create those files hence the failure.
Yup, Aaron found a folder I missed when checking permissions. It’s good to have a second set of eyes sometimes to double check. 
Just curious, what do you mean by “folder”?
An actual folder on a path on the App server?
Or a virtual folder in Reports DB?
Ah I see you guys work together, I didn’t notice until now 
both Elkay
Virtual folder in Reports DB via browser:
Yup, Elkay saved me when Siffron was moving off of Epicor to Nav.
I didn’t realize that you had to (or could) set security on those. Is it strictly a windows thing?
And do you have to make sure individual AD users/groups have access, or just a specific account used by the E10 App?
So far as I can tell, you only need to set the service account used by the app pool.
We did have to set permissions for me and Randy in order to edit the reports, however.
Just adding to this, 6 years later… we ran into this issue earlier this week, and the issue was directly related to the permissions that were set on our SRSS Report Server.
When we set the user/password privileges there correctly, this was resolved. We had updated the report server and missed this. Oddly, it still did allow us to print preview the PDFs, but not the Excel Output.
FWIW