BUG: SQL Server 7.0 Uninstall Does Not Remove Licensing Information (277842)



The information in this article applies to:

  • Microsoft SQL Server 7.0

This article was previously published under Q277842
BUG #: 55653 (SQLBUG_70)
BUG #: 52689 (SQLBUG_70)

SYMPTOMS

If you uninstall SQL Server 7.0 by using the Add/Remove Programs applet in Control Panel or by using the Uninstall icon inside the SQL Server 7.0 program group, the uninstall completes successfully. However, the entry for SQL Server 7.0 remains in the Windows NT License Manager, including the number of SQL Server licenses previously on the computer.

If you attempt to perform an unattended installation after SQL Server 7.0 has been removed, the installation succeeds but the unattended installation is not able to change the Licensing Mode from Per Server to Per Seat or to add additional Per Server concurrent connection licenses.

For example, the first installation of SQL Server 7.0 had a Licensing Mode of Per Server with 5 concurrent connections. SQL Server 7.0 was then uninstalled. Later, an unattended installation was performed on the same computer and the Licensing Mode specified in the .iss file was PERSEAT. However, after the unattended installation completes, the Licensing Mode in the License Manager still shows as Per Server with 5 concurrent connections.

This problem does not occur on a manual installation using the setup from the GUI. During installation, the GUI setup calls the Windows NT License Manager applet and allows the user to manually edit the information in the licensing screens.

WORKAROUND

You can use any of the following workarounds:
  • If SQL Server has already been installed and you need to change the licensing from Per Server to Per Seat or you need to add additional concurrent connection licenses, you can edit the license information by using the Control Panel Licensing applet.

    -or-

  • Use the GUI SQL Server 7.0 setup and specify the changes needed in the Licensing screens.

    -or-

  • If the License Mode you have purchased for the installation is Per Server and the previous installation was Per Seat, because the SQL Server Licensing does not allow you to change the mode from Per Seat to Per Server, continue to use the Per Seat Licensing Mode.

STATUS


Microsoft has confirmed this to be a problem in SQL Server 7.0.

Modification Type:MajorLast Reviewed:10/16/2002
Keywords:kbBug kbDSupport KB277842