System Configuration Manager 2007 R2 Gone Bad
I should title this system configuration manager gone bad #1 as I am sure this will not be the last time I will be writing about it.
In a situation where the success of advertisments to desktops is unpredictable and deployment of packages to desktops are not working start with the following article, during which if you notice that your servers mp_location.log error is full of errors return to this post and read on.
Insider’s Guide to Troubleshooting Client Content Download in Configuration Manager 2007
Step 3 of the article above desribes the mp_location.log file found on your Management Point server under \Program Files\SMS_CCM\Logs\, and possible errors it may contain. But it does not cover the following error which if you are using Trace32 from the Configuration Management Toolkit V2 will be a screen of red.
MPDB ERROR – CONNECTION PARAMETERS
SQL Server Name : database_servername
SQL Database Name : sms_sitename
Integrated Auth : True
MPDB ERROR – EXTENDED INFORMATION
MPDB Method : Init()
MPDB Method HRESULT : 0×80004005
Error Description : Cannot open database “sms_sitename” requested by the login. The login failed.
OLEDB IID : {0C733A8B-2A1C-11CE-ADE5-00AA0044773D}
ProgID : Microsoft OLE DB Provider for SQL Server
MPDB ERROR – INFORMATION FROM DRIVER
SQL Server Name : database_servername
Native Error no. : 4060
Error State : 1
Class (Severity) : 11
Line number in SP : 1
In addition your database server may well be logging event id 6512
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 6512
Date: 24/11/2010
Time: 18:18:53
User: domain\serviceaccount
Computer: database_servername
Description:
Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0×80004005. You need to restart SQL server to use CLR integration features.
When you check the whether CLR is enabled using the SQL Server Surface Area Configuration you may find it is, and that it has been enabled in the past because advertisments and deployments worked in the past.
It is the solution though, no matter how much you don’t like it, a critical update or service pack may have been applied to the .net framework 2.0 since it last worked and SQL Server requires a restart. If you want to be sure you can browse the database assemblies under programability and you will probably receive the same error message.
Time to suck it up, stay late and do a 30 second restart of the SQL server and agent services. Following that restart the SMS Executive and related services on your Configuration Manager server and within minutes your world will be a better place.
