This article was previously published under Q314128
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 356323 (SHILOH_BUGS)
In SQL Server 2000 Service Pack 2 (SP2), when you run a SQL Profiler trace that includes RPC events (RPC:Starting or RPC:Completed), a statement that includes a bit parameter that has a value that is greater than 9 causes an access violation in CNetInputBuffer::Init.
In SQL Server 2000 Service Pack 1 (SP1), the trace is truncated, and you receive an error message in SQL Profiler, but no access violation occurs in SQL Server. The data type of the table column is irrelevant; only the data type of the parameter is relevant to this problem.
NOTE: The table column may be another type other than bit.
SQL Server 2000 SP2 (8.00.534) generates the following stack dump:
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack
NOTE: The following hotfix was created before the release of Microsoft SQL Server 2000 Service Pack 3.
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Version Size File name ------------------------------------------------ 12-DEC-2001 8.00.552 7,442,513 Sqlservr.exe
NOTE: Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.
To reproduce the access violation, run a SQL Profiler trace that includes at least one of the RPC events (RPC:Starting or RPC:Completed), and then run the following C code: