I am using a custom task to run PowerShell scripts that migrate users to Office 365. After the initial migration is complete, I'm running a second script asynchronously that monitors the progress of the migration then triggers another task when the migration is complete.
The scripts are timing out and getting "the pipline has been stopped" errors after 10 minutes, even though I have modified the timeout setting (Change softerra.adaxes.service.exe.config file and set maxCommandExecutionTimeSec=”900”) as described here: Exchange 2007 move mailbox fails.
Why is this setting not working? Has something changed?
Event log entry:
Softerra.Adaxes.CommandPipeline.CommandProcessingException: The following command threw an exception while being executed: Run PowerShell script 'check status of move' for 'O365Test, T1 (westfarm.com\Darigold Users\Adaxes_Test)'. ---> System.Management.Automation.PipelineStoppedException: The pipeline has been stopped.
at #2i.#1i.#i.#4i.#81(String script, String scriptName)
at #2i.#1i.#i.#4i.#71(String script, String scriptName, ExecuteScriptContextBase context)
at Softerra.Adaxes.Adsi.AdmObject.RunScript(ADM_SCRIPTTYPE_ENUM type, String scriptText, String scriptDescription, String principal, String password, Guid commandId, IAdmAction contextAction)
at Softerra.Adaxes.CommandPipeline.Actions.RunScriptAction.ExecuteAction(IAdmTop targetObject)
at Softerra.Adaxes.CommandPipeline.Actions.ActionBase.Execute(IAdmTop targetObjectArg)
at Softerra.Adaxes.CommandPipeline.Actions.RunScriptAction.Execute(ICommand command)
--- End of inner exception stack trace ---