Below you will find error codes and error messages returned to a System Administrator user when they click the Test Connection button within the MS Exchange setup page while MSGraph is selected as the integration library.
Important Information
MS Graph Exchange Synchronization is only available when using Penelope 4.21.1.0 and above. If you have any questions please contact the Penelope Support Team.
Error Codes, Messages, Descriptions and Ref ID’s
Exchange Error Code: These are the error codes within the Penelope code base that are associated with these errors.
Error Message: This is what is actually displayed to the System Administrator within Penelope.
Description of Cause: This is the scenario that will cause this error message.
Ref ID: An ID of the row that can be referred to when mentioning individual error messages.
Exchange Error Code |
Error Message |
Description of Cause |
Ref ID |
FAILURE_TO_RETRIEVE_PERMISSIONS |
Unable to connect to Exchange due to invalid access token. Please contact the Penelope Support Team. |
Occurs when we are unable to retrieve the permissions of the app from the current MS Graph access token, either because the token was empty, we are unable to decode the token string or it is missing the ‘Roles’ array within its decoded payload. In any case. Please contact the Penelope Support Team. |
1 |
INCORRECT_APP_PERMISSIONS |
Unable to connect to Exchange because Application Id <id> is invalid. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant. |
This occurs when you enter an invalid app id. |
2 |
INCORRECT_APP_PERMISSIONS |
Unable to connect to Exchange because Tenant Id <id> is invalid. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant. |
This occurs when you enter an invalid tenant id. |
3 |
INCORRECT_APP_PERMISSIONS |
Unable to connect to Exchange because the secret is not correct. |
This occurs when you enter an invalid client secret. |
4 |
INCORRECT_APP_PERMISSIONS |
Unable to connect to Exchange because the configured application is missing required permissions. Must at least have ‘Calendar.ReadWrite’ and ‘User.Read.All’. |
This occurs whenever Penelope encounters a 403 Forbidden error from MS Graph and it then checks the permissions set by the current access token against what the expected roles are. The values in brackets will reflect what permissions are missing from the Azure app. If the app has the permissions assigned but they are not consented to, they do not show up in the access token and therefore would show up in the error message. |
5 |
FAILURE_TO_RETRIEVE_ENTITY |
Unable to connect to the Exchange because there is no user with email <attempted_email> |
This occurs when the email entered for Test Connection is not within the tenant directory of the configured azure app. |
6 |
FAILURE_TO_RETRIEVE_ENTITY |
Unable to connect to Exchange |
This occurs when the MS Graph SDK gives back a null User object. |
7 |
FAILURE_TO_RETRIEVE_ENTITY |
Unable to connect to Exchange because the user <ids> does not have a valid calendar. |
This occurs when MSGraph returned an empty page when searching for Calendars for the passed in user. |
8 |
FAILURE_TO_RETRIEVE_ENTITY |
Unable to connect to Exchange because user <ids> does not have a valid calendar <name>. |
This occurs when MSGraph returned no calendars with the name ‘Calendar’ for the passed in user. This is the default personal calendar name so this should always exist. |
9 |
FAILURE_TO_RETRIEVE_ENTITY |
Unable to connect to Exchange |
A generic cannot be found error to occur when MS Graph returns a 404 unexpectedly when adding or deleting an event. |
10 |
INVALID_TIMEZONE |
Unable to connect to Exchange because the configured Penelope timezone is not compatible with the user’s Outlook mailbox settings. Please contact the Penelope Support Team. |
This occurs when the JVM timezone of Penelope comes back as a string that is not supported by MS Graph. |
11 |
MULTIPLE_POSSIBLE_ENTITIES_FOUND |
Unable to connect to Exchange because user <ids> has multiple calendars with the name <name>. |
This occurs when multiple calendars of the same name are found for the passed in User. Penelope is not configured to have a user with multiple calendars with the same name. |
12 |
ACCESS_TO_ITEM_DENIED |
Unable to connect to Exchange because user <id>’s calendar is not editable |
This occurs when the personal calendar of a user (the calendar with the name ‘Calendar’) returns a CanEdit attribute value of false, meaning Penelope is unable to add/delete events from the found calendar. |
13 |
INVALID_REQUEST_DATA |
Unable to connect to Exchange due to unknown MS Graph error. Please contact the Penelope Support Team. |
Please contact the Penelope Support Team. |
14 |
UNKNOWN_ERROR |
Unable to connect to Exchange due to unknown MS Graph error. Please contact the Penelope Support Team. |
Possible causes: |
15 |
no error code |
Unable to connect to Exchange because the Secret is not correct. The Secret is set to temporary value. |
This occurs when the user has not saved an application secret previously and they try to save the delegated temporary secret value of ‘temp-********-secret’. |
16 |
Comments
0 comments
Please sign in to leave a comment.