BUG: AV in SEM Managing Logins Using Trusted Connections

• Microsoft SQL Server version 6.0

SYMPTOMS

If user who is not a member of the Administrators group or acting as SA connects to SQL Server version 6.0 using SQL Enterprise Manager (SEM) across a trusted connection, then expands the logins tree and selects themself from the list, an unhandled exception will be raised once they double-click their login ID. The error that is returned reads:

An application error has occurred and an application error log is being generated, SQLEW.exe exception access violation (0xc0000005) address 0x77ea3243.

WORKAROUND

Log in to Windows NT as a member of the local Administrators group, which inherits SA privileges under trusted connections, or login as a user who is mapped to the SA login. You could also register the server using standard security.

STATUS

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

MORE INFORMATION

In Chapter 9, Managing Security, of the SQL Server "Administrator's Companion," there is an section called Managing SQL Server Logins that states that only a system administrator (SA) can manage logins. If the server is registered using trusted connections, SQL server uses Windows NT to validate logins. A user who is not part of the local Administrators group in Windows NT or who is not mapped to the SA login does not have SA privileges if the server is registered using trusted connections. If that user logs on to Windows NT, then opens SQL Enterprise Manager and edits their own login ID or a group login of which they are a member, an unhandled exception will be encountered.

Additional query words: sql6 editing logins unhandled exception access violation winnt
integrated standard

Keywords          : kbinterop kbnetwork SSrvLAN kbbug6.00 
Version           : 6.0
Platform          : WINDOWS 
Issue type        : 

Last Reviewed: March 23, 1999