Upgrade from 5.1 to 5.2 Management server will not connect

HI,

What if you copy the version from:

C:\Program Files\Sophos\Enterprise Console\Plugins\AuditingService

to

C:\Program Files (x86)\Sophos\Enterprise Console

Are the ones in the sub dirs of:

C:\Program Files\Sophos\Enterprise Console\Plugins

all the same but differ from the one in:

C:\Program Files (x86)\Sophos\Enterprise Console\?

Regards,

Jak

no change

unable to log in as the specified user
----- [outer exception] -----
-- error: 0x800706BE
-- facility: Win32

at class ATL::CComPtr<struct IDispatch> __thiscall bl::CReusingManagementServiceClientBroker::logIn(const struct util::UserName &,class Loki::SmartPtr<class bl::SubEstate,class Loki::RefCountedMTAdj<class Loki::ClassLevelLockable>::RefCountedMT,struct Loki::DisallowConversion,struct util::NoDereferenceNull,class Loki::DefaultSPStorage>,const wchar_t *,class bl::UIControllerBase &)
at int __cdecl Run(int,class bl::CommandLine,enum bl::ConsoleType::Type)
at int __stdcall wWinMain(struct HINSTANCE__ *,struct HINSTANCE__ *,wchar_t *,int)

Trying to start the Sophos Management service manually gives 

Error 1067: The Process terminated unexpectedly

Hi,

What does the Windows Application log say when you start the management service now?

If it's a .NET assembly binding issue, you could enable fusion logging:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion] 
"ForceLog"=dword:00000001 
"LogFailures"=dword:00000001 
"LogResourceBinds"=dword:00000001 
"LogPath"="C:\\Temp\\FusionLog\\"

Ensure the backslah on the logpath.

If you search for Fusion logging on Google you'll find plenty of info...but essentially you should end up with a log file for each .NET assembly loaded.  Is there a problem with the WilsonORMapper?  If so, that log should help.

Regards,

Jak

Went through and followed the KB instructions after getting this error in the Event log:

Data&colon; Incompatible database schema. Expected: 550000.5 actual: 450000.1

Cause The management service is pointing at the wrong database.
What to do
Ensure that the database the management service is pointing to is correct. In the example above a console 4.5 management service is pointing to a SOPHOS4 database rather than a SOPHOS45 database.

Check the DatabaseConnectionMS registry key has the correct "Catalog" value.

HKEY_LOCAL_MACHINE\SOFTWARE\[Wow6432Node]Sophos\EE\Management Tools\DatabaseConnectionMS
The string should be in the format:

Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=SOPHOS45;Data Source=Server\SOPHOS;

The registry key is not wrong though

Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=SOPHOS52;Data Source=(local)\SOPHOS;

Still stuck.

Hello Sid_RE,

this looks like either the database named SOPHOS52 actually contains a SOPHOS45 database or the SOPHOS52 database got distorted (don't ask me how). I think the stored procedure dbo.GetInterfaceVersion is the place where the "schema" values are taken from. The procedure is created upon database initialization (calling InstallDBEx.bat which in turn executes Procs.sql).

Christian

That is very strange.  I am looking at the InstallDBex and it is showing that yes it sets the DB name to SOPHOS45.  Weird.  I am attempting a reinstall with the instructions and will see how that goes.

Nope reinstall did not help.  Now I am back to "unable to log in as the specified user" and "The RPC server is unavailable."(I am guessing due to the service not being able to start.)  I know it has the correct user and the user is in the correct groups.

The Event Log is being no help this time as it is only recording the two errors below

.NET runtime 1026

Application: MgntSvc.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException
Stack:
at Sophos.Management.Data.PersistSession.Dispose(Boolean)
at Sophos.Management.Data.PersistSession.Finalize()

and 

Application Error 1000

Faulting application name: MgntSvc.exe, version: 5.2.0.566, time stamp: 0x50ec6bc2
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18015, time stamp: 0x50b83c8a
Exception code: 0xe0434352
Fault offset: 0x0000c41f
Faulting process id: 0x43e4
Faulting application start time: 0x01ce4fdd7b28aa74
Faulting application path: C:\Program Files (x86)\Sophos\Enterprise Console\MgntSvc.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: b995fc0e-bbd0-11e2-a615-6431504df318

This is frustrating.  I should have stopped when I got 5.1 working.

Hello Sid_RE,

please note that the database scripts are now in the \DB\Core\ subdirectory of \Enterprise Console\ (and under the 64bit Program Files). I think when I upgraded from 4.7 to 5.0 the scripts (.bat) have been removed from \DB\ - so they should no longer be there.

Christian

Well I got fed up.  Uninstalled.  Reinstalled 5.1 instead of 5.2 and viola it is now working.   I will be taking a break before I attempt 5.2 again.  If I even try to install 5.2.  This should have been a simple process of an upgrade and it turned into a week of poking in the dark......