Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, December 3, 2014 1:03 AM
hello i have a problem deploying a OS( win 7 sp1 ), always error Download() failed. 80072efe. SendWinHttpRequest failed. 80072efe. my SCCM ( 2012 r2 cu2 ) is in miami and the clients/pc are in the El salvador. i have two local DP and the same problem with both, the OS image are replicated sucessfully and i have the network access account, i can ping the MP, DP, SCCM from machine , i have added the two variables :SMSTS Download RetryCount and SMSTS DownloadRetryDelay and the same problem . i have tested with a phisical machine and a virtual machine ( workstation ) and both failed, the sccm is a virtual machine running in a hyper-v server, i created a vm in the same hyper-v in miami and finished sucessfully , i checked the firewall , antivirus they are disabled . the DP has allow clients to connect anonymously checked . please help me.
Erickson Martinez
All replies (4)
Wednesday, December 3, 2014 2:04 AM âś…Answered
80072efe = "The connection with the server was terminated abnormally"
This is a winhttp error meaning it was issued by the client because of a failure to communicate with IIS. Ultimately, this means that "something" interrupted the session. What that "something" is is outside the control or visibility of ConfigMgr and is most likely network related.
Setting the two task sequence variables is a possible solution (of course make sure you are using SMSTSDownloadRetryCount and SMSTSDownloadRetryDelay with no spaces) for a known timing issue in the task sequence engine.
FInally, allowing anonymous client connections is not recommended and is not needed.
Jason | http://blog.configmgrftw.com | @jasonsandys
Wednesday, December 3, 2014 2:21 PM
80072efe = "The connection with the server was terminated abnormally"
This is a winhttp error meaning it was issued by the client because of a failure to communicate with IIS. Ultimately, this means that "something" interrupted the session. What that "something" is is outside the control or visibility of ConfigMgr and is most likely network related.
Setting the two task sequence variables is a possible solution (of course make sure you are using SMSTSDownloadRetryCount and SMSTSDownloadRetryDelay with no spaces) for a known timing issue in the task sequence engine.
FInally, allowing anonymous client connections is not recommended and is not needed.
Jason | http://blog.configmgrftw.com | @jasonsandys
thanks for reply yes the variables that i am using are with no space, when you state a "failure to communicate with the IIS " you are talking about the IIS of the local DP or the SCCM ? also i going to double check the network .
Erickson Martinez
Wednesday, December 3, 2014 3:20 PM
It's most likely the DP, but the log does tell you where it's trying to connect to.
Torsten Meringer | http://www.mssccmfaq.de
Wednesday, December 3, 2014 7:46 PM
After troubleshooting was a network problem, we tested with local DP in same subnet/lan and work fine, so we are going to check the network /firewall issues.
thanks for your help .
Erickson Martinez