EIB Migration Fails: Transport Protocol Validation Error
The error SOAP-ENV:Client:ValidationError: Validation Error Occured. If a value for ID is not provided, or the ID does not represent an existing Transport Protocol, then 2 of the Transport Protocol Data sub-elements is required.
What it means
You're using Object Transporter (OX) to migrate an EIB integration between tenants, and the target tenant doesn't have a Transport Protocol connection configured to match what the source EIB references. The migration package expects an existing Transport Protocol ID or full connection details, and finds neither.
Troubleshooting
- Open Integration Maintenance in the target tenant and check whether the Transport Protocol referenced by the EIB (e.g., an FTP/AS2 connection) already exists there.
- If it doesn't exist, either create the matching Transport Protocol first, or ensure the OX package includes the full Transport Protocol Data sub-elements (host, port, credentials) instead of just an ID reference.
- Compare the EIB's Integration System settings between source and target tenants - transport config is tenant-specific and never migrates automatically with OX.
- Re-run the migration after the transport protocol exists in the target, or after editing the connection step manually.
⚡ Quick fix
Manually create the missing Transport Protocol connection in the target tenant before re-running the OX migration.
✓ Permanent fix
Document each EIB's external transport dependencies (FTP/AS2 connections) in the migration runbook, and pre-provision them in every target tenant before running Object Transporter, rather than assuming OX carries connection config across.
Was this helpful?