CRJAZ2054E The Jazz Team Server version is not compatible with this application. The version is 4.0.0.1, but it must be in the range [4.0.1,5.1.0).
Aaron Folden (11●1●1)
| asked Oct 09 '12, 12:46 p.m.
edited Oct 10 '12, 11:02 a.m. by Ralph Schoon (63.5k●3●36●46)
Cannot Register Change and Configuration Management in the admin console, full error below
HTTP Status 409 - CRJAZ2054E The Jazz Team Server version is not compatible with this application. The version is 4.0.0.1, but it must be in the range [4.0.1,5.1.0). type Status report --------------------------------------------------------------------------------
showing 5 of 7
show 2 more comments
|
Accepted answer
Andy - see https://jazz.net/forum/questions/163505/has-anyone-installed-git-adapter-with-clm-5-error-in-registering-application According to that post, the adapter is not supported with CLM 5 and the suggestion is to use the native capability in RTC 5.0
Ralph Schoon selected this answer as the correct answer
|
2 other answers
Hi Aaron,
It looks like the application you're trying to register is versioned 4.0.0.1, and it needs to be at least 4.0.1. Comments Thank you.
I will give a reinstall a shot.
@foldena: Actually I think the JTS version is 4.0.0.1 but the application that is trying to get registered requires a JTS version at least 4.0.1. This will happen if the application is version 4.0.1 which requires a JTS at least its version. You will either have to install an application with a version at most the same version as your JTS, or you must upgrade your JTS.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
I wish you would provide a question that one can work with instead of the minimal effort above.
For example which versions are you installing. The message seems to imply a milestone build for 4.0.1. OS, application server (which i can sort of see however).
The better the data you provide the easier to help. Are you trying to mix versions here?
Sorry but I'm not doing this in my spare time - I'm trying to get a product to work correctly so IBM can make some money. If I'm short it's because I have more going on than installing DOORS next. So if we're done not acting professional - what kind of question are you looking for? I installed a product, it isn't working correctly, I gave you the exact error along with what I was doing. That said, I will go ahead and uninstall everything and start from scratch to see if that will help.
Neither are we.
Readers are just looking for the most basic information. Product, Product version, any other details you can think of. In your case, knowing it is a Milestone build or not. Is essential. (Is it a milestone?)
If this basic information missing it is likely that your question will not be answered.
So are you installing a Doors next beta? In this case it would be good to say so and select the product when filing the question so that the tagging helps users to understand the context better.
DOORS Next, Team Concert, and possibly the Architect SW. All on a VM
I'll give you more background. We have been working with DOORS products since DOORS was telelogic, all of our RM work uses DOORS. We are wanting to get a test VM working with the new IBM products so we can evaluate if want to upgrade when the time comes. We met with IBM reps last week to discuss the jazz platform, tokens, etc. So here I am trying to figure out a couple of issues
OK, Aaron, fair enough. From the download page of the latest Doors.Next milestone, I see that it ships all products in its own install download. So I would assume that these products shipped, including the JTS are all 4.0.1 compatible.
I would assume you have to use these products together and you can not use them with a regular 4.0 install for JTS/RTC/QM/RM. If you have more install packages connected to the IM, make sure not to, accidentally, select to install a 4.0 version.
I have not tried that my self, but the error message implies something like that could have happened and the registration, or what ever operation you ran, fails due to it.