We are getting this Alert in SCOM: The version store has reached its maximum size because of unresponsive transaction. Updates to database are rejected until the long-running transaction is omitted or rolled back. Path: Servername.I tried searching technet and it suggested to look for event IDs-1022,1069,623 and none of these event ids could be found in eventviewer.what could be wrong?I also checked eventvwr for critical events and none of these could be found.The exchange is running in CCR mode and it is a high end server having ample resources available.

Nobody sent a very large attachment went into a runaway loop? This can cause the long running transaction by eating up your resources and consuming your version store memory. I would check message tracking around the time of the event. I also recall when an admin opened up a very large mailbox and then kicked off an outlook rule on it and caused the version store to run out of memory, however the box was also experiencing performance issues which exacerbated the issue. James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com