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

Sophos Management Service won't start

essdeeay

I've installed SEC 5.2.1 and specified a different port.  Now the Management Service won't start, event log shows:

ID 8004

Initialization failed.

Step: Creating a database connection
Error: std::runtime_error
Data: [DBNETLIB][ConnectionOpen (ParseConnectParams()).]Invalid connection.

ID 8025

There is no database connection. Management Service will be shut down.

I can confirm that the SophosManagement user is a member of the Sophos DB Admins local group. Is this because of the different port number, and how can I fix?

Many thanks,

Steve

:41161


This thread was automatically locked due to age.
  • 0

    Hello essdeeay,

    which port did you change, port 80?

    Don't think it is an issue with the account. This is a fresh install and after the install and logoff/logon the Console never came up? Is your database local and what's the data in HKLM\SOFTWARE\Wow6432Node\EE\Management Tools\\DatabaseConnectionMS?

    Christian

    :41163
  • 0

    Hi Christian,

    I don't have the exact REG location you specified, but I do have

    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sophos\EE\Management Tools]
    "DatabaseConnectionMS"="Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=SOPHOS521;Data Source=(local)\\SOPHOS;"

    One missing but of information, I originally installed it but something else was using port 80, so I removed it, removed the database instance (using Add/Remove on Microsoft SQL Server R2 (64-bit), then remove the remaining Sophos folder from C:\Program Files\Microsoft SQL Server, before reinstalling.

    Steve

    :41165
  • 0

    Hello Steve,

    too late now but as Why is port 80 required ... says the port can be reconfigured by running the installer again.

    so I removed it

    All components (i.e. Sophos Database, Console and SUM)?

    removed the database instance

    Also no need to remove the instance if you intend to use it later. Did the installer correctly create a new one, i.e. does the instance exist once more, is accessible and contains the database? Just in case, some useful commands are in Sqlcmd commands for accessing the Sophos core database and extracting information.

    Christian

    :41169
  • 0

    Hi Christian,

    Thanks again for your reply...

    Another bespoke application uses port 80 - which I didn't realise at the time, which is why I selected a different port in the installer, the next time around.

    Yes, all Sophos components were removed.  I removed the database aswell as when trying to connect to an existing instance, the installer kept failing, even though I could verify the username/password were correct.  The reason I couldn't reinstall the first few times was because of the Sophos database directory stil being in place, which I had to remove manually - see previous post.

    So I guess my question is, why doesn't the Sophos Management service start?

    Thanks,

    Steve

    PS. Thanks for the link to th sql commands - very useful.

    :41173
  • 0
    Hello Steve,

    just noticed - are there really TWO backslashes in the Source= parameter? Think it should be a single one

    Christian
    :41175
  • 0

    Sorry Christian - the regedit export has to escape backslashes, hence the two you see.

    :41185
  • 0

    Hello Steve,

    my bad, should have thought of it.

    Tried to evoke this message by fiddling with the DatabaseConnectionMS as well as the SQL instance (on a test server of course :smileyvery-happy:) but without success. 

    So you say the database is there, you can access it and successfully use the commands from the article (e.g. sqlcmd -E -S .\sophos -d sophos521 -Q "select name from computersanddeletedcomputers)?

    Christian

    :41223
  • 0

    Hi Christian,

    I get something like "---------------------------------------------------------- (0 rows affected)" which I assume means things are working OK.  I wouldn't expect any data to be in there because I've never been able to open the management console to do anything, but it looks like the database aspect works OK.

    Steve

    :41229
  • 0
    Hello Steve,

    the table is initially empty - as you said it seems to be ok. I suspect - though I might be wrong - the error to be in some intermediate component as both ends (the db and the registry value) look fine.
    You can always call Support, maybe the SDU logs give enough insight to suggest a solution - maybe not. I'd modify the DatabaseConnectionMS value to see if this changes the error (reverting each modification immediately afterwards). The instance name in the "Data Source" first, if you get the same error when starting the mgmt service the issue is not with SQL/database. Replacing "(local)" with the hostname or "." would be next. "Initial Catalog" and "Integrated Security" would only have effect if the instance has, but anyway I'd give it a try.

    Anyway, this is academic ... more pragmatic: re-run the installer (as if changing the port, you can actually change it since you don't have installed clients which would be affected), any error might help in getting to the cause of the problem. If afterwards the situation is the same it's likely necessary to uninstall the SEC components (not touching SQL) - if at reinstall setup has again a problem with the existing SQL instance it's perhaps the same as the service has.

    Christian
    :41247