Kevin Holman's System Center Blog

Posts in this blog are provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified in the Terms of UseAre you interested in having a dedicated engineer that will be your Mic

29106 event on RMS – Index was out of range. Wait. What?

29106 event on RMS – Index was out of range. Wait. What?

  • Comments 7
  • Likes

Was working with a customer on this one – figured it might help others.

Saw a lot of these VERY SPECIFIC 29106 events on the RMS, specifically with the text: 

System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.

 

Here is the full event:

Event Type:      Warning
Event Source:    OpsMgr Config Service
Event Category:  None
Event ID:        29106
Date:            11/10/2009
Time:            12:43:24 PM
User:            N/A
Computer:        AGENTNAME
Description:
The request to synchronize state for OpsMgr Health Service identified by "3688d65d-a16c-2be6-7e84-5faf8a9cffe0" failed due to the following exception "System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index

What we found was – that we could look up these health service ID’s – by pasting them in the following SQL query:

select * from MTV_HealthService
where BaseManagedEntityId = '3688d65d-a16c-2be6-7e84-5faf8a9cffe0'

This would give us the name of the agent.

In the console, under Agent Managed – we found all of these agents were in “Unmonitored” state – on the agents themselves, they were stuck.  They looked like they got installed, but could not get config.  We deleted them from agent managed, waited a few minutes, and let them show back up in Pending Management.  Approved them – then they were able to come back in and work properly.  These looked for the most part like orphaned machines, and several were computers that were renamed, or old DC’s that were demoted.

Comments
  • Good Morning Kevin. Question: If I delete agents from Agent Managed, do they get a new id? If that so, I guess that all overrides are no relevant anymore?

    Thanks

    Yaniv.

  • Hi Kevin. In addition to my question: I get 29106 event but the description is: "The request to synchronize state for OpsMgr Health Service identified by "83723021-5587-3763-c876-343d82f6c4fb" failed due to the following exception "Microsoft.Mom.ConfigService.Public.ConfigServiceException: An instance was deleted before its properties could be read. ---> Microsoft.EnterpriseManagement.Common.DataItemDoesNotExistException: An instance was deleted before its properties could be read.

      at Microsoft.Mom.ConfigService.DataAccess.DatabaseAccessor.QueryInstanceProperties(ReadOnlyCollection`1 instances)

      at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems.Instances.CollectPublicProperties(ReadOnlyCollection`1 identities, IConfigurationDataAccessor dataAccessor)

      at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems.ConfigurationItemCollection`2.CollectPublicProperties(IConfigurationDataAccessor dataAccessor)

      at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems..ctor(StateContext stateContext, IConfigurationDataAccessor dataAccessor)

      --- End of inner exception stack trace ---

      at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ConfigurationItems..ctor(StateContext stateContext, IConfigurationDataAccessor dataAccessor)

      at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.CreateResponse(Managers managers)

      at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.Managers.Synchronize(OnDoSynchronizedWork onDoSynchronizedWork)

      at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.Run(Guid source, String cookie, Managers managers, IConfigurationDataAccessor dataAccessor, Stream stream, IConnection connection)".

    What does it mean?

    Thanks

    Yaniv

  • I could resolve this issue restarting the Healthservice in all servers with this problem.

    Chau!

  • I recently implemented SCOM 2007 and get these errors shortly after an agent has been deployed to a server. Strangely enough the error does not persist the next day, and the agents show as monitored. Would you recommend I still delete them from agent managed and then approve in pending management? Just wanted to know if you've seen this sort of scenario before. Thanks.

  • @Adam - I havent seen that - but no - if you dont have agents in an unmonitored state - I wouldnt mess with them.  This is likely just a transient error caused by initial discovery of instances in your case.

  • Thanks for the hint, currently cleaning up SCOM and that event is on my list for a long time.

    I tried to query for these Ids in powershell months ago already, couldn't find anything.

  • I have the same problem like Yaniv Shmulevich ... but no a lot of servers including RMS!!!!

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Search Blogs