Search Engine: Elastic

Article ID: 3550, created on Jan 8, 2008, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation 5.4
  • Business Automation


A staff member (user) of a customer account exists in the Parallels Business Automation (PBA) Control Panel, but there is no such staff member in the account in Parallels Operations Automation (POA). As a result, it is not possible to log into the Customer Control Panel (CCP) as this user.


For POA version 5.4:

The problem is most commonly caused by a lack of the 'Additional Staff Members' resource in customer subscriptions in POA when the new staff member (user) is created in PBA.

In this situation, a new user is created in PBA (since PBA does not limit the number of users in customer accounts), but it is not created in POA due to a lack of the required resource.

The 'Additional Staff Members' resource limits the number of staff members a customer may create in their account in POA.

For POA version 5.5:

The 'Additional Staff Members' resource has been removed since POA version 5.5.

Another possible cause of the issue is when a user with the same login already exists in POA. This can be verified in the POA System > Users, search by Login Name (login names are case-insensitive in POA).


For POA version 5.4:

First, make sure the customer has available units of the 'Additional Staff Members' resource in any existing subscription in POA.

As soon as the correct resource is available, you can resubmit the user creation:

  • Go to PBA Home > Configuration Director > Event Manager > Event Log
  • Find the failed 'User Created' event with the ID of the problem user in the Parameters field, as shown in the screenshot below:

Your text to link here...

  • Click on the failed event and resubmit it. It should process successfully

Alternatively, you can use the following API XML RPC request to force PBA to add a staff member in an account in POA. The command should be executed on the PBA Application Server:

# curl --connect-timeout 10 -d@addAccountMemberToPEM.xml -H'Content-type: text/xml'

...where the 'addAccountMemberToPEM.xml' file contains the following XML request:

<?xml version="1.0" encoding="UTF-8" ?>

<member_id> is the ID of the problem user.

For POA version 5.5:

This issue will be fixed after implementing request PBA-12789: A user with an already existing login cannot be created in POA. Choose another login instead.

198398b282069eaf2d94a6af87dcb3ff 8fc71f07abe5b233fea1ae0377cd5e3d 5356b422f65bdad1c3e9edca5d74a1ae ac82ce33439a9c1feec4ff4f2f638899 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF