Unable to run delivery report from EAC or from PowerShell in Exchange 2013

Encountered this issue earlier today in Exchange 2013 EAC when trying to track a message from one user to another.

error: failed to compare two elements in the array.

I thought I would then be able to do it via the shell, but  get a similar error when running Search-MessageTrackingReport.

WARNING: An unexpected error has occurred and a Watson dump is being generated: Failed to compare two elements in the
array.
Failed to compare two elements in the array.
    + CategoryInfo          : NotSpecified: (:) [Search-MessageTrackingReport], InvalidOperationException
    + FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.Exchange.Management.Tracking.SearchMessageTra
   ckingReport
    + PSComputerName        : ********************

Does anyone have any insight?

This seems to happen with some users and mailboxes but not all.

Jahan De Silva

December 10th, 2013 5:53pm

Hi,

Please do message tracking for both the sender and the recipient who are Exchange account to check whether the issue persists.

Generally, if Exchange 2013 is there in co-existence with a third party email system, we will see this issue. Please check whether Exchange 2013 is in co-existence with a third party email system. If it is, just migrating the users to Exchange completely, this issue would be resolved.

Thanks,

Free Windows Admin Tool Kit Click here and download it now
December 11th, 2013 5:52am

Hi Winnie,

In this instance, I am able to track from the sender as the sender is also a local Exchange user; but in some instances the sender is external and I am not able to trace from the sender.

This is an Exchange 2013 environment with no co-existence; there are no users to migrate anywhere.

Any other ideas?

Jahan De Silva

December 11th, 2013 6:27am

Hi,

Whats the details about the sender is external? If it means that the sender is not the user in your organization by using the Microsoft Outlook or Outlook Web App email clients, it is by design that Delivery Reports doesn't track messages sent from POP or IMAP email clients.

Delivery Reports is a message tracking tool in the Exchange Administration Center (EAC) that you can use to search for delivery status on email messages sent to or from users in your organization's address book, with a certain subject. You can track delivery information about messages sent by or received from any specific mailbox in your organization. For more information about it, we can refer to:

http://technet.microsoft.com/en-us/library/jj150554(v=exchg.150).aspx

Thanks,

Free Windows Admin Tool Kit Click here and download it now
December 11th, 2013 7:48am

Winnie,

You have misunderstood. Please let me attempt to clarify.

User A - Organization user with Exchange Mailbox

User B - Organization user with Exchange Mailbox

User C - External user

I have seen the error in the following scenarios.

Mailbox to search:User A; mail received from User B

Mailbox to search:User A; mail received from User C

However if I search mailbox User B; mail sent to User A I do not get the error.

I hope that clarifies the issue.

Jahan De Silva

December 11th, 2013 7:57am

I too have the same issue. It seems mostly to occur when trying to track messages sent to or from our internal users to external users outside our organization. This makes absolutely no sense being as the previous versions of Exchange seemed to flawlessly handle message tracking. Is there a fix for this yet? OUr Executives aren't a fan of me saying "I can't even search for that missing email. Sorry"
Free Windows Admin Tool Kit Click here and download it now
February 13th, 2015 11:05am

I too have the same issue. It seems mostly to occur when trying to track messages sent to or from our internal users to external users outside our organization. This makes absolutely no sense being as the previous versions of Exchange seemed to flawlessly handle message tracking. Is there a fix for this yet? OUr Executives aren't a fan of me saying "I can't even search for that missing email. Sorry"

What command are you using?

Get-MessageTrackingLog works fine and tracks the message as far as it can within the Exchange 2013 org.

February 13th, 2015 11:09am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics