Skip to content

Commit 3dbe086

Browse files
committed
Merge branch 'main' into Meera-SupportArticles-Working
2 parents bcd099d + 77e6f37 commit 3dbe086

47 files changed

Lines changed: 951 additions & 1371 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

.openpublishing.redirection.json

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13761,6 +13761,45 @@
1376113761
{
1376213762
"source_path": "support/windows-client/performance/stop-error-or-blue-screen-error-troubleshooting.md",
1376313763
"redirect_url": "/troubleshoot/windows-client/performance/stop-code-error-troubleshooting"
13764+
},
13765+
{
13766+
"source_path": "support/power-platform/power-automate/desktop-flows/office-automation/excel/launch-excel-action-failures.md",
13767+
"redirect_url": "/troubleshoot/power-platform/power-automate/desktop-flows/office-automation/excel/troubleshoot-excel-errors"
13768+
},
13769+
{
13770+
"source_path": "support/sql/database-engine/install/windows/install-reporting-service.md",
13771+
"redirect_url": "/previous-versions/troubleshoot/sql/install/install-reporting-service",
13772+
"redirect_document_id": false
13773+
},
13774+
{
13775+
"source_path": "support/sql/database-engine/install/windows/issues-install-sql-server.md",
13776+
"redirect_url": "/previous-versions/troubleshoot/sql/install/issues-install-sql-server",
13777+
"redirect_document_id": false
13778+
},
13779+
{
13780+
"source_path": "support/sql/database-engine/install/windows/sql-server-2008-setup-issues.md",
13781+
"redirect_url": "/previous-versions/troubleshoot/sql/install/sql-server-2008-setup-issues",
13782+
"redirect_document_id": false
13783+
},
13784+
{
13785+
"source_path": "support/sql/database-engine/install/windows/sql-server-2012-setup-issues.md",
13786+
"redirect_url": "/previous-versions/troubleshoot/sql/install/sql-server-2012-setup-issues",
13787+
"redirect_document_id": false
13788+
},
13789+
{
13790+
"source_path": "support/sql/database-engine/security/instructions-in-fips-140-2-compliant-mode.md",
13791+
"redirect_url": "/previous-versions/troubleshoot/sql/security/instructions-in-fips-140-2-compliant-mode",
13792+
"redirect_document_id": false
13793+
},
13794+
{
13795+
"source_path": "support/sql/database-engine/security/sql-2014-fips-140-2-compliant-mode.md",
13796+
"redirect_url": "/previous-versions/troubleshoot/sql/security/sql-2014-fips-140-2-compliant-mode",
13797+
"redirect_document_id": false
13798+
},
13799+
{
13800+
"source_path": "support/sql/tools/error-you-run-sqlmaint-utility.md",
13801+
"redirect_url": "/previous-versions/troubleshoot/sql/tools/error-you-run-sqlmaint-utility",
13802+
"redirect_document_id": false
1376413803
}
1376513804
]
1376613805
}

Exchange/ExchangeOnline/email-delivery/ndr/non-delivery-reports-in-exchange-online.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -56,8 +56,8 @@ The following table contains the error codes (also known as enhanced status code
5656
|550 5.1.20|`Multiple From addresses are not allowed without Sender address`|An email message has multiple email addresses in the **From** field, but no email address in the **Sender** field.|For more information, see [Fix NDR error code 550 5.1.20 "Multiple From addresses are not allowed without Sender address"](/exchange/troubleshoot/email-delivery/ndr/fix-error-code-550-5-1-20-multiple-from-addresses).|
5757
|5.1.90|`Your message can't be sent because you've reached your daily limit for message recipients`|The sender has exceeded the recipient rate limit, as described in [Sending limits](/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#sending-limits).|This could indicate that the account was compromised and is being used to send spam. For more information, see [Responding to a compromised account](/defender-office-365/responding-to-a-compromised-email-account).|
5858
|5.2.2|`Submission quota exceeded`|The sender has exceeded the recipient rate limit or the message rate limit as described in [Sending limits](/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#sending-limits).|This could indicate the account was compromised and is being used to send spam. For more information, see [Responding to a compromised account](/defender-office-365/responding-to-a-compromised-email-account).|
59-
|5.2.121|`Recipient's per hour message receive limit from specific sender exceeded`|The sender has exceeded the maximum number of messages that they're allowed to send per hour to a specific recipient in Exchange Online.|The automated mailer or sender should try again later, and reduce the number of messages that they send per hour to a specific recipient. <br/><br/> This limit helps protect Microsoft 365 or Office 365 users from rapidly filling their Inboxes with many messages from errant automated notification systems or other single-sender mail storms.|
60-
|5.2.122|`Recipient's per hour message receive limit exceeded`|The Microsoft 365 or Office 365 recipient has exceeded the number of messages that they can receive per hour from all senders.|The automated mailer or sender should try again later, and reduce the number of messages that they send per hour to a specific recipient. <br/><br/> This limit helps protect Microsoft 365 and Office 365 users from rapidly filling their Inboxes with many messages from errant automated notification systems or other mail storms.|
59+
|5.2.121|`Recipient's per hour message receive limit from specific sender exceeded`|The sender has exceeded the maximum number of messages that they're allowed to send per hour to a specific recipient in Exchange Online.|The automated mailer or sender should try again later, and reduce the number of messages that they send per hour to a specific recipient. <br/><br/> This limit helps protect Microsoft 365 and Office 365 users from rapidly filling their Inboxes with many messages from errant automated notification systems or other single-sender mail storms. <br/><br/> The ["Mailboxes exceeding receiving limits"](/exchange/monitoring/mail-flow-reports/mailboxes-exceeding-receiving-limits-report) report shows detailed information about the mailboxes that are receiving large volumes of messages in a short time.|
60+
|5.2.122|`Recipient's per hour message receive limit exceeded`|The Microsoft 365 or Office 365 recipient has exceeded the number of messages that they can receive per hour from all senders.|The automated mailer or sender should try again later, and reduce the number of messages that they send per hour to a specific recipient. <br/><br/> This limit helps protect Microsoft 365 and Office 365 users from rapidly filling their Inboxes with many messages from errant automated notification systems or other mail storms. <br/><br/> The ["Mailboxes exceeding receiving limits"](/exchange/monitoring/mail-flow-reports/mailboxes-exceeding-receiving-limits-report) report shows detailed information about the mailboxes that are receiving large volumes of messages in a short time.|
6161
|5.3.190|`Journaling on-premises messages to Microsoft 365 or Office 365 not supported when Journaling Archive is disabled`|Journaling on-premises messages to Microsoft 365 or Office 365 isn't supported for this organization because the organization hasn't turned on Journaling Archive in its settings.|A journaling rule is configured in the organization's on-premises environment to journal on-premises messages to Microsoft 365 or Office 365, but Journaling Archive is disabled. For this scenario to work, the organization's Office 365 administrator should either enable Journaling Archive or change the journaling rule to journal messages to a different location.|
6262
|5.4.1|`Relay Access Denied`|The mail server that's generating the error doesn't accept mail for the recipient's domain. This error is caused by mail server or DNS misconfiguration.|For more information, see [Fix email delivery issues for error code 5.4.1 in Exchange Online](https://support.microsoft.com/topic/c0e98a8e-81db-49c2-9bf1-32a1734d3e77).|
6363
|5.4.1|`Recipient address rejected: Access denied`|The recipient's address doesn't exist.|For more information, see [Use Directory Based Edge Blocking to reject messages sent to invalid recipients](/exchange/mail-flow-best-practices/use-directory-based-edge-blocking).|

0 commit comments

Comments
 (0)