....that worked for me, trying to install sql2005 developer. Used the ms clean up tool as noted in post and installed the msxml6 msi, worked for me.



Data Blueprint wrote:

This fix is related ... hope it helps someone.
04-Jan-09

This fix is related ... hope it helps someone.

I could not install MS Business Contact Manager (for Outlook 2007). It was
telling me that the install of MSXML 6 was failing, and therefore so was the
install of SQL Server Express, a prerequisite of BCM (Business Contact
Manager).

After searching and research for nearly 6 hours, I finally found a thread
which was on target:

http://social.msdn.microsoft.com/for...-3897921a866a/

The problem is that MSXML is system-protected under SP3, which I had
installed just prior to the BCM install.

The fix that finally worked was this one from Mark King - USM - Posted on
Saturday, April 12, 2008 2:53:37 PM.


All it took was:

1) removing the existing MSXML 6 file (which cannot be done via add/remove)
.... you must use this Windows cleanup installer:

http://download.microsoft.com/downlo...bd/msicuu2.exe

2) re-installing MSXML 6 from:

http://www.microsoft.com/downloads/d...displaylang=en


Then, re-install BCM. This worked for me.

Previous Posts In This Thread:

On Friday, December 12, 2008 4:18 PM
tackett wrote:

SQLServer 2005 Tools (MSXML 6) install fails on clean XP Pro SP3
Anyone else see this?

On clean XP Pro SP3, install SQLServer 2005 Tools
(en_sql_2005_ent_x86_dvd.iso)

1. Passes perquisites
2. Gets to where its dropping files
3. Install nearly everything else, then fails to install MSXML, says read log
4. Log says MSXML 6 SP2 failed to install (KB954459)

5. So I grab the MSXML 6 SP2 from MS downloads
(WindowsXP-KB954459-x86-ENU.exe) to update my system - or see why its failing
6. Log from that MSXML 6 SP2 install says it failed, and here is the log:

[KB954459.log]
0.719:
================================================== ==============================
0.719: 2008/12/12 15:12:17.030 (local)
0.719: c:\68ad68138e0fcc604b\update\update.exe (version 6.3.13.0)
0.719: Hotfix started with following command line: /log:C:\Downloads\MSXML
XP Security Update\
0.734: In Function GetReleaseSet, line 1240, RegQueryValueEx failed with
error 0x2
1.000: In Function TestVolatileFlag, line 11825, RegOpenKeyEx failed with
error 0x2
1.000: In Function TestVolatileFlag, line 11857, RegOpenKeyEx failed with
error 0x2
1.000: DoInstallation: CleanPFR failed: 0x2
1.000: In Function GetReleaseSet, line 1240, RegQueryValueEx failed with
error 0x2
1.000: SetProductTypes: InfProductBuildType=BuildType.Sel
1.000: SetAltOsLoaderPath: No section uses DirId 65701; done.
1.016: DoInstallation: FetchSourceURL for
c:\68ad68138e0fcc604b\update\update_SP3GDR.inf failed
1.016: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
0xe0000102
1.016: BuildCabinetManifest: update.url absent
1.016: Starting AnalyzeComponents
1.016: AnalyzePhaseZero used 0 ticks
1.016: No c:\windows\INF\updtblk.inf file.
1.016: OEM file scan used 0 ticks
1.031: AnalyzePhaseOne: used 15 ticks
1.031: AnalyzeComponents: Hotpatch analysis disabled; skipping.
1.031: AnalyzeComponents: Hotpatching is disabled.
1.031: FindFirstFile c:\windows\$hf_mig$\*.*
1.078: KB954459 Setup encountered an error: The update.ver file is not
correct.
1.078: KB954459 Setup encountered an error: The update.ver file is not
correct.
1.078: KB954459 Setup encountered an error: The update.ver file is not
correct.
1.078: KB954459 Setup encountered an error: The update.ver file is not
correct.
1.078: KB954459 Setup encountered an error: The update.ver file is not
correct.
1.078: KB954459 Setup encountered an error: The update.ver file is not
correct.
1.109: AnalyzeForBranching used 0 ticks.
1.109: AnalyzePhaseTwo used 0 ticks
1.109: AnalyzePhaseThree used 0 ticks
1.109: AnalyzePhaseFive used 0 ticks
1.109: AnalyzePhaseSix used 0 ticks
3.094: AnalyzeComponents used 2078 ticks
3.094: Downloading 0 files
3.094: bPatchMode = FALSE
3.094: Inventory complete: ReturnStatus=0, 2078 ticks
3.562: CreateUninstall = 0,Directory = C:\WINDOWS\$NtUninstallKB954459$
3.562: Num Ticks for invent : 2546
3.578: VerifyTargetFileSize: Unable to verify size as Source = NULL for file
c:\windows\inf\HFX183.tmp
3.578: Copied file: c:\windows\inf\branches.inf
29.906: Allocation size of drive C: is 4096 bytes, free space = 55745986560
bytes
29.922: Drive C: free 53163MB req: 5MB w/uninstall 0MB
29.922: CabinetBuild complete
29.922: Num Ticks for Cabinet build : 26360
29.922: DynamicStrings section not defined or empty.
29.922: FileInUse:: Detection disabled.
30.922: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed:
0xe0000102
34.125: System Restore Point set.
34.156: Copied file: C:\WINDOWS\system32\spmsg.dll
34.266: PFE2: Not avoiding Per File Exceptions.
34.703: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\68ad68138e0fcc604b\update\update_SP3QFE.inf ->
c:\windows\$hf_mig$\KB954459\update\update_SP3QFE. inf.
35.172: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\68ad68138e0fcc604b\spuninst.exe ->
c:\windows\$hf_mig$\KB954459\spuninst.exe.
35.391: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\68ad68138e0fcc604b\spmsg.dll -> c:\windows\$hf_mig$\KB954459\spmsg.dll.
35.437: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\68ad68138e0fcc604b\update\spcustom.dll ->
c:\windows\$hf_mig$\KB954459\update\spcustom.dll.
35.453: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\68ad68138e0fcc604b\update\KB954459.CAT ->
c:\windows\$hf_mig$\KB954459\update\KB954459.CAT.
35.609: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\68ad68138e0fcc604b\update\update.exe ->
c:\windows\$hf_mig$\KB954459\update\update.exe.
35.625: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\68ad68138e0fcc604b\update\updspapi.dll ->
c:\windows\$hf_mig$\KB954459\update\updspapi.dll.
35.641: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\68ad68138e0fcc604b\update\update.ver ->
c:\windows\$hf_mig$\KB954459\update\update.ver.
35.812: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\68ad68138e0fcc604b\update\updatebr.inf ->
c:\windows\$hf_mig$\KB954459\update\updatebr.inf.
35.812: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\68ad68138e0fcc604b\update\eula.txt ->
c:\windows\$hf_mig$\KB954459\update\eula.txt.
35.859: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\68ad68138e0fcc604b\update\branches.inf ->
c:\windows\$hf_mig$\KB954459\update\branches.inf.
35.875: DoInstallation: Installing assemblies with source root path:
c:\68ad68138e0fcc604b\
35.875: Num Ticks for Copying files : 5953
35.875: Num Ticks for Reg update and deleting 0 size files : 0
36.062: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is
empty; nothing to do.
85.469: RebootNecessary = 0,WizardInput = 0 , DontReboot = 1, ForceRestart = 0

==========


7. Thought it was a permissions issue, but I am an Admin on the box.. So
this should not be. Also tried to add permissions to the Windows Installer
Service user, no success...
8. Grasping at straws now...

Any ideas?

Thanks!

On Tuesday, December 16, 2008 11:27 AM
Chris Wood wrote:

Dave,I had heard that MSXML6 is now protected in XP SP3.
Dave,

I had heard that MSXML6 is now protected in XP SP3. We have not had this
problem when upgrading from XP SP2 to SP3 but brand new installs I believe
have this issue. Look at the XP SP3 release notes about protection.

HTH

Chris

"Dave" <tackettd (AT) grangeinsurance (DOT) no.com.spam> wrote


On Tuesday, December 16, 2008 12:28 PM
tackett wrote:

Thanks Chris!!!
Thanks Chris!!!

That bit of knowledge lead me to a different google search -- that then let
me in on the issue.

This link points to a MS descritpion of the problem / ticket AND an status
of: "Status Resolved (Won't Fix)"

http://connect.microsoft.com/SQLServ...dbackID=361660

Looks like MS is saying this shouldnt happen.. Though it seems its happening
in SQL Server 2005 (from my experience) and 2008 (ticket references 2008)
installs.


Microsoft,

Please try to install this MSDN DVD - en_sql_2005_ent_x86_dvd.iso onto a XP
Pro SP3 loaded system and confirm this issue does exist. When looking at the
ticket (noted above) -- I see the following statment: "Expected Results
Reason for error. Error shouldn't occur." This seems like someone
in MS said - this cant happen, but didnt test it.

This is going to effect any developer in my company trying to install the
SQL Server 2005 dev tools onto their PC with XP Pro SP3 loaded.

Thanks!

Dave


"Chris Wood" wrote:

On Tuesday, December 16, 2008 3:39 PM
Aaron Bertrand [SQL Server MVP] wrote:

No, this is not true. That comment was made by the original poster of thebug.
No, this is not true. That comment was made by the original poster of the
bug. "Expected results" means what does the submitter think should have
happened. Obviously the submitter wouldn't need to file a bug if the error
didn't occur.

On Tuesday, December 16, 2008 4:38 PM
tackett wrote:

Thanks Aaron, thats good news, I misunderstood the ticket format.
Thanks Aaron, thats good news, I misunderstood the ticket format. What
about the status on the ticket: "Status Resolved (Won't Fix)"

Does this mean -- that MS won't fix this issue OR that a workaround given
didnt fix it?

There is another post/thread asking about the same issue posted today "SQL
2005 Developer Install Failed on XP".

Does anyone know if MS is working on this?

-Dave


"Aaron Bertrand [SQL Server MVP]" wrote:

On Tuesday, December 16, 2008 7:03 PM
Aaron Bertrand [SQL Server MVP] wrote:

They're saying they won't fix it.
They're saying they won't fix it. In this specific case, it is because they
can not go back in time and push a lower version of MSXML6 with XP SP3.
Have you tried running the install and choosing to NOT update that specific
component? As the Microsoft person said, it should just be a message and
should not prevent the installation of other components from happening.
Maybe you need to post them the entire logs and show them exactly why the
rest of your install doesn't work, because as far as they're concerned, it
is not because of this conflict with MSXML6 on XP SP3.

A

On Tuesday, December 30, 2008 6:52 AM
bo wrote:

Dear Dave,I have read with interest your post.
Dear Dave,

I have read with interest your post.

I am trying to install SQL Server 2005 Standard Edition on an XP SP3 32-bit
platform (AMD 64bit CPU).

Here is an extract from the Log:-

Property(S): WrongPackage = This MSXML6 Service Pack 2 (KB954459) package is
not supported on the current processor type.

The above line seems to suggest that the 64-bit CPU might have something to
do with it.

I cannot uninstall MSXML6 SP2, have tried several methods.

Here is the message when using Add/Remove Programs:-

Setup was interrupted before MSXML 6 Service Pack 2 (KB954459) could be
completely installed.

I have seen a post on a German blog with the same error message as above but
its in German and so can't really understand the discussion.

Have you found a way of removing the MSXML 6 Service Pack 2 (KB954459) ?

Would like to keep in touch on this one.

--
Bob Snedden, MCT, MCSD.Net


"Dave" wrote:

On Tuesday, December 30, 2008 7:03 AM
bo wrote:

Dear Aaron,I too have experience of the original issue raised by Dave.
Dear Aaron,

I too have experience of the original issue raised by Dave.

Can't install SQL Server 2005 on an XP Pro SP3 32-bit installation.

Fails on the MSXML 6.0 pre-requisite.

Cannot unistall MSXML 6 Service Pack 2 (KB954459) and so I appear blocked
when trying to go back to pre-SP2.

Can you advise how to unistall ? I have tried the procedure from Article
909967

http://support.microsoft.com/kb/909967

but cannot remove it.

I feel if I can unistall SP2 I will be able to proceed with the install.

Thank you.

--
Bob Snedden, MCT, MCSD.Net


"Aaron Bertrand [SQL Server MVP]" wrote:

On Tuesday, December 30, 2008 11:42 AM
bo wrote:

RE: SQLServer 2005 Tools (MSXML 6) install fails on clean XP Pro S
Dear Balmukund,

Your advice regarding:-

Download windows installer cleanup utility using this link
http://download.microsoft.com/downlo...bd/msicuu2.exe

worked perfectly and so MSXML 6.0 SP2 is now removed.

Thanks for your help.


--
Bob Snedden, MCT, MCSD.Net


"Microhands, Edinburgh" wrote:

On Thursday, January 01, 2009 11:39 PM
Abdul Rehman wrote:

Thank you so much
Thank you so much for sharing such a useful information that helped me saving hours of hit and trials. Microsoft should get better on this.

On Sunday, January 04, 2009 3:13 AM
Data Blueprint wrote:

This fix is related ... hope it helps someone.
This fix is related ... hope it helps someone.

I could not install MS Business Contact Manager (for Outlook 2007). It was
telling me that the install of MSXML 6 was failing, and therefore so was the
install of SQL Server Express, a prerequisite of BCM (Business Contact
Manager).

After searching and research for nearly 6 hours, I finally found a thread
which was on target:

http://social.msdn.microsoft.com/for...-3897921a866a/

The problem is that MSXML is system-protected under SP3, which I had
installed just prior to the BCM install.

The fix that finally worked was this one from Mark King - USM - Posted on
Saturday, April 12, 2008 2:53:37 PM.


All it took was:

1) removing the existing MSXML 6 file (which cannot be done via add/remove)
.... you must use this Windows cleanup installer:

http://download.microsoft.com/downlo...bd/msicuu2.exe

2) re-installing MSXML 6 from:

http://www.microsoft.com/downloads/d...displaylang=en


Then, re-install BCM. This worked for me.

On Wednesday, February 04, 2009 3:51 PM
Jesse Munro wrote:

Thank you
THIS IS THE SOLUTION
1. download and install the cleanup utility
2. Run the cleanup tool "Remove" the MSXML 6.0 SP2
3. Install SQL
4. Life was good once again

On Thursday, February 12, 2009 3:14 PM
Bill Hepler wrote:

MSXML 6.0 SP2 and MS SQL
That worked for us too. Thanks for the concise explanation!

Bill Hepler

On Monday, May 04, 2009 2:09 AM
nitin wrote:

SQLServer 2005 Tools (MSXML 6) install fails on clean XP Pro SP3
You are required to be a member to post replies. After logging in or becoming a member, you will be redirected back to this page.

On Saturday, June 20, 2009 1:05 AM
jim lawson wrote:

MSXML 6.0 SP2 clean up
You are required to be a member to post replies. After logging in or becoming a member, you will be redirected back to this page.

On Tuesday, January 05, 2010 10:46 AM
Bader Cheema wrote:

SQLServer 2005 Tools (MSXML 6) install fails on clean XP Pro SP3
This worked. Thanks for sharing the experience.

On Friday, February 05, 2010 9:22 AM
S Oe wrote:

Great
Thanks so much!!!

On Monday, February 15, 2010 8:17 AM
sneha B wrote:

awesome
awesome it really worked for me too... thanx a ton...

On Sunday, June 06, 2010 9:54 AM
Dilip S wrote:

Unable to uninstall MSXML 6.0 on Win XP Pro SP3
Dear Bob,

Thanks for the tip. Running the clean up util resulted in the following results.

Script: C:\DOCUME~1\......\Temp\IXP000.TMP\StartMsi.vbs
Line: 2
Char: 1
Error:The specified module could not be found.
Code: 8007007E
Source: (null)

The title of the message box is "Windows Script Host"

I had cleaned the temp folders.

So, any help with resolution of manual removal and restoring ability to install SQL Express 2005 on Win XP Pro SP3 would be appreciated.

Thanks and Regards,

Dilip


Submitted via EggHeadCafe - Software Developer Portal of Choice
Composite UI Pattern And Enterprise Settings
http://www.eggheadcafe.com/tutorials...-settings.aspx