Upgrading an SMS 2003 SP3 with remote SQL server to SCCM 2007 SP1 is giving a lot of “failure audit” events on the remote SQL server

April 17, 2009 at 6:05 am in ConfigMgr, ConfigMgr 2007, sccm, SCCM 2007, SMS, Sms 2003 by Kenny Buntinx [MVP]


After the upgrade was done from SMS 2003 SP3 , we had a lot of “failure audit” events on the remote sql server (every 20 min).

Warnings are logged for an account that wants to access the SQL server. (Account is specified as network access account and Push installation account)

This is also logged in the ccm.log file on the SCCM 2007 SP1 primary site.

We have identified a cause for the errors being logged in the CCM.LOG. It appears to occur due to the SMS_CLIENT_CONFIG_MANAGER key in the registry, this key doesn’t appear
to be created in a fresh install of SCCM (checked on the fresh installed SCCM server in my sandbox)

Deleting this key will make the errors go away, the errors don’t cause any harm or functionality issues.


Actions taken:

-       Delete the registry key HKLM\Software\Microsoft\SMS\Components\SMS_CLIENT_CONFIG_MANAGER

-       Restarted the smsexec service and no failure audit anymore

-       Wait for another 20 min and no failure audit warnings anymore.


The Environment we worked on :

– SMS 2003 SP3 with remote SQL server.

– Server 2003 SP2 server OS


Thanks to Kurt Van Hoecke for putting this to our attention !

However , this method is NOT supported by Microsoft !

This posting is provided AS IS with no warranties !

Hope it Helps ,

Kenny Buntinx

Tweet about this on TwitterShare on FacebookShare on Google+Share on LinkedInPin on Pinterest