|
2 | 2 | title: UnknownIncomingEmailIntegrationError during server-side synchronization |
3 | 3 | description: Solves the UnknownIncomingEmailIntegrationError logged in a Microsoft Dynamics 365 mailbox record. |
4 | 4 | ms.reviewer: |
5 | | -ms.date: 12/26/2024 |
| 5 | +ms.date: 12/31/2024 |
6 | 6 | ms.custom: sap:Email and Exchange Synchronization |
7 | 7 | --- |
8 | 8 | # UnknownIncomingEmailIntegrationError logged in mailbox alerts in Microsoft Dynamics 365 |
9 | 9 |
|
10 | | -This article provides a solution to the `UnknownIncomingEmailIntegrationError` error code logged in mailbox alerts in Microsoft Dynamics 365. |
| 10 | +This article provides a solution to the `UnknownIncomingEmailIntegrationError` error code logged in the [Alerts](/power-platform/admin/monitor-email-processing-errors#view-alerts) section of the mailbox in Microsoft Dynamics 365. |
11 | 11 |
|
12 | 12 | _Applies to:_ Microsoft Dynamics 365 |
13 | | -_Original KB number:_ 4471762 |
| 13 | +_Original KB number:_ 4471762, 4556408, 4551335, 4551320, 4471947, 4471980 |
14 | 14 |
|
15 | | -## Symptoms |
16 | | - |
17 | | -When [viewing the Alerts section](/power-platform/admin/monitor-email-processing-errors#view-alerts) within a mailbox record in Dynamics 365, you might see the following message: |
18 | | - |
19 | | -> An unknown error occurred while receiving email through the mailbox "\<Mailbox Name>". The owner of the associated email server profile \<Profile Name> has been notified. The system will try to receive email again later. |
20 | | -> |
21 | | -> **Email Server Error Code:** Exchange server returned UnknownIncomingEmailIntegrationError -2147220956 exception. |
22 | | -
|
23 | | -## Cause |
24 | | - |
25 | | -The error code indicates an IsvUnexpected error. It typically means that a custom plugin or workflow throws an error, causing the item creation to fail. |
26 | | - |
27 | | -## Resolution |
28 | | - |
29 | | -To solve this issue, check if any custom plugins or workflows are running synchronously when creating the record type (email, appointment, contact, or task) mentioned in the error. If a plugin or workflow causes an error during record creation, [server-side synchronization](/power-platform/admin/server-side-synchronization) can't create the record successfully. |
30 | | - |
31 | | -The following steps can help you identify any workflows or plugins in your organization running during email creation. By replacing `Entity` with the appropriate record type, these steps can also be used for other entities like appointments and tasks. |
32 | | - |
33 | | -### Workflow |
34 | | - |
35 | | -1. In the Dynamics 365 web application, navigate to **Settings**, and then select **Processes**. |
36 | | -2. Change the view to **Activated Processes**. |
37 | | -3. Sort on the **Primary Entity** column and look for any rows with **Email** as the primary entity and **Workflow** as the category. |
38 | | - |
39 | | - Instead, you can use the filtering options in the grid to filter on **Category = Workflow** and **Primary Entity = Email**. |
40 | | - |
41 | | -4. Open each workflow you find that meets the preceding criteria (if any). |
42 | | -5. If the **Start when** options have the **Record is created** option selected, and the **Run this workflow in the background (recommended)** option isn't selected, this workflow might be the cause. |
43 | | - |
44 | | - > [!NOTE] |
45 | | - > If you're troubleshooting this type of error with an appointment, contact, or task, also check if the workflow is configured to run during the update of that type of record. |
46 | | -
|
47 | | -6. Select **Process Sessions** on the left side of the page and look for failures related to the email that wasn't created successfully. |
48 | | - |
49 | | -### Plugin |
50 | | - |
51 | | -1. In the Dynamics 365 web application, navigate to **Settings** > **Customizations**, and then select **Customize the System**. |
52 | | -2. Select **Sdk Message Processing Steps**. |
53 | | -3. Sort on the **Primary Object Type Code (SdkMessage Filter)** column and look for any rows for the **Email** entity. |
54 | | -4. If the **Execution Mode** in those rows is set to **Synchronous**, it might interfere with the email creation. |
55 | | - |
56 | | -If you're able to reproduce the issue consistently, you can try disabling the workflow or plugin temporarily to determine if it's the cause of the problem. |
57 | | - |
58 | | -## Other email server error codes |
| 15 | +## The email server error codes |
59 | 16 |
|
60 | 17 | |Email server error code|Cause|Resolution| |
61 | 18 | |--|--|--| |
| 19 | +|UnknownIncomingEmailIntegrationError -2147220956|The error code indicates an IsvUnexpected error. It typically means that a custom plugin or workflow throws an error, causing the item creation to fail.|[Check if any custom plugins or workflows are running synchronously when creating the record type (email, appointment, contact, or task) mentioned in the error.](unknownincomingemailintegrationerror-2147220891.md#resolution) | |
62 | 20 | |UnknownIncomingEmailIntegrationError -2147220970|This error might occur if [server-side synchronization](/power-platform/admin/server-side-synchronization) tries to retrieve emails but receives an unexpected error. This is typically a temporary issue, and the emails will be retrieved successfully in the next synchronization cycle (typically 15 minutes.)|<ul><li>If this message doesn't persist in the next synchronization cycle (typically 15 minutes), ignore this warning.</li> <li>If this message persists, contact Microsoft Support through the **Help + Support** experience in the [Power Platform admin center](https://admin.powerplatform.microsoft.com/support).</li></ul>| |
63 | 21 | |UnknownIncomingEmailIntegrationError -2147218677|This error occurs if an invalid email address is included in the **To** or **Cc** line of an email.|Review the email message that received this error and verify that all email addresses in the **To** and **Cc** lines are [valid](https://tools.ietf.org/html/rfc5322#section-3.4.1).| |
64 | 22 | |UnknownIncomingEmailIntegrationError -2147220192|This error indicates the owner of the queue doesn't have sufficient privileges to work with the queue. The user might lack sufficient **Read** access to the `Queue` entity.|Verify that the user's Dynamics 365 security role has **Read** access to the `Queue` entity. Within a Dynamics 365 security role, privileges for the `Queue` entity are located on the **Core Records** tab. <br><br> **Note**: If you verify that the owner of the mailbox record has **Read** access to the `Queue` entity, check if there are other Dynamics 365 users or queues that receive the same email. You might also need to verify privileges for those users.| |
|
0 commit comments