/
Steve
-Original Message-
From: Joseph L. Casale [mailto:jcas...@activenetwerx.com]
Sent: 06 July 2012 03:50
To: MS-Exchange Admin Issues
Subject: RE: Live@EDU exception handling
Should be in $_.Exception.CategoryInfo.Reason or
$_.Exception.SerializedRemoteException.CategoryInfo.Reason
I am trying to catch and account for various exceptions in some automation.
It seems with New-Mailbox I am not able to catch a specific exception related to
an existing user (already exists).
Is my only resolve to matching on the error text returned?
Thanks!
jlc
---
To manage subscriptions
You probably want to catch a generic outer exception and then examine the
InnerException.
-Original Message-
From: Joseph L. Casale [mailto:jcas...@activenetwerx.com]
Sent: Thursday, July 05, 2012 6:49 PM
To: MS-Exchange Admin Issues
Subject: Live@EDU exception handling
I am trying
You probably want to catch a generic outer exception and then examine the
InnerException.
Hrm, looks like that cmdlet left it unpopulated? It was empty when accessing
it...
PS C:\ $error[0]
Windows Live ID xxx@xxx already exists as a managed Windows Live ID. To use
the existing Windows Live
??
Right here: WLCDManagedMemberExistsException.
-Original Message-
From: Joseph L. Casale [mailto:jcas...@activenetwerx.com]
Sent: Thursday, July 05, 2012 8:26 PM
To: MS-Exchange Admin Issues
Subject: RE: Live@EDU exception handling
You probably want to catch a generic outer exception
??
Right here: WLCDManagedMemberExistsException.
Must be a caveat of the remoting?
$_.Exception |fl * -Force
SerializedRemoteException :
Microsoft.Exchange.Management.Tasks.WLCDManagedMemberExistsException: Windows
Live ID xxx@xxx already exists as a managed Windows Live ID. To use the
Should be in $_.Exception.CategoryInfo.Reason or
$_.Exception.SerializedRemoteException.CategoryInfo.Reason
-Original Message-
From: Joseph L. Casale [mailto:jcas...@activenetwerx.com]
Sent: Thursday, July 05, 2012 9:21 PM
To: MS-Exchange Admin Issues
Subject: RE: Live@EDU exception
Should be in $_.Exception.CategoryInfo.Reason or
$_.Exception.SerializedRemoteException.CategoryInfo.Reason
Ugh, both of those were empty, but I did find it in
$_.Exception.ErrorRecord.CategoryInfo.Reason
which allowed me to remove the crappy regex.
Thanks!
jlc
---
To manage subscriptions
