Some Users Not Created w/ ActiveSync Enabled

Question

Here's a strange one for you all. Some of our users are getting created with Activesync enabled, and some are getting created with it disabled. Both creations are done using the exact same process within Adaxes.

Users that DO get Activesync enabled are showing this error in the Operation Execution Log for the "Create Exchange Mailbox" operation:

The cmdlet extension agent with the index 5 has thrown an exception in OnComplete(). 
The exception is: Microsoft.Exchange.Provisioning.ProvisioningException: ScriptingAgent: Exception thrown while invoking scriptlet for OnComplete API: Cannot convert 'System.Object[]' to the type 'Microsoft.Exchange.Configuration.Tasks.MailboxIdParameter' required by parameter 'Identity'. 
Specified method is not supported.. 
---> System.Management.Automation.ParameterBindingException: Cannot convert 'System.Object[]' to the type 'Microsoft.Exchange.Configuration.Tasks.MailboxIdParameter' required by parameter 'Identity'. Specified method is not supported. 
---> System.NotSupportedException: Specified method is not supported.    at System.Management.Automation.ParameterBinderBase.CoerceTypeAsNeeded(CommandParameterInternal argument, String parameterName, Type toType, ParameterCollectionTypeInformation collectionTypeInfo, Object currentValue)    

--- End of inner exception stack trace ---    

at System.Management.Automation.CmdletParameterBinderController.VerifyArgumentsProcessed(ParameterBindingException originalBindingException)    at System.Management.Automation.CmdletParameterBinderController.BindCommandLineParametersNoValidation(Collection`1 arguments)    at System.Management.Automation.CmdletParameterBinderController.BindCommandLineParameters(Collection`1 arguments)    at System.Management.Automation.CommandProcessor.BindCommandLineParameters(CommandParameterInternal[] parameters)    at System.Management.Automation.CommandProcessor.Prepare(CommandParameterInternal[] parameters)    at System.Management.Automation.CommandProcessorBase.DoPrepare(CommandParameterInternal[] parameters)    at System.Management.Automation.Internal.PipelineProcessor.Start(Boolean incomingStream)    at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)    

--- End of inner exception stack trace ---    

at Microsoft.Exchange.ProvisioningAgent.ScriptingAgentHandler.OnComplete(Boolean succeeded, Exception e)    at Microsoft.Exchange.Provisioning.ProvisioningLayer.OnComplete(Task task, Boolean succeeded, Exception exception)

Users that DO NOT get ActiveSync Enabled, show no error at all. I know, its strange that users that work properly get an error.

I think this has to do with a Commandlet Extension Agent that our Exchange Admins have in place, but without fully understanding what commands adaxes is actually using to create a mailbox, I can't build a case to send to our Exchange Admins.

So, how do I find out the exact command(s) that Adaxes is issuing to the exchange servers? We're using the 'out of the box' action "Create an Exchange mailbox" in our business rules.

Any help to point me in the right direction would be greatly appreciated. Thanks in advance!

Comments

Hello,

For this purpose, you can enable tracing of commands sent by Adaxes to your Exchange Server(s). To do this:

1. Open the Softerra.Adaxes.Service.exe.Config file with a text editor. The file is located in the folder where your Adaxes service is installed, which is C:\Program Files\Softerra\Adaxes 3\Service by default.

2. Find the following lines in the file:

    <powerShell ...>
        ...
        <trace enabled="false" outputFilePath="exchange.powershell.trace.txt" />
    </powerShell>
   

3. Set the enabled parameter of the trace XML element to true.

        <trace enabled="true" outputFilePath="exchange.powershell.trace.txt" />
   

4. When tracing is enabled, Adaxes outputs all commands sent to Exchange Servers to a text file located in the folder for Adaxes service. The file name is specified by the outputFilePath parameter. Modify it, if necessary.

5. Save the file.

6. Restart Adaxes service.

   Caution:

   The trace file can grow very fast, which decreases the overall Adaxes performance. For this purpose, it is recommended to enable tracing only when needed. To disable tracing when it becomes unnecessary, set the enabled parameter of the trace XML element back to false.

---

Thanks for the info. We've sent our findings to the Exchange team. I'll post again when I have more info.