Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 2 subscribers
  • Views 7767 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

Upgraded to Enterprise Console 5.4 now I can't open it !

Kennysarmy

2016-04-28 13:54:31.33 Server Microsoft SQL Server 2008 R2 (SP2) - 10.50.4042.0 (X64)
Mar 26 2015 21:18:04
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)

2016-04-28 13:54:31.36 Server (c) Microsoft Corporation.
2016-04-28 13:54:31.36 Server All rights reserved.
2016-04-28 13:54:31.36 Server Server process ID is 1464.
2016-04-28 13:54:31.36 Server System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
2016-04-28 13:54:31.36 Server Authentication mode is WINDOWS-ONLY.
2016-04-28 13:54:31.36 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SOPHOS\MSSQL\Log\ERRORLOG'.
2016-04-28 13:54:31.37 Server This instance of SQL Server last reported using a process ID of 1496 at 28/04/2016 13:53:48 (local) 28/04/2016 12:53:48 (UTC). This is an informational message only; no user action is required.
2016-04-28 13:54:31.37 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.SOPHOS\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.SOPHOS\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.SOPHOS\MSSQL\DATA\mastlog.ldf
2016-04-28 13:54:31.42 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2016-04-28 13:54:31.42 Server Detected 2 CPUs. This is an informational message; no user action is required.
2016-04-28 13:54:31.74 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2016-04-28 13:54:32.15 Server Node configuration: node 0: CPU mask: 0x0000000000000001:0 Active CPU mask: 0x0000000000000001:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2016-04-28 13:54:32.40 spid7s Starting up database 'master'.
2016-04-28 13:54:32.56 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2016-04-28 13:54:32.77 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SOPHOS'.
2016-04-28 13:54:32.88 spid7s SQL Trace ID 1 was started by login "sa".
2016-04-28 13:54:32.90 spid7s Starting up database 'mssqlsystemresource'.
2016-04-28 13:54:32.90 spid7s The resource database build version is 10.50.4042. This is an informational message only. No user action is required.
2016-04-28 13:54:33.28 spid10s Starting up database 'model'.
2016-04-28 13:54:33.28 spid7s Server name is 'FP6\SOPHOS'. This is an informational message only. No user action is required.
2016-04-28 13:54:33.34 spid7s Informational: No full-text supported languages found.
2016-04-28 13:54:33.34 spid7s Starting up database 'msdb'.
2016-04-28 13:54:33.40 spid10s Clearing tempdb database.
2016-04-28 13:54:33.52 Server A self-generated certificate was successfully loaded for encryption.
2016-04-28 13:54:33.52 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SOPHOS ].
2016-04-28 13:54:33.52 Server Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SOPHOS\sql\query ].
2016-04-28 13:54:33.53 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2016-04-28 13:54:33.65 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/FP6.curriculum.local:SOPHOS ] for the SQL Server service.
2016-04-28 13:54:33.65 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2016-04-28 13:54:35.94 spid10s Starting up database 'tempdb'.
2016-04-28 13:54:36.26 spid13s The Service Broker protocol transport is disabled or not configured.
2016-04-28 13:54:36.29 spid13s The Database Mirroring protocol transport is disabled or not configured.
2016-04-28 13:54:36.46 spid13s Service Broker manager has started.
2016-04-28 13:54:36.46 spid7s Recovery is complete. This is an informational message only. No user action is required.
2016-04-28 13:54:36.48 spid51 Starting up database 'SOPHOS540'.
2016-04-28 13:54:40.65 spid51 Starting up database 'SOPHOSPATCH52'.
2016-04-28 13:50:05.92 Logon Error: 18456, Severity: 14, State: 38.
2016-04-28 13:50:05.92 Logon Login failed for user 'CURRICULUM\SophosManagement'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]
2016-04-28 13:50:05.94 Logon Error: 18456, Severity: 14, State: 38.
2016-04-28 13:50:05.94 Logon Login failed for user 'CURRICULUM\SophosManagement'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]



This thread was automatically locked due to age.
Parents
  • 0
    I tried following the instructions here:
    and used these commands and it's still not allowing me to start the service: Sophos Management Service
    sqlcmd -E -S .\SOPHOS -Q "IF  EXISTS (SELECT * FROM sys.server_principals WHERE name = N'FP6\Sophos DB Admins') DROP LOGIN [FP6\Sophos DB Admins]"

    sqlcmd -E -S .\SOPHOS -Q "CREATE LOGIN [FP6\Sophos DB Admins] FROM WINDOWS"

    sqlcmd -E -S .\SOPHOS -d SOPHOS540 -i "C:\Program Files (x86)\Sophos\Enterprise Console\ResetUserMappings.sql"
    sqlcmd -E -S .\SOPHOS -d SOPHOSPATCH52 -i "C:\Program Files (x86)\Sophos\Enterprise Console\ResetUserMappings.sql"
  • 0 in reply to Kennysarmy

    Hello Kennysarmy,

    you say the Sophos Management Service fails to start? The error in the SQL log might not be the cause though - I see the same errors (which are apparently transient) after a server reboot. If there is no telling event in the Event log maybe the sophos-management-services.log (in %ProgramData%\Sophos\Sophos Endpoint Management\log\) has some useful information. 

    Christian

Reply
  • 0 in reply to Kennysarmy

    Hello Kennysarmy,

    you say the Sophos Management Service fails to start? The error in the SQL log might not be the cause though - I see the same errors (which are apparently transient) after a server reboot. If there is no telling event in the Event log maybe the sophos-management-services.log (in %ProgramData%\Sophos\Sophos Endpoint Management\log\) has some useful information. 

    Christian

Children
Unfiltered HTML