BUG: RPC Using SQL_PARAM_OUTPUT and SQL_PARAM_DEFAULT May Cause AVID: Q223257
|
The SQL Server process may experience multiple exceptions, generally access violations (AVs), and/or may stop unexpectedly if the first invocation of a given procedure is an SQL remote procedure call (RPC) event using the SQL_PARAM_OUTPUT and SQL_PARAM_DEFAULT bindings during initial submittal.
A supported fix that corrects this problem is now available from Microsoft, but
it has not been fully regression tested and should be applied only to systems
experiencing this specific problem. If you are not severely affected by this
specific problem, Microsoft recommends that you wait for the next SQL Server service pack
that contains this fix.
To resolve this problem immediately, contact Microsoft Product Support Services
to obtain the fix. For a complete list of Microsoft Product Support Services
phone numbers and information on support costs, please go to the following
address on the World Wide Web:
http://www.microsoft.com/support/supportnet/overview/overview.aspThe English version of this fix should have the following file attributes or later:
Version File name Platform
-------------------------------------
7.00.654 S70654i.exe Intel
7.00.654 S70654a.exe Alpha
Q154871 Determining If You Are Eligible for No-Charge Technical Support
To work around this problem, do either of the following:
create procedure spTest @strData char(80) = "RD"
WITH RECOMPILE
as
begin
select 1
end
Microsoft has confirmed this to be a problem in SQL Server version 7.0.
Additional query words: abnormal termination terminate terminated
Keywords : SSrvGPF kbbug7.00
Version : winnt:7.0
Platform : winnt
Issue type : kbbug
Last Reviewed: July 2, 1999