Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 1 subscriber
  • Views 1070 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

New Install

Peter

I currently have installed already an older version of the Enterprise Console/Manager.  The server this is running on will soon be decommissioned and I need to install the latest version (4) onto a different server, I have just run through the install and encountered the following error:

Error 25075. Cannot add user SophosUpdateMgr on server . Either the user already exists, or access is currently denied.

It then tells me to run SUM.msi at a later date.

I have checked and yes the domain account does exist, is there a way to get it to use this account while the old version is still accessing it.  I have no idea what the password for this is as I guess I was never told it due to be being randomly created when the original version was installed, I don't want to reset the password incase it causes problems with my existing setup.

Thanks.

Peter.

:293


This thread was automatically locked due to age.
  • 0

    Hi Peter,

    Did you attempt to upgrade the original version of Enterprise Console at any point prior to this seperate installation? The SophosUpdateMgr account is not created or used by previous versions of the console (at least not by default) so it is unlikely this account is being used by the original server unless it was upgraded to SEC4

    The migration guide might be of use if you haven't seen it already:

    http://www.sophos.com/support/knowledgebase/article/28276.html

    Cheers,

    Luke

    :322
  • 0

    I recieved the same error message, turning on TCP/IP & Named Pipes within SQL for the Sophos database resolve our issue, please see below:

    After SQL Server 2005 Express is installed, enable TCP/IP connections using SQL Server Surface Area Configuration. 

    • Click Start > Microsoft SQL Server 2005 > SQL Server Surface Area Configuration.
    • Click Surface Area Configuration for Services and Connections and expand Database Engine.
    • Select Remote Connections and select Local and remote connections. Ensure Using both TCP/IP and named pipes is selected. Click OK, and OK again to the window informing you that changes will not take affect until the database services are restarted. Restart the required services by accessing 
    Hope this helps!
    Cheers,
    Tim.
    :9949
Unfiltered HTML