cannot install the Sophos Antivirus home edition in Mac Pro 2008

Hi,

I've got the same situation even after checking Time and Proxy settings.

In my case, I've had several network settings, and it seemed to be the reason

my installation failed. Here's what I did;

From the Apple menu, select System Preferences... .

In System Preferences, from the View menu, select Network.
If you have several settings and your 'Location' set to 'Auto', Sophos AntiVirus

doesn't seem to allow installation (fail to connect to the Sophos server).

So, choose one of them except for 'Auto', then click 'Apply'.
And try the installation again. I hope it will work.

Cheers.

I have been having the same problem for the past three hours and have now given up.

I tried all the bizzare tactics involving the clock (which was always right from the outset) and the strange changing of locations for the network.

None of them have worked.

If any representative from Sophos would like to assist, then I'll try again.

Untill then i recommend anyone who has this problem to get another free anti virus package from the app store as they are perfectly adequate.

Internet settings are fine, time/clock/year are fine. Still cannot install. This is clearly a  Sophos issue that needs to be addressed. Seems I'll have to use avast! free for Mac until Sophos addresses this issue.

Sad....

Hi All!

I was facing the same problem on a brand new MacBook Air - Sophos Installer couldn't connect. 

Well - HERE'S THE SOLUTION !!! (partly - works only if you already have Sophos installed on another Mac...  I'll explain)

The problem is that the installer cannot connect to the registration server, so no account can be created to identify your installation of SophosAV.

To get around this problem you'll need to take the following steps (bit *fumbly*, but works):

1. This is important!

     Get your hands on your other Mac and copy the following file to a thumbdrive:

    (on the root of your MacintoshHD):    /Library/Sophos Anti-Virus/com.sophos.sau.plist

     This file contains the login-data to connect to your existant autogenerated Sophos account.

     If you don't habe this file - STOP HERE! It won't work... 

2. Back to the other Mac...  Open the Installer .dmg file

3. locate Sophos Anti-Virus Home Edition.mpkg - ctrl-click on that file and choose "show package contents"

4. copy the folder "contents" to your desktop (or download folder or whatever you prefer)

5. open "contents" , you'll see a folder named "Packages" in there - open it.

6. in "Packages" you'll find 5 .(m)pkg files, doubleclick and install them one after another.

7. Now the tricky bit... Open the activity window from Spotlight (click on the loupe symbol in the right upper corner of your desktop and type "activity", click on the activty app)

8. kill all Sophos services (you can sort all running processes alphabetically)

9. copy the file "com.sophos.sau.plist" from your thumbdrive to /Library/Sophos Anti-Virus/ on your MacintoshHD

10. Now open up a Terminal window and type the following (without the quotes):

11. "cd /Library/Soph" (hit TAB to autocomplete the line)

12.  "sudo chown root:admin com.sophos.sau.plist"

13. you'll be asked to type in your login password - do so!

14. close the Terminal window

15. Use Finder to go to /Library/Sophos Anti-Virus/ on your Macintish HD

16. doubleclick on SophosUIServer.app

17. the Sophos shield icon should now be visible somewhere in the status bar - click on that and choose "Show Preferences"

18. In the preferences window go to "AutoUpdate" and click on the lock icon - type in your login password.

19. click on "recover presets" (maybe called differently, I've got the german version here...)

20. you should now see some login data in the fields underneath "Update from primary server".

21. If so - reboot!  After the reboot you should be able to update Sophos Pattern as expected.

I hope this is not too complicated - I tried my best to explain as easy as possible...

Cheers!

So, anyone from Sophos have any news on this error?

Hi rlaussat,

Just wanted to say a HUGE thank you for post...it worked like a charm. I followed the instructions to the letter (they were really clear and concise) and I now have Sophos AV Home for Mac 7.3 installed, running and updated.

Sophos take note...so much for tech support. 6 months and nothing, yet a customer fixed the problem for you!

Thanks again and best wishes rlaussat

Tried all recommendations except the one requiring a Mac with Sophos already installed.  Couldn't install Sophos and gave up.  I'll find another Antivirus tool. :smileysad:

Had the same message. Shut downn SugarSync, which was running in the background, and the problem went away. SugarSync is like Dropbox, it runs in the background to sync data over the internet. I imagine other such programs could cause the same problem, so shut them down and try installing again.

@ olliedee

No such luck. iCloud sync hasn't been activated. I have no need for any sync apps, so none are installed or in use. Though thanks for the tip. Hope others are helped by that.

Now, if Sophos would only fix this issue instad of so many of us  searching for workarounds and hacks.

At the risk of being flamed for cross-posting:

Apologies for not responding to the community sooner on this issue. It's clearly a frustrating experience and not one that I am happy with.

We believe this problem happens when the installer fails to complete an HTTPS connection to the Sophos registration server. One of the causes seems to be conflicts between the Sophos Installer and other applications that hold open SSL connections, which we think explains why poking applications in the menu bar, or changing network locations can sometimes release the conflict and solve the problem. It can also be caused by failure to validate the registration server's certificate, which could be related to time/date issues.

Our engineering team is currently investigating this specific issue along with some other install problems that have been reported via the FreeTalk forum. Assuming we can track down the root causes of these issues and determine a way to resolve them, we would like to include these fixes in a release in February 2012.

In the meantime, I will update the forum with any information we learn that would help work around the problem.

Regards

Richard Baldry

Product Manager