Home

Office 365 local share download keeps failing with proxy errors

%3CLINGO-SUB%20id%3D%22lingo-sub-889147%22%20slang%3D%22en-US%22%3EOffice%20365%20local%20share%20download%20keeps%20failing%20with%20proxy%20errors%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-889147%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EOne%20of%20our%20customer%20sites%20isn't%20working.%20We%20are%20setting%20up%20Office%20365%20proplus%20to%20have%20the%20setup%20files%20downloaded%20to%20a%20share%20on%20the%20server%20from%20which%20the%20clients%20will%20then%20install%20from.%20This%20works%20fine%20on%20other%20customer%20sites%20but%20on%20this%20one%20the%20office%20setup%20logs%20are%20showing%20proxy%20errors%20and%20the%20cab%20files%20etc%20are%20not%20being%20downloaded.%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20proxy%20is%20set%20to%20bypass%20these%20addresses%3A%26nbsp%3Bofficecdn.microsoft.com%3Bofficecdn.microsoft.com.edgekey.net%3Bofficecdn.microsoft.com.edgesuite.net%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20main%20issue%20in%20the%20logs%20is%3A%3C%2FP%3E%3CP%3E10%2F02%2F2019%2015%3A52%3A37.356%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BSETUP%20(0x12b0)%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B0x2808%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BIdentity%20Http%20Client%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3Bbbvo3%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BMonitorable%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%5BHttpWin%5D%20sendInternal%20%7B%22Message%22%3A%20%22WinHttpSendRequest%20failed%22%2C%20%22Url%22%3A%20%22%3CA%20href%3D%22http%3A%2F%2Fofficecdn.microsoft.com%2Fpr%2F7ffbc6bf-bc32-4f92-8982-f9dd17fd3114%2FOffice%2FData%2Fv64_16.0.11328.20420.cab%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fofficecdn.microsoft.com%2Fpr%2F7ffbc6bf-bc32-4f92-8982-f9dd17fd3114%2FOffice%2FData%2Fv64_16.0.11328.20420.cab%3C%2FA%3E%22%2C%20%22SH_ErrorCode%22%3A%2012002%7D%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E10%2F02%2F2019%2015%3A52%3A37.356%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BSETUP%20(0x12b0)%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B0x2808%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BIdentity%20Http%20Client%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3Ba9ido%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BMedium%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%5BHttpUtil%5D%20IsKnownProxyError%20%7B%22SH_ErrorCode%22%3A%2012002%2C%20%22Message%22%3A%20%22Detected%20a%20proxy%20failure%22%7D%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20then%20finally%20fails%20with%20error%26nbsp%3BAdminBootstrapper%3A%3AMain%3A%20Installation%20came%20back%20with%20-2147418113%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnything%20obvious%20people%20can%20advise%20about%20the%20proxy%20bypass%20list%20or%20similar%20before%20we%20have%20to%20start%20looking%20at%20the%20traffic.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3ENigel%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-889147%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1021042%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20local%20share%20download%20keeps%20failing%20with%20proxy%20errors%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1021042%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20ran%20into%20this%20in%20my%20tests.%20If%20you're%20behind%20a%20proxy%20server%2C%20you%20have%20to%20hard%20code%20the%20path%20of%20your%20proxy.%3C%2FP%3E%3CP%3EElevated%20Command%20Prompt%3A%3C%2FP%3E%3CP%3E%22netsh%20winhttp%20set-proxy%20proxy-server%3D%3CEM%3Eipaddress%3Aport%20%22%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3EWhen%20finished%20downloading%2C%20be%20sure%20to%20reset%20it%20back.%20%22netsh%20winhttp%20reset%20proxy%22%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20haven't%20had%20an%20opportunity%20to%20test%20the%20latest%20ODT%20tool%20released%20on%2010%2F31%2C%20but%20release%20notes%20show%20it%20may%20allow%20for%20downloads%20on%20other%20ports%20without%20having%20to%20set%20the%20winhttp%20proxy.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1023567%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20local%20share%20download%20keeps%20failing%20with%20proxy%20errors%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1023567%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20John%20for%20the%20info.%20It%20turned%20out%20to%20be%20a%20firewall%20%2F%20port%20issue%20in%20the%20Smoothwall%20config%20and%20not%20the%20proxy.%20I%20thought%20this%20would%20only%20need%20port%20443%20for%20SSL%20but%20the%20customer%20ended%20up%20opening%20all%20ports%20to%20get%20it%20to%20download.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENigel%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1048101%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20local%20share%20download%20keeps%20failing%20with%20proxy%20errors%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1048101%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F210134%22%20target%3D%22_blank%22%3E%40Nigel%20Archer%3C%2FA%3EI%20also%20noticed%20that%20the%20Office%20Deployment%20Tool%20had%20an%20updated%20version%20that%20allows%20for%20downloads%20on%20other%20ports%2C%20other%20than%20Port%2080.%26nbsp%3B%20Might%20want%20to%20make%20sure%20they're%20using%20the%20latest%20version%20of%20the%20ODT.%20%26nbsp%3B%20There's%20also%20a%20couple%20powershell%20scripts%20in%20the%20TechNet%20Gallery%20for%20downloading%20the%20Office%20365%20C2R%20Bits%20without%20ODT.%20I%20found%20the%20below%20quite%20useful%20since%20I%20have%20to%20download%20the%20bits%20for%20each%20Update%20Channel%20every%20month%20to%20keep%20our%20install%20packages%20up%20to%20date.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FOfficeDev%2FOffice-IT-Pro-Deployment-Scripts%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2FOfficeDev%2FOffice-IT-Pro-Deployment-Scripts%3C%2FA%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%3E%22Download-OfficeProPlusChannels.ps1%22%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Nigel Archer
Occasional Contributor

Hi,

One of our customer sites isn't working. We are setting up Office 365 proplus to have the setup files downloaded to a share on the server from which the clients will then install from. This works fine on other customer sites but on this one the office setup logs are showing proxy errors and the cab files etc are not being downloaded. 

The proxy is set to bypass these addresses: officecdn.microsoft.com;officecdn.microsoft.com.edgekey.net;officecdn.microsoft.com.edgesuite.net

 

The main issue in the logs is:

10/02/2019 15:52:37.356        SETUP (0x12b0)        0x2808                Identity Http Client        bbvo3        Monitorable        [HttpWin] sendInternal {"Message": "WinHttpSendRequest failed", "Url": "http://officecdn.microsoft.com/pr/7ffbc6bf-bc32-4f92-8982-f9dd17fd3114/Office/Data/v64_16.0.11328.20...", "SH_ErrorCode": 12002}        

10/02/2019 15:52:37.356        SETUP (0x12b0)        0x2808                Identity Http Client        a9ido        Medium        [HttpUtil] IsKnownProxyError {"SH_ErrorCode": 12002, "Message": "Detected a proxy failure"}       

 

This then finally fails with error AdminBootstrapper::Main: Installation came back with -2147418113

 

Anything obvious people can advise about the proxy bypass list or similar before we have to start looking at the traffic. 

 

Thanks,

Nigel

3 Replies

I've ran into this in my tests. If you're behind a proxy server, you have to hard code the path of your proxy.

Elevated Command Prompt:

"netsh winhttp set-proxy proxy-server=ipaddress:port "

 

When finished downloading, be sure to reset it back. "netsh winhttp reset proxy"

 

I haven't had an opportunity to test the latest ODT tool released on 10/31, but release notes show it may allow for downloads on other ports without having to set the winhttp proxy. 

Thanks John for the info. It turned out to be a firewall / port issue in the Smoothwall config and not the proxy. I thought this would only need port 443 for SSL but the customer ended up opening all ports to get it to download.

 

Nigel

@Nigel ArcherI also noticed that the Office Deployment Tool had an updated version that allows for downloads on other ports, other than Port 80.  Might want to make sure they're using the latest version of the ODT.   There's also a couple powershell scripts in the TechNet Gallery for downloading the Office 365 C2R Bits without ODT. I found the below quite useful since I have to download the bits for each Update Channel every month to keep our install packages up to date. 

 

https://github.com/OfficeDev/Office-IT-Pro-Deployment-Scripts

"Download-OfficeProPlusChannels.ps1"

Related Conversations