Last February / March, I wrote several posts about an issue with MSXML6 on Windows XP which prevented the installation of SQL Server 2005, SQL Server 2008, and even service packs or cumulative updates in some cases:
There are also a couple of Connect items talking about the error itself or a potential workaround:
The latter article was recently updated by Peter Saddow of Microsoft, who said, "Just providing an update on this issue. We are planning to address in SP4." I guess this will ultimately help Express users to some degree, but not regular edition customers – SQL Server 2005 does not support slipstream, so if MSXML6 is blocking the engine installation, SP4 is not going to do you much good. (I posted yesterday that a public preview of SQL Server 2005 SP4 is available.)
For a short while, the KB article developed as a response to this issue (KB #968749) had instructions on using the Windows Installer Cleanup Utility to remove MSXML6 completely, and then reinstall it. This utility has since disappeared from Microsoft's web site, so now the KB article just says the following:
I've recently been told that there is a new EXE that has been published by Microsoft specifically to clean up MSXML6, on Windows XP systems only, so that SQL Server can be installed. Please use this file at your own risk, and if possible, wait until its use is fully documented in KB #968749. But if you can't wait, the file is here:
When you run this file, you'll have a EULA to agree to, and then a self-extracting WinZip archive:
Make a new folder before clicking Unzip because, if you dump this in your standard temp folder, you'll have no idea which files were extracted.
Now, when you unzip the installer, you end up with these files, and no instructions:
(Note the last modified dates of the important files – this will come up later.)
If you quickly scan the VBS file, you'll see that it references the MSP file, so it is clear that to get the ball rolling, you can double-click the VBS file. I don't have an XP system, so on Windows 7, I can't tell you exactly what the EXE does, as I get the following error:
It would be easy enough to edit the VBS file to bypass the local operating system check, but that kind of defeats the purpose. You should ONLY try to apply this fix on a machine that is the correct operating system and is clearly exhibiting the symptoms in KB #968749.
See, my concern (well, let's call it after-the-fact disappointment) is that these files were created LAST JUNE… and then Microsoft sat on them for almost a year and a half. By now, I would bet that 99% of the people affected by this issue have either (a) found another workaround because they were sick of waiting, or (b) subsequently upgraded to a more recent operating system which, as an added bonus, is not affected by this issue in the first place. So from my point of view this fix – even if it works – is too little, too late.