You may occasionally encounter error messages while using Scheduled Reports. When these errors occur, you will receive alerts to ensure timely follow-up on unsent reports.
This article lists common error messages and how to fix them.
Below is a sample alert message.
| Error Message | Category | Description | Solution |
| The recipient email address does not match any client in your PSA. | Company slicer related | This indicates that the recipient email address you entered does not match any client in your PSA. | Please verify and update the recipient email address or client info in you PSA, so they match each other. |
| The client name associated with this email address in your PSA is empty. | Company slicer related |
This indicates that the company name retrieved from PSA for the recipient email address you entered is empty. | Please verify and update the recipient email address or client info in you PSA, so they match each other. |
| We could not find the client name associated with this email address. | Company slicer related | This indicates that the client name retrieved from the Contact List for the recipient email address you entered is null. | Please verify and update the email address and client info in the Contact List. |
| Recipient email address is not valid. | Email address error | This indicates that the recipient email address is invalid. | Please check and enter a correct recipient email address. |
| Permission error while opening the report, please open the schedule and save again to fix the issue. | Error opening the report | This indicates that the shared scheduled report has been deleted or moved. |
Please open the schedule and save again to fix the issue. |
| There is an authentication issue with the outgoing email mailbox. Please check the mailbox settings at Settings-System-Outgoing Mail. | Outgoing mailbox error | This indicates that authentication failed, and the user credentials were incorrect. |
Please check the mailbox settings at Settings-System-Outgoing Mail. |
| There is a configuration issue with the outgoing email mailbox. Please check the mailbox settings at Settings-System-Outgoing Mail. | Outgoing mailbox error | This indicates that your mailbox settings are incorrect. |
Please check the mailbox settings at Settings > System > Outgoing Mail. |
| Your outgoing email mailbox is either inactive, soft-deleted, or is hosted on-premise. Please check the mailbox settings at Settings-System-Outgoing Mail. | Outgoing mailbox error | This indicates that the mailbox is either inactive, soft-deleted, or is hosted on-premise. |
Please check the mailbox settings at Settings-System-Outgoing Mail. |
| The user account that authenticates your outgoing mailbox does not have the right to send mail on behalf of the "User Name" in Settings. Please ensure both accounts match in the mailbox settings at Settings-System-Outgoing Mail. | Outgoing mailbox error | This indicates that in your outgoing email mailbox settings, the user account used to submit this request does not have the right to send mail on behalf of the specified sending account. Cannot submit message. |
Please ensure both accounts match in the mailbox settings at Settings-System-Outgoing Mail. |
| There is an authentication issue with the outgoing email mailbox. Please check the mailbox settings at Settings-System-Outgoing Mail. | Outgoing mailbox error | This indicates that the email account has been disabled in your outgoing email mailbox settings. |
Please check the mailbox settings at Settings-System-Outgoing Mail. |
| SQL Error: An attempt was made to divide by zero in the SQL code. | SQL error |
This indicates that your SQL code has a divide by zero error. |
Please check and fix your measures in the widgets, then retry. |
| SQL Error: The column "xxx" could not be found in the database. Please verify the column name and try again. | SQL error | This indicates that the column name in your SQL code does not exist in the database. |
Please verify the column name and try again. |
| The report failed to open due to a timeout; please verify that all widgets in the report can be loaded correctly. | Timeout |
This indicates that your request may conflict with recovery operations, statement timeout, or the query may be too slow due to large data volume, or other issues resulting in timeout. |
Please verify that all widgets in the report can be loaded correctly. |