My Oracle Support Banner

E1: INST: "Failed to Connect" Errors After Adding Data Server to Existing AS400 iSeries Enterprise Server Configuration (Doc ID 631012.1)

Last updated on JANUARY 24, 2020

Applies to:

JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.


In this scenario, customer has setup an AS/400 data server to an existing AS400 iSeries Enterprise Server.  The data server will hold CRP business data only, it will not process any EnterpriseOne logic (i.e. it will not run UBEs on this server).  We have modified the Business Data - CRP datasource to point to the new AS/400 data server, however we cannot connect to a remote AS/400 to get the data.   Jobs run fine locally but not to the Enterprise Server.  

The following error messages appear:

OS40002001 - Error Type: SOCKET  errno: 34250
JDB9900164 - Failed to connect to Business Data - NPL TEST
JDB9909003 - Could not init connect.
JDB9909100 - Get connect info failed: Transaction ID =
JDB3100013 - Failed to get connectinfo
MSC0000025 - Could not load F0009 cache - ENVCACHE
OS40002001 - Error Type: OTHER  enum: 6 - Illegabl connect handle specified!
OS40001078 - DoPrepare:  sql code is -901
JDB9900168 - Failed to initialize db request
JDB9909007 - Unable to obtain driver request handle



To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.