Enterprise Console 4.5 Upgrade Failure [Topic title changed]

Hi,

Are the following correct:

1. The server name where the SQL instance resides is on the machine TITAN?
2. The SQL instance name is SOPHOS?
3. The domain name where the SQL instance resides is HTLINCS?

Also:

Is this a distributed install or is everything be installed on the same machine?

Was the SOPHOS SQL instance created by the Sophos installer or created manually?

What is the version of SQL, 2005 Express? 2005? 2008? 2008 Express.

Was the version of SQL upgraded as part of this install?

Thanks,

Jak

Hi

Thanks for responding.

The Server name that SQL is installed on is Titan
The original instance name was SOPHOS4 - at least this what was backed up.
The domain name is HTLINCS, Titan is a domain controller in the HTLINCS domain.

I ran the stand-alone installer via remote desktop on Titan. Everything is installed on Titan.
Accepted the default configuration - no manual customisation was made.
The SQL version is 2008 Express
As far as I am aware, no changes to SQL were made.

You should also be aware that I am not at all familiar with SQL.

I have the installation log if that would be useful.

I'm not going to be able to get back to this until tomorrow evening (it's 1:30pm now in the UK), so I can always give Support a ring on Monday and see if they can help. I was just wondering if a simple tweak could be used to allow a successful installation.

If I need to ring Support, I'll post the solution.

Thanks again!

Hello Blood,

The SQL version is 2008 Express

Hm, thought you get 2008 Express only when it is a new install or the existing database is MSDE. Did the installer tell you something about why it did install 2008?

And right now you are without working SEC? I also had a small problem during upgrade (but it was my fault) and I suggest that you check the following:

Registry value HKLM\Software\Sophos\EE\Management Tools\\DatabaseConnectionMS, it should contain Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=SOPHOS45;Data Source=TITAN\SOPHOS; (the last item is server and instance name - which should be the same as the value ...\Database Installer\\Instance). BTW: what's TITAN's OS version (and if it's a 64-bit system the keys are in HKLM\Software\Wow6432node\...)?

From a command prompt

osql -E -S TITAN\SOPHOS -Q "Select name FROM sysdatabases"

which should list among others SOPHOS4 and SOPHOS45. If the above keys contain different values for the instance run the command also for this one (-S TITAN\instance).

Any incorrect results?

As long as you haven't used the SOPHOS45 database it is in my experience safe to re-run InstallDB.bat manually (using the correct parameters of course, especially the database name!).

Christian 

Hi, Christian

Thanks for your reply.

The reason that SQL 2008 Express is installed is because several months ago I had a database issue and my DB had to sent to Sophos and fixed. During the fixing process the DB was upgraded to V2008 which meant that I had to upgrade the SQL installation here from 2005 Express to 2008 Express.

Anyway, I have been on the phone to Sophos Support for several hours today trying to sort this out.

Something drastic occurred as the ..\enterprise console\db\ folder was empty. Also, after cleaning the server up and manually checking the registry and all folder locations, the stand-alone SQL installation was still identifying a Sophos instance. After a lot of checking we decided the best course of action was to install Sophos Enterprise Console 4.5 on a different server.

I lost my previous configuration (4 years worth), but at least now I can upgrade all the clients to 9.5 and bring them up to date.

Thanks are due to Support for their help with this.

Cheers!

Hello Blood,

I lost my previous configuration

You didn't have a backup or you couldn't restore it?

I have a daily scheduled BackupDB on every management server, it takes only seconds (perhaps minutes in the worst case) and it saves you a lot of troubles. This way I also can't "forget" to backup before upgrading. But it wasn't before "someone" inadvertently zilched part of the SAN and although SQL has been backed up regularly they couldn't successfully restore it that I implemented the "simple" Sophos DB backup ...   

Something drastic occurred as the ..\enterprise console\db\ folder was empty

I've encountered something similar once during a Beta - I ascribed it to "heavy testing" (on an already successfully upgraded system). As at this time I wasn't interested in the upgrade process I didn't revert to the previous version (you guess - I had no backup from the upgraded system and thus had lost the latest changes anyway, fortunately this being a beta it was neither much nor critical).

Good to hear it's sorted out

Christian 

Hi, Christian

I made a backup of the Sophos database before upgrading as per the instructions in the Upgrade Advisor.

I think that despite the fact that SAV worked beforehand, the Support Technician I was working with yesterday was literally flabbergasted at the size of the database files. The mdf was 23MB and the ldf was 1.62GB. There are only 34 clients on the network...

When I sent the DB to Sophos several months ago the files were even larger, and when returned were 20MB and 40MB respectively. I have to admit that because of my lack of SQL knowledge I never thought to check the size of the files, and even then I would not know what was too large etc

So, at the end of the day, I learnt some more things about how it all works. The other benefit, of course, is that the previous installation had been in place since 2006 with several upgrades, so a new installation and setting the configuration from scratch is a good thing. I don't want to restore the DB in case I introduce a problem. The main issue the Support Technician had yesterday was trying to remove all references to the previous Sophos4 instance in SQL. I wonder if the instance was 'healthy'.

Thanks for your comments. I will schedule the backupdb batch file to copy the database to a remote machine from where it can be backed up to tape each night.

Cheers!