Home Dashboard Directory Help
Search

SQL Server Express 2008 Installation - Update msxml6r error by KJatWork


Status: 

Closed
 as Won't Fix Help for as Won't Fix


12
0
Sign in
to vote
Type: Bug
ID: 361660
Opened: 8/13/2008 9:41:01 AM
Access Restriction: Public
1
Workaround(s)
view
6
User(s) can reproduce this bug

Description

During Installation the following error occured:


Running Action: Install_Msxml6_Cpu32_Action
Target package: "c:\9e32673e33ccf996493d46cfbeadde\x86\setup\x86\msxml6.msi"
MSI Error: 1931 The Windows Installer service cannot update the system file c:\WINDOWS\system32\msxml6r.dll because the file is protected by Windows. You may need to update your operating system for this program to work correctly.
Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Programme\Microsoft SQL Server\100\Setup Bootstrap\Log\20080811_224055\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Programme\Microsoft SQL Server\100\Setup Bootstrap\Log\20080811_224055\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Programme\Microsoft SQL Server\100\Setup Bootstrap\Log\20080811_224055\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
The Windows Installer service cannot update the system file c:\WINDOWS\system32\msxml6r.dll because the file is protected by Windows. You may need to update your operating system for this program to work correctly.
Watson bucket for Msi based failure has been created
InstallPackage: MsiInstallProduct returned the result code 0.
RunMsiCore succeeded.
Checkpoint: INSTALL_MSXML6_CPU32_ACTION
Completed Action: Install_Msxml6_Cpu32_Action, returned True
Details
Sign in to post a comment.
Posted by FZB on 7/13/2010 at 2:46 AM
cant agree on "neither sql server 2008 nor xml is affected". the installation of developer 2008 (management studio feature) fails due to not being able to install xml6, i would consider that an issue
Posted by Ken Zook on 9/16/2009 at 7:29 AM
Has anyone solved this problem with SQL Server 2005 Express? We also depend on this with our installation, and it is failing to install on a Turkish XP with SP3.
Posted by JohnReam on 2/19/2009 at 1:23 PM
Any new news here? Its been 3 weeks. We agree with RexHeadlong, this is a critcal problem, SQL Server 2005 Express Edition. We need 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.

Posted by Steve Harding Trade Service on 1/30/2009 at 9:44 AM
This is a CRITICAL issue. For years we have bundled SQL Server Express 2005 into our product as a silent install. This issue causes the SQL Server installation to fail, which prevents our product from installing. We have 4 customers now who can't install our product because of this issue. They are all running the English - US version of Windows XP SP3.
Posted by AngelsFlyHigh on 12/9/2008 at 1:42 AM
I'v been working on making our installer to run silent and then SP3 came and SQL 2005 will break when run silent.
There must be another workaround than to force a user to ignore an error message?
Posted by ManServ on 9/24/2008 at 11:00 AM
With SQL Server 2005 the MSXML6R issue will cause the setup to FAIL. So if you ignore it you won't get SQL server 2005 installed.
Posted by Microsoft on 9/23/2008 at 7:44 PM
kjatwork,

Thanks for reporting this issue. Upon our investigation, we determined that we will not fix this issue. Below is an explanation as to why.

----------------------------

This error is known. Neither SQL Server 2008 installation nor MSXML6 on the machine is affected by it. Users can ignore the error message.

On Windows XP or lower OS, MSXML6 was only installed by MSI package. Things have been changed since Windows XP SP3. The individual MSXML6 files (msxml6.dll and msxml6r.dll) have been shipped within Windows XP SP3 as well as Vista or higher OS. The files have become the system protected files in Windows XP SP3. When MSXML6 msi is trying to install files again, MSI will hit the system protection error with the message like below.


MSI Error: 1931 The Windows Installer service cannot update the system file c:\WINDOWS\system32\msxml6r.dll because the file is protected by Windows.


Actually Windows XP SP3 contains the version of files either higher or equal version to MSXML6 MSI



Files         XP SP3     MSXML6 MSI

========================================

Msxml6.dll     6.20.1076.0 6.10.1200.0

Msxml6r.dll    6.0.3883.0 6.0.3883.0



Usually msi won't install files again. However, MSXML6 has the different resource files msxml6r.dll but all are under the same system directory "system32\msxml6r.dll". When Windows XP is Germany (non-English) and MSXML6 msi is English, msi will try to install English msxml6r.dll from msi package, which triggered the installation action and hit this error.



On the other hand, the error is just a message. MSXML6 on Windows XP SP3 is intact. SQL installation should be not affected neither. You can safely ignore this error.

----------------------------

Thanks,

Max Verun
SQL Server
Posted by Microsoft on 8/19/2008 at 10:41 AM
kjatwork,

Thanks for the report - we are investigating this failure.

-Richard Waymire
Posted by ManServ on 8/14/2008 at 3:20 PM
Also Occurs with SQL Server 2005 and is related to localized XP SP3 systems. See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3748801&SiteID=1&mode=1 for details.
Sign in to post a workaround.
Posted by ManServ on 8/14/2008 at 3:21 PM
Set SFCDisable to 2 in the registry (http://support.microsoft.com/kb/222473 / "%SystemRoot%\System32\REG.exe" ADD "\\%ComputerName%\HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v SFCDisable /t REG_DWORD /d 2 /f).