SCOM R2 Health Service Event ID 7009 The Health Service cannot find the credential for the action account
-
Thursday, December 03, 2009 6:59 PMHello everyone,
I am am having issue, I have two server, they are clustered, recently i needed to remove agents those two agents. Today I tried to install agent on both node, in one node i got installed right away, on the other node i had to import "WindowsAccountLockDownSD" key from another machine in order to start health service on the server. When i looked the these two agents under agent managed they look health and cluster names has discovered. How ever i am getting following errors on these two server;
Event Type: Error
Event Source: HealthService
Event Category: Health Service
Event ID: 7009
Date: 12/3/2009
Time: 1:44:11 PM
User: N/A
Computer: ABCSQL01
Description:
The Health Service cannot find the credential for the action account for management group ABC. Monitoring will be significantly impacted
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
and
Event Type: Error
Event Source: HealthService
Event Category: Health Service
Event ID: 7005
Date: 12/3/2009
Time: 1:44:11 PM
User: N/A
Computer: ABCSQL02
Description:
The Health Service was unable to publish its public key to management group ABC and will be unable to receive secure messages until this key is published. Attempts to publish the key will continue.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
and on the RMS server;
Event Type: Warning
Event Source: OpsMgr Config Service
Event Category: None
Event ID: 29106
Date: 12/3/2009
Time: 1:41:01 PM
User: N/A
Computer: ABCSCOM01
Description:
The request to synchronize state for OpsMgr Health Service identified by "393cdce1-0858-1429-35d2-18e833395111" failed due to the following exception "Microsoft.Mom.ConfigService.DataAccessAbstraction.HealthServicePublicKeyNotRegisteredException: Missing certificate for Healthservice id 393cdce1-0858-1429-35d2-18e833395111 ---> Microsoft.EnterpriseManagement.Common.ObjectNotFoundException: Missing certificate for Healthservice id 393cdce1-0858-1429-35d2-18e833395111
at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.RootConnectorMethods.GetHealthServicePublicKey(Guid healthServiceId)
at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.RootConnectorMethods.EncryptContentForHealthService(Guid healthServiceId, Byte[] content)
at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.RootConnectorMethods.EncryptContentForHealthService(Guid healthServiceId, String content)
at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.RootConnectorMethods.OnRetrieveSecureData(Guid healthServiceId, ReadOnlyCollection`1 addedSecureStorageReferences, ReadOnlyCollection`1 removedSecureStorageReferences, ReadOnlyCollection`1 modifiedSecureStorageReferences, ReadOnlyCollection`1 addedSecureStorageElements, ReadOnlyCollection`1 removedSecureStorageElements, ReadOnlyCollection`1 modifiedSecureStorageElements)
--- End of inner exception stack trace ---
Server stack trace:
at Microsoft.EnterpriseManagement.Mom.ServiceDataLayer.RootConnectorMethods.OnRetrieveSecureData(Guid healthServiceId, ReadOnlyCollection`1 addedSecureStorageReferences, ReadOnlyCollection`1 removedSecureStorageReferences, ReadOnlyCollection`1 modifiedSecureStorageReferences, ReadOnlyCollection`1 addedSecureStorageElements, ReadOnlyCollection`1 removedSecureStorageElements, ReadOnlyCollection`1 modifiedSecureStorageElements)
at Microsoft.EnterpriseManagement.Mom.Sdk.Service.SDKReceiver.OnRetrieveSecureData(Guid healthServiceId, ReadOnlyCollection`1 addedSecureStorageReferences, ReadOnlyCollection`1 removedSecureStorageReferences, ReadOnlyCollection`1 modifiedSecureStorageReferences, ReadOnlyCollection`1 addedSecureStorageElements, ReadOnlyCollection`1 removedSecureStorageElements, ReadOnlyCollection`1 modifiedSecureStorageElements)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.EnterpriseManagement.Mom.Internal.ISdkService.OnRetrieveSecureData(Guid healthServiceId, ReadOnlyCollection`1 addedSecureStorageReferences, ReadOnlyCollection`1 removedSecureStorageReferences, ReadOnlyCollection`1 modifiedSecureStorageReferences, ReadOnlyCollection`1 addedSecureStorageElements, ReadOnlyCollection`1 removedSecureStorageElements, ReadOnlyCollection`1 modifiedSecureStorageElements)
at Microsoft.Mom.ConfigService.Networking.ConnectionFactory.Connection.Sender.OnRetrieveSecureData(Guid healthServiceId, ReadOnlyCollection`1 addedSecureStorageReferences, ReadOnlyCollection`1 removedSecureStorageReferences, ReadOnlyCollection`1 modifiedSecureStorageReferences, ReadOnlyCollection`1 addedSecureStorageElements, ReadOnlyCollection`1 removedSecureStorageElements, ReadOnlyCollection`1 modifiedSecureStorageElements)
at Microsoft.Mom.ConfigService.Networking.ConnectionFactory.Connection.OnRetrieveSecureData(Guid healthServiceId, ReadOnlyCollection`1 addedSecureStorageReferences, ReadOnlyCollection`1 removedSecureStorageReferences, ReadOnlyCollection`1 modifiedSecureStorageReferences, ReadOnlyCollection`1 addedSecureStorageElements, ReadOnlyCollection`1 removedSecureStorageElements, ReadOnlyCollection`1 modifiedSecureStorageElements)
at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ResponseWriter.SecureDataWriter.Write(StateSyncResponseMessage response)
at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ResponseWriter.WriteState(StateSyncResponseMessage response)
at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ResponseWriter.Write(StateSyncResponseMessage response)
at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.ResponseWriter.Write(StateContext stateContext, ConfigurationItems configurationItems, StateSyncResponseMessage response, IConnection connection)
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.Execute(Managers managers)
at Microsoft.Mom.ConfigService.Engine.ConfigurationEngine.CommunicationHelper.StateSyncRequestTask.Run(Guid source, String cookie, Managers managers, IConfigurationDataAccessor dataAccessor, Stream stream, IConnection connection)".
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: OpsMgr SDK Service
Event Category: None
Event ID: 26316
Date: 12/3/2009
Time: 2:02:09 PM
User: N/A
Computer: ABCSCOM01
Description:
A certificate was not found for Health Service with identifier 393cdce1-0858-1429-35d2-18e833395111.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I tried to repair two agents under agent managed, it did not work;
I remove the agents and delete the agents certificates on both server and delete the registry entries, and installation folder.
I install agents again, unfortunately it did not resolve the issue.
any suggestions?
RMS: SCOM R2 6.1.7221.0
MS: R2 6.1.7221.0
Two agents;
Win2003 X64 SQL Clusters;
Agent version: 6.1.7221.0
Any suggestion? any idea?
Thanks,
Orhan
Orhan Taskin
All Replies
-
Friday, December 04, 2009 7:25 PM
Solution worked;
Remove uninstall or remove agent from operation console.
Deploy agent from operation console or install manually,
re-import the mentinoned key from previous posts and start the service.
Stop RMS config service
Start RMS config service,
Stop RMS health service
Start RMS health Service.
Check event log; it should be communicating correctly.
Orhan Taskin- Marked As Answer by Orhan Taskin Friday, December 04, 2009 7:26 PM

