Error At Winhttpsendrequest
Contents |
2012 R2 SP1Philipp Today i ran into a little problem in a customers SCCM environment. A colleague
Winhttpsendrequest Error 12029
wanted to reinstall his SCCM Agent because it was not winhttpsendrequest error 12007 behaving as it should and noticed that the client push, he initiated did not work… so
Ccmsetup Failed With Error Code 0x80072ee2
I had a look at the "CCMsetup.log". The log showed this INI Checking the URL 'http://XXX:80/CCM_Client/ccmsetup.cab' ccmsetup 29/05/2015 15:16:02 916 (0x0394) PROPFIND 'http://XXX:80/CCM_Client' ccmsetup 29/05/2015 failed to send http request. (error at winhttpsendrequest: 12029) 15:16:02 916 (0x0394) Failed to send HTTP request. (Error at WinHttpSendRequest: 12029) ccmsetup 29/05/2015 15:16:03 916 (0x0394) Failed to check url http://XXX:80/CCM_Client/ccmsetup.cab. Error 0x80072efd ccmsetup 29/05/2015 15:16:03 916 (0x0394) Accessing the URL 'http://XXX:80/CCM_Client/ccmsetup.cab' failed with 80072EFD ccmsetup 29/05/2015 15:16:03 916 (0x0394) Checking the URL 'http://XXX:80/CCM_Client/ccmsetup.cab' ccmsetup 29/05/2015 15:16:03 916 (0x0394) PROPFIND 'http://XXX:80/CCM_Client' failed to send http request. (error at winhttpsendrequest: 12007) ccmsetup 29/05/2015 15:16:03 916 (0x0394) Failed to correctly receive a WEBDAV HTTP request.. (StatusCode at WinHttpQueryHeaders: 405) ccmsetup 29/05/2015 15:16:03 916 (0x0394) Failed to check url http://XXX:80/CCM_Client/ccmsetup.cab. Error 0x80004005 ccmsetup 29/05/2015 15:16:03 916 (0x0394) Accessing the URL 'http://XXX:80/CCM_Client/ccmsetup.cab' failed with 80004005 ccmsetup 29/05/2015 15:16:03 916 (0x0394) Next retry in 10 minute(s)... ccmsetup 29/05/2015 15:16:03 916 (0x0394) Shutdown has been requested ccmsetup 29/05/2015 15:16:03 916 (0x0394) 123456789101112 Checking the URL 'http://XXX:80/CCM_Client/ccmsetup.cab' ccmsetup 29/05/2015 15:16:02 916 (0x0394)PROPFIND 'http://XXX:80/CCM_Client' ccmsetup 29/05/2015 15:16:02 916 (0x0394)Failed to send HTTP request. (Error at WinHttpSendRequest: 12029) ccmsetup 29/05/2015 15:16:03 916 (0x0394)Failed to check url http://XXX:80/CCM_Client/ccmsetup.cab. Error 0x80072efd ccmsetup 29/05/2015 15:16:03 916 (0x0394)Accessing the URL 'http://XXX:80/CCM_Client/ccmsetup.cab' failed with 80072EFD ccmsetup 29/05/2015 15:16:03 916 (0x0394)Checking the URL 'http://XXX:80/CCM_Client/ccmsetup.cab' ccmsetup 29/05/2015 15:16:03 916 (0x0394)PROPFIND 'http://XXX:80/CCM_Client' ccmsetup 29/05/2015 15:16:03 916 (0x0394)Failed to correctly receive a WEBDAV HTTP request.. (StatusCode at WinHttpQueryHeaders: 405) ccmsetup 29/05/2015 15:16:03 916 (0x0394)Failed to check url http://XXX:80/CCM_Client/ccmsetup.cab. Error 0x80004005 ccmsetup 29/05/2
the client computer and found this. Failed to send HTTP request. (Error at WinHttpSendRequest: 12002) ccmsetup 25/1/2011 4:29:59 PM 6600 (0x19C8)Can't connect to or retrieve file: http://
Getdplocations Failed With Error 0x80072ee2
ccmsetup 25/1/2011 4:29:59 PM 6600 (0x19C8)Next retry in 10 minute(s)… ccmsetup 25/1/2011 4:29:59 PM 6600 sending with winhttp failed; 80072ee2 (0x19C8) Though it is a pretty simple solution at the end but it may screw with some of us. The first thing
Getdplocations Failed With Error 0x80072efd
I did was find out why it could not retrieve the file. At the end it was the DNS record being the culprit this time. This caused the client computer not being able to resolve the http://freshblog.azurewebsites.net/2015/06/04/sccm-client-push-installation-fails-with-failed-to-check-url-error/ SCCM server correctly thus not being able to download the file. A simple task to update the A record on the DNS server to the correct IP address started resolving the SCCM server correctly and everything worked fine after that. Always always check that you MP is functioning too. Enjoy!!! Like this:Like Loading... This entry was posted on January 25, 2011 by weikingteh. It was filed under Uncategorized . → ← https://weikingteh.wordpress.com/2011/01/25/sccm-client-agent-push-failed/ 3 responses Yavuz Selim Atmaca Your advise really solved my problem. Thanks🙂 June 20, 2011 at 9:49 pm Reply Chris what changes are required to the DNS. March 17, 2012 at 2:28 pm Reply weikingteh You need to check that DNS is resolving the computer name to the correct IP address. Sometimes you may find duplicate or outdated A records (host records). Go to your DNS console and look for the particular computer name you're trying to push the SCCM agent to and make sure it is resolving to the correct IP address that it is having. Good luck. March 19, 2012 at 1:52 pm Reply Leave a Reply Cancel reply Enter your comment here... Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are commenting using your Twitter account. (LogOut/Change) You are commenting using your Facebook account. (LogOut/Change) You are commenting using your Google+ account. (LogOut/Change) Cancel Connecting to %s Notify me of new comments via email. Teh Wei King Recent Posts Setting Up An EMS Lab in ARM (Azure Resource Manager) Step-By-Step – Part7 Cannot Turn On Features in Configuration Manager CurrentBranch Automating Start/Stop Azure VMs (ResourceManager) Setting Up An EMS Lab in ARM (Azure
those computers couldn't resolve the SCCM server name. I've checked the DNS IP and it is configured correctly. For temporary solution, I included the SCCM server and IP http://scexblog.blogspot.com/2011/11/failed-to-send-http-request-error-at.html in to the host list located at C:\Windows\System32\drivers\etc\hosts. After that, the SCCM agents deployed smoothly without any issue. More troubleshooting will be done as the solution above is just temporary. Stay tuned!!! Posted http://blog.danovich.com.au/2010/07/09/sccm-clients-not-installing-in-native-mode/ by Hau at 2:52 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: ConfigMgr, Configuration Manager, SCCM 1 comment: AnonymousJanuary 26, 2012 at 9:32 PMSir: After beating my head against a wall error at for days, I tried this, and it worked! Have you followed up on your research? I think it may have something to do with a BITS problem. Please let me know what you found: bdbuchanan@gmail.comReplyDeleteAdd commentLoad more... Newer Post Older Post Home Subscribe to: Post Comments (Atom) Total Pageviews About Me Hau Hau is a technical consultant at Infront Consulting Group. He is also an Microsoft error at winhttpsendrequest MVP for Enterprise Client Management. His main focus is around Configuration Manager, SCCM, EMS and Microsoft Intune. View my complete profile Labels 1511 Active Directory Announcement App-V 5.0 Applocker APPV BitLocker Client Push ConfigMgr Configuration Manager Custom Reports Deploy Expert Distribution Point Endpoint Protection GPO Hyper-V IIS IPv6 MAM Managed Apps Management Point MBAM MDM MDT MDT 2012 Med-V 2.0 MEDV Microsoft Intune Office 365 OOB OSD Out Of Band Powershell Reporting Right Click Tools SCCM SCCM 1511 SCCM 1602 SCCM 2012 SCCM 2012 R2 SCCM 2012 SP1 SCCM CB SCCM Current Branch SCEP Schema Extension SCUP Sequencing Recipe SQL Symantec System Center 2012 R2 UNIX Linux USMT Virtual PC 2007 VPro WDS Windows 10 10586 Upgrade Windows 7 Windows 8.1 Windows Intune Windows Server 2003 Windows Server 2008 Windows Server 2012 Windows Server 2012 R2 Windows Virtual PC Windows XP Mode WMI Query WSUS Popular Posts (30 days) Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error Failed to Run Task Sequence; Error 0x80004005 While Retrieving Policy SCCM 2012 R2: VPN Profiles Step-by-step Guide Could not connect to the RootDSE container in Active Directory. HRESULT=0x8007052E WSUS Post-deployment Configuration Failed Co
noticed that none of my clients have the SCCM agent installed after a few days. The log contained at c:windowsccmsetupccmsetup.log on the client showed that the installation was failing and the error messages included: WINHTTP_CALLBACK_STATUS_FLAG_CERT_CN_INVALID is set Failed to send HTTP request. (Error at WinHttpSendRequest: 12175) This indicates that the computer name that the client is using to contact the management point doesn't match the FQDN in the Web Server certificate Subject, which is installed on the server and configured in IIS. The solution was to request (from the enterprise certificate authority) and assign a new certificate in IIS. Using IIS 7.5, open the IIS manager console, click on the server name, double-click Server Certificates and then Create Domain Certificate. Fill in the details and select your enterprise EA server. It is important here to use the FQDN of the server in the Common Name section. Once complete, head to the Default Web Site, edit Bindings and click on edit for https, then select your newly issued certificate. You don't need to restart IIS. Initiate a new client install - it should be successful this time. ---------------------------------------------------------------------------- I use a maximum of one Google Ad per post to help offset some of my blog hosting costs. ---------------------------------------------------------------------------- Tags: ccmsetup.log, Certificates, client push, Error at WinHttpSendRequest: 12175, SCCM, sccm client failed, sccm native mode, WINHTTP_CALLBACK_STATUS_FLAG_CERT_CN_INVALID Posted July 9, 2010 by danovich in category Certificates, SMS / SCCM Post navigation App-V sequenced applications not keeping settings / preferences New Microsoft TS certifications Leave a Reply Cancel reply Home About Consulting Contact RSS Feed Recent Posts CISSP exam passed Microsoft MCSE Private Cloud recertification - exam 70-981 Upgrade from Windows 8.1 Enterprise to Windows 10 Professional Azure Multi-Factor Authentication Server as a RADIUS server Windows 10 peer-to-peer (P2P) patching System Center Endpoint Protection