Using installDB to create SOPHOS521

Hello the_man and welcome,

unless my eyesight has gone very bad you haven't posted details of the failure, have you? You want to have the database on a separate SQL server but mot in its own instance?

Christian

Hello the_man and welcome,

unless my eyesight has gone very bad you haven't posted details of the failure, have you? You want to have the database on a separate SQL server but mot in its own instance?

Christian

Hello QC,

Yes, correct.
I have separated SQL server 2012 with instance name are MSSQLSERVER on Windows 2008r2 SP1 (hostname : win2008r2).
And I was try to using installDB.bat but always failed. And I believe, I just follow the kb. There any mistake in my side? and also, the log generated for me not enough to give detail error information.

Hello the_man,

guess the log doesn't contain any confidential information and it's not very long so you could post it here. Without the log it's impossible to say what the problem could be - always failed is too general.

Christian

Hi QC,

I has addresses the log to C:\SOPHOS521.LOG and content like below:

"InstallDB (local)\MSSQLSERVER WIN2008R2 SOPHOS521 C:\SOPHOS521.LOG

started

Mon 08/31/2015

02:33 PM

================"

Hello the_man,

this is what one sees when sqlcmd is not available on the computer (server). Just type sqlcmd in a cmd window - if you get an is not recognized message please see for example sqlcmd Is Missing From SQL Server 2012.    

HTH

Christian

Hi QC,

sqlcmd found in server. Please see capture below for sqlcmd, installdb and log capture. 

Hello the_man,

edit InstallDBEx.bat and on the first sqlcmd line (after the Execute SQL scripts comment) add a STDERR redirection ( ... >> %logoutput% 2>&1). Or modify the two @EXIT statements at the end of InstallDBEx.bat to @EXIT /B 1 and @EXIT /B 0 respectively.

Christian

Hello QC,

we get the log error more detail after modify the InstallDBex.bat like capture below: (what must I do, since I also not to familiar with SQL, hehehe...)

Hello the_man,

didn't think of it before, sorry. MSSQLSERVER is the default instance name. Please try just the machine name (or even only a dot .) instead of (local)\MSSQLSERVER for the instance name.
not too familiar with SQL - who is at your site? Why do you want to use the default and not a named instance?

Christian

Hii QC,

Thank for the replied. I was try  dot instead of (local) and here are log was appear 

Hello the_man,

so it seems that the connection succeeds using just a dot. The second parameter (as far as I can see you've used \MSSQLSERVER) is the accountDomainName though - first of all it shouldn't start with a "\" and it should be either the domain, if you've created Sophos DB Admins as a domain group, or the local server (in your case WIN2008R2) - you did create the group, didn't you?

Christian