Search Engine: Elastic

Article ID: 130555, created on Mar 31, 2017, last review on Mar 31, 2017

  • Applies to:
  • Operations Automation 6.0

Symptoms

APS account actualization process fails with the message below, which could be found in task output:

Service Creation Failed: Parallels Operations Automation error #error_code=1000; extype_id=1000; module_id=AccountManagement; xxx is invalid: No @ at address..

The error originates from the following line in core.log on the Management node:

[ SaaS::<unnamed>::parseEmailForDomain] {module_id="AccountManagement"; code="1000"} mayƩ is invalid: No @ at address.
[ SaaS::<unnamed>::fillMailRecipientInfo] <=== EXIT (by exception) [0.059431]
[ SaaS::processMailRecipients] <=== EXIT (by exception) [13.845942]
[ SaaS::<unnamed>::MailEntityProcessor::processMailboxes] <=== EXIT (by exception) [13.938160]
[ SaaS::SaaSManager_impl::syncMailObjects]

As we may see in log preceding the error, OA creates APS resources for mailboxes of all customer's service users one by one and the error itself occurs on the latest one:

Begin request: "GET /aps/2/resources?limit(0,1),userId=eq=1178672,implementing(http:%2F%2Fparallels.com%2Faps%2Ftypes%2Fpa%2Fservice-user%2F1.1)"
Begin request: "GET /aps/2/resources?limit(0,1),userId=eq=1178673,implementing(http:%2F%2Fparallels.com%2Faps%2Ftypes%2Fpa%2Fservice-user%2F1.1)"

Cause

Actualized account uses Exchange service and has several mailboxes assigned to its service users. The issue occurs if OA is unable to validate e-mail address of the user. For example, when address does not contain '@' or is malformed.

Resolution

Please review mailbox addresses (including additional addresses) of Exchange users on OA side. Fix or remove any invalid addresses found.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF