Symptoms

Mail2World APS 1.2 task "APS application 'Mail2World', id XXX, instance XXX-> service 'account', instance XXX: executing configuration script" fails with one of the following outputs:

1. Application configuration script reported errors: ' error id "API-error", setting id "Get GUID": The following http code [403] is returned for url : http://.api.mail2world.com/restapi/login*?GUID=* Description:'

2. Application configuration script reported errors: ' error id "API-error", setting id "mailbox create": The following http code [404] is returned for url : http://.api.mail2world.com/restapi/login*?GUID=* Description:'

3. Application configuration script reported errors: ' error id "API-error", setting id "Get member Id": The following http code [500] is returned for url : http://.api.mail2world.com/restapi/login*?GUID=* Description:Mailbox does not exist.'

Cause

The issue is caused by a discrepancy on the Mail2World (external) service side.

Resolution

Since this issue is not related to Operations Automation provisioning side, contact Mail2World support team in order to troubleshoot it from their side. Use the failed task's full output as a reference. Additionally, you can collect the data exchange between OA and Mail2World and pass it to Mail2World support team. This can be accomplished by the following steps:

Run command tcpdump on provisioning gateway server (linpgh):

#tcpdump -i any -Xs2000 -w outfile_1 host *.api.mail2world.com

where *.api.mail2world.com - API endpoint for Mail2World APS from the task's output;
Resubmit the failed task;
As the task will fail, interrupt tcpdump command by pressing ctrl^c.

The resulting file outfile_1 will contain the full request which is sent to the Mail2World side.