Broker:Forwarded Message Dropped Event Class

Broker:Forwarded Message Dropped Event Class

 

Applies To: SQL Server 2016

SQL Server generates a Broker:Forwarded Message Dropped event when Service Broker drops a message that was intended to be forwarded.

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
BigintData1bigintMessage sequence number.52No
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 databasestatement has been issued for a given instance. SQL Server Profiler displays the name of the database if the Server Name 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
DatabaseNamenvarcharThe name of the database in which the user statement is running.35Yes
DBUserNamenvarcharThe broker instance identifier that this message is from.40No
ErrorintThe message id number in sys.messages for the text in the event.31No
EventClassintThe type of event class captured. Always 191 for Broker:Forwarded Message Dropped.27No
EventSequenceintSequence number for this event.51No
FileNamenvarcharThe name of the service that the message is to.36No
GUIDuniqueidentifierThe conversation id of the dialog. This identifier is transmitted as part of the message, and is shared between both sides of the conversation.54No
HostNamenvarcharThe 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
IndexIDintThe number of hops remaining for the forwarded message.24No
IntegerDataintThe fragment number of the forwarded message.25No
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
ObjectIdintThe time to live value of the forwarded message.22No
ObjectNamenvarcharMessage ID of the forwarded message.34No
OwnerNamenvarcharThe broker instance identifier for the destination of the message.37No
RoleNamenvarcharThe role of the conversation handle. One of:

-Initiator. This broker initiated the conversation.

-Target. This broker is the target of the conversation.
38No
ServerNamenvarcharThe name of the instance of SQL Server being traced.26No
SeverityintSeverity number for the text in the event.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
SuccessintThe amount of time that the message has been alive. When this value is greater than or equal to the time to live, the message is dropped.23No
TargetLoginNamenvarcharThe network address that the message would have been forwarded to.42No
TargetUserNamenvarcharThe name of the initiating service for the message.39No
TextDatantextDescription of the reason that SQL Server dropped the message.1Yes
Transaction IDbigintThe system-assigned ID of the transaction.4No

The TextData column of this event contains a description of the reason that SQL Server dropped the message.

SQL Server Service Broker

Community Additions

ADD
Show:
© 2016 Microsoft