I am working on converting over to the latest 4.0.2 Windows Scripting
driver (using the scripting service) from the earlier 3.6.1 driver. I
am running into an issue where if Exchange slows down a bit on
provisioning or some other cmdlets that I get the following:

7/21/2014 09:00:19 System.Threading.ThreadAbortException: Thread was
being aborted.
at System.Threading.WaitHandle.WaitOneNative(SafeHand le
waitableSafeHandle, UInt32 millisecondsTimeout, Boolean
hasThreadAffinity, Boolean exitContext)
at System.Threading.WaitHandle.InternalWaitOne(SafeHa ndle
waitableSafeHandle, Int64 millisecondsTimeout, Boolean
hasThreadAffinity, Boolean exitContext)
at
System.Management.Automation.Runspaces.PipelineBas e.Invoke(IEnumerable
input)
at System.Management.Automation.RunspaceInvoke.Invoke (String script,
IEnumerable input, IList& errors)
at
Novell.IDM.WSD.ScriptService.ScriptServiceServer.E xecuteScript(String
sScriptPath, String sArg0, String sArg1, String sArg2, String sArg3,
String sArg4, String sArg5, String sArg6, String sArg7, String sArg8,
String sArg9)


After which, it doesn't ever really recover and get endless exceptions
like:

7/21/2014 09:00:25
System.Management.Automation.PSInvalidOperationExc eption: Pipeline not
run because a pipeline is already running. Pipelines cannot be run
concurrently.
at
System.Management.Automation.Runspaces.PipelineBas e.DoConcurrentCheck(Boolean
syncCall, Object syncObject, Boolean isInLock)
at
System.Management.Automation.Runspaces.RunspaceBas e.DoConcurrentCheckAndAddToRunningPipelines(Pipeli neBase
pipeline, Boolean syncCall)
at
System.Management.Automation.Runspaces.PipelineBas e.CoreInvoke(IEnumerable
input, Boolean syncCall)
at
System.Management.Automation.Runspaces.PipelineBas e.Invoke(IEnumerable
input)
at System.Management.Automation.RunspaceInvoke.Invoke (String script,
IEnumerable input, IList& errors)
at
Novell.IDM.WSD.ScriptService.ScriptServiceServer.E xecuteScript(String
sScriptPath, String sArg0, String sArg1, String sArg2, String sArg3,
String sArg4, String sArg5, String sArg6, String sArg7, String sArg8,
String sArg9)


I have extended the script timeout, but this doesn't seem like a
graceful way of handling this.


--
schwoerb
------------------------------------------------------------------------
schwoerb's Profile: https://forums.netiq.com/member.php?userid=2338
View this thread: https://forums.netiq.com/showthread.php?t=51377