You enable the Scripting Agent cmdlet extension agent in a Microsoft Exchange Server 2010 environment.
A script is configured to contain an OnComplete handler.
You add the script to a configuration file.
You run a cmdlet to process multiple objects in a pipeline by using the Exchange Management Shell.
In this scenario, the cmdlet extension agent fails after it processes the first object. Additionally, you receive the following error message in the shell:
WARNING: The cmdlet extension agent with the index Number has thrown an exception in OnComplete(). The exception is: System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Exchange.Configuration.MonadDataProvider.MonadCommand.set_CommandType(CommandType value) at Microsoft.Exchange.ProvisioningAgent.ScriptingAgentHandler.OnComplete(Boolean succeeded, Exception e) at Microsoft.Exchange.Provisioning.ProvisioningLayer.OnComplete(Task task, Boolean succeeded, Exception exception)
This issue occurs because the OnComplete handler incorrectly sets the powershell connection to null before all commands in the pipeline are processed. This causes an access violation when subsequent commands in the pipeline are executed.
To resolve this issue, install the following update rollup:
2645995 Description of Update Rollup 1 for Exchange Server 2010 Service Pack 2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about cmdlet extension agents, visit the following Microsoft website: