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 setup - cant deploy to users - installation could not be started

Hi guys

OK i have installed

Enterprise Console 5 on a server 2008 machine.

I had problems with the database at first and it wouldnt load the interface.  Followed steps online and after lots of messing around I managed to load the console succesfully.

I have managed to protect the server it is already on OK

However, this is a new domain with new antivirus - I can see the 1st workstation i have setup when I do a scan via active directory.  But when I try to protect the computer after a while I get:

Installation could not be started 0x0000002e

Ive done the usual google searches and cant get it to work.

The workstation I am trying to protect is windows 7 64bit.

I have tried to follow the below:

http://www.sophos.com/en-us/support/knowledgebase/111180.aspx

I think I have done it correctly 

Firewall rules and services seem to be correct.

Are there any tests I can do to see what I have missed?

when i do protect computer the administrator password is accepted but then at the end i get the error

Can it be to do with a problem connecting to the database still? If i right click the problem computer in sophos to view computer details i get the error "cannot open database sophos51.  Login failed for user sophosm (which is what the account is in active directory)

Any help appreciated, I did try to follow the setup steps but what they dont seem to match with what I have on screen

thanks!

:27283


This thread was automatically locked due to age.
Parents
  • HI,

    The Windows security group "Sophos DB Admins" is used to grant the "database" account, in your case: "sophosm" access to the databases. i.e. SOPHOS51, SOPHOSENC51 and SOPHOSPATCH51.

    When you install SEC on a DC, "Sophos DB Admins" will be a domain local group.

    If you install on a member server or in a workgroup, then the group will be a local group.

    You should be able to:

    1. Re-create the databases using the batch files as per:

    http://www.sophos.com/en-us/support/knowledgebase/116768.aspx

    So essentially you are running against the Sophos instance of SQL:

    C:\sec_51\ServerInstaller\DB\Core\Installdb.bat .\sophos [domainname] SOPHOS51

    where [domainname] should be the short form of your domain as "Sophos DB admins" is a domain group.

    C:\sec_51\ServerInstaller\DB\Patch\CreatePatchDB.bat .\sophos [domainname] SOPHOSPATCH51

    C:\sec_51\ServerInstaller\DB\Encryption\InstallEncryptionDB.bat .\sophos [domainname] SOPHOSENC51

    This will create you the 3 new databases, and grant the Sophos DB admins group the correct access.  As long as "sophosm" is a member of the group you should be ok.

    Re-running the core and patch databases drop and re-create the database, the encryption database isn't dropped, so you may have to run:

    SQLCMD -E -S .\sophos -Q "DROP DATABASE SOPHOSENC51"

    If it says it is in use, stop the service "Sophos Encryption Business Logic Service"

    Regards,

    Jak

    :27329
Reply
  • HI,

    The Windows security group "Sophos DB Admins" is used to grant the "database" account, in your case: "sophosm" access to the databases. i.e. SOPHOS51, SOPHOSENC51 and SOPHOSPATCH51.

    When you install SEC on a DC, "Sophos DB Admins" will be a domain local group.

    If you install on a member server or in a workgroup, then the group will be a local group.

    You should be able to:

    1. Re-create the databases using the batch files as per:

    http://www.sophos.com/en-us/support/knowledgebase/116768.aspx

    So essentially you are running against the Sophos instance of SQL:

    C:\sec_51\ServerInstaller\DB\Core\Installdb.bat .\sophos [domainname] SOPHOS51

    where [domainname] should be the short form of your domain as "Sophos DB admins" is a domain group.

    C:\sec_51\ServerInstaller\DB\Patch\CreatePatchDB.bat .\sophos [domainname] SOPHOSPATCH51

    C:\sec_51\ServerInstaller\DB\Encryption\InstallEncryptionDB.bat .\sophos [domainname] SOPHOSENC51

    This will create you the 3 new databases, and grant the Sophos DB admins group the correct access.  As long as "sophosm" is a member of the group you should be ok.

    Re-running the core and patch databases drop and re-create the database, the encryption database isn't dropped, so you may have to run:

    SQLCMD -E -S .\sophos -Q "DROP DATABASE SOPHOSENC51"

    If it says it is in use, stop the service "Sophos Encryption Business Logic Service"

    Regards,

    Jak

    :27329
Children
No Data