My Oracle Support Banner

WebLogic Server (WLS) Support Pattern: Troubleshooting jCOM Issues (Doc ID 1224223.1)

Last updated on OCTOBER 01, 2020

Applies to:

Oracle WebLogic Server - Version 6.1 to 10.3.3
Information in this document applies to any platform.

Purpose

Problem Description

WebLogic jCOM is a software bridge that allows bidirectional access between Java/J2EE objects deployed in WebLogic Server, and Microsoft ActiveX components, Visual Basic and C++ objects, and other COM/DCOM environments. This pattern provides information on some common exceptions and errors that can result from misconfiguration, licensing, upgrade, and registry issues, and how to resolve these problems. Background information on COM, DCOM, and jCOM is also provided, as well as steps to get WLS-to-COM working and to obtain debug information.

Problem Troubleshooting

Please note that not all of the following items would need to be done. Some issues can be solved by only following a few of the items.

Troubleshooting Steps

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
Purpose
 Problem Description
 Problem Troubleshooting
Troubleshooting Steps
 Why does the problem occur?
 License Error
 Unable to run stand-alone java client to com
 AutomationException: 0x80040154 - Class Not Registered
 Issues with Early Bound method calls
 Other Issues / Tips
 What is COM?
 COM Features
 COM Configurations
 What is DCOM?
 DCOM Features
 jCOM Overview
 What is jCOM?
 COM to Java
 Steps to get WLS-to-COM Working
 All WLS Versions
 Getting Debug Information
 WLS 6.1
 WLS 7.0 / WLS 8.1
 External Resources
 Known Issues
 Need further help?
References

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