BUG: Xp_logininfo Returns Error 8198

Article translations Article translations
Article ID: 233161 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 55139 (SQLBUG_70)
Expand all | Collapse all

On This Page

Symptoms

If a Microsoft Windows NT local or global group has the same name as the domain, the computer, or another domain with trusts established, the xp_logininfo extended stored procedure returns error 8198 when it is executed for a Windows NT user of that local or global group.

Workaround

To work around this problem, do either of the following:
  • Change the Windows NT local or global group name.

    -or-
  • Remove the user from that local or global group.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

More information

Steps to Reproduce the Problem

NOTE: This example assumes the following:
  • Domain name = TEST1
  • Local/global group name = test1
  • Windows NT user account name = USER1
  1. Use Windows NT User Manager for Domains to create a new user account with the name "USER1".
  2. Also use User Manager for Domains to create a local or global group that has the same name as the Domain (in this example, "test1").
  3. Add the user you created in step 1 above to this newly-created group.
  4. Execute the following script:
    use master
    go
    
    xp_grantlogin 'TEST1\USER1'
    go
    
    xp_logininfo 'TEST1\USER1'
    go
    					
You will receive the following error message:
Server: Msg 8198, Level 16, State 10, Procedure xp_logininfo, Line 58
Could not obtain information about Windows NT group/user 'test1'.

Properties

Article ID: 233161 - Last Review: January 16, 2015 - Revision: 5.0
Applies to
  • Microsoft SQL Server 7.0 Standard Edition
  • Microsoft SQL Server 2000 Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbpending KB233161

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com