Microsoft KB Archive/152106

= BUG: Executing Two or More xp_logevents Causes Server Hang =

Article ID: 152106

Article Last Modified on 11/14/2003

-

APPLIES TO


 * Microsoft SQL Server 4.21a Standard Edition
 * Microsoft SQL Server 6.0 Standard Edition
 * Microsoft SQL Server 6.5 Standard Edition

-



This article was previously published under Q152106



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: KB152106

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.