Quantcast
Channel: Configuration Manager 2007 Operating System Deployment forum
Viewing all articles
Browse latest Browse all 1063

Task Sequence Auto Apply Drivers fails - CMPDBConnection::ExecuteSQL(): ICommandText::Execute() failed with 0x80040E14

$
0
0

SCCM 2007 SP2 R2--

I have copied my working task sequences for Operation System Deployment (Windows 2008 R2) because I am introducing new hardware into our environment.  After adding new drivers to the Boot image and to the Drivers catalog, I am now experiencing an issues when running the TS.


In my SMSTS.log, I see these errors:

***************    SMSTS.LOG   ********************************

Processing driver match result.    OSDDriverClient    7/25/2012 9:48:01 AM    1296 (0x0510)
XML parsing error at line 1 char 1: Invalid at the top level of the document.
Request failed (Code 0x80040e14)    OSDDriverClient    7/25/2012 9:48:01 AM    1296 (0x0510)
bSuccess == ((VARIANT_BOOL)-1), HRESULT=80004005 (e:\nts_sms_fre\SMS\common\inc\ccmxml.h,1116)    OSDDriverClient    7/25/2012 9:48:01 AM    1296 (0x0510)
spXMLDoc.loadFromXML(pszResponse), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\onlinedrivercatalog.cpp,536)    OSDDriverClient    7/25/2012 9:48:01 AM    1296 (0x0510)
Server response: Request failed (Code 0x80040e14)    OSDDriverClient    7/25/2012 9:48:01 AM    1296 (0x0510)
processDriverResponse( sResponseBody, fpCallbackProc, pvCallbackData, matchResultMap ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\onlinedrivercatalog.cpp,457)    OSDDriverClient    7/25/2012 9:48:01 AM    1296 (0x0510)
Failed to process driver catalog response. Code 0x80004005    OSDDriverClient    7/25/2012 9:48:01 AM    1296 (0x0510)
pDriverCatalog->match( deviceList, m_fpCallbackProc, m_pvCallbackData, matchResultMap ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,854)    OSDDriverClient    7/25/2012 9:48:01 AM    1296 (0x0510)
pDriverInstaller->AutoInstallDrivers( pDriverCatalog, bBestMatch ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,286)    OSDDriverClient    7/25/2012 9:48:01 AM    1296 (0x0510)
Failed to auto provision driver. Code 0x80004005    OSDDriverClient    7/25/2012 9:48:01 AM    1296 (0x0510)
ProcessAutoProvision( pDriverInstaller, bBestMatch ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,415)    OSDDriverClient    7/25/2012 9:48:01 AM    1296 (0x0510)
Failed to auto provision drivers.  Code 0x80004005    OSDDriverClient    7/25/2012 9:48:01 AM    1296 (0x0510)
Exiting with return code 0x80004005    OSDDriverClient    7/25/2012 9:48:01 AM    1296 (0x0510)
Process completed with exit code 2147500037    TSManager    7/25/2012 9:48:01 AM    1632 (0x0660)
!--------------------------------------------------------------------------------------------!    TSManager    7/25/2012 9:48:01 AM    1632 (0x0660)
Failed to run the action: Post Install - Auto Apply Drivers.
Unspecified error (Error: 80004005; Source: Windows)    TSManager    7/25/2012 9:48:01 AM    1632 (0x0660)

I have also checked my NLB MP's and have found this error in the MP_DriverMgr.log

********************* MP_DriverMgr.log  *******************************************

CMPDBConnection::ExecuteSQL(): ICommandText::Execute() failed with 0x80040E14    MP_DriverManager    7/24/2012 12:47:50 PM    7436 (0x1D0C)
=======================================    MP_DriverManager    7/24/2012 12:47:50 PM    7436 (0x1D0C)

MPDB ERROR - CONNECTION PARAMETERS
SQL Server Name     : SERVERNAME
SQL Database Name   : SMS_AM0_RPL
Integrated Auth     : True

MPDB ERROR - EXTENDED INFORMATION
MPDB Method         : ExecuteSP()
MPDB Method HRESULT : 0x80040E14
Error Description   : Syntax error or access violation
OLEDB IID           : {0C733A63-2A1C-11CE-ADE5-00AA0044773D}
ProgID              : Microsoft OLE DB Provider for SQL Server

MPDB ERROR - INFORMATION FROM DRIVER
null    MP_DriverManager    7/24/2012 12:47:50 PM    7436 (0x1D0C)
=======================================
    MP_DriverManager    7/24/2012 12:47:50 PM    7436 (0x1D0C)
Failed to execute strored procedure: MP_MatchDrivers, hr=0x80040e14    MP_DriverManager    7/24/2012 12:47:50 PM    7436 (0x1D0C)
Failed to execute MatchDrivers task, hr=0x80040e14    MP_DriverManager    7/24/2012 12:47:50 PM    7436 (0x1D0C)
Response message sent to the client    MP_DriverManager    7/24/2012 12:47:50 PM    7436 (0x1D0C)
Failed to execute task, hr=0x80040e14    MP_DriverManager    7/24/2012 12:47:50 PM    7436 (0x1D0C)
Executing Driver Request - Match    MP_DriverManager    7/25/2012 9:48:01 AM    3740 (0x0E9C)
XML Schema support is not installed, XML validation will be skipped.    MP_DriverManager    7/25/2012 9:48:01 AM    3740 (0x0E9C)
CMPDBConnection::ExecuteSQL(): ICommandText::Execute() failed with 0x80040E14    MP_DriverManager    7/25/2012 9:48:01 AM    3740 (0x0E9C)
=======================================    MP_DriverManager    7/25/2012 9:48:01 AM    3740 (0x0E9C)

MPDB ERROR - CONNECTION PARAMETERS
SQL Server Name     : SERVERNAME
SQL Database Name   : SMS_AM0_RPL
Integrated Auth     : True

MPDB ERROR - EXTENDED INFORMATION
MPDB Method         : ExecuteSP()
MPDB Method HRESULT : 0x80040E14
Error Description   : Syntax error or access violation
OLEDB IID           : {0C733A63-2A1C-11CE-ADE5-00AA0044773D}
ProgID              : Microsoft OLE DB Provider for SQL Server

MPDB ERROR - INFORMATION FROM DRIVER
null    MP_DriverManager    7/25/2012 9:48:01 AM    3740 (0x0E9C)
=======================================
    MP_DriverManager    7/25/2012 9:48:01 AM    3740 (0x0E9C)
Failed to execute strored procedure: MP_MatchDrivers, hr=0x80040e14    MP_DriverManager    7/25/2012 9:48:01 AM    3740 (0x0E9C)
Failed to execute MatchDrivers task, hr=0x80040e14    MP_DriverManager    7/25/2012 9:48:01 AM    3740 (0x0E9C)
Response message sent to the client    MP_DriverManager    7/25/2012 9:48:01 AM    3740 (0x0E9C)
Failed to execute task, hr=0x80040e14    MP_DriverManager    7/25/2012 9:48:01 AM    3740 (0x0E9C)

*********************************

Any pointer where to look to troubleshoot this issue more? 


Viewing all articles
Browse latest Browse all 1063

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>