Skip to content

Commit 0ef7583

Browse files
authored
Merge pull request #7747 from MicrosoftDocs/lucciz01-improve-unknownincomingemailintegrationerror-2147220891.md
AB#2729: Update unknownincomingemailintegrationerror-2147220891.md
2 parents f9794ac + 30819d9 commit 0ef7583

2 files changed

Lines changed: 18 additions & 19 deletions

File tree

Lines changed: 17 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,11 @@
11
---
2-
title: UnknownIncomingEmailIntegrationError -2147220891
2+
title: UnknownIncomingEmailIntegrationError -2147220891 or 80040265
33
description: Provides a solution to an error that occurs within mailbox alerts in Microsoft Dynamics 365.
44
ms.reviewer:
5-
ms.topic: troubleshooting
6-
ms.date: 11/19/2024
5+
ms.date: 12/20/2024
76
ms.custom: sap:Email and Exchange Synchronization
87
---
9-
# UnknownIncomingEmailIntegrationError -2147220891 exception error appears within mailbox alerts in Microsoft Dynamics 365
8+
# UnknownIncomingEmailIntegrationError -2147220891 or 80040265 appears in mailbox alerts in Microsoft Dynamics 365
109

1110
This article provides a solution to an error that occurs within mailbox alerts in Microsoft Dynamics 365.
1211

@@ -15,7 +14,7 @@ _Original KB number:_   4466423
1514

1615
## Symptoms
1716

18-
When viewing the alerts section within a mailbox record in Dynamics 365, you see one of the following messages:
17+
When [viewing the alerts section](/power-platform/admin/monitor-email-processing-errors#view-alerts) within a mailbox record in Dynamics 365, you see one of the following messages:
1918

2019
- > "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.
2120
>
@@ -27,33 +26,33 @@ When viewing the alerts section within a mailbox record in Dynamics 365, you see
2726
2827
## Cause
2928

30-
Error code 80040265 and -2147220891 indicates an IsvAborted error.
29+
Error code 80040265 or -2147220891 indicates an IsvAborted error.
3130

32-
If you see the first message listed in the [Symptoms](#symptoms) section, it's typically caused by a workflow or custom plugin that runs on the creation of an email record.
31+
If you see the first message listed in the [Symptoms](#symptoms) section, it's typically caused by a workflow or custom plugin that runs when an email record is created.
3332

34-
If you see the second message listed in the [Symptoms](#symptoms) section, it's typically caused by a workflow or custom plugin that runs on the creation of an appointment, contact, or task record.
33+
If you see the second message listed in the [Symptoms](#symptoms) section, it's typically caused by a workflow or custom plugin that runs when an appointment, contact, or task record is created.
3534

3635
## Resolution
3736

38-
Check to see if you have any custom plugins or workflows that run synchronously on the creation of the record type mentioned in the error (ex. email, appointment, contact, or task). If a plugin or workflow is causing an error during the creation of the record, Server-Side Synchronization can't create the record successfully. The steps below can help you identify if there are any workflows or plugins in your organization that run during creation of an email. The same steps can be used for other entities like appointment if it's the record type that is failing to be created:
37+
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 is causing an error during record creation, server-side synchronization can't create the record successfully. The following steps can help you identify if there are any workflows or plugins in your organization that run during the creation of an email. Use the same steps for other entities like appointments and tasks by replacing the Entity with the appropriate record type.
3938

4039
### Workflow
4140

42-
1. Within the Dynamics 365 web application, navigate to **Settings** and then select **Processes**.
41+
1. In the Dynamics 365 web application, navigate to **Settings**, and then select **Processes**.
4342
2. Change the view to **Activated Processes**.
4443
3. Sort on the **Primary Entity** column and look for any rows with **Email** as the primary entity and **Workflow** as the category.
4544

46-
Instead, you can use the filtering options in the grid to filter on **Category = Workflow** and **Primary Entity = Email**
45+
Instead, you can use the filtering options in the grid to filter on **Category = Workflow** and **Primary Entity = Email**.
4746

48-
4. Open each workflow you find that meets the criteria above (if any).
49-
5. If the **Start when** options have the **Record is created** option is selected, and the **Run this workflow in the background (recommended)** option isn't selected, this workflow could potentially be the cause.
47+
4. Open each workflow you find that meets the preceding criteria (if any).
48+
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.
5049
6. Select the **Process Sessions** section on the left side of the page and look for any failures related to the email that wasn't created successfully.
5150

52-
### Plugins
51+
### Plugin
5352

54-
1. Within the Dynamics 365 web application, navigate to **Settings**, **Customizations**, and then select **Customize the System**.
53+
1. In the Dynamics 365 web application, navigate to **Settings** > **Customizations**, and then select **Customize the System**.
5554
2. Select **Sdk Message Processing Steps**.
56-
3. Sort on the **Primary Object Type Code (SdkMessage Filter)** column and look for any rows for the Email entity.
57-
4. If you find any rows and the Execution Mode is Synchronous, it could potentially be interfering with the creation of the email.
55+
3. Sort on the **Primary Object Type Code (SdkMessage Filter)** column and look for any rows for the **Email** entity.
56+
4. If the **Execution Mode** in those rows is set to **Synchronous**, it might interfere with the email creation.
5857

59-
If the issue reproduces consistently and it's possible to temporarily disable the workflow or plugin as a test, it can allow you to determine if the workflow or plugin is the cause.
58+
If you're able to reproduce the issue consistently, you can try disabling the workflow or plugin temporarily to determine if the workflow or plugin is the cause of the problem.

support/power-platform/dataverse/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@
9090
href: email-exchange-synchronization/error-when-testing-enabling-mailbox.md
9191
- name: '"The SMTP address has no mailbox associated with it" error'
9292
href: email-exchange-synchronization/the-smtp-address-has-no-mailbox.md
93-
- name: unknownincomingemailintegrationerror -2147220891
93+
- name: UnknownIncomingEmailIntegrationError -2147220891 or Crm.80040265.ISV
9494
href: email-exchange-synchronization/unknownincomingemailintegrationerror-2147220891.md
9595
- name: '"You cannot send email as the selected user" error'
9696
href: email-exchange-synchronization/cannot-send-email-as-another-user.md

0 commit comments

Comments
 (0)