Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 18 replies
  • Subscribers 1 subscriber
  • Views 9637 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

4.7 console install

LukeA

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.
Parents
  • 0

    Then it's basically working.

    I'd start with LogViewer.exe (in the ...\SUM directory). Select Severity: Error. Likely you'll see "groups" (i.e. with same or almost same timestamp) of errors - the bottommost of a group is usually the interesting one. You'd then take a look a the SUMTraceyyyymmddThhmmss logs and locate the timestamp (note that these 4 logs span only a few hours so you can't search for errors from a few days ago).  If it doesn't make sense to you feel free to post the "suspicious" lines here (note that there's a limit in this forum - if you want to post larger excerpts upload them at some site and link to them).

    Christian

    :13457
Reply
  • 0

    Then it's basically working.

    I'd start with LogViewer.exe (in the ...\SUM directory). Select Severity: Error. Likely you'll see "groups" (i.e. with same or almost same timestamp) of errors - the bottommost of a group is usually the interesting one. You'd then take a look a the SUMTraceyyyymmddThhmmss logs and locate the timestamp (note that these 4 logs span only a few hours so you can't search for errors from a few days ago).  If it doesn't make sense to you feel free to post the "suspicious" lines here (note that there's a limit in this forum - if you want to post larger excerpts upload them at some site and link to them).

    Christian

    :13457
Children
No Data