SQL2005 SP3 Setup fails when MSXML 6.0 SP2
John
We know about the fix/workaround, which is to uninstall XML via the Windows
installer cleanup utility.
Question: When is MS going to give us a better solution? Something more
graceful and easier for the end user?
Such as:
1. Immediately update/fix/re-release the SQL 2005 Express Edition SP3
Setup.exe, to better DEAL with the possibility of MSXML 6.0 SP2's on the
client machine. Don't HALT the rest of the SQL Installation.
2. Immediately release a one liner utility allowing us to REMOVE MSXML 6.0
SP2 so that our clients can then install SQL 2005 trouble free. Same result
was as cleanup utility.
Our clients who need SQL 2005 Express Edition are all bombing, and there's
no graceful/easy fix.
Aaron Bertrand [SQL Server MVP]
> installer cleanup utility.
>
> Question: When is MS going to give us a better solution?
They are working on it. I can't give much more details than that, except
that it is not a simple fix, because this is something the Windows side did
(make MSXML files protected), and not some bug on the SQL side.
I plan to post a detailed blog entry on this problem once I am released to
do so (sorry, right now most of the details are NDA).
John
Aaron - Thanks for the reply.
Seriously, how hard can it be for the SQL team modify the SQL Setup.exe to
allow it to see that MS MSXML 6.0 SP2 is already installed on the client PC
and not HALT with errors.
I must repectfully disagree with you, the bug is on the SQL Side. It's the
SQL Setup.exe. There no reason it should fail/halt when a newer MSXML 6.0
SP2 exists. Setup is is NOT seeing that a newer version exists, and passing
thru the step. I don't know how anyone could intrepert this any
differently.
Aaron Bertrand [SQL Server MVP]
> allow it to see that MS MSXML 6.0 SP2 is already installed on the client PC
> and not HALT with errors.
The change is probably not hard. The problem is that the service pack must
be completely regression tested and it takes time to do this without the
guffaws of previous service packs (do you remember them re-releasing service
packs multiple times? Server egg-on-face they'd likely not want to repeat).
I've filed bugs against setup dialogs and wizards where a mere typo just did
not meet the bar to make it into the release because of all the re-work that
has to be done. And unfortunately XP SP3 obviously did not make it onto the
testing matrix when the service pack was initially in testing (and it was in
testing for a LONG time).
> I must repectfully disagree with you, the bug is on the SQL Side.
Well, that is not what Microsoft tells me, so you're not disagreeing with
me. I believe there will be a valid workaround from the SQL side, but as
above, it's not a one-line change and ship it.
Also, the problem isn't just that there's a different (unrecognized) version
on disk, it is also that because the files are now protected, setup can't do
anything with them. I agree that the solution is simple, but aren't all
solutions in hindsight? It was an unforeseen side effect of an OS change
that wasn't known at the time of testing. I'm not sure that you can
legitimately expect any more than knowing that a fix is forthcoming and that
it cannot possibly be immediate.
John
Thanks Aaron, I appreciate your comments.
We'll continue to instruct our clients do the workaround as needed. Got to
wonder how the big software vendors who embed 2005 ExprEd are documenting the
issue and workaround. Vendors like Sage ACT!, and I just glanced at their
support site and they're struggling with this issue too, same ugly
workaround, surprise, surprise.
Blog: I found your Blog. Very nice. A new desktop bookmark for me. I kppe
an eye out for any news on the issue.
Thanks. John
Aaron Bertrand [SQL Server MVP]
When I get more information from my contact at MS I will post that as well.
On 2/20/09 9:36 AM, in article
A11ECC90-13AB-4A2E...@microsoft.com, "John"