Internal Error Could Not Complete Connection To Specific Host
specified host" Technote (troubleshooting) Problem(Abstract) When testing an AS2 partner profile, the TestNowAS2 BP fails with "Could not complete connection to specified host" Symptom Clicking the Test button next to the trading partner relationship shows an error on the HTTP connectivity test. httpclient.log displays the following error: ERROR CustomConnectAgent.connectFailed() - Received signal from Perimeter due to fail to make connection with message [Could not complete connection to specified host] Cause By default, the TestNowAS2 BP uses the default HTTPClientAdapter configuration for its connection to the partner. This adapter comes configured to use the local perimeter server on node 1. If firewall rules block outbound traffic to the partner, then this traffic must be routed through an external perimeter server in the DMZ. In this particular case, the firewall was blocking outbound http traffic from the network to destination ports other than port 80, the standard HTTP port. The test was working for some partners where no port was specified in the endpoint. Diagnosing the problem Test connectivity to the partner endpoint from the Sterling B2B Integrator server using command line tools such as wget or through a packet trace. Many network administrators will block traffic for telnet or ping, so those may not be as reliable of an indicator. Even opening the partner's endpoint in a web browser can provide information. If an HTTP Error Code is returned, such as a 500 Internal Server Error or a 403 Forbidden, it shows that you have reached the server and it has returned an error code. Resolving the problem In this particular instance, a number of external perimeter server had been configured in the DMZ, which the AS2 Send processes had been reconfigured to use through a service group. The TestNowAS2 BP, however, had not been modified to use those same adapters. Rather than modifying the business process, in this case, the HTTPClientAdapter was re-configured to route through an external perimeter server in the DMZ. This resulted in successful tests when clicking the Test button next to the trading partner relationship. Document information More support for: Sterling B2B Integrator Software version: 5.2, 5.2.1, 5.2.2, 5.2.3, 5.2.4, 5.2.4.1 Operating system(s): Platform Independent Reference #: 1649190 Modified date: 2013-09-06 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
RSS Tags Why does Support need that when -- analyzing problems sending AS2 and HTTP John Perry in Michigan 270004Q6G1 | | Visits (1177) Tweet I know we drive our customers crazy at times when we ask for particular data, because they tell me so. We are looking for specific information, but it may not be obvious why we want it and what we are going to do with it. I thought maybe it would help if I explain why it is an analyst would ask for certain data. In this blog entry, I will outline the log information that's most useful for diagnosing problems with sending data using the AS2 and http://www-01.ibm.com/support/docview.wss?uid=swg21649190 HTTP protocols. I plan to follow up with some other articles to discuss other protocols.When someone tells me they cannot send data using HTTP (which includes AS2) I ask for a set of details, as follows:I ask for general information to outline the problem. Is it a new configuration, or one that worked but then stopped? If it used to work, then it has to have stopped because something changed. The focus https://www.ibm.com/developerworks/community/blogs/SterlingB2B/entry/Why_does_Support_need_that_when_analyzing_problems_sending_AS2_and_HTTP will be to find out what that is, and to do what's needed to correct it.I ask if it affects all partners, because that defines the scope of the problem. It can also pinpoint the source. If a problem occurs for one partner, it might be an error on the partner's system. If it's more than one, it's pretty sure to be an issue within Sterling b2B Integrator.I ask if it happens every time or if it is intermittent. If it is intermittent, there's a difference between the occurrences that work and those that do not. In order to establish a pattern to help determine what those differences are, I will want to know how often the problem occurs. I will want to know what times, and whether it always occurs on one node. I'll want to ask whether other events were happening such as heavy traffic from partners or system activity such as backups. I'll ask anything I can think of that distinguishes the errors from events that work correctly.I also ask for some specific data:1) Output from dump_info.sh or dump_info.cmd: My colleague Dana explained why we ask for this. I have nothing to add to her explanation, which is here:https://www-304.ibm.com/connections/blogs/SterlingB2B/entry/why_does_ibm_ask_for_your_dump_info?lang=en_us
2) Screen prints showing all of the steps of an example of tprotection by CloudFlare Ray ID: 2f40456db42f16c4
Services Database Administrator's Guide and the Analytic Services Technical Reference for more information on how to fix errors. Click an error message number to view information about that error message. 1040002 1040019 1042003 1042022 1040003 1041000 1042004 1042023 1040004 1041002 1042006 1042024 1040006 1041003 1042007 1042025 1040007 1041004 1042008 1040008 1041005 1042009 1040010 1041006 1042010 1040011 1041007 1042011 1040012 1041008 1042012 1040013 1041009 1042013 1040014 1041011 1042015 1040015 1041012 1042017 1040016 1041013 1042018 1040017 1041014 1042019 1040018 1042002 1042020 1040002 Too many arguments supplied for this request Possible Problems The actual number of buffers to be sent is not the same as the number of buffers predicted at the start of the session. In the networking layer, make sure that the number of buffers predicted to be sent in this session is correct. Possible Solutions This is an internal error. Contact Hyperion Technical Support. 1040003 No length specified for data type Possible Problems The network cannot determine the length of the network buffer based on the type of the buffer. In the networking layer, specify the length of the buffer explicitly. Possible Solutions This is an internal error. Contact Hyperion Technical Support. 1040004 Invalid structure type. An application protocol error might exist between server and client processes. Possible Problems Analytic Services encountered data with an incorrect data type. Possible Solutions Make sure that the client computer and the server computer are running the same release of ODBC. Increase the values for NETDELAY and NETRETRYCOUNT. 1040006 No message database specified Possible Problems Analytic Services did not have a message database defined. Possible Solutions This is an internal error. Contact Hyperion Technical Support. 1040007 Cannot find message database fileName, which is required for normal operations. Make sure your PATH and ARBORPATH variables are pointing to the correct directories. Make sure that databaseName exists in the $ARBORPATH\bi