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? 

Looks like access denied when it tries to run a the stored procedure MP_MatchDrivers

Any configuration changes on your sql server?

• Marked as answer by Sabrina Shen Thursday, August 09, 2012 6:26 AM
• Unmarked as answer by y2kBug_sp7 Thursday, October 11, 2012 6:17 PM

Looks like access denied when it tries to run a the stored procedure MP_MatchDrivers

Any configuration changes on your sql server?

• Marked as answer by Sabrina Shen Thursday, August 09, 2012 6:26 AM
• Unmarked as answer by y2kBug_sp7 Thursday, October 11, 2012 6:17 PM

Hello,

I'm getting exactly the same problem as you. I can't work out how access is being denied, there have been no configuration changes on our SQL box but some of our task sequences have this error - could you expand on how you resolved the problem.

Any help would be good, am doing a lot of head scratching right now :-)

I have the exact same error today as well.  Any more information about this?  Auto Apply Drivers was working as intended up to just two weeks ago.

No, sorry, I never got the problem solved.  Instead I started using Driver Packages instead or Auto Apply Drivers TS step... 

• Proposed as answer by trenthoffer Friday, September 07, 2012 11:51 AM

No, sorry, I never got the problem solved.  Instead I started using Driver Packages instead or Auto Apply Drivers TS step... 

• Proposed as answer by trenthoffer Friday, September 07, 2012 11:51 AM

Hi y2kBug_sp7,

Yes, the same here, we had it with some new Dell R620s, the only workaround we found was using the Dell Driver Packages and removing the Apply Device Drivers step from our Task Sequence. We did phone Dell support but didn't get very far especially as the guy dealing with our case didn't know what SCCM was, ho hum

Hi Trenthoffer,

Funny... that is very similar to what happened to us.  We were adding drivers for some 12th Generation Dell servers too (R720, M620, M820, T320, T620) and began seeing the issue.  I guess this has something to do with the updated Dell drivers.

Same problem here, only with Lenovo D30.

I can't see how it would be an Access Denied issue as we have many, many other models that work just fine.

Nick.

Hi All Did  you guyz find a resolution for this ? I am having same error while Installing Power edge R620 

Below shows SMSTS.log

Failed to process driver catalog response. Code 0x80004005 OSDDriverClient 10/11/2012 12:31:21 PM 1084 (0x043C)
pDriverCatalog->match( deviceList, m_fpCallbackProc, m_pvCallbackData, matchResultMap ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,854) OSDDriverClient 10/11/2012 12:31:21 PM 1084 (0x043C)
pDriverInstaller->AutoInstallDrivers( pDriverCatalog, bBestMatch ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,286) OSDDriverClient 10/11/2012 12:31:21 PM 1084 (0x043C)
Failed to auto provision driver. Code 0x80004005 OSDDriverClient 10/11/2012 12:31:21 PM 1084 (0x043C)
ProcessAutoProvision( pDriverInstaller, bBestMatch ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,415) OSDDriverClient 10/11/2012 12:31:21 PM 1084 (0x043C)
Failed to auto provision drivers.  Code 0x80004005 OSDDriverClient 10/11/2012 12:31:21 PM 1084 (0x043C)

Below is the MP Driver log

CMPDBConnection::ExecuteSQL(): ICommandText::Execute() failed with 0x80040E14 MP_DriverManager 10/11/2012 11:12:59 AM 11228 (0x2BDC)
======================================= MP_DriverManager 10/11/2012 11:12:59 AM 11228 (0x2BDC)

MPDB ERROR - CONNECTION PARAMETERS
SQL Server Name     : sqlserver
SQL Database Name   : SMS
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 10/11/2012 11:12:59 AM 11228 (0x2BDC)
=======================================
MP_DriverManager 10/11/2012 11:12:59 AM 11228 (0x2BDC)
Failed to execute strored procedure: MP_MatchDrivers, hr=0x80040e14 MP_DriverManager 10/11/2012 11:12:59 AM 11228 (0x2BDC)
Failed to execute MatchDrivers task, hr=0x80040e14 MP_DriverManager 10/11/2012 11:12:59 AM 11228 (0x2BDC)

Anyone found a resolution for this ?Storage drivver is H710 mini and because of this error,storage driver is not getting installed, and hence OS installation is failing

No, I never got this solved. 

You had any workaround atleast?

yup...

(already posted)

Ohhh yes..i missed it..sorry...So  you created a different driver package for your dell servers ?if yes can you please tell me what version of drivers were using??I tried create a driver package but it didnt get apply :(

 At last Apply driver package worked :)

Earlier i was not having this option selected :)

Auto apply driver is still not working..

Here's some results from our testing...

We are having the issue when attempting to build a Lenovo D30.  We can build an S30 without issue.

So what's the difference?  Well, the D30 has 2 physical CPU's, which the S30 has a single CPU.  As a test, we pulled out the 2nd CPU (effectively turning the D30 into an S30), and now the build process works!!!

Our current memory configuration is a single 4GB DIMM in slot 1 for CPU1, and a single 4GB DIMM in slot 1 for CPU2.

Not quite the answer to the problem, but we may be on to something here.  Testing is ongoing...

Nick.

Had any luck solving this?

No success yet.

We shipped one of our D30's to our sister company to check whether the issue was specific to our environment, or specific to the model of machine.  They experienced the same issue.  And it's not just one specific machine as Auto Apply Drivers fails when we try it with a different D30.

Lenovo suggested that we contact Microsoft.  We haven't contacted Microsoft yet as I'm afraid they will just suggest that we contact Lenovo.

I just got SCCM 2012 installed in our lab.  Our next test will be to load only the drivers that are specific to the D30, and see what happens with  Auto Apply Drivers.  We may also do the same with our lab installation of SCCM 2007.

Nick.

• Edited by Nick P. - SCCM Guy Thursday, December 20, 2012 11:39 PM

No success yet.

We shipped one of our D30's to our sister company to check whether the issue was specific to our environment, or specific to the model of machine.  They experienced the same issue.  And it's not just one specific machine as Auto Apply Drivers fails when we try it with a different D30.

Lenovo suggested that we contact Microsoft.  We haven't contacted Microsoft yet as I'm afraid they will just suggest that we contact Lenovo.

I just got SCCM 2012 installed in our lab.  Our next test will be to load only the drivers that are specific to the D30, and see what happens with  Auto Apply Drivers.  We may also do the same with our lab installation of SCCM 2007.

Nick.

• Edited by Nick P. - SCCM Guy Thursday, December 20, 2012 11:39 PM

Test results from our lab...

SCCM 2012, SQL 2008 R2 SP2, MDT 2012, full set of drivers loaded (identical to our production SCCM 2007 environment).

The D30 built OK without error.

We have plans to install SCCM 2012 in the coming months, so I doubt we will be spending much more effort trying to debug the production environment issue.

Nick.

• Proposed as answer by Isaac GamboaMicrosoft employee Thursday, December 27, 2012 10:40 PM
• Unproposed as answer by Isaac GamboaMicrosoft employee Thursday, December 27, 2012 10:40 PM

Test results from our lab...

SCCM 2012, SQL 2008 R2 SP2, MDT 2012, full set of drivers loaded (identical to our production SCCM 2007 environment).

The D30 built OK without error.

We have plans to install SCCM 2012 in the coming months, so I doubt we will be spending much more effort trying to debug the production environment issue.

Nick.

• Proposed as answer by Isaac GamboaMicrosoft employee Thursday, December 27, 2012 10:40 PM
• Unproposed as answer by Isaac GamboaMicrosoft employee Thursday, December 27, 2012 10:40 PM

When you run the Auto Apply Drivers step, a hardware inventory file is generated. The file is then processed by the MatchDrviersSP stored procedure. In ConfigMgr 2007 the file size limit for the hardware inventory file is 100k. When this file is over 100k it is not able to be processed. The workaround is to use the Apply Driver Package step.

This is not a issue in 2012 because the file size limit has now been increased to 1MB.

Isaac G.

• Proposed as answer by Isaac GamboaMicrosoft employee Thursday, December 27, 2012 10:48 PM

When you run the Auto Apply Drivers step, a hardware inventory file is generated. The file is then processed by the MatchDrviersSP stored procedure. In ConfigMgr 2007 the file size limit for the hardware inventory file is 100k. When this file is over 100k it is not able to be processed. The workaround is to use the Apply Driver Package step.

This is not a issue in 2012 because the file size limit has now been increased to 1MB.

Isaac G.

• Proposed as answer by Isaac GamboaMicrosoft employee Thursday, December 27, 2012 10:48 PM

Thanks Isaac, it looks like that's the missing piece of the puzzle.

Nick.

• Edited by Nick P. - SCCM Guy Friday, December 28, 2012 5:15 AM

Thanks Isaac, it looks like that's the missing piece of the puzzle.

Nick.

• Edited by Nick P. - SCCM Guy Friday, December 28, 2012 5:15 AM

Thanks so much for answering this question.  I ran into it this week when building an HP Z840.  Hadn't used Apply Driver Packages since XP days!  Worked perfectly.  Looking forward to migrating to SCCM 2012 in a couple of months.

-Russell