Microsoft Exchange "findItems" not fetching new emails

Sir.Murky 0

Hello,

There is some sort of a problem with an email, but I can't log error why.

I am using ExchangeVersion.Exchange2015

//Normally I am trying to get 100 emails per findItems, but if any email is "bad" I don't get any of emails...
var itemView = new ItemView(1, 0, OffsetBasePoint.Beginning);

itemView.OrderBy.Add(ItemSchema.DateTimeReceived, SortDirection.Descending);

FindItemsResults<Item> findResults = service.FindItems(WellKnownFolderName.Inbox, filter, itemView).Result;

And I get error:

Name cannot begin with the '<' character, hexadecimal value 0x3C. Line 1, position 23012.

I have enabled tracer:

service.TraceEnabled = true;

service.TraceFlags = TraceFlags.All;

service.TraceListener = new EwsReaderTraceListener();

public void Trace(string traceType, string traceMessage)

{

 _log.Information("");

 _log.Information("EWS_TRACING_BEGINS");

 _log.Information(traceType);

 _log.Information(traceMessage);

 _log.Information("EWS_TRACING_ENDS");

 _log.Information("");
}

Debugger stops two times, one is with response of findItems being 200 and the other traceMessage says "System.IO.MemoryStream" and that's all.

If I call service.FindItems(WellKnownFolderName.Inbox, filter, itemView) it works

If I call service.FindItems(WellKnownFolderName.Inbox, filter, itemView) .Result it crashes

If I change sorting from "Descending" to "Ascending" then it works, which indicates that there is a problem with the newest email, but how do I catch what is the error in my tracer

Thank you all in advance :)

Jiale Xue - MSFT 47,581 Microsoft Vendor

Hi @Sir.Murky , Welcome to Microsoft Q&A,

You can customize the TraceListener to capture and log all trace information. Since you are encountering an issue with the XML format, adding detailed log information can help you identify the exact location of the problem. Here is an example:

public class EwsReaderTraceListener : ITraceListener
{
public void Trace(string traceType, string traceMessage)
{
// Log trace information to the log
_log.Information("EWS_TRACE_START");
_log.Information($"Trace Type: {traceType}");
_log.Information("Trace Message: " + traceMessage); // Log the complete traceMessage
_log.Information("EWS_TRACE_END");
}
}

In the traceMessage, you should be able to capture the details of the XML response, including the part that caused the problem.

When calling FindItems, you can add error catching and log detailed exception information to catch and identify the cause of the problem:

try
{
FindItemsResults<Item> findResults = await service.FindItems(WellKnownFolderName.Inbox, filter, itemView);
foreach (var item in findResults.Items)
{
// Process the mail item normally
_log.Information("Processed Item with Subject: " + item.Subject);
}
}
catch (ServiceResponseException sEx)
{
// If there is a problem with the EWS service response, log detailed response information
_log.Error("EWS Service Response Error: " + sEx.Message);
_log.Error("Status Code: " + sEx.StatusCode);
_log.Error("Additional Details: " + sEx.ErrorDetails);
}
catch (Exception ex)
{
// Log general exception information
_log.Error("General Error: " + ex.Message);
}

If you identify a problematic email, you can choose to skip it in production code or, if possible, access the mailbox to modify or delete it manually.

Sir.Murky 0 Reputation points

2024-11-15T13:08:05.0966667+00:00

Hello,

Stack trace:

Tracers logs:
Jiale Xue - MSFT 47,581 Reputation points Microsoft Vendor

2024-11-18T06:51:47.13+00:00

If you find a problematic email, you can choose to skip it in your production code, or if possible, access the mailbox to modify or delete it manually. You should not modify incorrect emails through code.
Sir.Murky 0 Reputation points

2024-11-18T09:00:59.9466667+00:00

Hello,

The only way I can skip it is if I would fetch 1 email at a time, then I can go with try catch and increase an offset on an error, but since I am fetching 50 emails at a time I receive none of them because of 1 problematic email. Even if I decide to go with 1 email fetching at a time, I can't just ignore problematic email and I need to inform user about it (email "subject" was not imported due to an error or something like this), but how can I do that If I can't get email information at all? Thank you in advance

Jiale Xue - MSFT 47,581 Microsoft Vendor

Normally, when the XML content of a message is not well-formed, you cannot load its details, but you can still get metadata such as ItemId, DateTimeReceived, and Subject through FindItems. After getting the id, you can notify the user.

If you are unable to retrieve this email, you can simply notify the user that a message could not be imported.

try
{
    var findResults = service.FindItems(WellKnownFolderName.Inbox, filter, itemView).Result;

    foreach (var item in findResults.Items)
    {
        try
        {
            item.Load();
            _log.Information($"Processed email: {item.Subject}");
        }
        catch (Exception emailEx)
        {
            _log.Warning($"Skipped problematic email. ItemId: {item.Id.UniqueId}, Subject: {item.Subject}. Error: {emailEx.Message}");
        }
    }
}
catch (Exception batchEx)
{
    _log.Error($"Batch processing failed: {batchEx.Message}");
}

Sir.Murky 0 Reputation points

2024-11-18T09:51:55.58+00:00

Well, in my case this line "var findResults = service.FindItems(WellKnownFolderName.Inbox, filter, itemView).Result;" would throw an exception and I would not be able to even start a foreach cycle. But I guess I got all the information I needed here.

Thank you

Share via

Microsoft Exchange "findItems" not fetching new emails

Your answer