Forum Discussion
Exchange 2016 ERROR - The following recipient(s) cannot be reached:
Hi everyone,
Over the last 2-3 months, we have been experiencing issues with sending and sometimes receiving emails from both internal and external organizations.
Error message: (When our users send emails or when external companies send emails, the issue occurs in both situations)
Exchange server is installed on Windows Server 2016,
Exchange server version is 2016, build number - Exchange/15.01.2507.037
We have 3 Exchange servers, all in a DAG.
For those wondering, this email message does not include any attachments—just a few words, that's it.
We have 2 users trying to send message to our users (internally) , new error message showed up
New Err message :
Remote Server returned '554 5.2.0
STOREDRV.Deliver. Exception:StoragePermanent Exception.MapiExceptionDatabaseError; Failed to process message due to a permanent exception with message Cannot find row based on condition. 16.55847:3F010000,
17.43559:54040000940000000000000002000
00000000000, 4.32881:54040000,
0.50035:F1030000, 4.64625:54040000, 20.52176:010FCB89250000109A310000,
20.50032:010FCB899517F01 FA4000000, 0.50128:56000000, 255.1494:80030400, 4.56380:D3FBFFFF, 4.64456:54040000,
255.1750:80030400, 255. 1494:00000000, 4.56380:D3FBFFFF, 4.64456:54040000,
255.1750:010FCB89, 0.50288:6C2C0000,
4.23354:54040000, 0.35180:00000000, 0.25913:0A000000, 255.21817:54040000,
0.29726:05000780, 4.18462:54040000 [Stage:
OnPromotedEvent][Agent: Conversations
Processing Agent]'
Another ERR MESSAGE
#######################################################
Your message did not reach some or all of the intended recipients.
Subject: RE: Service cargo Bishkek
Sent: 13.06.2024 10:38
The following recipient(s) cannot be reached:
'Nazim Samadov' on 13.06.2024 10:38
Tofig Musayev on 13.06.2024 10:38
Ramin Iskenderov on 13.06.2024 10:38
Rahman Ahmedov on 13.06.2024 10:38
Murad Novruzov on 13.06.2024 10:38
This message could not be sent. The client operation failed. Try sending the message again later, or contact your network administrator.
__________________________________________________
Diagnostic information for administrators:
__________________________________________________
Error is [0x80004005-0x00000454-0x00000501].
Exchange response headers:
request-id: 95f83b2e-afc2-46c0-bf4e-24164af2cf02
X-ServerApplication: Exchange/15.01.2507.037
X-FEServer: #
X-BEServer: #
X-CalculatedBETarget: #
X-RequestId: {65E93A56-416F-4C98-9426-1F8A6FEA9BBA}:19
X-ClientInfo: {2452A84E-2772-430F-9385-B4B3E5728F59}:231160020
X-ElapsedTime: 51
X-ResponseCode: 0
X-DiagInfo: #
X-RequestType: Execute
__________________________________________________
ROPs Summary:
0: ropSetProps (10) Processed(1) Completed(0)
ROP result: 0
Response codes: 0
1: ropSetProps (10) Processed(1) Completed(0)
ROP result: 0
Response codes: 0
2: ropFlushRecipients (14) Processed(1) Completed(0)
ROP result: 0
Response codes: 0
3: ropSetProps (10) Processed(1) Completed(0)
ROP result: 0
Response codes: 0
4: ropTransportSend (74) Processed(1) Completed(0)
ROP result: 0
Response codes: 1108
__________________________________________________
Response Exceptions:
ROP Index: 4
ROP Associated: ropTransportSend (74)
Microsoft.Exchange.Data.Storage.StoragePermanentException: Cannot find row based on condition. ---> Microsoft.Mapi.MapiExceptionDatabaseError: MapiExceptionDatabaseError: Unable to find table row. (hr=0x80004005, ec=1108)
Diagnostic context:
Lid: 55847 EMSMDBPOOL.EcPoolSessionDoRpc called [length=289]
Lid: 43559 EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x454][length=154][latency=27]
Lid: 32881 StoreEc: 0x454
Lid: 50035
Lid: 64625 StoreEc: 0x454
Lid: 52176 ClientVersion: 15.1.2507.37
Lid: 50032 ServerVersion: 15.1.2507.6037
Lid: 50128
Lid: 1494 ---- Remote Context Beg ----
Lid: 56380 StoreEc: 0xFFFFFBD3
Lid: 64456 StoreEc: 0x454
Lid: 1750 ---- Remote Context End ----
Lid: 1494 ---- Remote Context Beg ----
Lid: 56380 StoreEc: 0xFFFFFBD3
Lid: 64456 StoreEc: 0x454
Lid: 1750 ---- Remote Context End ----
Lid: 50288
Lid: 23354 StoreEc: 0x454
Lid: 35180
Lid: 25913
Lid: 21817 ROP Failure: 0x454
Lid: 29726
Lid: 18462 StoreEc: 0x454
at Microsoft.Mapi.MapiExceptionHelper.InternalThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarnings, Int32 ec, DiagnosticContext diagCtx, Exception innerException)
at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, IExInterface iUnknown, Exception innerException)
at Microsoft.Mapi.MapiTable.FindRow(Restriction restriction, BookMark bookmark, FindRowFlag flag)
at Microsoft.Exchange.Data.Storage.QueryResult.SeekToCondition(UInt32 bookMark, Boolean useForwardDirection, QueryFilter seekFilter, SeekToConditionFlags flags)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Storage.QueryResult.SeekToCondition(UInt32 bookMark, Boolean useForwardDirection, QueryFilter seekFilter, SeekToConditionFlags flags)
at Microsoft.Exchange.Data.Storage.Conversations.ConversationAggregationByReferencesSubjectProcessor.<>c__DisplayClass32_0.<SearchByReferences>b__1(QueryResult queryResult)
at Microsoft.Exchange.Data.Storage.AllItemsFolderHelper.RunQueryOnAllItemsFolder[G](IMailboxSession session, SupportedSortBy supportedSortBy, DoQueryProcessing`1 queryProcessor, ICollection`1 properties, ItemQueryType itemQueryType)
at Microsoft.Exchange.Data.Storage.AllItemsFolderHelper.RunQueryOnAllItemsFolder[G](IMailboxSession session, SupportedSortBy supportedSortBy, DoQueryProcessing`1 queryProcessor, ICollection`1 properties)
at Microsoft.Exchange.Data.Storage.Conversations.ConversationAggregationByReferencesSubjectProcessor.SearchByReferences(ICorePropertyBag persistPropertyBag, Boolean searchByDupedMessage, IStorePropertyBag& foundPropertyBag, InternetIdSource& parentItemSource, PropertyDefinition[] propsToReturn)
at Microsoft.Exchange.Data.Storage.Conversations.ConversationAggregationByReferencesSubjectProcessor.TryAggregate(ICorePropertyBag item, ConversationAggregationResult& result)
at Microsoft.Exchange.Data.Storage.Conversations.ConversationAggregator.<>c__DisplayClass7_0.<Aggregate>b__0()
at Microsoft.Exchange.Data.Storage.Conversations.Diagnostics.ConversationOperationTracker.Track(String operationName, IExtensibleLogger logger, TrackableOperationDelegate aggregation)
at Microsoft.Exchange.Data.Storage.Conversations.ConversationAggregator.Aggregate(ICoreItem message)
at Microsoft.Exchange.Data.Storage.MessageItem.AggregateMessageInConversation(ICoreItem item, CoreItemOperation operation)
at Microsoft.Exchange.Data.Storage.MessageItemSchema.CoreObjectUpdate(CoreItem coreItem, CoreItemOperation operation)
at Microsoft.Exchange.Data.Storage.CoreItem.InternalFlush(SaveMode saveMode, CoreItemOperation operation, OperationContext operationContext)
at Microsoft.Exchange.Data.Storage.CoreItem.<OnBeforeSend>b__113_0()
at Microsoft.Exchange.Data.Storage.CoreItem.TransportSend(PropertyDefinition[]& propertyDefinitions, Object[]& propertyValues)
at Microsoft.Exchange.RpcClientAccess.Handler.Message.Tra
Transport-Send failed: failure enum(25), HResult(0x00000000), EC(1108).
Transport-Send failed: failure enum(22), HResult(0x00000000), EC(1108).
Submit-Message failed: message id(33), failure enum(13), HResult(0x80004005), EC(1108).
3 Replies
Mailbox is highly corrupt and needs to be repaired, What is the behavior when you try send emails on OWA
Hi ,
Possible root cause based on your error
a corrupted mailbox item or issues with the mailbox database, typically affecting Conversation View aggregation.
Causes:- Corrupt mailbox item or folder (e.g. Conversation index)
- Database index corruption
- Issues with the mailbox move history or tombstoned folders
- Third-party add-ins or antivirus scanning mailbox data
Actions:
- Identify if it's user-specific
Check if this error only occurs for:
A single user
Multiple users on the same mailbox databaseIf it’s user-specific, proceed to mailbox repair (step 2). If multiple users are affected, investigate the database and server-level issues.
- Run a mailbox repair (ISInteg style)
Use New-MailboxRepairRequest on the affected user’s mailbox:
New-MailboxRepairRequest -Mailbox "username" -CorruptionType ProvisionedFolder,SearchFolder,AggregateCounts,FolderViewYou can monitor the repair progress in the Event Viewer (Application log, source: MSExchangeIS).
- Check if it's reproducible
Ask the user to try: - Forwarding the email
- Rewriting it from scratch
- Sending without attachment
If one of these works, the item is likely corrupted
- Move the mailbox to a new database
If mailbox repair fails or error persists:
New-MoveRequest -Identity "username" -TargetDatabase "NewDatabaseName"A mailbox move can purge corrupt folders/items that cause MAPI-level errors.
- Check Event Logs
On the Exchange server(s), look in: - Application logs (for MSExchangeIS and MSExchangeTransport)
- System logs (hardware or disk issues)
Check for recurring 1108 or MAPI errors.
WorkAround
Disable Conversation View (workaround)
Temporarily disable conversation processing for the mailbox as a test :Set-Mailbox <username> -MessageCopyForSentAsEnabled $false Set-Mailbox <username> -MessageCopyForSendOnBehalfEnabled $falseOr disable it in Outlook to avoid the problematic agent (not a fix, but a workaround).
if it’s still unsolved:
- Use MFCMAPI tool to inspect the problematic message/folder
- Export the message to PST and reimport after scan
- Open a Microsoft support case if multiple users are impacted
NOTE Exchange 2016 is end of extended support as of oktober 14, 2025
Regards
Checking recipient address validity and then restarting the Exchange transport service basically fixes the delivery failure issue.
