Windows 10: Windows 10 Event Log ESENT 623

There are a lot of errors with 623 code in my Event Log:

SearchIndexer (6624, D, 23) Windows: The version of this instance (0) has reached its maximum size of 128 MB. It is likely that a long-running transaction makes it impossible to clean the version store and increases its size. Updates will be discarded until the long-term transaction is fully approved or revoked.

Probable long-term transaction:
Session ID: 0x000001EF41D310C0: 0x52f9e8
Session context: 0x00000000
Session context thread ID: 0x000000000000787C
Cleansing: 1
Session tracking:
45861 @ 19: 44: 08
57573 @ 19: 44: 05

:)

 

Event 623 ESENT on Music.UI

I have the same problem as Bill,

I am running the anniversary edition of windows 10 pro x64 and recently noticed the same ESENT Event 623 related to Music.UI. I think this started after Cumulative update KB3176938.

Scannow and disk checks show no problems.

 

Event 623 ESENT on Music.UI

Please note: I guessed on "Windows topics" and "App category" so they may be incorrect.

Win10 64bit with Anniversary Update logs this error several times per day. (The numeric values sometimes repeat and sometimes differ.)

Date 2016-08-29 08:44:13

Type Error

Event 623

Source ESENT

Music.UI (8688) {4043BC4F-4F5A-4BBE-B70F-462B856B5EC9}: The version store for this instance (0) has reached its maximum size of 16Mb. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to build up in size.
Updates will be rejected until the long-running transaction has been completely committed or rolled back.

Possible long-running transaction:

SessionId: 0x000002439C4A1220

Session-context: 0x00000000

Session-context ThreadId: 0x0000000000002290

Cleanup: 1

Session-trace:

45861@08:44:13

0@08:44:10

0@08:43:54

Thank you very much for your assistance!! ..Bill..

 

Windows 10 (1607) Event ID: 623

On 2016.09.24 the Event Id error 623 starting appearing in the Event Logs. (Full message information shown below)

I ran SFC /scannow (2016.09.29) which did not find any problems.

I ran Malwarebytes (2016.09.29) which did not find any problems.

I ran ESET Smart Security virus scan (2016.09.29) which did not find any problems.

I retraced what I did on the 24th and uninstalled each of those applications, one-by-one. After each single uninstall, I cleaned out the environment running CCleaner and also cleaned up the registry using CCleaner. Also restarted Windows 10 after each and
every uninstall.

These are the application installs or updates or processes that there performed on the 24th:

Installed Microsoft Windows Automated Install Kit (I was building a Windows 7 installation DVD)

Updated Private Internet Access to v65

Turned on the Periodic Scan in Windows Defender to see if it would run while ESET SS was running (it did)

Uninstalled Windows AIK 2016.10.01. Ran CCleaner and restarted. Event 623 persisted.

Uninstalled Windows ADK 2016.10.01. Ran CCleaner and restarted. Event 623 persisted.

Ran routine to clear out Event Viewer Logs to make checking easier.

Uninstalled Private Internet Access v65. Ran CCleaner and restarted. Event 623 persisted.

Turned off Windows Defender Periodic Scan. Restarted, Event 623 persisted.

Cleaned out Event Viewer Logs and restarted. Within a few minutes Event 623 was back.

I've run out of ideas! Any thoughts out there?

Here is a cut-n-paste of the recent event log entry:

Log Name: Application

Source: ESENT Logged: 10/3/2016 2:30:59 PM

Event ID: 623 Task Category: Transaction Manager

Level: Error Keywords: Classic

User: N/A Computer: P8P67Pro

OpCode:



More Information: Event Log Online Help (which goes to Microsoft marketing site)



General Information



Music.UI (5692) {FE4C2F06-B7E2-4796-B602-44C5187212A1}: The version store for this instance (0) has reached its

maximum size of 16Mb. It is likely that a long-running transaction is preventing cleanup of the version store and

causing it to build up in size. Updates will be rejected until the long-running transaction has been completely

committed or rolled back.

Possible long-running transaction:

SessionId: 0x000002456A871220

Session-context: 0x00000000

Session-context ThreadId: 0x0000000000002464

Cleanup: 1

Session-trace:

45861@2:30:59 PM

0@2:30:58 PM

0@2:30:58 PM

Cheers,

Bob