Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Upgrade error

Hello,
I'm upgrading now RTC from 3.0.1.3 to 4.0.2 .
Because of 4.0.2 version needs WAS 8 - I'm installing the 4.0.2 on a new WAS.
JTS upgrading seceded but CCM gave the following error:
[wasadm@scmt <> /products/IBM/JAZZ/402/JazzTeamServer/server]$ upgrade/ccm/ccm_upgrade.sh -oldApplicationHome /products/IBM/JazzTeamServer/server/conf -updateTomcatFiles no
....
Repo Tools
Provisioning using "./conf/ccm/provision_profiles".
  Change and Configuration Management - Core Libraries, Version 4.0.2 (RTC-I20130222-1633)
  Jazz Foundation - Core Libraries, Version 4.0.2 (RJF-I20130222-1204)

CRJAZ1363I Loading the configuration from "bundleresource://363.fwk1540447185/teamserver.properties".
Validating JTS configuration files...
Checking the old application version...
CRJAZ2129E An error occurred while checking the version of the old application. More information "The version string "  -Dcom.ibm.team.repotools.rcp.allowInvalidBundles=true" is not properly formatted.".
CRJAZ2123E The old application version could not be determined.  Verify that the oldApplicationHome is pointed at the correct installation and specify the version using the oldApplicationVersion parameter.

The ccm upgrade failed at step 0.  Correct the problem and run the script again starting at step 0.

Variable oldApplicationHome is pointing to the right path.
I removed our custom plugins from /products/IBM/JazzTeamServer/server/conf/ccm/sites/
and provision_profiles libraries.
How can I uninstall plugin without running the application ?
What should I do ?


0 votes

Comments

Hi Yehiel, it would be great if you can post back if the technote Kot has pointed out has resolved the problem.


Accepted answer

Permanent link

The following technote talks about similar error when upgrading to 4.0.

http://www-01.ibm.com/support/docview.wss?uid=swg21608026

New URL to the technote: https://supportcontent.ibm.com/node/213009

Yehiel Glass selected this answer as the correct answer

4 votes

Comments

I agree with Kot.  This has resolved the same error for me in the past a couple of times.  

I am sure it does most of the time but believe me I hit a scenario where it didn't

Hey Josh/Kot, no offense intended here and to share my past experience, take a look at this post. I am pretty sure I did tried that technote and after running the repotools with -clean, it complained about the missing bundles and was still stuck with the upgrade.

1 vote


One other answer

Permanent link
Hello Kot,
Your link solved the problem and I finished the upgrade process successfully.
Thanks !

0 votes

Your answer

Register or log in to post 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 2,357

Question asked: Jun 12 '13, 10:40 a.m.

Question was seen: 6,555 times

Last updated: Sep 29 '20, 3:13 p.m.

Confirmation Cancel Confirm