Online convert OLM to PST

Aspose.Email Product Family
1

Hi,

My query is related to the Online Converter OLM to PST.
The contacts are not working — it throws an exception while saving them to the PST file.
Could you please let me know the reason why the contact data is failing?

The exception shown is: “Not a valid Win32 FileTime.”

Please provide the code to resolve this issue.
Thanks & Regards,
Anjali

2

@Anjali12

:warning: Speculative guidance – no verified documentation was found for this scenario.

No exact match was retrieved and the SDK schema could not confirm the referenced API members. The following notes are hypotheses derived from unverified sources; please validate them before applying any changes.

Impacted product context: email.

Potential leads to investigate:

  • Reproduce the scenario on the prior SDK version to confirm the regression window.

  • Compare recent release notes for layout/rendering changes and test with AutoFit disabled or re-applied.

  • Share these hypotheses with support engineers alongside logs, code samples, and the exact SDK version so they can confirm the behaviour.

I could not find a verified document or sandbox reproduction for this scenario, so please treat the notes below as an investigation checklist.

Recommended next steps:

  • Capture before/after samples or logs so that the regression window can be reproduced internally.
  • Mention the exact SDK version/build to eliminate version drift between your environment and the indexed documentation.
  • Share the minimal code path (plus relevant options such as SaveOptions/Table settings) with the support engineers.

Question summary: Online convert OLM to PST Hi, My query is related to the Online Converter OLM to PST. The contacts are not working — it throws an exception while saving them to the PST file. Could you please let me know the reason why the contact data is failing? The exception shown is: **“No…

3

Hello @Anjali12,

The error “Not a valid Win32 FileTime” usually occurs when a contact item contains an invalid or corrupted date-time value, or any custom date field that falls outside the valid Win32 FILETIME range (before January 1, 1601 or after December 31, 9999).
If you’d like us to investigate the issue more precisely, please send us an example of the source OLM file (or the specific problematic contact). This will allow us to analyze the exact property causing the error.

Thank you.