11 réponses à ce sujet

[Barrett R]

EDIT: Solution is to manually install MSSQL 2008 and ignore MSXML6 issue. However, if that still doesn't work, rollback to Windows XP Service Pack 2, install toolset normally, then re-update Windows to SP3.

Ahoy! I've been trying for hours to get the toolset setup, and I finally seem to be grounded. It seems the jist of my issue is this: 
I have WinXP SP3. From what I've uncovered, as of XP SP3, MSXML6 (part of the SQL Express install) has been ingrained within the Windows File Protection system, which will generate a conflict between the version being installed by SQL Server 2005 and the version already installed with SP3. When I try install MSXML6 and/or the SQL Express bundled with the toolset installer, it doesn't allow me, saying it's protected by Windows. (see answer posted to this question on MSDN) I've tried numerous methods to no avail.

My current option appears to be to rollback to an earlier service pack for windows, but I forsee that causing more harm than good. Anyone have any ideas before I try a service pack rollback? I'd really like to avoid that if possible.
Thanks!

Modifié par Barrett R, 13 mars 2010 - 01:53 .

[nezroy]

I would suggest just doing a full manual install of SQL Express 2008 first, and then installing the toolset without the embedded DB and pointing it at the independent SQL install. It's the most complicated setup option, but also the most likely to work properly and, in my opinion, the best option for visibility and understanding

There's an article on the wiki for doing a manual DB install but it's targeted at 2005. I've also got a sort-of-guide post for doing a 2008 install over here: http://thenexusforum...dpost&p=1616852

I've had no problems running the toolset on 2008 with the toolset DB setup in 2005 compatibility mode.

Modifié par nezroy, 09 mars 2010 - 11:24 .

[Barrett R]

After jumping through numerous hoops getting the 2008 installer to run, I ended up with the same issue. 2008 still seems to require MSXML6, which is still "protected" by SP3 and can't be overridden. :/

[TimelordDC]

Download this - http://download.micr...1bd/msicuu2.exe, launch it and remove MSXML6 reference. After that, download MSXML6 SP 2 from http://www.microsoft...&displaylang=en and install it.
After that, try installing the toolset (or the SQL server edition of your choice)

Modifié par TimelordDC, 11 mars 2010 - 04:15 .

[Barrett R]

That Windows Cleanup doesn't find any MSXML6 (or any other software). It starts then finishes without actually displaying any selectable references. MSXML6 isn't actually listed in my add/remove programs either - seems it's the ingrained version within XP SP3 that's getting in the way of a fresh MSXML6 install.

[TimelordDC]

At minimum, the Windows Cleanup should display all items in the Add/Remove Programs list that were installed using Microsoft Installer. If that utility doesn't show anything, something is wrong with your system.

[Barrett R]

Hmm, I'm not sure that's quite accurate. According to http://support.microsoft.com/kb/290301 it says Windows Installer CleanUp Utility does not perform the removal of any programs that are installed by Windows Installer. I presume it just removes any leftover installer files from old/incomplete uninstalls (of MSXML6, for example). However, I don't think I have any trace of the proper MSXML6, just the silly one included deep within SP3.

I'll probably end up attempting a rollback to SP2 tomorrow. Hopefully my Windows will be merciful...

Modifié par Barrett R, 11 mars 2010 - 05:55 .

[Barrett R]

Success~

Rolled back to SP2, installed the toolset with the default SQL2005 without issue. Then took all day to reinstall SP3 and the plethora of Windows updates. After manually recreating the toolset DB, it appears to be in proper working order.



So beware those on XP SP3 installing the toolset fresh! You may need to go through the hassle of rolling back to SP2 in order to get going.

[nezroy]

BTW according to MS, you can just ignore the MSXML6 error when doing an SQL Express 2008 install on XP SP3; it doesn't affect or break the install.

http://connect.micro...e-msxml6r-error

However I'm sure it still plays havoc on the embedded sql 2005 installer the toolset is running.

Modifié par nezroy, 12 mars 2010 - 10:30 .

[Barrett R]

Ah, good to know. When I saw that error, I assumed the install failed (like it did/does for 2005). Not that I want to try that all again just to confirm...

[KillingMoon]

I had this problem as well, setup of Microsoft SQL server 2005 failed, so couldn't use the toolset.
Also for me it was MSXML6 that broke the install. But I found a simpler solution here: support.microsoft.com/kb/968749
A couple of solutions are mentioned on this page, like downloading a huge servicepack, but I used the 'fix it yourself' option, which means downloading a 200Kb fix for MSXML6 that basically uninstalls MSXML6.
My initial problem was that MSXML6 was already detected on my system when Microsoft SQL server 2005 was being installed and that silly enough makes the whole install fail. When I reinstalled the toolset after removing MSXML6 everything went fine. 

[WonderGamer]

I was having the same problem with my new installation of XP 64-bit.  Took me an entire day to figure out how to fix it, so I'm going to post how I fixed so others don't have to go through what I did.  This should work for all XP systems & will save a bunch of time over having to reinstall full OS service packs:

• [list=1]
• Uninstall your version of MSXML 6.0 using Add and Remove Programs (you likely have a newer version of it install which is screwing up the installation of the Toolset).
• Reinstall the standard MSXML 6.0 version from here.
• Manually install Microsoft SQL Server 2005 Express from here.
• Patch back up MSXML 6.0 using Microsoft Update.
• Restart your computer.
• Install the DA Toolset.

If the SQL Server (BWDATOOLSET) does not show in your list of services after installing it, you will need to overwrite the database for the one that is listed & redirect the Toolset to that server. Steps on how to do this can be found here. I suggest you backup the default database before overwriting it should you need to restore it later.

Modifié par WonderGamer, 05 mai 2011 - 09:55 .