Re: SQLServer 2005 Tools (MSXML 6) install fails on clean XP Pro SP3

#11

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

Quote:

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!

#12

Quote:

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.