Today I decided to upgrade my windows internal database on my “VMWare-SharePoint-Development-System”. An upgrade was not possible so I removed the internal database (Microsoft##SSEE) and tried to install the new SQL Server (installation platform is w2k3-server, x86). My development system is a WSS 3.0 SP1 + Visual Studio 2008 environment.
Clicking through the installation wizard went fine but then the installation cancelled with “nice” red error icons. A look into the logfile showed the following.
Property(S): ACTION = INSTALL MSI (s) (08:D0) [23:01:25:354]: Note: 1: 1708 MSI (s) (08:D0) [23:01:25:354]: Produkt: MSXML 6.0 Parser (KB933579) -- Die Installation ist fehlgeschlagen. MSI (s) (08:D0) [23:01:25:354]: Das Produkt wurde durch Windows Installer installiert. Produktname: MSXML 6.0 Parser (KB933579). Produktversion: 6.10.1200.0. Produktsprache: 1031. Erfolg- bzw. Fehlerstatus der Installation: 1603. MSI (s) (08:D0) [23:01:25:385]: Cleaning up uninstalled install packages, if any exist
I downloaded the MSXML 6.0 Parser from the Microsoft Download page and tried to install it. Error! A newer product is already installed. A short look into “Software Installation” revealed that I have MSXML Parser 6.0 SP2 installed. Okay looks good for me but not for SQL Server 2008.
Being up-to-date is not always good
The installation routine depends on the installation of the MSXML Parser 6.0… In the end I uninstalled MSXML Parser 6.0 SP2 and started the installation again. Tadaaaa! It works. SQL Server was installed successfully. Now I can “re-apply” SP2 for the MSXML Parser 6.0
I started the windows
command-line and entered
date. It showed
2009-01-28. As you can see the year is 2009!
Having to do such steps to get an installation of SQL Server 2008 made me think I am in the year 1998! Wtf?!
Update: A friend of mine had problems with SQL Server 2008 installation, too.
- January 28th