Share via

SSRS 2016 (V13.0.6470.1) Error: Failure sending mail: An internal error occurred on the report server.

Brian 1 Reputation point
2026-04-13T21:38:01.45+00:00

Receiving issue with SSRS e-mail subscriptions. Can send e-mails via the shared mailbox using PowerShell on same server successfully. Issue is only when trying to send via SSRS 2016. It started occurring 2 days ago and was working prior. Makes me think it's either an update or maybe some permission configurations. The full error message from SSRS is:

Failure sending mail: An internal error occurred on the report server. See the error log for more details.Mail will not be resent.

Digging deeper:

library!ReportServer_0-1!94c!04/13/2026-14:12:56:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.NotEnabledException: , Microsoft.ReportingServices.Diagnostics.Utilities.NotEnabledException: The requested functionality is not currently enabled.;

extensionfactory!ReportServer_0-1!94c!04/13/2026-14:12:56:: i INFO: Skipped instantiating Report Server PowerBI report server extension. Extension was not enabled.

schedule!WindowsService_0!1ce0!04/13/2026-14:13:01:: i INFO: Handling event with data: TimeEntered: 04/13/2026 14:13:01, Type: Event, EventType: TimedSubscription, SubscriptionID: eab3106c-0d2c-40e5-82aa-cd892654ced3.

library!WindowsService_0!1ce0!04/13/2026-14:13:02:: i INFO: Schedule 5b010bfe-5fc4-425a-857b-dd8d9350e77f executed at 04/13/2026 14:13:02.

schedule!WindowsService_0!1ce0!04/13/2026-14:13:02:: i INFO: Creating Time based subscription notification for subscription: eab3106c-0d2c-40e5-82aa-cd892654ced3

library!WindowsService_0!1ce0!04/13/2026-14:13:02:: i INFO: Schedule 5b010bfe-5fc4-425a-857b-dd8d9350e77f execution completed at 04/13/2026 14:13:02.

library!WindowsService_0!1228!04/13/2026-14:13:03:: i INFO: Initializing EnableExecutionLogging to 'True' as specified in Server system properties.

notification!WindowsService_0!1228!04/13/2026-14:13:03:: i INFO: Handling subscription eab3106c-0d2c-40e5-82aa-cd892654ced3 to report RPT_Its_Anameab, owner: Domain\myUser, delivery extension: Report Server Email.

library!WindowsService_0!1228!04/13/2026-14:13:03:: i INFO: RenderForNewSession('/RPT/RPT_Its_Anameab/RPT_Its_Anameab')

library!WindowsService_0!1228!04/13/2026-14:13:04:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.WindowsAuthz5ApiException: , Microsoft.ReportingServices.Diagnostics.Utilities.WindowsAuthz5ApiException: Windows returned a ERROR_ACCESS_DENIED error when Reporting Services attempted to call the Windows Authz APIs. If this issue persists the Reporting Services account may not possess permission to perform authentication checks. Check the Windows Authz documentation for more information and details on diagnosing issues. Authz method: AuthzInitializeContextFromSid, Error code: 5, UserName: Domain\myUser.;

library!WindowsService_0!1228!04/13/2026-14:13:04:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.WindowsAuthz5ApiException: , Microsoft.ReportingServices.Diagnostics.Utilities.WindowsAuthz5ApiException: Windows returned a ERROR_ACCESS_DENIED error when Reporting Services attempted to call the Windows Authz APIs. If this issue persists the Reporting Services account may not possess permission to perform authentication checks. Check the Windows Authz documentation for more information and details on diagnosing issues. Authz method: AuthzInitializeContextFromSid, Error code: 5, UserName: Domain\myUser.;

library!WindowsService_0!1228!04/13/2026-14:13:04:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: AccessCheck: Win32 error:6, Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details.;

library!WindowsService_0!1228!04/13/2026-14:13:04:: e ERROR: Report server dump occured. Exception: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., Message: , Unhandled Exception: False

library!WindowsService_0!1228!04/13/2026-14:13:04:: e ERROR: Report server unique dump occured. Exception: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., Message: , Unhandled Exception: False

library!WindowsService_0!1228!04/13/2026-14:13:07:: i INFO: Dump result: External dump process return code 0x20000001.

External dump process returned no errors.

Not sure what the error is or how to fix it. I've tried down the Windows Authz path but I'm not sure about how to configure that.

SQL Server Reporting Services
SQL Server Reporting Services

A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.

0 comments No comments

Answer recommended by moderator

Akhil Gajavelly 1,825 Reputation points Microsoft External Staff Moderator
2026-04-15T07:26:06.8566667+00:00

Hi @Brian ,

This isn’t really a mail issue the failure is happening earlier during report execution.

The key part in your log is: AuthzInitializeContextFromSid → ERROR_ACCESS_DENIED

In simple terms, SSRS is unable to validate the user (Domain\myUser) while running the subscription.

Since this started suddenly, I’d suggest checking:

  • whether the SSRS service account was changed
  • or if any recent patch/GPO update removed its access

Quick way to confirm: Try running the same report subscription using a different account (like your own or a known working account). If that works, it clearly points to a permission issue with the service account or that specific user context.

Once you confirm that, fixing the service account permissions should resolve the email failure as well.

This approach helps you prove the root cause quickly instead of changing settings blindly.

Thanks,
Akhil.

Was this answer helpful?


1 additional answer

Sort by: Most helpful
  1. AI answer

    2026-04-13T21:38:18.6266667+00:00

    The log shows a WindowsAuthz5ApiException on AuthzInitializeContextFromSid with ERROR_ACCESS_DENIED. This is a known issue with Reporting Services when the RS service account lacks required Windows authorization permissions. The mail error (Failure sending mail: An internal error occurred on the report server) is just the generic wrapper; the root cause is the Authz failure.

    To fix the problem, adjust the permissions for the account that runs the SSRS Windows service using one of the documented methods:

    Method 1 – Add the SSRS service account to required AD groups

    1. Identify the Windows account that the SQL Server Reporting Services Windows service runs under.
    2. In Active Directory Users and Computers, add that account to:
      • Pre-Windows 2000 Compatible Access group.
      • Windows Authorization Access Group.
    3. Restart the server (or at least restart the SQL Server Reporting Services service) so the new group memberships take effect.

    This guarantees that Reporting Services can access the TGGAU attribute and successfully call AuthzInitializeContextFromSid during subscription processing.

    Method 2 – Run SSRS under a domain user account If the service is currently running under a local or system account and changing group membership is not preferred:

    1. Configure the Reporting Services Windows service to run under a domain user account.
    2. Ensure that account has the necessary permissions in SQL Server and on the server.
    3. Restart the service and test the subscription again.

    After applying one of these methods, re‑run the failing subscription. The internal error should be resolved, and e‑mail delivery should succeed (assuming SMTP configuration itself is correct).


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.