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.
Parents
  • 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
Reply
  • 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
Children
No Data