Kevin79 Posted November 1, 2013 Report post Posted November 1, 2013 I recently upgraded to SCCM 2012 R2. Now my secondary sites are getting the following error in the SMS_MP_CONTROLLER_MANAGER log file: Source: SMS Server Component: SMS_MP_CONTROL_MANAGER Severity: Error Message ID: 5420 Process ID: 1952 Thread ID: 4876 Description: Management Point encountered an error when connecting to the database <database name> on SQL Server <server name>\CONFIGMGRSEC. The OLEDB error code was 0x80040E14. The database is the version that is included with SCCM, so 2012 SQL (Express?) with Service Pack 1 and is one the secondary site server. Any idea how to resolve this error? Quote Share this post Link to post Share on other sites More sharing options...
Kevin79 Posted November 8, 2013 Report post Posted November 8, 2013 Anyone? I am getting this on most of my secondary sites (5 of 8) and reinstalling those secondary sites doesn't seem to help. Quote Share this post Link to post Share on other sites More sharing options...
geckostech Posted November 29, 2013 Report post Posted November 29, 2013 I'm getting this on one of mine too Quote Share this post Link to post Share on other sites More sharing options...
tecxx Posted December 17, 2013 Report post Posted December 17, 2013 hello, same issue here. happens with secondary sites that we upgraded from SCCM2012SP1, and happens with freshly installed SCCM2012R2 sites. Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted December 17, 2013 Report post Posted December 17, 2013 Check the version of SQL Express that's being installed. I noticed that I had to manually install SP1 on SQL Server 2012 Express. Quote Share this post Link to post Share on other sites More sharing options...
tecxx Posted December 18, 2013 Report post Posted December 18, 2013 Check the version of SQL Express that's being installed. I noticed that I had to manually install SP1 on SQL Server 2012 Express. i noticed the same, and was shocked that Microsoft is installing a three year old SQL Version with the R2 release. but well. SP1 is now installed, i will wait for some days and then post again if this solved the issue.... cheers Quote Share this post Link to post Share on other sites More sharing options...
