Upgrade of RTC 3.0 to 3.0.1 fails

After running upgrade script while using web UI, was able to configure all, but when it came to Finish Registration, it fails, with the following exception.

Now that this application's database has been configured, this operation will complete the application's registration with the Jazz Team Server.
Unable to save the consumer key and secret into the application's database. See details for more information.ID CRJAZ1850E

This operation will synchronize the user records stored in the Jazz Team Server into this application.

Hi,

I can only suggest to review the migration log files and the log files of the application and the JTS. Potentially I'd look into the database logs too. If there is any more information you will find it there. I have seen another post with a similar issue here. Unfortunately also with no details that would enable to help.

I can only guess this is about RTC and the 3.0.1 upgrade. On which operating system? What application server? Which database type?

If you can provide more of this vital information, and some hints in the lig files, maybe we can help. You can also create a work item or a PMR (if under support). that would also require to provide the information mentioned above.

The operating System is Windows 2003, Database is DB2,
Both for JTS and CCM
the migration has succeeded as per the logs.
This is the current CCM Log's exception.
I logged in as ADMIN once created a user called rtcadmin and disabled default ADMIN access...when it failed...then I logged in as rtcadmin and tried the steps and when it came to Finalize setup for CCM, getting this error.
SO I tried logging as ADMIN, but the permission was revoked.
What needs to be done?

2011-08-05 19:24:22,196 ERROR com.ibm.team.repository - CRJAZ1455E Error encountered when synchronizing user data between servers in the background. The synchronizer will silently continue to attempt to synchronize the data.
com.ibm.team.repository.common.TeamRepositoryException: CRJAZ1832E The user configured to perform the request "https://ch2dlfi012.in.ibm.com:9443/jts/contributorRecords/?query=since+%3E%3D+%222011-07-22T09%3A09%3A35Z%22%5E%5EdateTime&withExtensions=true" on the JTS is not authorized. There may not be a functional user configured for the oauth consumer, or the functional user that is configured does not have sufficient privileges to perform the requested operation. Connection Error: Unauthorized

The error in the log does not indicate that the user you are logging in does not have the right permissions, but that (as you describe above) the registration process between CCM and JTS did not happen correctly.

This means there is no connection between JTS and CCM that is authorized so that JTS can copy the user data over.

I am not sure why the registration did not happen. I have seen cases with WAS and Tomcat (not sure what appserver you have, you did not provide that information). We were able to detect that trying to connect to https://<server>:<port>/ccm/web or https://<server>:<port>/ccm/scr. If the page is not available I'd try to redeploy CCM. In Tomcat stop the server and delete the folder <instDir>/server/webapps/ccm folder if this is a fresh install.

Restart the server and try to get to the CCM application, at least the web page should be there.

If that is the case, try to run https://<server>:<port>/jts/setup again, log in with you new admin user and see if the ccm application is able to register.

If so, complete the setup. If not, provide what you see.

I am using Tomcat 5.5, how to redeploy the ccm app once again. Does it mean rerunning the upgrade script for CCM?

I am using Tomcat 5.5, how to redeploy the ccm app once again. Does it mean rerunning the upgrade script for CCM?

No, in the installation directory e.g. JazzTeamServer in server/tomcat/webapps delete the directory ccm. That gets created when Tomcat unpacks the ccm.war file in the webapps folder. Next server start it gets recreated. But, this is ONLY a potential solution if indeed the CCM application is not correctly started and not reachable. If that is the case the registration could fail. This is because if you co-install on one tomcat JTS searches the filesystem for ccm.war etc. to create the list of applications to register.

One more thing, if the registration is done JTS and CCM have friends/consumers setup using jts_user and ccm_user which are technical users that do not require to be stored in LDAP.