System Center operations Manager logo http://www.Oostdam.infoSystem Center Operations Manager 2007 R2 is a great product. It has some difficulties, but doesn't have any products have a problem here and there? Now this article has been made here, for several reasons. First of all, I collected all these errors and warnings for my own personal reference. But, it is always better to share knowledge, so I decided to publish these articles, with a little extra explanation on this site, through these articles. So, I hope this article will help you with your problem as well.

So enjoy! (if you did not allready knew this...)

Version store out of memory (-1069):
SCOM R2 Version Store out of memory (-1069) www.Oostdam.Info
This is an error that might come up in your System Center Operations Manager 2007 R2 console.

Here on the right, you can see an example of this error. It is mostly caused by slow logical disk performance on your SQL OpsMgr- or DataWarehouse database.

Clicking on the hyperlink "Show additional information about this error" will give you an output, something like this below:

Note: The following information was gathered when the operation was attempted.  The information may appear cryptic but provides context for the error.  The application will continue to run.
 Microsoft.Mom.Isam.IsamVersionStoreOutOfMemoryException: Version store out of memory (-1069)   at Microsoft.Mom.Isam.?A0x5359b89f.HandleError(Int32 err)   at Microsoft.Mom.Isam.EseInterop.JetPrepareUpdate(JET_TABLEID& tableid, JET_PREP prep)   at Microsoft.Mom.Isam.Cursor.BeginEditForUpdate()   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Cache.EseRow.InsertUpdateRecord(Boolean insert)   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Cache.EseRow.EditRecord(Boolean insert)   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Cache.IndexTable.MarkAsObsolete()   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Cache.Query`1.FullUpdateQuery(CacheSession session,
       IndexTable& indexTable, Boolean forceUpdate, DateTime queryTime)
   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Cache.Query`1.InternalSyncQuery(CacheSession session,
       IndexTable indexTable, UpdateReason reason, UpdateType updateType)
   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Cache.Query`1.InternalQuery(CacheSession session, UpdateReason reason)   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Cache.Query`1.TryDoQuery(UpdateReason reason, CacheSession session)   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Cache.Query`1.DoQueryJob(Object sender, ConsoleJobEventArgs args)   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent component,
       EventHandler`1 job, Object sender, ConsoleJobEventArgs args)

I can image this is a little cryptic, as it stated on top. But I give you underneath several clue's to help you detect the real problem, as this error can be caused, by several things.

  • Check if there are any TCP/Network problems between your MS- and DataWarehouse server. This could indicate that buffering and queue's are relatively high which could lead to this error.
  • Go through the SQL error logs on your OpsMgr- & DataWarehouse databases. See if there's anything unexpected there. Look for event id 7886, which indicates a slow logical disk access, and the SQL server will experience troubles updating your console alerts (reads) and moving older alerts (writes) to the DataWarehouse at the same time. This is the most common issue when you receive this message. You can easily see it through the Permon counter "Average Disk Queue Length" as well. Check if nothing wrong with your RAID set perhaps?
  • Check if the SQL memory option has been set correctly at your instance. Do not use the maxium available, but leave a minimum for the operating system as well. Also check if other instances exist on the machine, this can cause the disk/buffering/Query error as well. It is recommendation that no other instances are present on the SQL servers, for reasons like this error.

Now, overall, as earlier mentioned, most common cause is a lack in logical disk performance. Basically, when you are opening a console view, many reads are executed to provide the actual console information. This is often done whithout the use of locking, to speed up the performance. When the data in these objects is changed, due to normal writes, the correct version of some records, cannot be determined by SQL server and it will trow out this error. If you would like to dive deeper in this, go and check out the difference in how the SCOM console picks up the data from the databases in various ways. Important to know is that the actual data in the database will still be correct. No question about that. The writes are done to the database involved, and the error mainly indicates that a data (record) change occured. So do not worry. Reload the console and start controlling again. 

Have fun, using System Center Operation Manager!

Ben OostdamBen Oostdam has been working with Windows systems since 1993. Worked for several companies as a system administrator, and is currently a Senior Support Engineer for Qurius Customer Care in the Netherlands, specialized in System Center Solutions.

Disclaimer: The information contained in this website/article is for general information purposes only. The information is provided as is, by Ben Oostdam and while we endeavour to keep the information up to date and correct, we make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability or availability with respect to the website or the information, products, services, or related graphics contained on the website for any purpose. Any reliance you place on such information is therefore strictly at your own risk. In no event will we be liable for any loss or damage including without limitation, indirect or consequential loss or damage, or any loss or damage whatsoever arising from loss of data or profits arising out of, or in connection with, the use of this website. Through this website you are sometimes able to link to other websites which are not under my control. I have no control over the nature, content and availability of those sites. The inclusion of any links does not necessarily imply a recommendation or endorse the views expressed within them. Every effort is made to keep the website up and running smoothly. However, I take no responsibility for, and will not be liable for, the website being temporarily unavailable due to technical issues beyond our control. All entries in these articles, are my individual opinion, or from co-writers and they don't necessary reflect the opinion of my employer.


Friday the 7th, May 2021. All rights reserved.. // Oostdam WebDesign