SCOM 2012 SP1 UR5 Failed

Today we have to update our management server from SCOM 2012 SP1 UR4 to SCOM 2012 SP1 UR5.

We have installed the KB 2904680 in the management server and after rebooting it, the Microsoft System Center Data Access Service started and died ten seconds later, generating the following errors in the event viewer under de Operations Manager log:

Event  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.IAuthorizationFeature, Microsoft.EnterpriseManagement.DataAccessService.Core, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' cannot be added to the container. ---> System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.UnknownAuthorizationStoreException]: The creator of this fault did not specify a Reason.

   at Microsoft.EnterpriseManagement.Mom.Sdk.Authorization.AzManHelper.Initialize(String pathToStore, String appName, AzManHelperModes helperMode, String storeDesc, String appDesc)

   at Microsoft.EnterpriseManagement.Mom.Sdk.Authorization.AuthManager.Initialize(AuthManagerModes authMode)

   at Microsoft.EnterpriseManagement.ServiceDataLayer.AuthorizationFeatureImplementation.Initialize(IContainer container)

   at Microsoft.EnterpriseManagement.SingletonLifetimeManager`1.GetComponent[K]()

   at Microsoft.EnterpriseManagement.FeatureContainer.GetFeatureInternal[T](Type type, 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.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

   at System.Threading.ThreadHelper.ThreadStart(Object obj)

Event 26339

-----------------

An exception was thrown while initializing the service container.

 Exception message: Initialize

 Full exception: Feature of type 'Microsoft.EnterpriseManagement.ServiceDataLayer.IAuthorizationFeature, Microsoft.EnterpriseManagement.DataAccessService.Core, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' cannot be added to the container.

Event 26325

-----------------

An authorization store exception was thrown in the System Center Data Access service. Exception message: Unable to perform the operation because of authorization store errors.

After two hours of looking for the problem and with the help of  one guy from SCOM Microsoft Support, we found it.
The problem was in the SQL mixed authentication, SCOM doesn't allow you to have one SQL user (not domain user) as db_owner rol in the SCOM operations database.

I don´t know if it is a SCOM bug or not, I have found some reference in this post http://blogs.technet.com/b/mihai/archive/2012/05/23/know-issues-when-upgrading-from-om-2007-r2-to-om-2012.aspx and official documentation here http://technet.microsoft.com/en-us/library/dn249696.aspx.

The generated events were confusing and this exception should be handled, to make the debugging  easier.
In conclusion, be careful with SQL authentication users into the SCOM database.