Search Engine: Elastic

Article ID: 121540, created on May 10, 2014, last review on May 10, 2014

  • Applies to:
  • Operations Automation 5.4
  • Operations Automation 5.3


When trying to move BES users to Exchange 2013 platform through the use of BES Transporter Tool to move the backend BES service and then POA API to add the BES service to the user in the frontend.

Task of the following type failed:

Create BlackBerry account 'username@testdomain.tld' (id=123) 
Last execution output Provisioning request failed. Error in 'BESProvider.addUser'.
BESUserAdmin Error. More than one user found: username@testdomain.tld,THHSTBESFE01,EMAIL_ADDRESS. Error code: -1.
Type: BESProvider.BESAdminException. 

Such tasks are designed to be re-entrant, and therefore if the user exists when Parallels attempts to create them, it should see that it has no work to do and complete successfully matching up the user account with the pre-existing one. This is not happening in this case.


The state of migrated accounts is not fully compatible with POA provisioning engine, MPS provider cannot handle returning error code properly, thus does not treat them as "already created", which causes task failure.


The issue will be fixed in future in scope of the request POA-81047, please contact your Account Manager to track down the status of request.

a8cdca46e4357a6e38fded820770e272 caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e ac82ce33439a9c1feec4ff4f2f638899 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF