Event ID 30201
Ok I seem to be getting this message crop up a couple of times in the event log. I have done the usual trawl through Google and forums. and can not seem to come up with any information regarding it. would someone please shed some light on this for me?
Event ID 30201
The SCE Group identified by 'e05fcdb2-fe77-7f55-74b5-6e4d89487586' could not synchronize to its associated WSUS Group identified by 'dc75d636-c36a-4034-ae59-ff6239afd' because the SCE Group could not be found. The module will be unloaded. Management Group: GLOB_MG Rule: System.SCE.MP.GroupSynchronizationRule Instance: dc75d636-c36a-4034-ae59-ff6239afdf5e.e05fcdb2-fe77-7f55-5-6e4d89487586 Instance Id:{4C239FA7-A511-5239-0180-9E2D277B7F66}
Answers
Hi, Nigeld
Generally, this event ID indicates that WSUS computer groups are not same with SCE computer groups. It’s especially from that a computer group was deleted from the WSUS console, instead of using the SCE console.1. Open SCE console and navigate to Computers panel, check the SCE computer groups.
2. Open WSUS console and expand SCESERVER -> Computers -> All Computers, check the WSUS computer groups.
3. Make sure the two sets of computers groups are all same.
By the way, please note that it is NOT recommended to use WSUS Console to add/delete computer groups.
Hope it helps.
Sincerely,
Yog Li
Microsoft Online Community Support
Hi,
To resolve this issue, you can try to delete the Group from the database. To do so, follow these steps.
1. Open the SQL Server Management Studio by clicking Start -> All Programs -> Microsoft SQL Server 2005 -> SQL Server Management Studio.
2. Type the correct name of the SQL server in the “Server name” dialog and click Connect.
3. Expand Databases -> OperationsManager -> Tables, find the table dbo.MT_DeploymentSettings.
4. Right-click the table and choose “Open Table”.
5. In the table, find the string 'd32129be-54a1-0e3d-ac53-830cada8a3f0', which comes from the error message. It is in the column “MOMGroupID_XXXXXX”.
6. Verify the Name in the same row to make sure it is just the SCE Group which was deleted.
7. Delete the entry for the Group.
Hope it helps. Thanks.
Sincerely,
Yog Li
Microsoft Online Community Support
All Replies
Hi, Nigeld
Generally, this event ID indicates that WSUS computer groups are not same with SCE computer groups. It’s especially from that a computer group was deleted from the WSUS console, instead of using the SCE console.1. Open SCE console and navigate to Computers panel, check the SCE computer groups.
2. Open WSUS console and expand SCESERVER -> Computers -> All Computers, check the WSUS computer groups.
3. Make sure the two sets of computers groups are all same.
By the way, please note that it is NOT recommended to use WSUS Console to add/delete computer groups.
Hope it helps.
Sincerely,
Yog Li
Microsoft Online Community Support
- Hi Yog Li,
I have the same problem here: What I did:
1) Used the Windows Client Vista MP default name for a new computer group, added 1 machine
2) Deleted the MP as required when importing the new Vista MP (http://www.microsoft.com/downloads/details.aspx?FamilyID=a2d42208-d4fd-46a6-9e8d-0ff7694b5634&displaylang=en)
3) The Computer Group was deleted from the view (because of deleting the MP) but not real, in WSUS it's still visible and I get the error:
The SCE Group identified by
'd32129be-54a1-0e3d-ac53-830cada8a3f0'
could not synchronize to its associated WSUS Group identified by
'3293877e-492f-42bd-80e2-d448302b2f33'
because the SCE Group could not be found.
The module will be unloaded.
Management Group: HIMALIA_MG
Rule: System.SCE.MP.GroupSynchronizationRule
Instance: 3293877e-492f-42bd-80e2-d448302b2f33.d32129be-54a1-0e3d-ac53-830cada8a3f0
Instance Id:{18E283E0-01B7-DDDE-D1CC-B246EAA0B73F}
4) Now if I created a computer group in SCE myself with exact the same name SCE says that it already exists...
What now? (deleting the group manualy in WSUS doesnt' help)
Yours B. Hi,
To resolve this issue, you can try to delete the Group from the database. To do so, follow these steps.
1. Open the SQL Server Management Studio by clicking Start -> All Programs -> Microsoft SQL Server 2005 -> SQL Server Management Studio.
2. Type the correct name of the SQL server in the “Server name” dialog and click Connect.
3. Expand Databases -> OperationsManager -> Tables, find the table dbo.MT_DeploymentSettings.
4. Right-click the table and choose “Open Table”.
5. In the table, find the string 'd32129be-54a1-0e3d-ac53-830cada8a3f0', which comes from the error message. It is in the column “MOMGroupID_XXXXXX”.
6. Verify the Name in the same row to make sure it is just the SCE Group which was deleted.
7. Delete the entry for the Group.
Hope it helps. Thanks.
Sincerely,
Yog Li
Microsoft Online Community Support
- Hi Yog Li,
thank you very much for you help, indeed that helped. Great to do some "real men" direct database editing in SCE
)
Maybe the synchronization mechanism will be improved in SP1, it's not stable!
I searched already in the DB but didn't find the right table...
Yours B. - Hi, maybe I was a little bit to fast, the 30201 error has gone, but instead a new one appears that maybe has something to do with db deletions: Error 29106 OpsMgr Config Service
The request to synchronize state for OpsMgr Health Service identified by "c74473dc-4d19-abed-cc6e-64f5479199cc" 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..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)".
Yours B. Hi,
Thank you for your kind words and I am happy that we are making progress.
Regarding the new event 29106, it is a warning, and means what has been discovered in your enterprise was changed quickly. As a result, the configuration service didn't get a clean read. This may be because we modified the database directly.
The configuration service should keep trying again until it gets a clean read, so the event will repeat continually. It's really annoying but the event is harmless. I think we can safely ignore it.
Thanks.
Sincerely,
Yog Li
Microsoft Online Community Support
