FIX: SQL Server Setup may fail if you select Per Processor licensing mode (273769)

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this fix should have the following file attributes or later:

   Version      File name       Platform
   -------------------------------------

   8.00.201     s80201i.exe     Intel
				

NOTE: Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.

A fix for this problem was originally released on 09/01/2000. You may encounter a problem with that version of this fix when using the Rebuildm.exe utility to rebuild the master database. If you applied the fix from 09/01/2000, Rebuildm.exe may fail with the following error: This is because the fix changed the version number to 8.00.201 in the following registry key: If you have already applied this fix and are encountering this problem with Rebuildm.exe, simply change the value of the above registry key back to 8.00.194. The problem for which the fix was created is still corrected and is not affected by this registry change.

For customers who have not applied this fix, a new release of the fix is available as of 02/18/2001 which does not change the version in the registry key.