none
svchost (3932) The version store for this instance

    Question

  • Hi,

    A couple of days ago the Application event log on my domain controller started to fill up with the message below:

    svchost (3932) The version store for this instance (0) has reached its maximum size of 2Mb. 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: 0x000000712FAF08A0 
    Session-context: 0x00000000 
    Session-context ThreadId: 0x0000000000000568 
    Cleanup: 0 
    Session-trace: 
    57573@1:51:45 PM

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="ESENT" />
      <EventID Qualifiers="0">623</EventID>
      <Level>2</Level>
      <Task>14</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated SystemTime="2017-04-11T20:52:45.000000000Z" />
      <EventRecordID>215472</EventRecordID>
      <Channel>Application</Channel>
      <Computer>qualtechs1-01.qualtechs1.qualtechcloud.com</Computer>
      <Security />
      </System>
    - <EventData>
      <Data>svchost</Data>
      <Data>3932</Data>
      <Data />
      <Data>0</Data>
      <Data>2</Data>
      <Data>0x000000712FAF08A0</Data>
      <Data>0x00000000</Data>
      <Data>0x0000000000000568</Data>
      <Data>0</Data>
      <Data>57573@1:51:45 PM</Data>
      </EventData>

     </Event>

    All I found pointed me to Exchange or the Remote Terminal Licensing role. This is a DC and no Exchange is installed in it neither the Remote Desktop Terminal Licensing role.

    Does anyone know what might be causing this and how to stop/fix it?

    Thanks

    Tony


    Tony

    Tuesday, April 11, 2017 9:11 PM

Answers

  • Just an update on this.

    Thanks Narayanan for the link on the buckets. After reading that article I added an entry to the registry HLM\system\controlset\services\ntds\parameters named EDB max ver pages (increment over the minimum) with a value of 9600.

    I rebooted the DC after the change and the error messages went way. Now this seems to be a problem that can occur over time so I'd think it's early to know if the has fixed the problem or if rebooting the server cleared the issue for the time being.

    Just wanted to leave an update and thank you guys for providing some direction.


    Tony

    • Marked as answer by Tony Amaral Thursday, April 13, 2017 5:53 PM
    Thursday, April 13, 2017 4:41 PM

All replies

  • Hi Tony,

    Please check if the below article helps:

    The domain controller runs slower or stops responding when the garbage collection process runs

    https://support.microsoft.com/en-us/help/974803/the-domain-controller-runs-slower-or-stops-responding-when-the-garbage-collection-process-runs

    Best Regards,

    Alvin Wang


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

    Wednesday, April 12, 2017 10:29 AM
    Moderator
  • Long running queries can exhaust the version store.

    what is version store?

    https://blogs.technet.microsoft.com/askds/2016/06/14/the-version-store-called-and-theyre-all-out-of-buckets/

    What can i do about this or find the long running transaction/queries ?

    https://blogs.technet.microsoft.com/askpfeplat/2015/05/10/how-to-find-expensive-inefficient-and-long-running-ldap-queries-in-active-directory/

    Wednesday, April 12, 2017 2:45 PM
  • Just an update on this.

    Thanks Narayanan for the link on the buckets. After reading that article I added an entry to the registry HLM\system\controlset\services\ntds\parameters named EDB max ver pages (increment over the minimum) with a value of 9600.

    I rebooted the DC after the change and the error messages went way. Now this seems to be a problem that can occur over time so I'd think it's early to know if the has fixed the problem or if rebooting the server cleared the issue for the time being.

    Just wanted to leave an update and thank you guys for providing some direction.


    Tony

    • Marked as answer by Tony Amaral Thursday, April 13, 2017 5:53 PM
    Thursday, April 13, 2017 4:41 PM
  • Thank you

    Please remember to mark as answered, if you liked the answer....

    Thursday, April 13, 2017 5:45 PM
  • I thought you will be marking my answer as the Answer :) lol 
    Thursday, April 13, 2017 6:24 PM