It's all about the answers!

Ask a question

M6 RTC Client: Client/server version mismatch


Tom Frauenhofer (1.3k58435) | asked Apr 09 '08, 7:21 a.m.
M6 Linux RHEL5, WAS 6.1, DB2

When I install the M6 RTC client using the Installation Manager I get:

Client/server version mismatch logging into 'fredserver'.
Version mismatch accessing service
"com.ibm.team.repository.common.internal.IRepositoryRemoteService". The
client is speaking version "5" and the server expects version "4".

I did notice that the Client Splash Page said Beta2, but the complaint
suggests that client is at a later version than the server, not earlier.

Maybe I've messed something up up .. I'll go re-check.

4 answers



permanent link
Tom Frauenhofer (1.3k58435) | answered Apr 09 '08, 9:22 a.m.
I re-installed the M6 client using the zipfile and I'm still getting
this complaint.

Is there an easy way to confirm the version of the server I've installed ?

David Ward wrote:
M6 Linux RHEL5, WAS 6.1, DB2

When I install the M6 RTC client using the Installation Manager I get:

Client/server version mismatch logging into 'fredserver'.
Version mismatch accessing service
"com.ibm.team.repository.common.internal.IRepositoryRemoteService". The
client is speaking version "5" and the server expects version "4".

I did notice that the Client Splash Page said Beta2, but the complaint
suggests that client is at a later version than the server, not earlier.

Maybe I've messed something up up .. I'll go re-check.

permanent link
Matthew Jarvis (2411) | answered Apr 09 '08, 9:49 a.m.
JAZZ DEVELOPER
David, since your client version is higher than the version expected by the server version, it sounds like the server is still using some old libraries. I have had this experience with WAS before... When uninstalling or upgrading an application, the temp directories are not always cleaned out, and the server uses some old JARs left over from the previous installation.

I would suggest:

1.) Uninstall the Jazz application from the WAS server
2.) Clean out all the WAS temp directories
3.) Re-install the Jazz application on the server

Hope that helps.

Matt Jarvis
Jazz Developer, Web UI

permanent link
Tom Frauenhofer (1.3k58435) | answered Apr 09 '08, 10:17 a.m.
Hi Matt

Yes, I am aware of that problem with WAS, and I thought that I had done
that clean-out work before installing ... but ...

I'll take your advice and cleanup and re-install the server.

mjarvis wrote:
David, since your client version is higher than the version expected
by the server version, it sounds like the server is still using some
old libraries. I have had this experience with WAS before... When
uninstalling or upgrading an application, the temp directories are
not always cleaned out, and the server uses some old JARs left over
from the previous installation.

I would suggest:

1.) Uninstall the Jazz application from the WAS server
2.) Clean out all the WAS temp directories
3.) Re-install the Jazz application on the server

Hope that helps.

Matt Jarvis
Jazz Developer, Web UI

permanent link
Tom Frauenhofer (1.3k58435) | answered Apr 09 '08, 1:53 p.m.
I've confirmed that I have a WAS issue .. If I bring up Tomcat, my RTC
client connects just fine.

So, I carefully did the following:

1) stopped the jazz app in WAS
2) uninstalled the Jazz app in WAS
3) did a find command to locate anything starting with jazz in the WAS
directory tree (i.e. jazz* files and directories)
4) removed anything that 3) showed
5) re-confirmed that "find . -name jazz\*" showed nothing
6) re-installed and restarted jazz in WAS

My RTC client still complains about version mismatches.

I tried bouncing the entire WAS server and that also didn't help.

Perhaps I need to delete something that is not in a directory beginning
with jazz* ?

mjarvis wrote:
David, since your client version is higher than the version expected
by the server version, it sounds like the server is still using some
old libraries. I have had this experience with WAS before... When
uninstalling or upgrading an application, the temp directories are
not always cleaned out, and the server uses some old JARs left over
from the previous installation.

I would suggest:

1.) Uninstall the Jazz application from the WAS server
2.) Clean out all the WAS temp directories
3.) Re-install the Jazz application on the server

Hope that helps.

Matt Jarvis
Jazz Developer, Web UI

Your answer


Register or to post your answer.