Knowledge Base: J-Integra : J-Integra for COM : ERRMSG

Resolving Compilation Errors for ACTIVEDS.DLL

J-Integra KB Admin — Tue, 24 Aug 2010 05:16:00 GMT

Abstract:

Resolving Compilation Errors for ACTIVEDS.DLL

When generating proxies for activeds.dll, the IADsADSystemInfo interface's 'get_IsNativeMode' conflicts with J-Integra's Dispatch object's 'isNativeMode' method, leading to the following compilation error:

IADsADSystemInfoProxy.java:231: isNativeMode() in Adsi.IADsADSystemInfoProxy cannot override isNativeMode() in com.linar.jintegra.Dispatch; overridden method is static public boolean isNativeMode () throws java.io.IOException, com.linar.jintegra.AutomationException

Because J-Integra has no mechanism for resolving this naming conflict, the proxies associated with the IADsADSystemInfo interface must be manually modified to change the method 'isNativeMode' to 'isNativeMode2' (or another name). This can be done by modifying the proxies in the following manner:

AdSystemInfo.java:
On Line 302, change 'isNativeMode' to 'isNativeMode2' On line 304, change call to 'isNativeMode' to 'isNativeMode2'
IADsADSystemInfo.java:
On line 103, change 'isNativeMode' to 'isNativeMode2'
IADsADSystemInfoProxy.java:
On line 231, change 'isNativeMode' to 'isNativeMode2'

These changes have already been made to pre-compiled versions of these proxies, available via the Precompiled Java Proxy JAR Files knowledge base article.

java.lang.NullPointerException

J-Integra KB Admin — Thu, 11 Jun 2009 03:47:00 GMT

Abstract:

java.lang.NullPointerException

Please refer to the Common Java Exceptions article.

java.io.IOException: Unable to establish RPC Connection to DCOM SCM on <hostname/ip> (Bind returned Bind_NAK)

J-Integra KB Admin — Wed, 10 Jun 2009 07:24:00 GMT

Abstract:

java.io.IOException: Unable to establish RPC Connection to DCOM SCM on <hostname/ip> (Bind returned Bind_NAK)

If using J-Integra for COM, please refer to the Common Java Exceptions article.

If using J-Integra for Exchange, please refer to the Common J-Integra for Exchange Problems article.

AutomationException: 0x5 - Access is denied

J-Integra KB Admin — Wed, 10 Jun 2009 07:17:00 GMT

Abstract:

AutomationException: 0x5 - Access is denied

If using J-Integra for COM, please refer to the Common Java Exceptions article.

If using J-Integra for Exchange, please refer to the Common J-Integra for Exchange Problems article.

AutomationException: 0x800706f8

J-Integra KB Admin — Wed, 10 Jun 2009 07:12:00 GMT

Abstract:

AutomationException: 0x800706f8

Please refer to the Common Java Exceptions article.

AutomationException: 0xc00e0007 - An invalid handle was passed to a function

J-Integra KB Admin — Wed, 10 Jun 2009 07:09:00 GMT

Abstract:

AutomationException: 0xc00e0007 - An invalid handle was passed to a function

Please refer to the Common Java Exceptions article.

java.lang.ClassNotFoundException

J-Integra KB Admin — Wed, 10 Jun 2009 07:05:00 GMT

Abstract:

java.lang.ClassNotFoundException

Please refer to the Common Java Exceptions article.

AutomationException: 0x80020003 - Member not found in ''IDispatch::invoke''

J-Integra KB Admin — Wed, 10 Jun 2009 07:02:00 GMT

Abstract:

AutomationException: 0x80020003 - Member not found in 'IDispatch::invoke'

Please refer to the Common Java Exceptions article.

java.lang.RuntimeException: Attempt to invoke a non-dispatch method on an object that only supports IDispatch

J-Integra KB Admin — Wed, 10 Jun 2009 06:59:00 GMT

Abstract:

java.lang.RuntimeException: Attempt to invoke a non-dispatch method on an object that only supports IDispatch

Please refer to the Common Java Exceptions article.

AutomationException: 0x80010001 - Call was rejected by callee. in ''Invoke''

J-Integra KB Admin — Wed, 10 Jun 2009 06:56:00 GMT

Abstract:

AutomationException: 0x80010001 - Call was rejected by callee. in 'Invoke'

Please refer to the Common Java Exceptions article.

AutomationException: 0x80080005 - Server execution failed

J-Integra KB Admin — Wed, 10 Jun 2009 06:52:00 GMT

Abstract:

AutomationException: 0x80080005 - Server execution failed

Please refer to the Common Java Exceptions article.

java.lang.ClassCastException

J-Integra KB Admin — Wed, 10 Jun 2009 06:48:00 GMT

Abstract:

java.lang.ClassCastException

Please refer to the Common Java Exceptions article.

Error "code too large"

J-Integra KB Admin — Fri, 20 Feb 2009 07:24:00 GMT

Abstract:

Error "code too large"

You may get this error if a generated Java proxy file exceeds the maximum length of byte code that a Java compiler can handle. For example, SUN's JDK 1.4.2_01 has a constraint that the length (in bytes) of a Java code cannot exceed 65535 bytes.

For example, consider TaskProxy.java generated from Microsoft Project 2003 C:\Program Files\Microsoft Office\OFFICE11\MSPRJ.OLB. To increase the memory for your Java compiler, you will need to use the -J-mx128m and -J-ms128m options.

However, compilation causes a "code too large" error at compile time:

The solution is to remove the methods you don't need from the Java class. You can download a slimmed down version of TaskProxy.java here.

Windows Error 3 occurred while using J-Integra installer

J-Integra KB Admin — Mon, 23 Jun 2008 05:33:00 GMT

Abstract:

Windows Error 3 occurred while using J-Integra installer

You may get the following error when use J-Integra installer.

"Windows error 3 occurred while loading the Java VM."

If the install package crashes when trying to invoke the JVM on your computer, it's usually an indication that your Java Runtime isn't properly configured.

In your Windows "System Properties" -> "Advanced" -> "Environmental Variables", please check that your have the Java bin folder added to your System Path.

Some variations of the path may be (depending on your installation folder and Java runtime version):
C:\Program Files\Java\JRE 1.6.0\bin
C:\Program Files\Java\JDK 1.6.0\jre\bin

If you receive this error while installing J-Integra on an x64 (e.g. Windows Server, XP, Vista) system, the cause is the new "Program Files" structure/naming. There are 2 possible workarounds:

Add quotation marks to the path contained in the JAVA_HOME System variable.
e.g. "C:\Program Files (x86)\Java\xxxxxxxx". OR
Uninstall and reinstall the Java JDK to a different directory.
e.g. "C:\Java\xxxxxxxx".

If this doesn't fix the installation problem, please go ahead and download the ZIP version of J-Integra for COM: http://j-integra.intrinsyc.com/download/default.aspx?ProductId=com.

Common Java Exceptions

J-Integra KB Admin — Tue, 03 Jun 2008 03:24:00 GMT

Abstract:

Common Java Exceptions

This article discusses the solutions to these common Java exceptions:

Errors when Releasing COM Objects from Java Clients

J-Integra KB Admin — Tue, 24 Jul 2007 03:04:00 GMT

Abstract:

Errors when Releasing COM Objects from Java Clients

SYMPTOMS

Sometimes COM objects are not released properly by the Java client. The client itself may execute normally. Errors listed below may be present in the jintegra.log file (note that the timestamp and objRefs will be different).

995005188493 *: Received a fault (code:2147549448) in response to IRemUnknown::RemRelease request, with RPC call id 80
995005188573 *: Error releasing batched objRefs: {00000022-013f-0000-3101-000022000000=30, 00000025-013f-0000-3101-000025000000=30, 00000023-013f-0000-3101-000023000000=5, 00000026-013f-0000-3101-000026000000=5, 00000024-013f-0000-3101-000024000000=5, 00000027-013f-0000-3101-000027000000=5} AutomationException: 0x80010108 - The object invoked has disconnected from its clients. in 'Invoke'
995005188673 *: IOException reading from socket: java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read to Net={aaa.bbb.ccc.ddd[xxxx]...
995005188673 *: RPC Connection Handler waitForResponse(2) failed: connection is dead to Net={{ 0x7, aaa.bbb.ccc.ddd[xxxx]}} Sec={{ .....
995005188673 *: Error releasing all objRefs: java.io.EOFException: The DCOM connection to the remote object has been disconnected (waitForResponse2)

CAUSE

"bad class file. class file has wrong version 50.0, should be 4x.0."

J-Integra KB Admin — Tue, 12 Jun 2007 04:36:00 GMT

Abstract:

"bad class file. class file has wrong version 50.0, should be 4x.0."

When compiling your code using the JAR files packaged with J-Integra for COM v2.7 or J-Integra for Exchange v2.7 (excel2007.jar & cdo.jar respectively) , you may receive an error similar to the one below:

SampleProgram.java:28: cannot access com.intrinsyc.cdo.Session
bad class file: C:\Program Files\J-Integra\Exchange\lib\cdo.jar(com/intrinsyc/cdo/Session.class)
class file has wrong version 50.0, should be 48.0
Please remove or make sure it appears in the correct subdirectory of the classpath.
            Session session = new Session(CDOmachine);
            ^
1 error

These types of errors are caused by a Java version mismatch between the compiled proxies and your runtime.

Below are a list of some of the version numbers and their corresponding Java runtimes:
Version 50.0 = Java 1.6.x
Version 49.0 = Java 1.5.x
Version 48.0 = Java 1.4.x

To resolve this issue, regenerate the proxies using com2java and compile them with your version of the Java SDK. Alternatively, you can download some precompiled proxies from our Precompiled Java Proxy JAR Files KB article.

Note: The downloadable proxies were compiled using Java 1.4, except for Excel 2007, which for compatibility reasons, was compiled using Java 1.5.

MIDL2021 duplicate id when use MIDL compile java2com generated IDL

J-Integra KB Admin — Fri, 03 Nov 2006 06:24:00 GMT

Abstract:

MIDL2021 Duplicate ID when use MIDL compile java2com generated IDL

You may get the following error when use midl.exe compile idl file generated by J-Integra java2com tool.

These midl error occur because of nested classes/interfaces. Notice that, in this case, java.io.PrintWriter extends java.io.Writer which in turn implements java.lang.Appendable. Therefore, the java2com tool generates an interface for each of java.io.PrintWriter, java.io.Writer, and java.lang.Appendable.

Because the COM IDL language does not know anything about Java inheritance, it generates 3 append method signatures for JavaLangAppendable, 6 append method signatures for JavaIoWriter, and 9 append method signatures for JavaIoPrintWriter. However, because of the Java inheritance involved, it ends up giving the same method id to the same append method signatures.

To resolve these errors, you need to use the Name Mappings option to tell java2com not to generate IDL definitions for the append() methods in java.io.Writer, and java.lang.Appendable:

Run the java2com (gui) tool.
Click Settings > Name Mappings.
On the left-hand side, click java > io > PrintWriter (its methods will appear to the right).
On the right-hand side, deselect the checkboxes beside the last 6 append methods.
Save settings and regenerate the proxies.

For more informaiton about J-

NullPointerException when Working with ActiveX Controls

J-Integra KB Admin — Thu, 17 Aug 2006 16:55:00 GMT

Abstract:

NullPointerException when Working with ActiveX Controls

When working with ActiveX controls, the control must first be displayed before invoking methods on it. If the control is not displayed first, often you will get a NullPointerException.

As an example, if com.activex.MapControl is an ActiveX component, doing something like this may cause a Null-pointer Exception:

com.activex.MapControl mapcontrol = new com.activex.MapControl();
mapcontrol.zoomIn(); // causes java.lang.NullPointerException

In this case, you may have to display the ActiveX component first, as below:

com.activex.MapControl mapcontrol = new com.activex.MapControl();

// code to display the MapControl should be placed here:
JFrame frame = new JFrame();
frame.setSize(400, 300);
frame.getContentPane().setLayout(new BorderLayout());
frame.getContentPane().add(mapcontrol, BorderLayout.CENTER);
frame.setVisible(true);

mapcontrol.zoomin(); // now it works

Notes:

(1) Actually, not all methods will cause a NullPointerException when called before the ActiveX control is displayed. Any setXX() method can be called beforehand. These setXX() methods will be queued up and automatically called once the ActiveX control is made visible.

(2) ActiveX controls hosted by J-Integra extend com.linar.jintegra.Ocx, which in turn extends java.awt.Canvas (see the generated proxies for details). All java.awt.Canvas components have a property called preferredSize. The preferredSize of any ActiveX control that is hosted by J-Integra defaults to 1

Knowledge Base: J-Integra : J-Integra for COM : ERRMSG

Resolving Compilation Errors for ACTIVEDS.DLL

Resolving Compilation Errors for ACTIVEDS.DLL

java.lang.NullPointerException

java.lang.NullPointerException

java.io.IOException: Unable to establish RPC Connection to DCOM SCM on <hostname/ip> (Bind returned Bind_NAK)

java.io.IOException: Unable to establish RPC Connection to DCOM SCM on <hostname/ip> (Bind returned Bind_NAK)

AutomationException: 0x5 - Access is denied

AutomationException: 0x5 - Access is denied

AutomationException: 0x800706f8

AutomationException: 0x800706f8

AutomationException: 0xc00e0007 - An invalid handle was passed to a function

AutomationException: 0xc00e0007 - An invalid handle was passed to a function

java.lang.ClassNotFoundException

java.lang.ClassNotFoundException

AutomationException: 0x80020003 - Member not found in ''IDispatch::invoke''

AutomationException: 0x80020003 - Member not found in 'IDispatch::invoke'

java.lang.RuntimeException: Attempt to invoke a non-dispatch method on an object that only supports IDispatch

java.lang.RuntimeException: Attempt to invoke a non-dispatch method on an object that only supports IDispatch

AutomationException: 0x80010001 - Call was rejected by callee. in ''Invoke''

AutomationException: 0x80010001 - Call was rejected by callee. in 'Invoke'

AutomationException: 0x80080005 - Server execution failed

AutomationException: 0x80080005 - Server execution failed

java.lang.ClassCastException

java.lang.ClassCastException

Error "code too large"

Error "code too large"

Windows Error 3 occurred while using J-Integra installer

Windows Error 3 occurred while using J-Integra installer

Common Java Exceptions

Common Java Exceptions

Errors when Releasing COM Objects from Java Clients

Errors when Releasing COM Objects from Java Clients

Contents

SYMPTOMS

"bad class file. class file has wrong version 50.0, should be 4x.0."

"bad class file. class file has wrong version 50.0, should be 4x.0."

MIDL2021 duplicate id when use MIDL compile java2com generated IDL

MIDL2021 Duplicate ID when use MIDL compile java2com generated IDL

NullPointerException when Working with ActiveX Controls

NullPointerException when Working with ActiveX Controls

Notes: