SSRS: A call to SSPI failed, see inner exception.Mail will not be resent

Question

Disclaimer: I'm no SQL/SSRS expert, but a user trying to resolve an issue.
SQL 2016 with SSRS and a 3rd party Report Manager application. We use this to schedule reports from a db, of servers/services and hardware for clients. I can pull manual reports fine, but unable to send them via email.
I have been unable to get this resolved with the aid of the provider. Their tool runs all the checks fine and should be able to email reports, however there seems to be no connection happening to the mail provider.
From the log file at C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\LogFiles

at Microsoft.ReportingServices.EmailDeliveryProvider.EmailProvider.Deliver(Notification notification)
notification!WindowsService_2!22a4!09/29/2021-20:10:40:: e ERROR: Error occurred processing subscription 535f9137-ae4a-49b8-882b-de1dbe7b5c55: Failure sending mail: A call to SSPI failed, see inner exception.Mail will not be resent.
notification!WindowsService_2!22a4!09/29/2021-20:10:40:: i INFO: Notification fd1f1cf6-1a71-4924-9ca6-77db5ac2868d completed. Success: False, Status: Failure sending mail: A call to SSPI failed, see inner exception.Mail will not be resent., DeliveryExtension: Report Server Email, Report: Site Overview Report, Attempt 0

I see a lot of issues around "A call to SSPI failed" but none appear to resolve this.

Any pointers or advice? I'm beginning to think the issue is with the error regarding subscription, but have no idea where to search.

Answer 1

Hi @Piet Moen ,
Judging from the error message, it seems to be related to TLS encryption. I don't think it has anything to do with the report server and subscription permissions.
I am sorry that I may not be able to give any advice on TLS encryption, you may need to seek the help of experts in this area. For enabling TLS1.2, you can refer to: How to enable TLS 1.2.
For any issues related to SSRS, please feel free to let me know.
Best Regards,
Joy

---

If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

A SSPI = "Security Support Provider Interface" is always a kind of permission problem, e.g. a Kerberos delegation problem, double hop, missing SPN = "Server Principal Name" registration.
Check all that points with your IT infrastructure guys.