"Cannot process argument transformation" error for cmdlets in Exchange Server 2013 with CU11

Applies to: Exchange Server 2013 EnterpriseExchange Server 2013 Standard Edition

Symptoms


When you use various cmdlets, scripts such as RedistributeActiveDatabases.ps1, or the Queue Viewer from the Exchange Toolbox in an Exchange Server 2013 environment that has Cumulative Update 11 installed, you receive one of the following error messages:

Cannot process argument transformation on parameter 'BookmarkObject'. Cannot convert the "Microsoft.Exchange.Data.QueueViewer.PropertyBagBasedQueueInfo" value of type "System.String" to type "Microsoft.Exchange.Data.QueueViewer.ExtensibleQueueInfo".

Cannot process argument transformation on parameter 'Identity'. Cannot convert value "<database name>" to type "Microsoft.Exchange.Configuration.Tasks.DatabaseCopyIdParameter". Error: "Cannot convert hashtable to an object of the following type: Microsoft.Exchange.Configuration.Tasks.DatabaseCopyIdParameter. Hashtable-to-Object conversion is not supported in restricted language mode or a Data section."

Additionally, when you use from Exchange Management Shell to run the Get-Queue cmdlet, the cmdlet may not automatically pull back the queue for the local server that the cmdlet is running on. However, when you run the Get-Queue -Server "Server Name" cmdlet, it works as expected.

Cause


This issue occurs if you don't have a mailbox associated with your account, or if the mailbox or arbitration mailboxes are hosted on an earlier version of Exchange Server. For more information about the changes to anchor mailbox functionality, see Exchange Management Shell and Mailbox Anchoring.

Workaround


To work around this issue, use one of the following methods:
  • Associate a mailbox with the account that's trying to use the Queue Viewer on an Exchange server, and the version of the Exchange server is the same as the one that you're trying to manage.
  • Move the arbitration mailbox to the version of Exchange that you're trying to manage.
Note This issue will be fixed in Cumulative Update 12 for Exchange Server 2013.

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.