Microsoft exchange 2010 the remote pipeline has been stopped

The disk had MB's of free disk space, which you would think would be enough as transaction logs are only 1MB in size each. This resolved the Available disk space for the database logs is extremely low. Message delivery to the database may be stopped error. The Send connector that services the domain has the local transport server configured as source server, and the Send connector is configured to use DNS routing. This value is the destination address space that's configured on the Send connector.

For example, contoso. This value is reserved for internal Microsoft use. For more information about heartbeat, see Shadow redundancy in Exchange Server. Note : This value isn't used by Exchange or later. The queue holds messages for delivery to recipients in a non-SMTP address space that's serviced by a Foreign connector. This value is the destination address space that's configured on the Foreign connector. The queue holds messages in a shadow queue.

This value is the FQDN of the primary transport server for which the shadow queue is holding redundant copies of the primary messages. This value is the list of smart hosts that are configured on the Send connector. The queue holds messages for delivery to Exchange or later mailbox recipients. This value is the name of the destination mailbox database.

This value is the name of the destination Send connector, Delivery Agent connector, or Foreign connector. The queue holds messages for delivery to Exchange or later mailbox recipients, where the destination mailbox database is located in a remote DAG. The queue holds messages for delivery to legacy mailbox recipients, where the destination mailbox is on an Exchange Mailbox server.

The queue holds messages for delivery to a remote destination, and the routing topology requires the message to be routed through a specific Active Directory site. This value is the target Active Directory site name.

The queue holds messages for delivery to a distribution group that's configured for a specific expansion server. This value is the FQDN of the target expansion server.

The queue holds messages for delivery to an external SMTP domain that's serviced by a Send connector that's configured on an Edge Transport server. This value is the name of the Send connector that sends outbound Internet mail from the Edge Transport server to the Internet. For the Submission queue, this value is Submisssion.

The rate that messages are entering the queue. The rate is the number of messages per second averaged over the last minute. The rate that messages are leaving the queue. The drain rate of the queue, calculated by subtracting the value of IncomingRate from the value of OutgoingRate. The last automatic or manual connection attempt failed, and the queue is waiting to retry the connection.

The queue has been manually suspended by an administrator to prevent message delivery. New messages can enter the queue, and messages that are in the act of being transmitted to the next hop will finish delivery and leave the queue. Otherwise, messages won't leave the queue until the queue is manually resumed by an administrator.

If the message is in a delivery queue, the message is being delivered to its destination. If the message is in the Submission queue, the message is being processed by the categorizer. This value is reserved for internal Microsoft use, and isn't used in on-premises Exchange organizations.

The message was deleted by the administrator, but the message was already in the act of being transmitted to the next hop. The message will be deleted if the delivery ends in an error that causes the message to reenter the queue. Otherwise, delivery will continue. The message was suspended by the administrator, but the message was already in the act of being transmitted to the next hop. The message will be suspended if the delivery ends in an error that causes the message to reenter the queue.

The last automatic or manual connection attempt fail for the queue that holds the message. The message is waiting for the next automatic queue connection retry. The message was manually suspended by an administrator. Displays one or more queues on a transport server. You can use the results to take action on the queues.

Procedures for queues. Temporarily prevent delivery of messages that are currently in the queue. The queue continues to accept new messages, but no messages leave the queue. Reverses the effect of the suspend queue action, and enables delivery of queued messages to resume.

Immediately tries to connect to the next hop. Without manual intervention, when the connection to the next hop fails, the connection is attempted a specific number of times after a specific time interval between each attempt. Whether the connection attempt is manual or automatic, any connection attempt resets the next retry time. For more information, see Message retry, resubmit, and expiration intervals.

Causes messages in the queue to be resubmitted to the Submission queue and to go back through the categorization process. Retry-Queue with the Resubmit parameter Note that you can use Queue Viewer to resubmit messages, but only from the poison message queue. To resubmit a poison message, you first need to resume the message in Queue Viewer, or by using the Resume-Message cmdlet.

Temporarily prevents delivery of a message. You can use the suspend message action to prevent delivery of a message to all the recipients in a specific queue or to all recipients in all queues.

Procedures for messages in queues. Reverses the effect of the suspend message action, and enables the delivery of queued messages to resume. You can resume the delivery of a message to all recipients in a specific queue, or to all recipients in all queues.

Permanently prevents the delivery of a message. You can prevent the delivery of a message to any recipients in a specific queue, or to all recipients in all queues. Optionally, you can send a non-delivery report also known as an NDR, delivery status notification, DSN or bounce message to the sender when the message is removed. Copies a message to the location that you specify.

The messages aren't deleted from the queue, but a copy of the message is saved as a file in the specified location. This enables administrators or officials in an organization to later examine the messages. Before you export a message, you need to temporarily suspend the message. Export messages from queues.

Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Sign in to vote. Hello, Our Exchange server message queue keeps reporting the following error The remote pipeline has been stopped. Friday, May 6, AM. That means there are dns issues in the server. Marked as answer by Niko. Cheng Thursday, June 2, AM. Saturday, May 7, AM.

I exteneded it just in case. Restart Information store process. Its the transport service that is responsible for this and not the store. If the store goes down you cant view email in say outlook.

In the cue viewer usually all the way to the right you will see the last error code for the tried send.

What does that say? It also might be as simple as deleting the cues to flush them out and everything will start to work again. Might have been the log drive extension or the restarting of Information Store process.

I want to personally thank everyone that helped in this situation. And appreciated all users input. And want to thank Spiceworks in general for having this wonderful tool and a great community!!! Glad you got it sorted. I would recommend you have a good look around and find out what the problem was though just in case it happens again. If your log files are growing you need to check your backups as well.