Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • +4 person also asked this people also asked this
  • Locked Locked
  • Replies 53 replies
  • Answers 2 answers
  • Subscribers 29 subscribers
  • Views 6257774 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problems with Office 365 / Office 2016

DanielWells

We are now unable to install Office365 / Office 2016 using the Office Deployment Tool.  Because we have a bunch of new things from Sophos going on (new firewall, anti-virus int he cloud and the "ultimate" beta) we are struggling to find the source of the problem.

We do know there are issues with the firewall and the download of the software.

We also know that once we get around the download problem the installation is failing both inside and outside the firewall, indicating that  it might be an antivirus issue. 

The error I can find is "C2R client returned failing error code 17002".  Following through Microsoft's troubleshooting, the one thing I haven't done yet is disable anti-virus.

When deploying to enterprises (even small ones like mine) having to disable anti-virus on each one to deploy software is going to be a pain in the butt. ( I posted  something about not being able to disable tamper protection for "Spectrum" / "Sophos Ultimate").

Please include ways that administrators can distribute software without massive painful hurdles to cross.



This thread was automatically locked due to age.
Parents
  • 0

    FYI - we have Intercept on Windows 7, 8, 8.1, and 10 machines (builds 1511 and 1607). We noticed that fresh installs of Office 2013/2016 on all operating systems were always failing around 76% with error code 30175-13 or 30175-11, install error code was 17002.

    We turned off realtime scanning and all additional features and were able to install without any issues. Another note - this also causes the streamlined updates to corrupt, thus corrupting the installation, causing instability. When a repair is attempted on the installation, Office will uninstall and attempt to reinstall everything, but fails with one of two messages:

    • Access denied to installation source
    • Installation failed. Please restart your computer.

    No messages were displayed at the time when these were being blocked. No logs were present to show these applications being blocked either. It would be quite helpful if we had a more definitive logging or alerting solution that would tell us when this scenario happens. I'm not entirely mad that it blocked these updates, but I am mad that it didn't alert that something happened, or at least have a centralized log that captured that block. 

    We have created exceptions for the main Office installation directories so that updates can proceed as planned, seems to be doing splendidly so far.

Reply
  • 0

    FYI - we have Intercept on Windows 7, 8, 8.1, and 10 machines (builds 1511 and 1607). We noticed that fresh installs of Office 2013/2016 on all operating systems were always failing around 76% with error code 30175-13 or 30175-11, install error code was 17002.

    We turned off realtime scanning and all additional features and were able to install without any issues. Another note - this also causes the streamlined updates to corrupt, thus corrupting the installation, causing instability. When a repair is attempted on the installation, Office will uninstall and attempt to reinstall everything, but fails with one of two messages:

    • Access denied to installation source
    • Installation failed. Please restart your computer.

    No messages were displayed at the time when these were being blocked. No logs were present to show these applications being blocked either. It would be quite helpful if we had a more definitive logging or alerting solution that would tell us when this scenario happens. I'm not entirely mad that it blocked these updates, but I am mad that it didn't alert that something happened, or at least have a centralized log that captured that block. 

    We have created exceptions for the main Office installation directories so that updates can proceed as planned, seems to be doing splendidly so far.

Children
No Data
Unfiltered HTML
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?