Introduction
This article explains the most commonly faced issues of document submission through different inbound channels. The possible solutions are also given to overcome the failures.
Audience
This document is meant for users troubleshooting transaction failures due to errors faced on document submission.
Document Submission Issues
The following tables explains the error message, inbound channel and Issue and its solution based on Response Code
Legend as below:
Code: Response Code received on submission
| Message |
Message received on document submission |
| Type |
HTTP, AS2,SFTP, RNIF |
| Issue |
Root issue for the failure |
| Solution |
Steps to resolve the document submission issue
|
Response Code : 400
| Message |
Invalid URL |
| Type |
HTTP, AS2, RNIF |
| Issue |
Inbound channel URL is not correct. |
| Solution |
Provide the correct Inbound Channel URL. Copy the URL from inbound channel summary page as shown in screenshot, provide in the client where the inbound channel is invoked.
|
Response Code : 401
| Message |
Invalid credential |
| Type |
HTTP, AS2, RNIF |
| Issue |
Partner User credentials are incorrect. |
| Solution |
Provide the correct Partner User credentials in the client where the inbound channel is invoked.
|
| Message |
Access Denied |
| Type |
HTTP, AS2, RNIF |
| Issue |
Partner User is associated to the partner but the status is Inactive. |
| Solution |
Set the status of the Partner User to Active in the Partner User page
|
| Message |
Access Denied |
| Type |
SFTP |
| Issue |
Does not have authorization to access the SFTP server. Observed when the document is not processed from the inbound channel. |
| Solution |
Update the SFTP partner user credentials to valid one, in the channel configuration.
|
Response Code : 403
| Message |
Channel is inactive. |
| Type |
HTTP, AS2, SFTP |
| Issue |
The status of the inbound channel is set to Inactive |
| Solution |
Set the status of the inbound channel to Active in channel properties page.
|
| Message |
Partner user sent this document posing as Unknown. |
| Type |
HTTP, SFTP |
| Issue |
1.The XML Document is not created
2.The status of the XML Document is set to Inactive
3.Document attribute extraction for the system attributes , SenderID and RecieverID is mandatory. These are not set in the Document Attributes.
|
| Solution |
1.Create XML document.
2.Set the status of the XML document to Active in Document page.
3.The extraction for the system attributes, SenderID and ReceiverID, has to be set in the document attribute page.
|
| Message |
Forbidden |
| Type |
AS2 |
| Issue |
The Partner User submitting the document is not associated to the sender partner profile. |
| Solution |
Associate the Partner User to the sender partner profile.
|
| Message |
Forbidden An error occurred while validating the partner. Error: Demo Sender is not a valid partner id |
| Type |
AS2 |
| Issue |
The Enterprise/Partner AS2's ID does not match the inbound message's AS2-from/AS2-to header |
| Solution |
Update the Enterprise/partner profile's EDIINT-AS2 idtype value
|
| Message |
Forbidden An error occurred while validating the partner. Error: new user is not allowed to perform this operation |
| Type |
AS2 |
| Issue |
AS2-Form and AS2-To is not providing in header |
| Solution |
Provide the AS2-Form and AS2-To headers
|
Response Code : 500
| Message |
Internal Server Error |
| Type |
HTTP, SFTP |
| Issue |
The Partner User submitting the document is not associated to the sender partner profile. |
| Solution |
Associate the Partner User to the sender partner profile.
|
| Message |
Internal Server Error |
| Type |
SFTP |
| Issue |
Invalid SFTP server .Observed when the document is not processed from the inbound channel. |
| Solution |
Update the SFTP server in the channel configuration to the correct one.
|
| Message |
Internal Server Error |
| Type |
HTTP |
| Issue |
The status of the Sender Partner Profile is set to Inactive |
| Solution |
Set the status of the Sender Partner Profile to Active in Partner page.
|
| Message |
Internal Server Error |
| Type |
SFTP |
| Issue |
Invalid credentials given for SFTP server connection. |
| Solution |
Update the user credentials given for SFTP server in channel details page.
|
Response Code : 200
| Message |
No error in webMethods.io B2B |
| Type |
AS2 |
| Issue |
B2B cloud's partner unable to parse the sync MDN received at their end frm B2Bcloud |
| Solution |
This is because some of the third party products unable to parse “X-Content-Type-Options” header which webmio adds before sending the sync MDN response
Below two solution will work
- Ask the partner to allow parsing of the header “X-Content-Type-Options”
- Switch to AsyncMDN as the above mentioned header wonnt be added to the async mdn
|
| Message |
No error in webMethods.io B2B |
| Type |
AS2,HTTPS/RNIF |
| Issue |
B2B cloud's partner unable to establish connection with B2BCloud |
| Solution |
-
Ensure partner is using the correct NAT address . https://www.softwareag.cloud/site/nat-servers.html#/
-
Ensure partner should have whitelisted the B2BCloud’s ip address in their platform
-
Partner must trust the B2BCloud’s public certificates.
-
The supported SSL version in B2BCloud is TLS 1.2
The cipher suites supported by channel endpoints are as follows:
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 128
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 256
TLS_RSA_WITH_AES_128_GCM_SHA256 128
TLS_RSA_WITH_AES_128_CBC_SHA256 128
TLS_RSA_WITH_AES_256_GCM_SHA384 256
TLS_RSA_WITH_AES_256_CBC_SHA256 256
|
| Message |
No error in webMethods.io B2B |
| Type |
AS2,HTTPS/RNIF |
| Issue |
B2B cloud's partner facing intermittent ssl handshake issue |
| Solution |
Wrong hostname resolution may be happening at the patner's end for WMIO B2B endpoints. This may lead to issues while connecting as it may resolve to wrong IP address.
Ask the partner to check their proxy, firewall and DNS server.
|
