-
标题
Inaccurate error message from Quick Connect Provisioning to Office 365 -
说明
Quick Connect reports an error when creating users but it has actually succeeded to create the user.
Error --> The operation couldn't be performed because object 'c25bc468-c67a-4d39-be8d-c96b1914a596' couldn't be found on 'Office365.myserver.prod.outlook.com'. Quest.QuickConnect.Connectors.Office365Connector.PowerShellRunspace.Execute 2013-12-02 15:23:43.8027 18 Error --> Outgoing exception Quest.QuickConnect.ServerCommon.ErrorHandling.SimpleErrorHandler.HandleError System.ApplicationException: Cannot perform the requested operation, because an Office 365 cmdlet has returned the following error: The operation couldn't be performed because object 'c25bc468-c67a-4d39-be8d-c96b1914a596' couldn't be found on 'DB3PR02A001DC06.EURPR02A001.prod.outlook.com'. at Quest.QuickConnect.Server.MainWCFService.RunWorkflowStepWithObject(Guid workflowId, Guid workflowStepId, SystemEntry sourceObject) at SyncInvokeRunWorkflowStepWithObject(Object , Object[] , Object[] ) at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs) at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc) at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
-
原因
This occurs when user object provisioning rules contain one of the following attributes:
- AllowUMCallsFromNonUsers
- AssistantName
- Company
- CountryOrRegion
- HomePhone
- Initials
- Manager
- Name
- Notes
- OtherFax
- OtherHomePhone
- OtherTelephone
- Pager
- Phone
- PhoneticDisplayName
- PostOfficeBox
- RemotePowerShellEnabled
- ResetPasswordOnNextLogon
- SimpleDisplayName
- StateOrProvince
- UMDtmfMap
- WebPage
- WindowsEmailAddress
-
解决办法
Create a Provision step with minimal attributes to create the account such as User Principal Name and assign a Password. Then create an Update step with the rest of the attributes necessary for the account.