Export (0) Print
Expand All
Expand Minimize

DeliveryFailure Enumeration

Specifies the possible types of delivery failure for a message read from the queue.

Namespace:  System.ServiceModel.Channels
Assembly:  System.ServiceModel (in System.ServiceModel.dll)

type DeliveryFailure

Member nameDescription
AccessDeniedThe sender does not have access rights to place messages in the destination queue.
BadDestinationQueueThe destination queue was not found.
BadEncryptionThe destination queue manager cannot decrypt the message.
BadSignatureThe destination queue manager cannot authenticate the message because the attached signature is invalid.
CouldNotEncryptThe source queue manager cannot encrypt the message.
HopCountExceededThe message hop count was exceeded, which indicates the number of intermediate servers.
NotTransactionalMessageA nontransactional message was sent to a transactional queue.
NotTransactionalQueueA transactional message was sent to a nontransactional queue.
PurgedThe message was purged before reaching the destination queue.
QueueDeletedThe destination queue was deleted before the message could be delivered to the application.
QueueExceedMaximumSizeThe message was not delivered because the destination queue is full.
QueuePurgedThe queue was purged and the message no longer exists.
ReachQueueTimeoutThe message did not reach the destination queue before timing out.
ReceiveTimeoutThe message was not delivered to the application on time.
UnknownAn unknown error occurred.

You can get the DeliveryFailure property to determine why a message failed delivery and was sent to the dead-letter queue. For additional information about message processing in a dead-letter queue, see Using Dead-Letter Queues to Handle Message Transfer Failures.

The example below shows how to access the DeliveryFailure of a message within a service operation.

No code example is currently available or this language may not be supported.

.NET Framework

Supported in: 4.5.2, 4.5.1, 4.5, 4, 3.5, 3.0

.NET Framework Client Profile

Supported in: 4, 3.5 SP1

Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)

The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.

Show:
© 2014 Microsoft