Article ID: 949767 - View products that this article applies to.
A task sequence does not run on a Microsoft System Center Configuration Manager 2007 client computer. This issue occurs when you use the Pre-Boot Execution Environment (PXE) to run the task sequence.
Additionally, the Smsts.log file on the client computer may contain an error message that resembles the following:
The Smspxe.log file may contain information that resembles the following:
<![LOG[no cert available for policy decoding]LOG]!><time="time" date="date" component="TSPxe" context="" type="3" thread="1336" file="libsmsmessaging.cpp:4020">
<![LOG[CMPDBConnection::Init(): IDBInitialize::Initialize() failed with 0x80004005]LOG]!> <![LOG[=======================================]LOG]!> <![LOG[ MPDB ERROR - CONNECTION PARAMETERS SQL Server Name : <server name> Database Name : <database name> Integrated Auth : True MPDB ERROR - EXTENDED INFORMATION MPDB Method : Init() MPDB Method HRESULT : 0x80004005 Error Description : [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. OLEDB IID : <GUID> ProgID : Microsoft OLE DB Provider for SQL Server MPDB ERROR - INFORMATION FROM DRIVER Native Error no. : 17 Error State : 1 Class (Severity) : 16 <![LOG[======================================= ]LOG]!> <![LOG[MP: RaiseDBFailureStatusMessage failed to open registry 2] <![LOG[Failed to read PXE DB settings. Unspecified error (Error: 80004005; Source: Windows)]LOG]!> [LOG] ERROR: PXE Cert not set. This might cause client failures.
If a problem prevents the SMSPXE module from connecting to the SMS database, the SMSPXE module does not retry the connection immediately. Therefore, the SMSPXE module cannot download a certificate.
The configuration settings and the certicate are updated after an hour or after the Windows Deployment Services server (WDSServer) service restarts.
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
PrerequisitesNo prerequisites are required.
Restart requirementYou do not have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
System Center Configuration Manager 2007, x86-based version
Collapse this tableExpand this table
System Center Configuration Manager 2007, x64-based version
Collapse this tableExpand this table
To work around this problem, follow these steps:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/LN/ )Description of the standard terminology that is used to describe Microsoft software updates