SQL errors after installing 2840628, (MS13-052)

There have been several reports of failures in the ConfigMgr environment shortly after installing this update. 

Scenario:
Server 2008  / 2008 R2
SQL 2012  / SQL 2012 SP1
ConfigMgr 2012 installed.
 KB 2840628, (MS13-052) .NET 4 update installed.



This update replaces (http://support.microsoft.com/kb/2656405/ )    MS12-034:


From Microsoft:


 

Issue 1: Configuration Manager 2012

Database replication between sites (CAS/Primary/Secondary) with SQL 2012 will fail.

The rcmctrl.log file on the failing site(s) will contain entries similar the following:

//

Launching 2 sprocs on queue ConfigMgrDRSQueue and 0 sprocs on queue ConfigMgrDRSSiteQueue. SMS_REPLICATION_CONFIGURATION_MONITOR

The asynchronous command finished with return message: [A .NET Framework error occurred during execution of user-defined routine or aggregate "spDRSActivation": ~~System.TypeInitializationException: The type initializer for 'System.Data.SqlClient.SqlConnection' threw an exception. ---> System.TypeInitializationException: The type initializer for 'System.Data.SqlClient.SqlConnectionFactory' threw an exception. ---> System.TypeInitializationException: The type initializer for 'System.Data.SqlClient.SqlPerformanceCounters' threw an exception. ---> System.MethodAccessException: Attempt by method 'System.Configuration.TypeUtil.CreateInstanceRestricted(System.Type, System.Type)' to access method 'System.Diagnostics.SwitchElementsCollection..ctor()' failed. ---> System.Security.SecurityException: Request failed… [truncated for readability]

//

Temporary workarounds

While investigation continues into the best long term solution, the following short term changes can be made to unblock customers in this state:

In SQL Management Studio on the affected server, change the Permission set to Unrestricted for the MessageHandlerService Assembly. This is done in the Assembly properties via:

SQL Server -> Databases -> (Site Database) -> Programmability -> Assemblies -> MessageHandlerService

Once the change is made, replication between sites should automatically recover within 5-10 minutes.

Issue 2: Configuration Manager 2012

Software Update Point synchronization may fail at the end of the sync process. The WSyncMgr.log will have entries similar to the following:

//

error 14: SQL Error Message Failed to generate documents:A .NET Framework error occurred during execution of user-defined routine or aggregate "fnGenerateLanternDocumentsTable": ~~System.TypeInitializationException: The type initializer for 'System.Data.SqlClient.SqlConnection' threw an exception. ---> System.TypeInitializationException: The type initializer for 'System.Data.SqlClient.SqlConnectionFactory' threw an exception. ---> System.TypeInitializationException: The type initializer for 'System.Data.SqlClient.SqlPerformanceCounters' threw an exception. ---> System.MethodAccessException: Attempt by method 'System.Configuration.TypeUtil.CreateInstanceRestricted(System.Type, System.Type)' to access method 'System.Diagnostics.SwitchElementsCollection..ctor()' failed. ---> System.Security.SecurityException: Request failed… [truncated for readability]

//

Temporary Workarounds

Similar to Issue 1, the SMSSQLCLR assembly Permission Set can be changed to Unrestricted. From SQL Management Studio:

SQL Server -> Databases -> (Site Database) -> Programmability -> Assemblies -> SMSSQLCLR

Issue 3: Configuration Manager 2007 <Unconfirmed>

Client location requests for content do not return any Distribution Points. The MP_Location.log on the Management Point will have entries similar to the following:

//

CMPDBConnection::ExecuteSQL(): ICommandText::Execute() failed with 0x80040E14

CHandleLocationRequest::CreateReply failed with error (80040e14).

//

Temporary Workarounds

We are still working to reproduce this internally. In the meantime, the same procedure noted in Issue 2 above should work around the issue.

Patch Uninstall

Uninstalling KB2840628 has been reported to resolve all issues.

However, removal of a security patch should not be a blanket recommendation; instead anyone that wishes to uninstall until a permanent solution is found should assess the risk of exposure in their own environment. Details on the security vulnerability can be found here:

https://technet.microsoft.com/en-us/security/bulletin/MS13-052

Update: Microsoft has released a blog about the topic so watch here for changes:
http://blogs.technet.com/b/configmgrteam/archive/2013/07/17/issues-reported-with-ms13-052-kb2840628-and-configmgr.aspx

 

Packages referenced by a specific task sequence that are Missing

So you have many task sequences but when you setup a DP you need to know if that DP is ready for that Task sequence. There are reports for Packages on a DP, Packages for a Task Sequence but here is a report that will tell you what packages are missing from the DP for the specific task sequence.

The current draw back is that this report doesn't check to makes sure the package is already installed, just deployed so I will update that soon. But here you go. Hope this helps with some deployments.



---------------------
TaskSequenceID = Task Sequence ID
ID = Distribution point ID

-----------------------------------------
SELECT ps.Name AS Name
, ps.SourceVersion
, ps.SourceDate
, ps.SourceSize
, ps.SourceCompressedSize
, ps.PackageID
FROM
(
SELECT DISTINCT v_TaskSequenceReferencesInfo.ReferencePackageID AS PackageID
FROM v_TaskSequenceReferencesInfo
WHERE v_TaskSequenceReferencesInfo.PackageID=@TaskSequenceID
) RefPkgs
JOIN v_PackageStatusRootSummarizer ps ON ps.PackageID = RefPkgs.PackageID
where RefPkgs.PackageID not in (SELECT v_Package.PackageID
FROM v_Package
INNER JOIN v_DistributionPoint ON v_Package.PackageID = v_DistributionPoint.PackageID
WHERE v_DistributionPoint.ServerNALPath LIKE '%' + @ID + '%')
ORDER BY ps.Name

SQL 2008 SP2 Support

I am sure many people have all been using it but it is now official that SQL 2008 SP2 is now supported on ConfigMgr 2007. According to Harini Muralidharan, Microsoft statement:

"System Center Configuration Manager 2007 SP1, SP2 and R2 now support Microsoft SQL Server 2008 SP2 as a Configuration Manager 2007 site database. The site system role of Reporting Services Point and the client status reporting feature of System Center Configuration Manager 2007 R2 are supported."

No updates are required to use it.

That being said many times people assume that they can just jump to the latest version of SQL or server platform. This is not always the case. The different product groups must test the new platforms to make sure they work correctly and stable with SCCM. Manytimes there might be a patch that needs to be install or a hotfix. As a general rule you can expect a notification from Microsoft no less than 90 Days after something like this happens. So while you can install it in your test enviroment you really should way the 90+ days for the product group to OK it. This will cause less Support calls to Microsoft and problems in your hiearchy.

Microsoft SQL Server 2008 R2 is now supported on Configuration Manager 2007 SP1 and SP2 and Configuration Manager 2007 R2

In case you missed the June annoucements from Microsoft regarding Configuration Manager 2007, SQL 2008 R2 is now supported for your enviroment.

http://blogs.technet.com/b/configmgrteam/archive/2010/06/30/configuration-manager-support-announcements-for-june-2010.aspx

SCCM support for SQL 2008

SQL Server 2008 is now supported on Configuration Manager 2007 RTM and SP1
System Center Configuration Manager 2007 (RTM and SP1) now supports the use of SQL Server 2008 as a site database. In order to upgrade a site-server database to SQL 2008 there are 2 hot fixes required:
· ConfigMgr 2007 RTM customers must apply hot fix KB955229
· ConfigMgr 2007 SP1 customers must apply hot fix KB955262

The following are requirements when performing a clean install on a SQL Server 2008 database:
· A clean install of ConfigMgr 2007 RTM on a SQL Server 2008 database is not supported. You must first install SQL Server 2005, upgrade to SQL Server 2008 and then apply hot fix KB955229
A clean install of ConfigMgr 2007 SP1 on a SQL Server 2008 database is supported, but should apply hot fix KB955262

Orignal link: http://social.technet.microsoft.com/Forums/en-US/configmgrannouncements/thread/729a17a4-eafa-4c98-b5d5-280aaa063f3a/