Unable to install database, A custom action failed.

Nikolai,

If you scroll up a few posts I did attach a txt file with my path output.

PATH=C:\Windows\system32\;C:\Windows;C:\Windows\system32\wbem;c:\tools;c:\program files (x86)\microsoft sql server\100\tools\binn;C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn;C:\Program Files (x86)\Sophos\AutoUpdate;C:\Program Files (x86)\Sophos\Enterprise Console;C:\ProgramData\tools\support;C:\ProgramData\pstools;C:\ProgramData\tools\ncftp;C:\ProgramData\tools\support;C:\ProgramData\pstools;C:\ProgramData\tools\ncftp;C:\ProgramData\tools\7-zip;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\ProgramData\chocolatey\bin;C:\ProgramData\tools\support;C:\ProgramData\pstools;C:\ProgramData\tools\ncftp;C:\Windows;C:\Windows\system;C:\Windows\system32;C:\Program Files\Microsoft SQL Server\100\Tools\Binn

Hello MartinRadicsh,

if required (several SEC versions used the same SOPHOS521 database but SEC5.4.0 has a new SOPHOS540) an upgrade installs a new database just like a clean install. IMO it's a flaw that the scripts only log STDOUT.

Christian

Ok I guess that I am right. Please truncate the Path a bit (keep the rest somewhere for backup)

try to remove either the /80/ or the /100/ paths.

see for example, only one might work with Sophos's MS SQL:

c:\program files (x86)\microsoft sql server\100\tools\binn

C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn

.. try to remove the "100" paths first.

Nikolai,

You appear to be right on the money.  The SQL server BINN was only part of the User path statement and not for the system.  I moved it to the System path variable and the install has now progressed beyond the Database installation.  Thank you for your help!

Great!

I think it is a matter of order - which path cames first and is the correct one for Sophos. So removing one "wrong" path is a clear solution. But it might disturb a different software then.

Sophos has trouble with installation for years now and IMHO people must continue to complain until they decide to increase the quality of installation and removal tools. Think about telling them directly about your trouble or send an idea-request / vote to one.

Hello NikolaiHartz and MartinRadicsh,

Sophos has trouble with installation for years
this is not in defence of Sophos (and I'm not Sophos BTW). I'd be the last to say that there aren't any shortcomings or that there haven't been any issues. In this particular case I fail to see where Sophos'  fault could be (except for the error logging in the script but likely it wouldn't have been of help here). As far as SEC, its installer and tools are concerned they are working with a SQL instance. They do not care how and where the instance is installed or what you do with it (you could move it as long it can be accessed using the Data Source value in the DatabaseConnectionMS string). Admittedly it would be possible (although the installer would have to know how to do it for all supported SQL Server versions) to determine the path to the "right" sqlcmd.exe  for a local instance - but not for a remote.  

Christian