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

4.7 console install

Ok so I seem to be having a bunch of troubles installing the new 4.7 console.  I was upgrading from the 4.5 version and somehow its all jacked up now.  When I go to install it gets to the screen where it asks for the custom or complete install, when I click on the complete install and next it starts for a second and then comes up with a error.  "The installation procedure cannot continue as user account SophosUpdateMgr already exists.  Please see KBA 61397 for more information."  So after looking 61397 over I deleted the SophosUpdateMgr account out of AD and tried the install again to come back to the same message.  Any ideas?  This is the first time I have done a Sophos install and I'm already not liking it....

:13383


This thread was automatically locked due to age.
  • SUM encounters a checksum error for the mentioned file and therefore aborts all other actions. In "my" Warehouse the file (0fc01608b56f932491b5e2e37ce64112x000 .dat) has a size of 2,611,804 bytes - is this what you see?

    First of all, please check the subscription if it looks correct or has any weird content (like here). If it does look ok stop the management service, empty the Warehouse and also delete SUM_status.xml and specialactions.xml . Start the service and instruct SUM to update. You already know how and where to look and what to post (the LogViewer screenshot is no longer needed) if there's again an error .

    Christian 

    :13471
  • I was unable to find that file in my warehouse at all, so I emptied it out again.  The subscription looks to be normal, I emailed a tech yesterday and they said to "rebuild my subscription", so I created a new one and set the update manager to that one.  I deleted the 2 files you listed and started it back up and its working on refilling the warehouse again.  Thank you for your expertise and help.  I will repost after warehouse fills and if errors arrise.

    :13473
  • 2011-05-27 09:03:52 : Package synchronisation started.
    2011-05-27 09:03:52 : Cmd-ALL << [I1012][0fc01608b56f932491b5e2e37ce64112x000.dat] Starting to synchronise file '0fc01608b56f932491b5e2e37ce64112x000.dat'...
    2011-05-27 09:03:52 : Error during package synchronisation: Checksum error: 0fc01608b56f932491b5e2e37ce64112
    2011-05-27 09:03:52 : Package synchronisation started.
    2011-05-27 09:03:52 : Finished package synchronisation.
    2011-05-27 09:03:52 : Package synchronisation started.
    2011-05-27 09:03:52 : Cmd-ALL << [I1012][0fc01608b56f932491b5e2e37ce64112x000.dat] Starting to synchronise file '0fc01608b56f932491b5e2e37ce64112x000.dat'...
    2011-05-27 09:03:52 : Error during package synchronisation: Checksum error: 0fc01608b56f932491b5e2e37ce64112
    2011-05-27 09:03:53 : Package synchronisation started.
    2011-05-27 09:03:53 : Finished package synchronisation.

    Looks like it has the same error again still.....and another search for that file comes up empty.

    :13475
  • Ok so looking more at the logviewer I noticed a few times it mentioned Linux so I took Linux off of my subscription and started the updates again and it is downloading more binaries now.  After it finished downloading again it came up with no errors, so it must have been something with the linux subscription that was screwing it up???  Thanks for all of your help with this.

    :13477
  • Good work - trying without the Linux subscription would have been my next suggestion. You should inform Support of this ASAP though as I can't imagine what on your side could cause this. Looks like an error in the source Warehouse.

    Christian
    :13481
  • i had a similar issue with just the recommended subscription for windows. i ended up removing and readding the subscription and then all my update managers started updating again
    :13609