Exchange – Pipeline not executed because a pipeline is already executing

Exchange Error: Pipeline not executed because a pipeline is already executing. Pipelines cannot be executed concurrently.

This error is caused because the Windows PowerShell remoting feature doesn’t
support more than one pipeline running at the same time. To resolve this
issue, store the output of the cmdlet earlier in the pipeline in a variable,
and then pipe the data stored in the variable to the ForEach cmdlet.

To resolve the error, store the output of the Get-Mailbox cmdlet in a
variable, and then pipe the variable to the ForEach cmdlet, as shown in this
example.

$Mailboxes = Get-Mailbox
$Mailboxes | ForEach { Set-Mailbox -ProhibitSendReceiveQuota 3GB }

or

$GM = Get-Mailbox
$GM | ForEach-Object {remove-MailboxFolderPermission $_”:\Calendar” -User alice.cooper} 

Last example removes alice.cooper’s permissions to see the shared calendars within the company/domain.

 

 

 

This entry was posted in Exchange. Bookmark the permalink.

3 Responses to Exchange – Pipeline not executed because a pipeline is already executing

  1. Martijn says:

    Thanks! This solution works for me.

  2. Kris says:

    It’s hard to find your blog in google. I found it on 14 spot, you should build quality backlinks , it will help you to increase traffic.

    • admin says:

      Kris,

      Thank you for your suggestion.
      I started this blog for my use only as I often do things at work that I keep forgeting after a while. Having some of them written in one place makes my life easier.
      I am not interested in getting a better position in Google searches.( not for now at least )
      If other people get here and find some of my posts useful, I’m happy that I could help.

      Regards,
      C.D.

Leave a Reply

Your email address will not be published. Required fields are marked *