Hi

We have some issues trying to use the Auto Apply Drivers step. We have 1 CAS and 3 primaries. This situation only happen on one primary

smsts.log :

MP_DriverManger.log on verbose mode:

I notify that the client fail before the process on the server complete.

All the process on the task sequence work fine except Auto Apply Driver steps.

Using Driver Package work fine but we are interested to use Auto Apply Driver that work fine on other sites.

Any clue about this?

Are your driver packages available on a DP at that primary site?

Jeff

Yes, like mentionned above if I use driver packages work fine,  they are available on DPs

This may or may not relate: https://social.technet.microsoft.com/Forums/en-US/0bb0b14f-7e9b-48ce-b945-b37bfdbf7911/0x80072ee2-at-contacting-server-for-device-drivers?forum=configmanagerosd

The "failed to send request" is suspicious. . .verify network connectivity to DPs and MP

Jeff

The network between MP and DP work fine not packet lost.

The error code 0x80072EE2 is "The operation timed out"  So, you still have a network issue or the client is not able to find the driver packages on the DP.  Have you validated boundaries and that the content for driver packages is truly on a local DP?

Jeff

If I use the drivers package work fine so the package is ready on DP but when I use Auto Apply Drivers limited to the category that I set to my drivers in the packages not work.

When I reproduce the problem the client closes the connection 8 minutes after it contacted the server the first time. But on the server side it's still working on it and response 21 minutes later to the client but the connection is closed.  There is something that is blocking because the others primaries share the same drivers and drivers packages and work fine and they answer on time. There is other places or logs involve on this to have more information about this process.

smsts.log:

---------------------------------------------------------------------------------

CLibSMSMessageWinHttpTransport::Send: URL: SERVER.DOMAIN:443  CCM_POST /ccm_system_AltAuth/request    OSDDriverClient    4/24/2015 10:08:08 PM    3052 (0x0BEC)
In SSL, but with no client cert    OSDDriverClient    4/24/2015 10:08:08 PM    3052 (0x0BEC)
In SSL, but with no media cert    OSDDriverClient    4/24/2015 10:08:08 PM    3052 (0x0BEC)
WinHttpReceiveResponse (hRequest, NULL), HRESULT=80072ee2 (e:\qfe\nts\sms\framework\osdmessaging\libsmsmessaging.cpp,8927)    OSDDriverClient    4/24/2015 10:16:08 PM    3052 (0x0BEC)
failed to receive response with winhttp; 80072ee2    OSDDriverClient    4/24/2015 10:16:08 PM    3052 (0x0BEC)
End of retries    OSDDriverClient    4/24/2015 10:16:08 PM    3052 (0x0BEC)

---------------------------------------------------------------------------------


MP_DriverMgr.log:

---------------------------------------------------------------------------------

Parsing request.    MP_DriverManager    4/24/2015 10:08:08 PM    11160 (0x2B98)
Verifying client's trust level.    MP_DriverManager    4/24/2015 10:08:08 PM    11160 (0x2B98)
Executing Driver Request - Match    MP_DriverManager    4/24/2015 10:08:08 PM    11160 (0x2B98)
XML Schema support is not installed, XML validation will be skipped.    MP_DriverManager    4/24/2015 10:08:08 PM    11160 (0x2B98)
Response message sent to the client    MP_DriverManager    4/24/2015 10:21:28 PM    11160 (0x2B98)
---------------------------------------------------------------------------------

• Edited by robeglez 11 hours 14 minutes ago More visibility

If I use the drivers package work fine so the package is ready on DP but when I use Auto Apply Drivers limited to the category that I set to my drivers in the packages not work.

When I reproduce the problem the client closes the connection 8 minutes after it contacted the server the first time. But on the server side it's still working on it and response 21 minutes later to the client but the connection is closed.  There is something that is blocking because the others primaries share the same drivers and drivers packages and work fine and they answer on time. There is other places or logs involve on this to have more information about this process.

smsts.log:

---------------------------------------------------------------------------------

CLibSMSMessageWinHttpTransport::Send: URL: SERVER.DOMAIN:443  CCM_POST /ccm_system_AltAuth/request    OSDDriverClient    4/24/2015 10:08:08 PM    3052 (0x0BEC)
In SSL, but with no client cert    OSDDriverClient    4/24/2015 10:08:08 PM    3052 (0x0BEC)
In SSL, but with no media cert    OSDDriverClient    4/24/2015 10:08:08 PM    3052 (0x0BEC)
WinHttpReceiveResponse (hRequest, NULL), HRESULT=80072ee2 (e:\qfe\nts\sms\framework\osdmessaging\libsmsmessaging.cpp,8927)    OSDDriverClient    4/24/2015 10:16:08 PM    3052 (0x0BEC)
failed to receive response with winhttp; 80072ee2    OSDDriverClient    4/24/2015 10:16:08 PM    3052 (0x0BEC)
End of retries    OSDDriverClient    4/24/2015 10:16:08 PM    3052 (0x0BEC)

---------------------------------------------------------------------------------


MP_DriverMgr.log:

---------------------------------------------------------------------------------

Parsing request.    MP_DriverManager    4/24/2015 10:08:08 PM    11160 (0x2B98)
Verifying client's trust level.    MP_DriverManager    4/24/2015 10:08:08 PM    11160 (0x2B98)
Executing Driver Request - Match    MP_DriverManager    4/24/2015 10:08:08 PM    11160 (0x2B98)
XML Schema support is not installed, XML validation will be skipped.    MP_DriverManager    4/24/2015 10:08:08 PM    11160 (0x2B98)
Response message sent to the client    MP_DriverManager    4/24/2015 10:21:28 PM    11160 (0x2B98)
---------------------------------------------------------------------------------

• Edited by robeglez Friday, April 24, 2015 8:30 PM More visibility

If I use the drivers package work fine so the package is ready on DP but when I use Auto Apply Drivers limited to the category that I set to my drivers in the packages not work.

When I reproduce the problem the client closes the connection 8 minutes after it contacted the server the first time. But on the server side it's still working on it and response 21 minutes later to the client but the connection is closed.  There is something that is blocking because the others primaries share the same drivers and drivers packages and work fine and they answer on time. There is other places or logs involve on this to have more information about this process.

smsts.log:

---------------------------------------------------------------------------------

CLibSMSMessageWinHttpTransport::Send: URL: SERVER.DOMAIN:443  CCM_POST /ccm_system_AltAuth/request    OSDDriverClient    4/24/2015 10:08:08 PM    3052 (0x0BEC)
In SSL, but with no client cert    OSDDriverClient    4/24/2015 10:08:08 PM    3052 (0x0BEC)
In SSL, but with no media cert    OSDDriverClient    4/24/2015 10:08:08 PM    3052 (0x0BEC)
WinHttpReceiveResponse (hRequest, NULL), HRESULT=80072ee2 (e:\qfe\nts\sms\framework\osdmessaging\libsmsmessaging.cpp,8927)    OSDDriverClient    4/24/2015 10:16:08 PM    3052 (0x0BEC)
failed to receive response with winhttp; 80072ee2    OSDDriverClient    4/24/2015 10:16:08 PM    3052 (0x0BEC)
End of retries    OSDDriverClient    4/24/2015 10:16:08 PM    3052 (0x0BEC)

---------------------------------------------------------------------------------


MP_DriverMgr.log:

---------------------------------------------------------------------------------

Parsing request.    MP_DriverManager    4/24/2015 10:08:08 PM    11160 (0x2B98)
Verifying client's trust level.    MP_DriverManager    4/24/2015 10:08:08 PM    11160 (0x2B98)
Executing Driver Request - Match    MP_DriverManager    4/24/2015 10:08:08 PM    11160 (0x2B98)
XML Schema support is not installed, XML validation will be skipped.    MP_DriverManager    4/24/2015 10:08:08 PM    11160 (0x2B98)
Response message sent to the client    MP_DriverManager    4/24/2015 10:21:28 PM    11160 (0x2B98)
---------------------------------------------------------------------------------

• Edited by robeglez Friday, April 24, 2015 8:30 PM More visibility

Robeglez,

Did you ever figure this out? We just started experiencing the same thing in our environment (2012 R2, 1 CAS, 3 Pri). If I use the driver packages then everything works but when I use the Auto Apply Drivers step it times out with the same error. I have starting using variables to extend the retry counts but this is just a work around. I'd like to know what is causing the issue.