SEC 4.7 upgrade to SEC 5.0 fail

Hello XM,

any indication what it is doing during this time? The Application Event log might have some details. Once it is up again I'd check what is running using Process Explorer - this and Process Monitor could also help in finding out what it does before shutting down.

I assume you are still getting errors after restart and SEC doesn't run? Please provide as much detail as possible.

Christian

Hi Christian,

Just now I run command se config after  and try restart server again, then now restart server speed back to normal and sophos management service also can auto start.  Thanks for your help.

Thanks & Regards

XM

Hello,

a completely different approach: 1603 is well known to all who need to install updates for Office or .Net Framework.

1603-failures at the installation of a msi or msp are mostly caused by a missing msi-file for the original product. When you install application2.msi which replaces application1.msi, the Windows Installer needs access to application1.msi to uninstall the old software package.

Translated to Sophos EC 5: In order to install server32.msi from EC 5.0, the installer will need to access server32.msi (if that is the old name) from EC 4.7 to gather uninstall information.

During installation of EC 4.7, all the installation ressources together with all the required msi-files were stored in c:\sec47. Is this folder still stored on c:? If it was removed before the upgrade, the Windows Installer will fail to uninstall 4.7-components during the installation of 5.0.

It may sound strange, but starting the 4.7-installer will recreate c:\sec47 and it's contents. Just start the installer, wait for the decompression of all files, and abort the installer for EC 4.7. The installation ressources for 4.7 will be recreated, so it is possible to do an upgrade to 5.0.

Best regards

Detlev

Hi Christian,

Now got one more issue, SEC cannot upate, show code : 80040401 and 80040406, need how to fix.

Thanks & Regards

XM

Hello XM,

80040401 is just the generic error code. As to 80040406 - is the error still present? Your server's update source is Sophos, isn't it? From the Update managers view select  View Update Manager Details under Software subscription status: What's the timestamp in Last successful download for the failed subscription (which one, BTW - Recommended)? Further down under History: are the errors reported for each update attempt or only occasionally?

Christian

Hi Christian,

Now the error fixed, restart the server, need waiting one day after, can auto update now, but now when new pc joined domain, click discover computers, these new pcs will come to unassigned group, and cannot click protect computers, need manual move the pc to global group,then can protect , need how to fix? and other one issue. if SEC side got  Duplicate computer need how to delete one?

Thanks & Regards

XM

Hello XM,

discover computers, these new pcs will come to unassigned group

which method do you use (there are four - to be exact, one is Import from AD and the others Discover? For the latter what you describe is the normal and correct procedure.

Duplicates can have a number of reasons - it is perhaps better you start a new thread for this. Generally you just delete the "unwanted" ones (e.g. those with a Last Message Time way in the past).

Christian

Hi Christian,

I am use import from AD, but waiting one day still cannot click protect computers, and duplicates pc , when i have deleted after run import form AD again, the pc will show again and is grey colour.

Thanks & Regards

XM

Hello XM,

when you import from AD the group structure should be built and the computers (if you have selected Computers and containers) appear in the correct group (not Unassigned - but see below).  Protect computers should then immediately be available (unless SUM has not yet successfully downloaded the software).

As you have upgraded you have an existing environment and computers running Sophos will connect to the management server (they should already have done so). But things can get complicated here.

Again, please start a new thread with this issue if possible - this one is getting convoluted. A few questions:

• After you have upgraded SEC - were your computers still there?
• Was and is Sophos installed on at least some clients? If so - did they report to the console?
• Why did you import from AD? To find new computers (or have you deleted the existing ones)?

Furthermore, one or two screenshots showing duplicates might help (preferably with the Computer Details tab open)

Christian