Monday, July 15, 2013

Unknown SQL error in ConfigMgr after installing DotNet updates

Today I did onsite support at a customer because of ConfigMgr failure. After the weekend OS deployment wasn't working anymore. In the ConfigMgr console the following errors were seen:

The State System message file processing could not process file '********.SMX' and moved it to the corrupt directory. Review the statesys.log file for further details.
Microsoft SQL Server reported SQL message 50000, severity 16: *** Unknown SQL Error!

*** *** Unknown SQL Error!
CMessageProcessor - Encountered a non-fatal SQL error while processing
CMessageProcessor - Non-fatal error while processing ********.SMX

omGetServerRoleAvailabilityState could not read from the registry on <ConfigMgr server>; error = 6;
---->: Failed to get the Availability State on server <ConfigMgr server> fro role Distribution Point.

For it seems DotNet software updates were installed before the weekend. In total 14 (!) DotNet updates were installed after patch tuesday. After uninstalling KB2835393, KB2804576 and KB2840628 everything was working okay again.

Hope that Microsoft will fix this soon, because this is a mayor issue for customers who are using ConfigMgr!

Source: Edugeek > Thanks for sharing!

Update 16-7-2013: Looking on Microsoft support it seems that the issue is available only with KB2840628. No need to uninstall the other DotNet updates mentioned before. Microsoft is working on a update for the issue, so stay tuned for more later!

Update 19-7-2013: Microsoft has confirmed a few different issues with the latest .NET Framework 4 security update, KB 2840628, when applied to SQL Server 2012 (all versions) servers in a Configuration Manager environment. Microsoft is working on a revised update and will keep you posted. In the meantime, you can find temporary solutions for these issues in this blog post: Issues Reported with MS13-052 (KB2840628) and Configuration Manager


  1. I just had this same issue. I suspected it might be due to Windows Updates since that was the only thing that changed on the SCCM server. I did not, however, know which updates were the culprit. Thank you for your post as you saved me quite a bit of time.

    1. For is seems it only is a issue with SQL Server 2012 (all versions). Just follow steps mentioned in the update!

  2. Captured by Brian Mason first...

  3. It's been a long time since I've had an update break something. I forgot how annoying it is. Mean while I think I have broken WDS. Ugh.

  4. Thank you for this post. Argh.

  5. Hi, I have the same error in my Logs but Dont have any .NET 4 updates installed. Im running Server 2012 R2 with SQL 2012 SP1. Any suggestions??

    1. Just do a search on Installed Updates for KB2835393, KB2804576 and KB2840628. Don't know of another issue at the moment..

  6. As this is post from 2013, DO we still have this issue as I am seeing this error since SQL SP was updated on SQL Server which is running 2012 OS.