locked
[Known Issue] ESENT event 642 logged in Application Event Log of Windows 10 Insider Preview Builds (20H1) / Windows 10, version 2004 devices RRS feed

  • General discussion

  • Symptom:
    ESENT Event 642 logged is logged in Application Event Log of 20H1 / 2004 devices with the following text:
    MessageId=642
    %1 (%2) %3 The database format feature version %5 could not be used due to the current database format %6, controlled by the parameter %4.

    Detail Event information such as below:
    Unexpected Warning '"avguard (6272,D,35) GaviDB_0: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x40000001 (JET_efvUseEngineDefault)"'
     
    Workaround:
    In general, Event 642 was logged for application developers after ESE took a change where it became necessary to track Exchange engine and DB version numbers.

    This event can be safely ignored, and that applications using ESENT continue to function correctly. Microsoft are working on it and we will update this post once it has been worked out. 

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, July 24, 2020 5:01 AM