Users of Sisense receive a variety of automated emails from Sisense. Sisense emails fall into two categories of emails:

System Emails: These emails include activation emails, password recovery emails, and updates regarding published dashboards.

Email Reports: These emails are dashboard reports in PDF/PNG format that are sent manually or according to a schedule you define.

The following steps will help you troubleshoot email-related issues such as emails not being sent/received.

Step 1 – Verify that Emails are Configured Correctly
Step 2 – Send a Test Email
Step 3 – Export the Dashboard to PDF
Step 4 – Verify System Load 
Step 5 – Verify Port Bindings
Step 6 – Custom Email Server
Step 7 – Verify the default.yaml Settings
Step 8 – Check Rebranded Email Settings
Step 9 – Verify Spam Protection

Step 1 – Verify that Emails are Configured Correctly

You may not receive emails from Sisense due to configuration issues. There are four potential configuration issues that can occur.

  1. Activate Sisense Emails: (All email types) Make sure that Sisense emails have been enabled within the System Configuration page of the Admin menu.
    sendemail
  2. Verify that the user you want to share the report with is selected: (Email reports only)  You can verify which users are selected by checking the wifitab  icon associated with their name. If the wifitab  icon is not highlighted, the user will not receive an email report. You can select the user by clicking the icon.
    shareduser
    If you are sharing your reports with a group, verify that all the members are included. An Administrator can check the list of users in a group from the Admin page by Selecting Admin > Groups > Edit.
    admingroups
    modifygroup
  3. Data Security: (Email reports) Verify with your Sisense Administrator that the user you want to share the report with has access rights to the dashboard’s ElastiCube.
  4. Verify Build Success: (Email reports only) If you send a report following each build, verify that dashboard’s ElastiCube was built successfully.

Step 2 – Send a Test Email

If you do not receive any emails from Sisense, email reports or system emails, you can verify whether or not you can receive emails from Sisense by sending a report to yourself. To send an email report, click the sharedicon icon of a dashboard and in the bottom-left corner of the the window, click Send me a report now to test the email’s functionality. If you receive an email, but do not receive your scheduled reports, see Contacting Technical Support.

sendreport

Step 3 – Export the Dashboard to PDF

This step is relevant for email reports. If your issue is related to system emails, goto Step 5.

If you cannot receive any email reports,  this may indicate a conflict with your plugins. By exporting your dashboard to PDF, you can verify if email reports are being sent and if not, what is the source of the problem.

  1. Check Plugins: You can check if your plugins are interfering with your email reports by renaming the plugin folder located at C:\Program Files\Sisense\PrismWeb\plugins to another name, for example, to “plugin1”. If the email succeeds, this indicates that one of your plugins is interfering with your emails and needs to be corrected.
  2. Check SSL: After checking your plugins, if you still do not receive dashboard reports, this may indicate a problem with SSL. If you are using SSL, follow the instructions in this forum post.

Step 4 – Verify System Load 

This step is relevant for email reports. If your issue is related to system emails, goto Step 5.

Verify that the system is not overloading by sending too many reports at the same time. For example, if your email reports are all scheduled for 5:00pm, this may overload the email server. You can verify if this is causing problems by scheduling email loads throughout the day.

Step 5 – Verify Port Bindings

Verify that your Port bindings are configured properly by using an HTTP port that is not used by other web sites on your IIS.
If you have a DNS configured make sure you have the required certificate for it.

Step 6 – Custom Email Server

This step is relevant for all email types.

By default, Sisense uses Mandrill for emailing services. Verify that you can reach mandrill.com from the server. If you can’t, this might indicate a network security restriction. Verify that the IP addresses listed here are whitelisted. If your network security restrictions prevent you from communicating with Mandrill email services, you can implement your own custom email server, see Setting Up a Custom Email Server.

Step 7 – Verify the default.yaml Settings

The default.yaml settings file is located in: C:\Program Files\Sisense\PrismWeb\vnext\config. These settings define which path Sisense uses for exporting emails.

‘webServer’ -> iisPort should be the same port as the binding in the IIS.

wbserver1

‘exporting’ –> host = “localhost”, port = “default”.
Note that the ‘exporting’ address should be accessible from inside the server, i.e. if you can’t access localhost from your browser, but you can access it using a DNS, change the export settings to use the DNS.

wbserver2

Step 8 – Check Rebranded Email Settings

This step is relevant for all email types.

If you have changed the default Sisense configuration, for example, when rebranding Sisense, run the following requests through REST API admin page

Verify the ‘senderEmail’ is configured correctly and not listed as ‘string’ or another erroneous sender. This can happen when someone uses POST /branding and does not enter a valid email address or leaves the value as ‘string’.

If you are whitelabeling Sisense and rebranding your emails and experience email problems, review the following steps as described here.

Step 9 – Verify Spam Protection

This step is relevant for all email types.

Make sure that emails sent from Sisense are whitelisted and not filtered by any spam protection. If you do not have access to your company’s Spam folder or Sisense emails may be filtered before arriving to your inbox, consult with your company’s IT administrator to verify that Sisense emails are not being filtered by your company’s Spam filters.

If none of the above steps have resolved the issue please contact Sisense Technical Support. When contacting Sisense Technical Support, please provide the following information to reduce the amount of time it takes to resolve your issue:

  • Time: When the issue occurred.
  • Logs: When encountering an error while trying to send email reports, Sisense maintains error logs that you can review or send to Sisense Technical Support. The logs are located at …Program Files\Sisense\PrismWeb\vnext\iisnode.
  • Steps Taken: List each of the steps you have taken to when trying to resolve the issue yourself.