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

SEC5.0 database fail to download

Junior

hi,

   im new on sophos product , please give some solution on it,

i wan to install the SEC 5.0 on a domain controller ,

but not recomented by SEC 5.0,

i have try many way to install but at last the database is failed to install.

:22035


This thread was automatically locked due to age.
  • 0

    Hi, 

    Although it is not recommended you install Enterpirse Console on a DC  it should be fine.   I think this mainly comes from the MS recommendation that you shouldn't install SQL on a DC.  However it's not best practice to overload roles, plus it rules out installing maybe insecure software on a important machine such as a DC.

    Anyway, when you say the database failed to install are you referring to the failure to install SQL Server 2008 Express or the failure to install the Sophos database into the SQL instance?

    The Sophos installer; setup.exe, installs pre-reqs which can include, if you choose the database component, SQL Express 2008. Once those are installed it goes on to install the 3 components of the Sophos installation.  Database, Server and Console.

    If the failure is with SQL, then SQL Server installer creates a wealth of logs for each install attempt under:

    "\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log \"

    If however it is the Sophos database component, the following logs are created in the installing users temp, i.e. %temp%:

    • Sophos_Database64msi [timestamp].log  (installing of the MSI)
    • Sophos_InstallCoreDB.log   (Installing of the SOPHOS50 database)
    • Sophos_InstallPatchDB.log    (Installing of the SOPHOSPATCH database)

    The boottrap log, also under %temp%:
    Sophos_bootstrapper [timestamp].log

    Is the main log of setup.exe and ties it all together.

    If the problem is with SQL, you might like to try downloading the SQL Server 2008 R2 and use that to create a SQL instance.  It may well be a bug that is fixed, who knows.  When you next run the Sophos installer you can specify that instance during the install.

    Regards,

    Jak

    :22041
  • 0

    hi jak,

    thank for your solution, that work , 

    thank you very much,

    :22167