Error 30174-4

To all who have struggled with this issue....

I too have ran into the SonicWall / 30174-4 Office365 Install error.  I have not found a fix, nor will I stop looking (cause this is driving me crazy).  Let me share with you what I have found thus far....

I have a pair of NSA 3500's, configured for high availability (Fail Over).  I have found when the click-to-run installer is used behind this firewall, in any zone, the install will fail anywhere between 25-75%, with the error 30174-4.  Microsoft, thank you at least bringing back error codes (previous failures just echoed:  "Something Went Wrong", no error codes).  To reset the installation (prep to try again), I am using the click-to-run uninstall cab found here:  http://support.microsoft.com/kb/2739501/en-us  This clears all settings and services as well has allows for the install to run again.

If the 3500 is bypassed (usable IP in WAN Zone/Network), the installation works fine, ruling out AV software issues, etc.  I have ran the click-to-run behind a TZ210 (fairly basic config), with the same AV software, Install works just fine.  I have also traveled to a colleagues network (University of Utah Network), which is a heavily filtered network.  He too has in inbound Sonicwall 3500 protecting a segment of his network, from which I ran the click-to-run, and the installation worked just fine (working through campus filtering, transparent firewalls and who knows what else).

I compared notes on basic and advanced setups, we have very similar configurations, the differences being in networks and firewall rule sets.  I was unable to find a difference that explains this behavor.  I have continued to run the install and track back through logs expecting to see notification of "blocked" traffic for some rule set.  To date I have not seen any such log entry.  I have tried turning off IDS, IPS, and content filtering, yielding the same results (failed install, no log entries).  I am currently working under the impression there is a lower level setting (such as adherence to RFC rules, stealth mode settings or IGMP settings) that is causing the problem and as such is not being reported in the log files.  I believe Microsoft is using some sort of multicasting protocol to deliver the click-to-run package and this is being filtered or broken by the firewall.

I hope this info helps someone.  I have being fighting this issue for close to six months.  Due to the work around of installing off network or bypassing the primary firewall, this has fallen off my priority list.  As soon as I have more time, I will be opening up a support case with SonicWall, in hopes of finding someone smarter or with more experience than me.

If I ever do find the answer, I will be sure to post it.  Good Luck to all and please post your findings as this information may help others to find the answer (or me!).

I was having the same error tonight, and went a bit scorched earth on it but was able to get this working again.

Since I could not repair, repair online, or uninstall due to this error, I deleted everything in C:\Program Files\Microsoft Office, as well as C:\Program Files (x86)\Microsoft Office, C:\Program Files\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform, C:\ProgramData\Microsoft\ClickToRun, and also C:\ProgramData\regid.1991-06.com.microsoft\

Then also deleted registry keys for HKCU\Software\Microsoft\Office and HKLM\Software\Microsoft\Office and HKLM\Software\Microsoft\OfficeSoftwareProtectionPlatform

With all of that gone, it let me remove the control panel \ Programs entry with an uninstall (nothing really uninstalled, just said could not find and then removed).

I was then able to download and run a fresh Click-To-Run installer, and it installed fine but didn't ask me for a license key and also did not activate. Had to call microsoft but worked with the automated system and activated with a verification code.

All set. I'm sure less could be done, but this process has fixed up every dumb Click-To-Run error I've encountered by completely removing click to run from the computer.

Also, the site in question happened to use a Sonicwall TZ 210. This doesn't necessarilly have anything to do with Sonicwalls, but could have something to do with a Proxy Server if someone was doing web based content filtering on a Sonicwall (or any firewall for that matter). Worth investigating as BGGF mentioned above, but not an end-all-be-all.

A big "thank you" to everyone on this thread.

Had the same issue as everyone else and after trying multiple remedies, I determined that it is indeed a network issue.

Long story short, I had to take my work laptop home with me and install Office 365 on my home network.

For what it is worth, just like the previous user mentioned, we also have a Sonicwall firewall in place at our office.

I've brought my laptop back to the office and so far Office 365 has been running well.

(I suspect if I try installing any additional Microsoft software, the same issue will repeat itself.)

Without the users on this thread I would have thrown my laptop out a window. 

Microsoft, you need to figure out a proper solution. In the meantime you owe the folks on this thread a "Thanks" as well.

I just discovered that this does not seem to be compatible with Sonicwall firewalls.  I have had several customers that could not get this to work and had to go to great lengths before it did.

I tried bypassing the Sonicwall firewall at this last customer and it worked perfectly with no issues.

I makes me wonder if other firewall devices are causing the same issue.

Out of my experience I can confirm that a "hidden proxy" (whatever that is, a proxy is supposed to be transparent, isn't it) can cause problems for these services:

• OneDrive
• Microsoft Store
• Windows Updates
• Installing and activating Office365
• Windows 8.1 to deduce Internet connectivity in general (it claims to have reduced or no access to the Internet)

and probably a number of other things.

It would be so nice of Microsoft to confirm this in a technical brief on TechNet or here. But in general it is causing quite a number of question on this site as well.

So Microsoft, either

1. Document it! There are circumstances that the above mentioned service are not available when behind a proxy server
2. Update your software. This has been going on since the start of 8.0 and really should be addressed (oh, and take a way the Start button while you are at it)

(I presume that Microsoft somehow links the services to a media access control address and in this way can make sure a legit user is accessing the above mentioned services. It breaks functionality of the product, though.)