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!).