KB Article #67762
Error message for incoming OFTP transfer "Connection abort indication: reason="14, Invalid remote identifier" /prot.diag="303, Unknown user code" / error=3" when Passport PM is used
* Error message for incoming OFTP transfer "Connection abort indication: reason="14, Invalid remote identifier" /prot.diag="303, Unknown user code" / error=3" when Passport PM is used
Resolution
- The log message could be as follows: e.g.
=================================
ODT201I 20.12.2010 15:37:54 .TODT.000001(5) connection established with LOCAL_SITE.
ODT217I 20.12.2010 15:37:54 .TODT.000001(5) disconnect indication received for LOCAL_SITE [reason="Unknown user code"].
. . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . .
SUP011W 20.12.2010 15:37:54 .TODT.000001(31457285) connection abort indication: reason="14, Invalid remote identifier" /prot.diag="303, Unknown user code" / error=3.
=================================
On the receiving side which is configured with Passport did not checks the partner detail in Passport PM and trying to check default local site and transfer not complete with above error message in log. "LOCAL_SITE" is the default local site name in receiving Gateway.
The behavior is normal on the receiving end because in Passport there is no way to specify an association between the local entity and the remote entity as we are allowed to do with normal Gateway objects through partner local alias field.
The link is necessary because in Gateway we can define more than one OFTP local identifier and the user has to specify which protocol identifier to use when communicating with different partners. The only way we can specify the link is to add it in the template site used to create the virtual sites with the partner information retrieved from Passport. The default template site for OFTP is TODT. For this to work the user has to create a OFTP local site with the local protocol identifier already configured or we can leave this field empty. After this site is created its alias has to be filled in the "Partner local alias" field of the TODT remote site.
So it can be done as follow:
1. Create a OFTP local site like "OFTP_TEST_LOCAL" and specify the local OFTP protocol id or leave it blank.
2. Specify this "OFTP_TEST_LOCAL" in the TODT remote site -- > General Tab -- >Partner local alias" parameter