This article was previously published under Q243292
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #:56481 (SQLBUG_70)
Creating a table in SQL Enterprise Manager (SEM), where the server is registered using a domain account, may cause a server-side access violation (AV). For the AV to occur the domain account has to be a member of a user-defined local group and the local group has to be granted login permissions to the SQL Server server.Here are a few ways to work around this behavior:
Grant direct SQL Server access to the Windows NT domain account instead of granting access through a local Microsoft Windows NT group.
Create the tables through T-SQL.
Using the original security credentials, where the Windows NT account is a member of a local group, create the very first table through T-SQL instead of through SQL Enterprise Manager. You can create every subsequent table by using the SQL Enterprise Manager.
Use a SQL Server security login.
Add the Windows NT domain account to a local Windows NT built-in group (for example, Administrators).
The access violation occurs if the Windows NT domain account is a member of a local user-defined group. If the local group is a built-in Windows NT group (for example, administrators), the access violation does not occur. The problem may also be avoided if the very first table creation is done using T-SQL instead of the Enterprise Manager Graphical interface.
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
Client workstations that register the SQL Server in the SQL Enterprise Manager must have Service Pack 2 (SP2) applied. A client with a version of SQL Enterprise Manager earlier than SP2 will still encounter a problem creating a table, even though SP2 has been applied to the server. The error that SQL Enterprise Manager might encounter is the following:
- Unable to create table. ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor state