E1: COM: COM Connector Unable to Connect to OCM
(Doc ID 638485.1)
Last updated on DECEMBER 16, 2019
Applies to:JD Edwards EnterpriseOne Tools - Version 9.1 and later
Information in this document applies to any platform.
When running VB application via JDE Com connector, interopDebug.log shows:
Failed to get OCM info for 'Business Function Name'
This shows when the session tries to execute the first BSFN and is caused to the fact that the connector is failing to connect to the OCM.
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