Impersonation Issue (FORMERLY: Report Style - Unable to create SSRS Report)

jhecker · December 21, 2023, 7:19pm

EDIT

New information has been discovered - This looks like it may be a place to start looking:

Does anyone know where to begin with trying to figure out the root cause of this?

ORGINAL POST

I am getting an error when in Report Style Maintenance creating a new Style for an RDD based Report. When I click on Actions > Create SSRS Report, the following is displayed:

The permissions granted to user 
'DOMAIN\epicoradmin' are insufficient for performing this operation. ---> 

Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: 
The permissions granted to user
'DOMAIN\epicoradmin' are insufficient for performing this operation.

I have checked IIS to ensure that the Application Pool has the Identity of that account, which it does:

I also checked the permissions for every folder on the SSRS Web Interface (starting at the root and going all the way to “CustomReports”, and that looks good to go as well:

So I checked the Computer User and Groups permissions:

What am I missing? As far as I can tell, DOMAIN\epicoradmin has permissions to everything.

dcamlin · December 21, 2023, 7:24pm

Does your Epicor “User Account” have permission?

jhecker · December 21, 2023, 7:25pm

Checked that too…yup, it is

jhecker · December 21, 2023, 7:30pm

I am able to log into the Reporting Services using SQL Management Studio with the DOMAIN\epicoradmin credentials as well.

Dragos · January 4, 2024, 3:04pm

I’m not an expert but I would check the following:

user & password are correct (i think you have this one)
you have exceptions added for the SQL ports in your SQL server Windows firewall
the user has the correct rights in SQL server. I have it set as public & sysadmin. Also, the user is mapped for all DBs with dbo schema as default

jhecker · January 4, 2024, 3:35pm

The account is set up with permissions in SQL:

And on the DB itself:

…and as I am typing this, I figured it out…it would seem that the Application Pool had an incorrect password set…how that would allow for [most] everything to still work is beyond me, but I digress…