BUG: Security Manager May Incorrectly Identify Orphans

• Microsoft SQL Server, version 4.2

SYMPTOMS

When searching for the 'Orphan SQL Login IDs', Security Manager displays the SQL Server login IDs which are not orphans after correctly checking for about 150 IDs. After this happens, Security Manager will not recognize any of the NT domain accounts on the SQL Server. You have to restart SQL Server in order to view the correct account information using the Security Manager.

For example:

There are 170 domain users on domain TEST and are granted user privilege to the SQL Server running on the Windows NT Advanced Server (NTAS). There are 180 login IDs on SQL Server, of which 10 are orphans. When you use the Security Manager to search for the orphans, it should display these 10 logins. However, it displays 60 logins, 50 of them are not orphans.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 4.2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.