The OMSDK on our DW server has stopped working.  When we try to start it manually it will stop after a few seconds with 2 errors being logged...

Error 1: Event ID 26339

An exception was thrown while initializing the service container.
 Exception message: Initialize
 Full exception: Feature of type 'Microsoft.EnterpriseManagement.ServiceDataLayer.ISecureStorageManagerFeature, Microsoft.EnterpriseManagement.DataAccessService.Core, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' cannot be added to the container.

Error 2: Event ID 26380

The System Center Data Access service failed due to an unhandled exception.  
The service will attempt to restart. 
Exception: 

Microsoft.EnterpriseManagement.ConfigurationReaderException: Feature of type 'Microsoft.EnterpriseManagement.ServiceDataLayer.ISecureStorageManagerFeature, Microsoft.EnterpriseManagement.DataAccessService.Core, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' cannot be added to the container. ---> Microsoft.EnterpriseManagement.ComponentActivationException: The constructor for the component threw an exception. Please see the inner exception for more details. ---> System.Security.Cryptography.CryptographicException: Bad Data.

   at System.Security.Cryptography.CryptographicException.ThrowCryptogaphicException(Int32 hr)
   at System.Security.Cryptography.Utils._DecryptKey(SafeKeyHandle hPubKey, Byte[] key, Int32 dwFlags)
   at System.Security.Cryptography.RSACryptoServiceProvider.Decrypt(Byte[] rgb, Boolean fOAEP)
   at Microsoft.EnterpriseManagement.Security.AsymmetricKeyManager.Initialize(Byte[] publicKey)
   at Microsoft.EnterpriseManagement.Security.AsymmetricKeyManager..ctor(Byte[] key, Boolean self)
   at Microsoft.EnterpriseManagement.Security.SecureStorageManager.Initialize()
   at Microsoft.EnterpriseManagement.ServiceDataLayer.SecureStorageManagerFeatureImplementation..ctor()
   --- End of inner exception stack trace ---
   at Microsoft.EnterpriseManagement.ComponentActivator.Activate[T](ActivationContext`1 context)
   at Microsoft.EnterpriseManagement.SingletonLifetimeManager`1.GetComponent[K]()
   at Microsoft.EnterpriseManagement.LifetimeManagerWrapper`2.GetComponent[K]()
   at Microsoft.EnterpriseManagement.FeatureContainer.GetFeatureInternal[T](Type type, String featureName)
   at Microsoft.EnterpriseManagement.FeatureContainer.AddFeatureInternal[T,V](ActivationContext`1 context, String featureName)
   --- End of inner exception stack trace ---
   at Microsoft.EnterpriseManagement.ConfigurationReaderHelper.ReadFeatures(XPathNavigator navi, IContainer container)
   at Microsoft.EnterpriseManagement.ConfigurationReaderHelper.Process()
   at Microsoft.EnterpriseManagement.ServiceDataLayer.DispatcherService.Initialize(InProcEnterpriseManagementConnectionSettings configuration)
   at Microsoft.EnterpriseManagement.ServiceDataLayer.DispatcherService.InitializeRunner(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart(Object obj)

Initially I thought the issue might be AzMan related as I found several threads referencing it however I was able to connect to the AzMan stores in both the Service Manager database and DWStagingAndConfig (both of which are stored on a different SQL Server than the DW Management server as we had to fail them over some time ago using a walkthrough article posted on TechNet).

Any ideas on where to start looking?

Note: None of the passwords for the service accounts we use for SCSM have changed

Hi,

Please refer to the link below:

System Center Data Access Service Start Up Failure Due to SQL Configuration Change

http://blogs.technet.com/b/servicemanager/archive/2011/10/04/system-center-data-access-service-start-up-failure-due-to-sql-configuration-change.aspx

I only get 2 of the 3 errors mentioned in that post, the 26339 and 26380.  I get a 26331 logged as information and it states that "The System Center Data Access service has reestablished database connectivity.".

I am also able to access the AzMan store for both the ServiceManager and DWStagingAndConfig databases, so unless there is a 3rd (or more) AzMan store there don't seem to be any issues with that.

I've gone over the SQL server security and logins and all the proper permissions/rights seem to be in place from the original server.