Broker:Corrupted Message Event Class


Applies To: SQL Server 2016

SQL Server creates a Broker:Corrupted Message event when Service Broker receives a corrupted message.

Data columnTypeDescriptionColumn numberFilterable
ApplicationNamenvarcharThe name of the client application that created the connection to an instance of SQL Server. This column is populated with the values passed by the application rather than the displayed name of the program.10Yes
BigintData1bigintThe sequence number of this message.52No
BinaryDataimageThe message body of the message.2Yes
ClientProcessIDintThe ID assigned by the host computer to the process where the client application is running. This data column is populated if the client process ID is provided by the client.9Yes
DatabaseIDintThe ID of the database specified by the USE database statement, or the ID of the default database if no USE database statement has been issued for a given instance. SQL Server Profiler displays the name of the database if the ServerName data column is captured in the trace and the server is available. Determine the value for a database by using the DB_ID function.3Yes
ErrorintThe message id number in sys.messages for the text in the event.31No
EventClassintThe type of event class captured. Always 161 for Broker:Corrupted Message.27No
EventSequenceintSequence number for this event.51No
FileNamenvarcharThe network address of the remote endpoint.36No
GUIDuniqueidentifierThe conversation ID of the conversation that the corrupted message belongs to. This identifier is transmitted as part of the message, and is shared between both sides of the conversation.54No
Host NamenvarcharThe name of the computer on which the client is running. This data column is populated if the host name is provided by the client. To determine the host name, use the HOST_NAME function.8Yes
IntegerDataintThe fragment number of this message.25Yes
IsSystemintIndicates whether the event occurred on a system process or a user process. 1 = system, 0 = user.60No
LoginSidimageThe security identification number (SID) of the logged-in user. Each SID is unique for each login in the server.41Yes
NTDomainNamenvarcharThe Windows domain to which the user belongs.7Yes
NTUserNamenvarcharThe name of the user that owns the connection that generated this event.6Yes
ObjectNamenvarcharThe service name of the other side of the conversation and the connection string that the remote database used to connect to this database.34No
RoleNamenvarcharThe role of the endpoint receiving this message. One of the following values.

 initiator: The receiving endpoint is the initiator of the conversation.

 target: The receiving endpoint is the target of the conversation.
ServerNamenvarcharThe name of the instance of SQL Server being traced.26No
SeverityintIf an error caused SQL Server to drop the message, the severity of the error.29No
SPIDintThe server process ID assigned by SQL Server to the process associated with the client.12Yes
StartTimedatetimeThe time at which the event started, when available.14Yes
StateintIndicates the location within the SQL Server source code that produced the event. Each location that may produce this event has a different state code. A Microsoft support engineer can use this state code to find where the event was produced.30No
TextDatantextDescription of the corruption detected.1Yes
Transaction IDbigintThe system-assigned ID of the transaction.4No

The TextData column of this event contains a message that describes the problem with the message.

Community Additions