locked
Version Store Out of Memory (-1069) RRS feed

  • Question

  • This occurred on my workstation console whilst adding Port Monitoring Performance Counters to the Monitoring Window.

    Date: 11/03/2009 5:52:13 PM
    Application: System Center Essentials
    Application Version: 6.0.1885.0
    Severity: Error
    Message:

    Microsoft.Mom.Isam.IsamVersionStoreOutOfMemoryException: Version store out of memory (-1069)
       at Microsoft.Mom.Isam.?A0x7361b391.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.EseRow.Update()
       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)



    Event ID 31555 occurred with this.

    Failed to generate data to be forwarded to the Data Warehouse. The operation will be retried. Exception 'OutOfMemoryException': Exception of type 'System.OutOfMemoryException' was thrown. One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DataWarehouse.Synchronization.Configuration

    The cause seems to be adding several TCP Port monitors, Then failure Event 31555 happens, followed soon after with success Event 31556.

    This is a Quad Core Xeon Server with 8GB RAM. I don't see how adding a few monitors make SQL access suffer.

    I should not have to deploy another watcher node to counter this problem.

    How do I fix this?







    Wednesday, March 11, 2009 7:11 AM

All replies

  • Hi Hittin,

    With my experience, please check your SQL Error logs to see if there is an error message as this:

    Event ID: 7886
    Description:
    A read operation on a large object failed while sending data to theclient. A common cause for this is if the application is running in READ UNCOMMITTED isolation level. This connection will be terminated.

    If yes, it could be caused by SQL Server Disk performance. Take a look a the Performance Monitor (perfmon) counters for the Logical Disks that SQL server users, such as the Average Disk Queue Length for each of the Logical Disks. Post back that number (take the average for about 1 hour) as well as your disk configuration, to see if you are indeed hitting a disk performance issue or not.

    Thanks,
    Yog Li - MSFT
    Friday, March 13, 2009 8:48 AM
  • Hi,

    No that event has not occurred.

    thanks
    Monday, March 16, 2009 1:29 AM
  • Hi there!

    Any solution concerning this issue?
    I have the same problem randomly on various computers running console.

    Regards,
    Patrick
    Monday, October 19, 2009 9:01 AM
  • Ok. This is it! What a ____ joke. Why are SCE 2007 treated as a joke?
    Thursday, April 22, 2010 2:36 PM