This article discusses a Beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.
No formal product support is available from Microsoft for this Beta product. For information about how to obtain support for a Beta release, see the documentation that is included with the Beta product files, or check the Web location where you downloaded the release.
Consider the following scenario on a computer that is running Windows Vista Release Candidate 1 (RC1):
User Account Control (UAC) is enabled.
You install the original release version of SQL Native Client (SNAC). To do this, you directly run the Sqlncli.msi file. The installation is successfully completed.
Note To directly run the Sqlncli.msi file, you install SQL Native Client by double-clicking the Sqlncli.msi file or by running the following command:
msiexec /I Path_of_MSIFile
You upgrade SNAC to Microsoft SQL Server 2005 Service Pack 1 (SP1).
In this scenario, the list of product codes that depend on SNAC may be lost after you upgrade to SQL Server 2005 SP1. This issue occurs if one of the following conditions is true:
You upgrade SQL Server 2005 to a different language version.
You download the Service Pack 1 version of SNAC from the Microsoft Web site. Then, you directly run the setup file.
After you upgrade to SQL Server 2005 SP1, the following error messages may be logged in the setup log file:
Action start 15:07:06: Sqlmsirc_BackupAppGuid.0D10D66A_FB58_4290_B8AC_58FF44A6C1F1. <Func Name='Sqlmsirc_BackupAppGuid'> Failed to query registry value (SOFTWARE\Microsoft\SNAC\MSIRefCount\Uninstall) Error: Access is denied. Failed to set registry value (SOFTWARE\Microsoft\SNAC\MSIRefCount\Uninstall) Error: Access is denied. Failed to query Uninstall value from registry. <EndFunc Name='Sqlmsirc_BackupAppGuid' Return='1603' GetLastError='0'>
If the list of product codes that depend on SNAC is lost, you will not receive a warning message when you uninstall SNAC. However, other SQL Server components may not function correctly after you uninstall SNAC.
This issue occurs because the setup file is not run under an account that has required permissions. Therefore, custom actions may not execute during the installation. This issue does not occur when you install SNAC by running the SQL Server 2005 Setup program. When you run the SQL Server 2005 Setup program, the SNAC setup operation is started from the Setup.exe process. The Setup.exe process runs under elevated permissions. Therefore, the custom actions will run under the Administrator account.
To work around this issue, install SNAC by running the SQL Server 2005 Setup program.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.