BUG: Executing Two or More xp_logevents Causes Server Hang

ID: Q152106

The information in this article applies to:

Microsoft SQL Server versions 4.2x, 6.0, 6.5

BUG# WINDOWS: 1795 (4.21a) (sqlserver)

SYMPTOMS

If a stored procedure or trigger executes two or more xp_logevents, the server prevents new connections from being granted. This is sometimes accompanied by the following message:

Extended procedure memory allocation failed for 'xp_logevent'.

WORKAROUND

"Wrap" the extended stored procedure call in a stored procedure.


create procedure spLogEvent (@iErrorNo int,
@strMessage varchar(255),
@strLevel varchar(255))
as
begin
exec master..xp_logevent @iErrorNo, @strMessage, @strLevel
end

STATUS

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

This problem does not occur in SQL Server 6.0.

Additional query words: xp_logevent


Keywords          : kbbug4.21a 
Version           : 4.21a, 4.21 SP1, 4.21 SP2, 4.21
Platform          : WINDOWS 
Issue type        :

Last Reviewed: March 26, 1999