Sophos upgrade need SQL help first to u/g MSDE to Sql 2005
We are on Enterprise Console 3 and are looking to u/g to 4.5.
One of the prerequisites is upgrading from the MSDE version to SQL 2005.
When I try and run the SQL 2005 setup program it finds the Sophos database but it is reporting it as:
MSDE Version 8.00.1100
it then fails with :
Name: Microsoft SQL Server Desktop Engine (SOPHOS)
Reason: Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Your upgrade is blocked because of edition upgrade rules. For more information about edition upgrades, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
From C:\Program Files\Microsoft SQL Server\MSSQL$SOPHOS\LOG
2010-11-02 12:56:19.93 server Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.2 (Build 3790: Service Pack 2)
2010-11-02 12:56:19.95 server Copyright (C) 1988-2002 Microsoft Corporation.
2010-11-02 12:56:19.95 server All rights reserved.
2010-11-02 12:56:19.95 server Server Process ID is 1436.
2010-11-02 12:56:19.95 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL$SOPHOS\LOG\ERRORLOG'.
2010-11-02 12:56:19.96 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2010-11-02 12:56:20.39 server SQL Server configured for thread mode processing.
2010-11-02 12:56:20.40 server Using dynamic lock allocation.  Lock Blocks,  Lock Owner Blocks.
2010-11-02 12:56:20.62 spid3 Starting up database 'master'.
2010-11-02 12:56:20.89 spid3 0 transactions rolled back in database 'master' (1).
2010-11-02 12:56:20.89 spid3 Recovery is checkpointing database 'master' (1)
2010-11-02 12:56:20.93 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2010-11-02 12:56:20.93 spid5 Starting up database 'model'.
2010-11-02 12:56:20.93 spid3 Server name is 'FP6\SOPHOS'.
2010-11-02 12:56:20.93 spid3 Skipping startup of clean database id 4
2010-11-02 12:56:20.93 spid3 Skipping startup of clean database id 5
2010-11-02 12:56:21.00 spid5 Clearing tempdb database.
2010-11-02 12:56:21.14 server SQL server listening on 10.7.43.156: 1767.
2010-11-02 12:56:21.14 server SQL server listening on 127.0.0.1: 1767.
2010-11-02 12:56:21.32 server SQL server listening on TCP, Shared Memory, Named Pipes.
2010-11-02 12:56:21.32 server SQL Server is ready for client connections
2010-11-02 12:56:21.34 spid5 Starting up database 'tempdb'.
2010-11-02 12:56:21.37 spid3 Recovery complete.
2010-11-02 12:56:21.37 spid3 SQL global counter collection task is created.
2010-11-02 12:56:25.23 spid51 Starting up database 'SOPHOS3'.
Product: SQL Server
Component: SQL Server Setup
Message: To continue you must provide a strong sa password.
You selected Mixed Mode authentication, but did not provide a strong password.
Mixed Mode authentication requires that you enter a strong sa password before you can continue to the next page of the Installation Wizard. A strong password must contain six or more characters, including at least one from three of the following categories: uppercase letters, lowercase letters, numbers, and non-alphanumeric characters (such as #, %, or ^). A strong password cannot be a reserved keyword, cannot include the computer name, and cannot include the username of the person logged onto the computer. For additional information on setting strong passwords, see the "Authentication Mode" topic in Books Online.
Had plenty of fun upgrading Sophos to 4.5 from 3.0 at various sites myself recently.
Can't help with your specific error, but I recommend removing all traces of Sophos, including the SQL instances, then installing the lot again from fresh. However, there is a certain order in which components need to be un-installed.
Can't remember it off the top of my head, but will be able to tell you in the morning.
You certainly shouldn't be having to mess around with SQL. The installer should be taking care of all of that for you.
Should you contact Sophos, I'd phone them as they won't respond to an email or online fault log. Not in my experience anyway.