Exchange Powershell script gives dr Watson

Question

Hi,
When running a powershell (scheduled) through a batchfile I get a dr. Watson error:
WARNING: An unexpected error has occurred and a Watson dump is being generated:
 Operation is not valid due to the current state of the object.
Get-ActiveSyncDeviceStatistics : Operation is not valid due to the current
state of the object.
At D:\Scripts\ActiveSyncExport.ps1:34 char:27
+ $Devices = $Mailboxes | %{Get-ActiveSyncDeviceStatistics -Mailbox
$_.Identity} | ...
+                           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Get-ActiveSyncDeviceStatistic
   s], InvalidOperationException
    + FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.Excha
   nge.Management.Tasks.GetMobileDeviceStatistics
But when I run this script from the Exchange Management Shell manually it works normally.
I tried this in the script, but that doesn't work either:
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri
http://casserver.ourdomain.com/PowerShell/ -Authentication Kerberos
Import-PSSession $Session
The servers are running Exchange 2010 SP3 with rollup 2.
It looks like a sort of buffer overflow error.
Does anybody know a solution?

Answer 1

Hi Guys,
this is probably due to the usual serialization / deserialization issue. Try importing the commands with
this function script.
Another note - try to avoid using Exchange Cmdlets in combination with ForEach-Object uses - go straight through the pipeline instead:
$mb = Get-Mailbox | Where { "Whatever Condition you need to apply" } | Select -ExpandProperty Identity | %{ $_.ToString() }
Get-ActiveSyncDevice | Where { $mbl -contains $_.UserDisplayName } | Get-ActiveSyncDeviceStatistics
Otherwise you'll exceed session limits, whether on the server or not.
Cheers,
Fred
There's no place like 127.0.0.1