CommunicationException - Incompatible versions

I have a situation where it is necessary to invoke a method on a stateless SessionBean that resides in WLS 6.1.2 from a client application class that resides externally on WLS 5.1.0. Everytime I try to establish a context from the 5.1 server (whether to try and access an MDB or use RMI and/or JMS) , it throws a Communication Exception - IncompatibleVersion.
javax.naming.CommunicationException. Root exception is weblogic.socket.UnrecoverableConnectException: [Login failed: 'Incompatible version:Incompatible versions - this server:6.1.2.0 client:5.1.0]
I can't be the first one that has run into this issue - if anyone has any ideas/input, I would really appreciate it.
Many thanks!
~ RomT

Hi,
Since they are talk to each other in two different languages, how do you expect that they can
know each other ? your environment could be complicated, but I suggest that you contact
the vendor for your question. Perhaps you need to upgrade your environment ? Perhaps you
could develop your solution out of the box of AP server ?
I have ever met a error that jsp container just prompt that internal error with lots of exception
messages. Finally , I know the reason why . Because my database server and the driver running
by the jsp applications are the different version. as yours. But my question is siimple, because
my environment is simple.
good luck,
Alfred Wu

Similar Messages

Incompatible version - this server:6.0.0b2 client:5.1.0]]

Hi, i have a client running on WLS 5.1, and i have to connect to a
server running on WLS 6.0 I got back following
error:
javax.naming.CommunicationException [Root exception
is
                                   weblogic.socket.Unrecover ableConnectException:
[Login failed:
                                   'Incompatible version:Incompatible versions
- this server:6.0.0b2
                                   client:5.1.0]]
I have tried to run a standalone client (outside
WLS) using classes from
WLS 6.0 and it works.
When i have tried to add the weblogic.jar (of
6.0) to the
WEBLOGIC_CLASSPATH of 5.1, i got the following
error:
Unable to initialize server: java.lang.ClassCastException:
weblogic.rmi.internal .BasicRuntimeDescriptor
fatal initialization
exception java.lang.ClassCastException:
weblogic.rmi.internal.BasicRuntimeDescriptor
at
weblogic.rmi.internal.DescriptorManager.resolveClass(DescriptorManage
r.java:59) at
weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManag
er.java:36) at
weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManag
er.java:27) at
weblogic.rmi.extensions.BasicServerObjectReference.<init>(BasicServer
ObjectReference.java:48) at
weblogic.rmi.extensions.BasicServerObjectAdapter.<init>(BasicServerOb
jectAdapter.java:42) at
weblogic.rmi.extensions.BasicRequestHandler.<init>(BasicRequestHandle
r.java:30) at
weblogic.rmi.extensions.BasicRequestDispatcher.<init>(BasicRequestDis
patcher.java:41) at
weblogic.rmi.internal.OIDManager.initializeServer(OIDManager.java:272
) at weblogic.rmi.internal.OIDManager.initialize(OIDManager.java:251)
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:141)
at
weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1111)
at
weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
at
java.lang.reflect.Method.invoke(Native Method)
at
weblogic.Server.startServerDynamically(Server.java:99)
at
weblogic.Server.main(Server.java:65) at
weblogic.Server.main(Server.java:55)
Can anyone help me?
thanx and regards marco

I do not have this information. However, your BEA sales rep can provide you
more information on release dates and availability of new
functionality/features.
Hope this helps,
Robert
"trond strømme" wrote:
Any clues as to when this service pack will be out?
.trond stromme, mogul technology.
"Robert Patrick" <[email protected]> wrote in message
news:[email protected]..
Please do not cross post (or post multiple times).
This has been a problem with WLS for years in that major versions are not
interoperable. I believe that they are targeting providing this
interoperability in an upcoming service pack release for WLS 5.1leveraging the
RMI/IIOP work done in WLS 6.1.
Gottfried Szing wrote:
hi
i try to connect a JMS queue hosted on WLS 6.1 from within a WLS5.1 but
i
receive always the same error message (see below). so what can i do to
solve this problem?
Exception in thread "main" javax.naming.CommunicationException. Root
exception is weblogic.socket.UnrecoverableConnectException: [Loginfailed:
'Incompatible version:Incompatible versions - this server:6.0.0b2
client:5.1.0]
at weblogic.socket.Login.checkLoginSuccess(Login.java:77)
at weblogic.socket.JVMSocketT3.connect(JVMSocketT3.java:85)
atweblogic.socket.JVMAbbrevSocket.connect(JVMAbbrevSocket.java:160)

szing@ispdev1#

Incompatible version:- this server:6.0.0b2 client:6.1.4.0

I am trying to connect my application (WLS 6.1.4) with another one (WLS 6.0) and
I am getting the following error. Any Idea?
NamingException:javax.naming.CommunicationException [Root exception is weblogic.socket.UnrecoverableConnectException:
[Login failed: 'Incompatible Version:Incompatible versions - this server:6.0.0b2
client:6.1.4.0]]

I am trying to connect my application (WLS 6.1.4) with another one (WLS 6.0) and
I am getting the following error. Any Idea?
NamingException:javax.naming.CommunicationException [Root exception is weblogic.socket.UnrecoverableConnectException:
[Login failed: 'Incompatible Version:Incompatible versions - this server:6.0.0b2
client:6.1.4.0]]

Incompatible version

Hi,
i have a client running on WLS 5.1, and i have to connect to a server running
on WLS 6.0
I got back following error:
javax.naming.CommunicationException [Root exception is weblogic.socket.Unrecover
ableConnectException: [Login failed: 'Incompatible version:Incompatible versions
- this server:6.0.0b2 client:5.1.0]]
I have tried to run a standalone client (outside WLS) using classes from WLS 6.0
and it works.
When i have tried to add the weblogic.jar (of 6.0) to the WEBLOGIC_CLASSPATH of
5.1, i got the
following error:
Unable to initialize server: java.lang.ClassCastException: weblogic.rmi.internal
.BasicRuntimeDescriptor
fatal initialization exception
java.lang.ClassCastException: weblogic.rmi.internal.BasicRuntimeDescriptor
at weblogic.rmi.internal.DescriptorManager.resolveClass(DescriptorManage
r.java:59)
at weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManag
er.java:36)
at weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManag
er.java:27)
at weblogic.rmi.extensions.BasicServerObjectReference.<init>(BasicServer
ObjectReference.java:48)
at weblogic.rmi.extensions.BasicServerObjectAdapter.<init>(BasicServerOb
jectAdapter.java:42)
at weblogic.rmi.extensions.BasicRequestHandler.<init>(BasicRequestHandle
r.java:30)
at weblogic.rmi.extensions.BasicRequestDispatcher.<init>(BasicRequestDis
patcher.java:41)
at weblogic.rmi.internal.OIDManager.initializeServer(OIDManager.java:272
at weblogic.rmi.internal.OIDManager.initialize(OIDManager.java:251)
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:141)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1111)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:99)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)
Can anyone help me?
thanx and regards
marco

The form complies on both machines correctly.
It runs on machine2 as expected, but when i try to run it on machine 1, some button clicks(update and insert buttons) cause the application to exit. any ideas?

Weblogic5.1 & weblogic6.1 - Incompatible Versions

Anyone run into this issue.
We are upgrading from 5.1 to 6.1 and are first attempting to use 6.1 as
a servlet container only. The beans are deployed in a 5.1 installation
of weblogic. Both instances start-up with no error messages, but when
you try to make one talk to the other, you receive the following
message:
java.lang.ExceptionInInitializerError:
javax.naming.CommunicationException. Root exception is
weblogic.socket.UnrecoverableConnectException: [Login failed:
'Incompatible version:Incompatible versions - this server:5.1.0
client:6.1.2.0]
After going through some of the newsgroups, I found a response that you
needed a sp12 for 5.1 and an sp3 for 6.1, both of which I received from
bea as early release patches. Neither solved my problem. Anyone have
any ideas?
[att1.html]

Hi.
You should take this up with support.
Regards,
Michael
Jeff Cantrill wrote:
Anyone run into this issue.
We are upgrading from 5.1 to 6.1 and are first attempting to use 6.1
as a servlet container only. The beans are deployed in a 5.1
installation of weblogic. Both instances start-up with no error
messages, but when you try to make one talk to the other, you receive
the following message:
java.lang.ExceptionInInitializerError:
javax.naming.CommunicationException. Root exception is
weblogic.socket.UnrecoverableConnectException: [Login failed:
'Incompatible version:Incompatible versions - this server:5.1.0
client:6.1.2.0]
After going through some of the newsgroups, I found a response that
you needed a sp12 for 5.1 and an sp3 for 6.1, both of which I received
from bea as early release patches. Neither solved my problem. Anyone
have any ideas?
Michael Young
Developer Relations Engineer
BEA Support

Weblogic 9.1 and Weblogic 6.1 "Incompatible versions " error

Hi,
When i tried to create InitalContext object on Weblogic 9.1 It gives me following error.
<i>"javax.naming.CommunicationException [Root exception is weblogic.socket.UnrecoverableConnectException: [Login f
ailed: 'Incompatible version: Incompatible versions - this server:6.1.7.0 client:9.1.0]]"</i>
The EJB is deployed on Weblogic 6.1 and client deployed on Weblogic 9.1 trying to access that EJB.
Please let me know how to resolve this issue.
Regards
Jagat Kansara

Hi,
When i tried to create InitalContext object on Weblogic 9.1 It gives me following error.
<i>"javax.naming.CommunicationException [Root exception is weblogic.socket.UnrecoverableConnectException: [Login f
ailed: 'Incompatible version: Incompatible versions - this server:6.1.7.0 client:9.1.0]]"</i>
The EJB is deployed on Weblogic 6.1 and client deployed on Weblogic 9.1 trying to access that EJB.
Please let me know how to resolve this issue.
Regards
Jagat Kansara

IPhoto won't run. iPhoto can not run due to an incompatible version of ProKit on this system.

Eh, See title. When I attempt to run iPhoto it pops up "iPhoto can not run due to an incompatible version of ProKit on this system." So. What's ProKit and...
I really need iPhoto today, quite urgent. iPhoto worked perfectly fine before the upgrade but now it seems to.. not be compatible. Yes it is the most updated version. I'm about to order a book and I really need to order today. And in other question, (Don't want to make an other one for no reason in the forums) how long does it normaly take for the books to print and arrive in Singapore? Please answer as quick as possible.
Thanks.

Did you install any third party software earlier? Pro Kit is a frame work in your system Library that is used by several multimedia applications. If you have an incompatible version, reinstall your system, that should fix it: Use the Client Combo to reinstall:
Download and reapply the OS X Lion Update 10.7.4 (Client Combo) updater.
Good Luck!
And sorry, I do not know anything about the book delivery in Singapore. But you live in a fine city!
Tegards
Léonie

TS2551 Photo can not run due to an incompatible version of ProKit on this system.

Message:"iPhoto can not run due to an incompatible version of ProKit on this system".It is a Lion system????I updated iphoto to version 9.3 and it is the message I receive every time I try to open iphoto. Please help me?

Try downloading and reapplying the OS X Lion Update 10.7.4 (Client Combo) updater followed by a repair of disk permissions with Disk Utility.
OT

IPhoto can not run due to an incompatible version of ProKit on 10.8

iPhoto can not run due to an incompatible version of ProKit on Mountian Lion 10.8

Did you install any third party software earlier? Pro Kit is a frame work in your system Library that is used by several multimedia applications. If you have an incompatible version, reinstall your system, that should fix it: Use the Client Combo to reinstall:
Download and reapply the OS X Lion Update 10.7.4 (Client Combo) updater.
Good Luck!
And sorry, I do not know anything about the book delivery in Singapore. But you live in a fine city!
Tegards
Léonie

Solaris 10 determining ZFS version of FAULTED rpool incompatible version

{0} ok boot cdrom -s
Boot device: /pci@7c0/pci@0/pci@1/pci@0/ide@8/cdrom@0,0:f File and args: -s
SunOS Release 5.10 Version Generic_118833-17 64-bit
Copyright 1983-2005 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Booting to milestone "milestone/single-user:default".
Configuring devices.
Using RPC Bootparams for network configuration information.
Attempting to configure interface ipge3...
Skipped interface ipge3
Attempting to configure interface ipge2...
Skipped interface ipge2
Attempting to configure interface ipge1...
Skipped interface ipge1
Attempting to configure interface ipge0...
Skipped interface ipge0
Requesting System Maintenance Mode
SINGLE USER MODE
# cat /cdrom/Solaris_10/Product/SUNWsolnm/reloc/etc/release
                       Solaris 10 6/06 s10s_u2wos_09a SPARC
           Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
                        Use is subject to license terms.
                             Assembled 09 June 2006
# zpool import
WARNING: /pci@780/pci@0/pci@9/scsi@0/sd@0,0 (sd1):
        Corrupt label; wrong magic number
WARNING: /pci@780/pci@0/pci@9/scsi@0/sd@0,0 (sd1):
        Corrupt label; wrong magic number
WARNING: /pci@780/pci@0/pci@9/scsi@0/sd@0,0 (sd1):
        Corrupt label; wrong magic number
WARNING: /pci@780/pci@0/pci@9/scsi@0/sd@0,0 (sd1):
        Corrupt label; wrong magic number
WARNING: /pci@780/pci@0/pci@9/scsi@0/sd@0,0 (sd1):
        Corrupt label; wrong magic number
WARNING: /pci@780/pci@0/pci@9/scsi@0/sd@0,0 (sd1):
        Corrupt label; wrong magic number
WARNING: /pci@780/pci@0/pci@9/scsi@0/sd@0,0 (sd1):
        Corrupt label; wrong magic number
WARNING: /pci@780/pci@0/pci@9/scsi@0/sd@0,0 (sd1):
        Corrupt label; wrong magic number
pool: rpool
    id: 383013941482167518
state: FAULTED
status: The pool is formatted using an incompatible version.
action: The pool cannot be imported. Access the pool on a system running newer
        software, or recreate the pool from backup.
   see: http://www.sun.com/msg/ZFS-8000-A5
config:
        rpool       UNAVAIL   newer version
          c0t1d0    ONLINE
          c0t2d0    ONLINE
          c0t3d0    ONLINE
# zpool upgrade -v
This system is currently running ZFS version 2.
The following versions are suppored:
VER DESCRIPTION
1   Initial ZFS version.
2   Ditto blocks (replicated metadata)
For more information on a particular version, including supported releases, see:
http://www.opensolaris.org/os/community/zfs/version/N
Where 'N' is the version number.
# zdb -l /dev/rdsk/c0t1d0s0 | head -9
LABEL 0
    version=22
    name='rpool'
    state=0
    txg=325246
    pool_guid=383013941482167518
    hostid=2221609516
Reference ZFS Pool Versions - Oracle Solaris ZFS Administration Guide

hello
the zpool version supported comes from the kernel patch this doc will provide you the information
ZFS Filesystem and Zpool Version Matrix (Doc ID 1359758.1)
So for version 22 as Pascal wrote sol10u9 or higher has to be used to import that pool
22
Received properties
9/10 (U9) - 142909-17/142910-17
Yes (snv_128)
Regards
Eze

Incompatible versions -- gsearch.jsp

When i enter http://localhost/ultrasearch/query/jsp/gsearch.jsp
the page display
Incompatible versions:
PL/SQL Package Version: null
Ultra Search Query Tool Version: 1.0.3.0.0

Answered this question. I found I had turned off open directory on the master to see if it would rebuild on turning on and got distracted. So this error actually means. "there is no open directory mastre on that machine you idiot" - me that is. so I am now back to error from last night from my upgraded one so the problem appears to be on the OD master.
8/10/12 8:43:41.433 PM Server[580]: An error occurred while configuring mahuserver4 as a directory replica:
Error Domain=XSActionErrorDomain Code=-1 "A child action failed" UserInfo=0x7f93e0c706c0 {XSActionErrorActionsKey=(
"Creating Open Directory replica"
), NSLocalizedDescription=A child action failed}
So I am now going to backup my OD master using terminal command
slapconfig -backup <filename>
then destroy the OD master and try to creat a blank new OD master and then try to create a replica of this and then see if I restore whether I can link up then. There does seem to be a message that flicks up whn starting the OD master suggesting it is having difficulty connecting to a replica - which may be its old ones. so I wonder if removing replicas before migrating might have been a good idea.

Import Log shows Incompatible version of Workspace Manager Installed

Hi,
I did an export of my DB using oracle 10.2.0.3 in Windows 2003 R2, I am trying to import the DB in Oracle 10.2.0.4 on Windows 2008 Server.
Question 1
I am getting the following error message
IMP-00003: ORACLE error 20000 encountered
ORA-20000: Incompatible version of Workspace Manager Installed
Is it safe to continue the import? Do I need to do any post import configuration to solve the above error message.
Question 2
I have few notes in the log which states, is it because of the above error message or can I ignore these notes
Note: table contains ROWID column, values may be obsolete 0 rows imported
Thank you

Pl see if these MOS Docs help
730373.1 - ORA-39083 ORA-20000 Incompatible Version of Workspace Manager Installed
743097.1 - IMP-00017 ORA-20000 Importing older version of OWM into a higher version
HTH
Srini

Can someone help with Incompatible versions error with taglib and project?

Evening all,
I am trying to import a tag library into my web project but I keep getting the error "Incompatible versions: Tag library is version 1.2, project version is version 1.1".
I am using IBM Rational Application Developer as my IDE, Tomcat 5.0 as my target server and I'm compiling my code with SUNs 1.4.2 JRE.
I created the tag library as a java project and my web site as a dynamic web project in IBM RAD.
If anyone can tell me why I'm getting this error message and, if possible, how to fix it I would be very grateful.
Thanks in advance,
Alex

Evening all,
I am trying to import a tag library into my web
project but I keep getting the error "Incompatible
versions: Tag library is version 1.2, project version
is version 1.1".1.1 and 1.2 might be referring to the servlet spec level supported by each.
I am using IBM Rational Application Developer as myIDE, Irrelevant, I believe.
Tomcat 5.0 as my target server and Tomcat version 5 implements the Servlet 2.4 and JavaServer Pages 2.0.
I'm compiling my code with SUNs 1.4.2 JRE.That's fine.
>
I created the tag library as a java project and my
web site as a dynamic web project in IBM RAD.I wonder if all you have to do is recompile and repackage your tag library. Maybe it's an older library that has to be updated to the spec supported by Tomcat 5.0
If anyone can tell me why I'm getting this error
message and, if possible, how to fix it I would be
very grateful.
Thanks in advance,
AlexSee if that helps, Alex.
%

There is an incompatible version of Nokia PC Suite...

Hi,
I just installed Nokia OVI Suite for my N97 and after reboot my PC, i tried to open OVI Suite but it gave me following error;
"There is an incompatible version of Nokia PC Suite installed on your PC. Please, uninstall it, or upgrade to recent version of Nokia PC suite.
Then re-install Nokia Ovi Suite(PC Connectivity SOLUTİON 8.15)"
Then I uninstalled all Nokia PC SUite and OVI and only installed OVI and reboot the PC again I got same error even I don't have PC Suite anymore.
Then I installed latest version of PC Suite and reboot the PC and again I got the same error.
I'm using Win XP Prof 2002 SP3.
Can you help me how can I fix this problem?
Thanks,

Hi,
It all depends on you
What applications you want to use does matters here
/discussions/board/message?board.id=pcsuite&message.id=31544#M31544
Now we have a lot of expectations in Nokia OVI Suite 2.0 which is in betalabs
Our expectation is
Nokia OVI Suite 2.0 = Nokia PC Suite 7.1.30.9 + Nokia NSeries PC Suite 1.x version + Nokia OVI Suite 1.1x version.
As of now, Nokia OVI Suite 2.0 is on nokia.com/betalabs. Once Nokia OVI Suite 2.0 is LIVE, there wont be any other desktop applications, which will do all other existing pc suites of Nokia does.....
If you are still intrested in Nokia OVI Suite 2.0, you can check this application in Nokia betalabs.... It will do more than what current PC suites of Nokia does
Message Conversation, Connection to Nokia OVI.com etc.,

BerkeleyDB & Incompatible versions of libdb & db.h

Hi all
I've been using the Postgrey[*1] package on a mailserver for about 12 months now without any trouble. Did my semi-regular system upgrade over the w/e and since have been unable to get it to start.
Additionally, the amavisd-new [*2] AUR package has also stopped working with the same error, although I've managed to find a work around for the moment.
# /etc/rc.d/postgrey start
:: Starting Postgrey [BUSY]
BerkeleyDB needs compatible versions of libdb & db.h
you have db.h version 5.2.28 and libdb version 5.2.36
Compilation failed in require at /usr/sbin/postgrey line 16.
BEGIN failed--compilation aborted at /usr/sbin/postgrey line 16.
[FAIL]
I get an identical error message when starting amavisd-new, but there's a flag to disable the db, which I has set so at least that's able to run.
I've tried updating both the per-berkeleydb packages and the postgrey packages but I still receive the same error. I've also installed them via the ABS, but as I didn't make any changes it didn't yield any results.
Is anyone using postgrey with an up-to-date system?
Any help would be greatly appreciated.
ETA : I'm currently building core/db via the ABS to see if that helps. If not I thought I might roll back to 5.2.28-1 as core/db has defiantly been updated in my last update.
[*1] - http://www.archlinux.org/packages/commu … /postgrey/
[*2] - http://aur.archlinux.org/packages.php?ID=573
[*3] - http://projects.archlinux.org/svntogit/ … ackages/db
Last edited by hokapoka (2011-10-25 15:15:22)

stephane : I did try to rebuild postgrey too, albeit just a perl script.
Got if fixed, by rolling back the following packages :
core/db => 5.2.28-1
community/perl-berkeleydb => 0.43-6
community/postgrey => 1.34-2
I used the packages that were in /var/cache/pacman/pkg Of course I had to remove all postgrey, amavid-new & perl-berkeleydb before I downgraded core/db to 5.2.28-1. Once I had done that reinstalled all of the other packages both amavisd-new and postfix started without the BerkeleyDB & Incompatible versions of libdb & db.h error.
I guess I need to file a bug now.

CommunicationException - Incompatible versions

Similar Messages

Maybe you are looking for