Poser une questionPoser une question
 

QuestionSCE SP1 Group Memberships Not Reflected in WSUS

  • lundi 30 novembre 2009 23:39Bob Laszko Médailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateur
     

    I've been researching this problem and trying fixes off and on for a few weeks. Hoping that someone with more experience with SCE and WSUS will be able to help me solve it. Sorry, but I cannot think of a single event or process that might have caused the issue, only that I noticed the problem and can replicate it at will. Not sure either if the problem resides in SCE or WSUS or a combination of both. I'll explain that below. Currently running SCE SP1 v.6.0.1885.0, WSUS v.3.2.7600.226 and SQL 2005 v.9.0.4053 on Server 2003 SP2. Everything patched current through last week. The SCE / WSUS environment has been stable for quite some time ... at least as stable as can be expected from the current SCE / WSUS versions. So ....... here are the symptoms ....

    1. Create a group in SCE with one member. The group appears in WSUS, but without any members. Count in WSUS shows 0 of 0, 47 total. Update status is 'Any'. (PROBLEM #1)

    2. Add more members to the group in SCE. All members appear if Properties are selected, but only the original computer is listed if the group name is selected in the Computers panel. (PROBLEM #2). No change in WSUS ... group name appears, but no members listed.

    I have tried using Refresh in both SCE and WSUS, but no change. Same if I restart the OpsMgr Health Service. Same if I wait 2+ hours to allow the System.SCE.MP.GroupSynchronizationRule to run. Same if I assign some updates to the group via SCE after creating the group.

    To the best of my recollection, I have not made changes in WSUS ..... only in SCE.


    Listed below are some of the OpsMgr events that I think are pertenant to this issue:

    Event Type: Warning
    Event Source: Health Service Modules
    Event Category: None
    Event ID: 31401
    Date:  11/30/2009
    Time:  12:15:25 PM
    User:  N/A
    Computer: ESC-IT-03
    Description:
    An exception occured processing a group membership rule -- retrying:
     Subscription ID: c16e296d-3ed4-4f49-8382-5f84bc78fb98
     Rule ID: 01837450-a5f0-70f1-7639-3a653f0be1dc
     Group ID: f983c360-58c7-bd3b-b4bf-95cd3ba31d92
     Group type name: Microsoft.SystemCenter.Essentials.DefaultUser.DeploymentGroup_c30f14b1701f442b9074d8aaf32978df
     Exception: System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
    Parameter name: index
       at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
       at System.ThrowHelper.ThrowArgumentOutOfRangeException()
       at System.Collections.Generic.List`1.get_Item(Int32 index)
       at System.Collections.ObjectModel.ReadOnlyCollection`1.System.Collections.Generic.IList<T>.get_Item(Int32 index)
       at Microsoft.EnterpriseManagement.Common.ResultSet.get_Item(Int32 index)
       at Microsoft.EnterpriseManagement.Mom.DataAccess.DataAccessUtility.GetManagedEntityKeyValuePairs(Guid baseManagedEntityId, Guid managedTypeId, Int32 mtvRow, QueryResults mtvQueryResults, ReadOnlyCollection`1 keyPropPairs, DatabaseConnection databaseConnection)
       at Microsoft.EnterpriseManagement.Mom.DataAccess.DataAccessUtility.GetManagedEntityKeyValuePairs(Guid baseManagedEntityId, DatabaseConnection databaseConnection)
       at Microsoft.EnterpriseManagement.Mom.DataAccess.EntityKeyValuePairCache.GetKeyValuePairs(Guid baseManagedEntityId, DatabaseConnection databaseConnection)
       at Microsoft.EnterpriseManagement.Mom.DatabaseQueryModules.ExpressionEvaluatorForSnapshot.GetIncludeListMembershipChangesForSnapshot(IList`1 includeList, Guid groupInstanceId, Guid groupTypeId, Guid relationshipId, Guid targetManagedTypeId, ReadOnlyCollection`1 groupKeyNameValuePairs, DatabaseConnection databaseConnection)
       at Microsoft.EnterpriseManagement.Mom.DatabaseQueryModules.MembershipRuleEvaluator.EvaluateSnapshot(MembershipSubscription subscription, DatabaseConnection databaseConnection)
       at Microsoft.EnterpriseManagement.Mom.DatabaseQueryModules.MembershipCalculationManager.SnapshotCalculation(MembershipSubscription membershipSubscription, DatabaseConnection databaseConnection)

    Event Type: Warning
    Event Source: Health Service Modules
    Event Category: None
    Event ID: 31401
    Date:  11/30/2009
    Time:  12:15:29 PM
    User:  N/A
    Computer: ESC-IT-03
    Description:
    An exception occured processing a group membership rule -- retrying:
     Subscription ID: a099fb9b-f8c1-48ec-8fcc-953a881cc529
     Rule ID: 335d2d7f-e371-d8be-b7a0-9b10f6f578e0
     Group ID: 4fd5c374-4b41-6506-1a2a-5ccc7d95bc7a
     Group type name: Microsoft.SystemCenter.Essentials.DefaultUser.DeploymentGroup_0ad21e48a77f4678be4362b3b8bd251a
     Exception: System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
    Parameter name: index
       at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
       at System.ThrowHelper.ThrowArgumentOutOfRangeException()
       at System.Collections.Generic.List`1.get_Item(Int32 index)
       at System.Collections.ObjectModel.ReadOnlyCollection`1.System.Collections.Generic.IList<T>.get_Item(Int32 index)
       at Microsoft.EnterpriseManagement.Common.ResultSet.get_Item(Int32 index)
       at Microsoft.EnterpriseManagement.Mom.DataAccess.DataAccessUtility.GetManagedEntityKeyValuePairs(Guid baseManagedEntityId, Guid managedTypeId, Int32 mtvRow, QueryResults mtvQueryResults, ReadOnlyCollection`1 keyPropPairs, DatabaseConnection databaseConnection)
       at Microsoft.EnterpriseManagement.Mom.DataAccess.DataAccessUtility.GetManagedEntityKeyValuePairs(Guid baseManagedEntityId, DatabaseConnection databaseConnection)
       at Microsoft.EnterpriseManagement.Mom.DataAccess.EntityKeyValuePairCache.GetKeyValuePairs(Guid baseManagedEntityId, DatabaseConnection databaseConnection)
       at Microsoft.EnterpriseManagement.Mom.DatabaseQueryModules.ExpressionEvaluatorForSnapshot.GetIncludeListMembershipChangesForSnapshot(IList`1 includeList, Guid groupInstanceId, Guid groupTypeId, Guid relationshipId, Guid targetManagedTypeId, ReadOnlyCollection`1 groupKeyNameValuePairs, DatabaseConnection databaseConnection)
       at Microsoft.EnterpriseManagement.Mom.DatabaseQueryModules.MembershipRuleEvaluator.EvaluateSnapshot(MembershipSubscription subscription, DatabaseConnection databaseConnection)
       at Microsoft.EnterpriseManagement.Mom.DatabaseQueryModules.MembershipCalculationManager.SnapshotCalculation(MembershipSubscription membershipSubscription, DatabaseConnection databaseConnection)

    ........ quite a few more event id 31401, then three event id 30202:


    Event Type: Error
    Event Source: System Center Essentials
    Event Category: None
    Event ID: 30202
    Date:  11/30/2009
    Time:  12:16:58 PM
    User:  N/A
    Computer: ESC-IT-03
    Description:
    The SCE Group identified by
    '30753587-1af7-90ce-c97f-f8f3d9a4e7e6'
    could not synchronize to its associated WSUS Group identified by
    '97b065a6-c64a-4e34-b86f-b5bbbf07b8ba'
    because the SCE Group could not be found.

    The module will be unloaded.

    Management Group: ESC-IT-03_MG
    Rule: System.SCE.MP.GroupSynchronizationRule
    Instance: 97b065a6-c64a-4e34-b86f-b5bbbf07b8ba.30753587-1af7-90ce-c97f-f8f3d9a4e7e6
    Instance Id:{BA6221CA-B360-CDC6-E589-AD426F8DA203}

    Event Type: Error
    Event Source: System Center Essentials
    Event Category: None
    Event ID: 30202
    Date:  11/30/2009
    Time:  12:16:58 PM
    User:  N/A
    Computer: ESC-IT-03
    Description:
    The SCE Group identified by
    '3b0d02f0-bed0-1fbf-91d0-21ac3d376c8b'
    could not synchronize to its associated WSUS Group identified by
    'e3aa4b1c-d214-4d76-adb7-a4caa52d6592'
    because the SCE Group could not be found.

    The module will be unloaded.

    Management Group: ESC-IT-03_MG
    Rule: System.SCE.MP.GroupSynchronizationRule
    Instance: e3aa4b1c-d214-4d76-adb7-a4caa52d6592.3b0d02f0-bed0-1fbf-91d0-21ac3d376c8b
    Instance Id:{9A65FE7B-1858-D381-8159-DC66C3272A9D}

    Event Type: Error
    Event Source: System Center Essentials
    Event Category: None
    Event ID: 30202
    Date:  11/30/2009
    Time:  12:16:58 PM
    User:  N/A
    Computer: ESC-IT-03
    Description:
    The SCE Group identified by
    '0c2e59d1-e3fd-8ced-cc99-9fa5c3c00dad'
    could not synchronize to its associated WSUS Group identified by
    'd77dee8c-8da5-41c9-ab4e-8adc39f01f8e'
    because the SCE Group could not be found.

    The module will be unloaded.

    Management Group: ESC-IT-03_MG
    Rule: System.SCE.MP.GroupSynchronizationRule
    Instance: d77dee8c-8da5-41c9-ab4e-8adc39f01f8e.0c2e59d1-e3fd-8ced-cc99-9fa5c3c00dad
    Instance Id:{82359ABD-7286-3FC2-0873-BF10CD46E852}

    There are a heckuva lot more event ids and instances than just these two. I'll be happy to post any of those or any other information that might assist in figuring out the problem(s).

    Thanks in advance,

    Bob Laszko
    Spanky's Portable Services
    rlaszko@spankysps.com

Toutes les réponses

  • mercredi 2 décembre 2009 11:40Yog Li - MSFTMSFT, ModérateurMédailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateur
     
    Hello Bob,

    Did you ever delete any Computer Group in WSUS console before this issue occured? For example, "All computers" or "All servers"? If so, try the solution in the thread below:

    Deleted "All Clients" group by mistake
    http://social.technet.microsoft.com/forums/en-US/systemcenter/thread/272c53de-cc76-44cc-a843-41dd62c5b5b7/

    Multiple issues
    http://social.technet.microsoft.com/forums/en-US/systemcenter/thread/01cd4140-a880-4792-be1d-930ab5d1958a/

    Besides, did the issue just occur after upgrading WSUS 3.1 to 3.2?

    Thanks,

    Yog Li - MSFT
  • mercredi 2 décembre 2009 14:35Bob Laszko Médailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateur
     
    Yog Li,

    Thanks for the reply.

    Yes, it's entirely possible that I deleted a group i WSUS. With that in mind, a couple of weeks ago I tried the suggstion from the the first link that you listed. All of the TargetGroupID records already matched the same groups listed in TargetGroupID field :<

    I have seen and reviewed the second link as well, but didn't think it would apply to my situation. If you're recommending that I try it, even though the 'default' groups of All Computers, All Servers and All Clients are intact, what steps, if any, should I take to preserve changes that could be wiped out by deleting MPs?

    We upgraded to WSUS 3.2 a couple of months ago. Everything worked fine until just a couple of weeks ago.

    Thanks again for your assistance.

    Bob Laszko

  • jeudi 3 décembre 2009 10:53Yog Li - MSFTMSFT, ModérateurMédailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateur
     
    Hello Bob,

    There's no need to try to restore the default groups if they are no deleted. If you did delete a group from WSUS console, try the steps in the following thread to delete the Group from the database.

    Event ID 30201
    http://social.technet.microsoft.com/Forums/en-US/systemcenter/thread/7ee2423f-4f89-4eef-aa6e-5bf8598686f8/

    Hope it helps,
    Yog Li - MSFT
  • lundi 7 décembre 2009 22:07Björn Axell MVP - Advisec ABMVPMédailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateur
     
    Bob,
    There is a limitation in SCE as for the number of groups that you can have. If you have more then 24-28 groups (inlcuding the default) you will start getting sync errors and the groups will be out of sync.

    How many groups do you have (if you look in the computer space)


    Björn Axell MVP - Advisec AB http://blog.advisec.com
  • jeudi 10 décembre 2009 16:31Bob Laszko Médailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateur
     
    Yog Li,

    Sorry for the delay in responding. I didn't get any auto-alert emails that you had left another message :<

    I had previously tried the tips given in the link you suggested (http://social.technet.microsoft.com/Forums/en-US/systemcenter/thread/7ee2423f-4f89-4eef-aa6e-5bf8598686f8/) but had no luck because the GUID identified  in "The SCE Group identified by" part of the event error was not listed in any record under in the MOMGroupIDxxxxxxxx field.

    However, I looked at it again this morning and found that the GUIDs identified in two of the three event errors were now in OperationsManager.MT_DeploymentSettings in the MOMGroupIDxxxxxx field. The group names matched what I had created in SCE. As a test, I have deleted one of the records. I'm going to let the synchronization happen 'naturally', so I'l wait two hours and see what happens. I'll post the results as soon as I can.

    Thanks again for the assist.

    Bob Laszko

  • jeudi 10 décembre 2009 16:32Bob Laszko Médailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateur
     
    Bjorn,

    Thanks for the tip, but I had already come across that one too. I only have eight groups defined.

    Bob Laszko
  • mercredi 16 décembre 2009 01:23Bob Laszko Médailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateurMédailles de l'utilisateur
     
    Yog Li,

    Sorry, but same results as I posted in my original message. Group members appear in the Computer pane of SCE if they are entered at the same time as the group is created. Otherwise, group members added after the group was created do not appear in the Computer pane, but do appear if the properties for the group are displayed.

    In all cases, the group names appear in WSUS, but without any members.