SSRS is Not Sending Emails: 10 Tested Ways to Fix it

This issue is usually due to lack of permissions or improper configuration

Reading time icon 5 min. read


Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team. Read more

What to do if SSRS is not sending emails

When SSRS (SQL Server Reporting Services) fails to send emails, that’s usually due to improper SMTP server configuration. You should also check the SSRS permissions. There are a lot more possible cause but we covered all with the solutions below.

What can I do if SSRS is not sending emails?

1. Check the SMTP server configuration

  1. Open the Reporting Services Configuration Manager on your SSRS server.
  2. Go to the Email Settings section.
  3. Verify the SMTP server settings, including the SMTP server name, port, and authentication method.
  4. Ensure Use SSL checkbox is ticked if your SMTP server requires a secure connection.
  5. Save the settings and restart the Reporting Services.

Ensuring that your SMTP server settings are correctly configured will allow SSRS to communicate properly with your email server, facilitating successful email delivery.

2. Ensure proper permissions

  1. Open the Reporting Services Configuration Manager.
  2. Go to the Service Account section.
  3. Ensure the service account used by SSRS has sufficient permissions to send emails.
  4. If using an Azure Active Directory, ensure the account is properly registered and has required permissions.

Correct permissions are crucial for the seamless sending of emails by SSRS, as insufficient permissions can block the email-sending process.

3. Update and configure .NET Framework for TLS 1.2

  1. Open the Registry Editor by typing regedit in the Run dialog (Win+R).
  2. Navigate to the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v4.0.30319
  3. Add or update the following DWORD values:
    • SystemDefaultTlsVersions = 1
    • SchUseStrongCrypto = 1
  4. Repeat these steps for the v2.0.50727 key.
  5. Restart the server to apply the changes.

Enabling TLS 1.2 ensures a secure and compatible connection with modern SMTP servers, potentially resolving many mail sending issues.

4. Check the log files for errors

  1. Navigate to the log files directory, usually found at: C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\LogFiles
  2. Open the latest log file and search for any errors related to email sending.
  3. Identify the error message and take corrective action based on the error details.

Log files provide detailed error messages which can help pinpoint the exact issue causing the failure in sending emails.

5. Use an alternative SMTP relay service

  1. Sign up for an SMTP relay service such as AuthSMTP.
  2. Configure SSRS to use the new SMTP relay server details in the Reporting Services Configuration Manager.
  3. Update the SMTP server, port, and authentication details as provided by the relay service.
  4. Save your changes and attempt to send a test email.

Using a reliable SMTP relay service can bypass issues caused by specific SMTP servers, ensuring consistent email delivery.

6. Restart the SQL server Reporting Services

  1. Open the Services Management Console by typing services.msc in the Run dialog (Win+R).
  2. Locate and select the SQL Server Reporting Services service.
  3. Right-click the service and select Restart.

Restarting the Reporting Services can resolve temporary glitches and refresh the service’s ability to send emails.

7. Validate the email address and addresses format

  1. Double-check the email addresses in the subscription settings for any typos.
  2. Ensure multiple email addresses are separated by semicolons (;).
  3. Validate that all email addresses conform to standard email formats.

Correct and properly formatted email addresses are essential for successful email delivery.

8. Investigate and resolve specific error codes

  1. Check the SSRS logs for specific error codes such as System.Net.Mail.SmtpException.
  2. Search for the error code online to find specific solutions or workarounds.
  3. Apply the recommended fixes based on the error code.

Addressing specific error codes can provide targeted solutions for issues that are hindering the email sending process.

9. Change email subscription owner

  1. Open SQL Server Management Studio (SSMS).
  2. Run the following query to identify the current owner: SELECT u.UserName, s.SubscriptionID FROM ReportServer.dbo.Subscriptions s INNER JOIN ReportServer.dbo.Users u ON s.OwnerID = u.UserID;
  3. Update the owner to a valid account: BEGIN TRAN DECLARE @newid UNIQUEIDENTIFIER; SELECT @newid = UserID FROM ReportServer.dbo.Users WHERE UserName = 'newuser'; UPDATE ReportServer.dbo.Subscriptions SET OwnerID = @newid WHERE OwnerID = (SELECT UserID FROM ReportServer.dbo.Users WHERE UserName = 'olduser'); COMMIT TRAN

Changing the ownership ensures that outdated or invalid user accounts do not block the email subscription process.

10. Use PowerShell to test email sending

  1. Open a PowerShell window on the server.
  2. Run the following command: Send-MailMessage -SmtpServer smtp.yourserver.com -To '[email protected]' -From '[email protected]' -Subject 'Test Email' -Body 'This is a test email.'
  3. Check if the test email is received.

Using PowerShell allows you to manually verify if the email configuration is correctly set up and working.

By following these steps, you should be able to resolve most issues related to SSRS not sending emails. To prevent future issues, regularly check your SMTP server settings and ensure your SSRS service account has the necessary permissions.

If you cleared out this issue, follow our guide on how to set up a SMTP server for Office 365. If you get a SMTP authentication error, click the highlighted link to learn how to fix it.

Hit the comments below to let us know if our guide help you fix the SSRS not sending emails problem.

More about the topics: Email error, SMTP

User forum

0 messages