install SQL Server 2005 Sept CTP -> cannot install Office 2003 SP1

[Luther Miller]

If you install SQL Server 2005 Sept CTP, then you when you try and install
Office 2003 SP1 you get prompted for OWC11.msi -- it will keep prompting you
if you try to use the Office 2003 CD's version; but if you give the verison
from the SQL Server 2005 CD, then it will choke, tell you the component you
are trying to update is newed, and SP1 will not be installed at all.

haven't tried SP2 yet.

Is there a workaround? Will this be a problem with SQL Server 2005 released
version and Office SP2?

 

[Peter Foldes]

Luther

I have the Sept CTP and I do not have or had this issue at all. Apart from the obvious and that is to install Office 2003 1st which you did not do. The Sept CTP of SQL is a Beta which you should not put on a system other than on one in a testing environment.

May I suggest that you remove the Beta and install Office 2003 with SP2 and all further issues with SQL sept CTP should be brought up in the appropriate Beta group where it should be discussed.

This is a Office related group and bringing up a Beta related problem does not belong here

 

[Luther Miller]

Hi Peter,

I certainly appreciate your quick response; I apologize if you believe that
I have posted this in the wrong group. The reason that I posted it in this
group is because it is not the SQL installation that fails, but the Office
SP1 installation. Also, I'd like to point out that this issue occurs in two
orders of installation:
1) SQL 2005; Office 2003; Office 2003 SP1
2) Office 2003; SQL 2005; Office 2003 SP1

I plan to test SP2 soon as well, however I am not sure all our clients will
be installed SP2 right away as it has just come out.

You also make the point that SQL 2005 is in beta; thank you for the advice
that, as such, it should only go on test systems - in fact, I encountered
this problem installing these applications in a test environment. It is
indeed likely that even the final release of SQL 2005 will include an updated
version of OWC11.msi, so it is not likely that I will be last person to
encounter this issue. Perhaps by then everyone will be using Office 2003 SP2
and the problem may be taken care of - I don't know.