It's all about the answers!

Ask a question

Error while running repotools-rm_finalizeApplicationMigration script to upgrade RQM from v4.0.3 to v5.0.1


Chaitra Elanjickal (31820) | asked Feb 24 '15, 9:32 a.m.

I'm getting the below error while running the repotools-rm_finalizeApplicationMigration script.

CRJAZ2422E An error occurred finalizing the application migration.
com.ibm.team.repository.common.TeamRepositoryException: CRJAZ2642E The migration cannot continue because the application being migrated is not registered with the Jazz Team Server that is being converted for use as the application database.
 at com.ibm.team.repository.migration.internal.service.HybridApplicationMigrationService.setIdOfApplicationMigrated(HybridApplicationMigrationService.java:157)
 at com.ibm.team.repository.migration.internal.service.HybridApplicationMigrationService.finalizeApplicationMigration(HybridApplicationMigrationService.java:99)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
 at java.lang.reflect.Method.invoke(Method.java:611)
 at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
 at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
 at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
 at com.sun.proxy.$Proxy259.finalizeApplicationMigration(Unknown Source)
 at com.ibm.team.repotools.commands.local.internal.FinalizeApplicationMigrationCommand.execute(FinalizeApplicationMigrationCommand.java:84)
 at com.ibm.team.repotools.command.AbstractCommand.execute(AbstractCommand.java:67)
 at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.run(RepositoryToolsApplication.java:816)
 at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.start(RepositoryToolsApplication.java:891)
 at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
 at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
 at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
 at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
 at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
 at java.lang.reflect.Method.invoke(Method.java:611)
 at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
 at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
 at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
 at org.eclipse.equinox.launcher.Main.main(Main.java:1384)

2 answers



permanent link
Martha (Ruby) Andrews (3.0k44051) | answered Mar 06 '15, 5:16 p.m.
JAZZ DEVELOPER
Hello,
The error is because the JTS does not have a Friend entry that matches the one passed in to the finalizeApplicationMigration command.This can happen if you do not pass an application id, or if you pass the wrong application id.

Did you have RM registered with the in the 4.x JTS before you started the migration? If so, is the application id the same as what you are using when your run finalizeApplicationMigration?

Ruby
Martha (Ruby) Andrews
Jazz Foundation L3 Development Team Lead

Comments
Sterling Ferguson-II commented Mar 18 '15, 1:38 p.m.

Hello Martha, I get this error message as well.

The finalization does not ask for an application ID, so where was that supposed to be given?

And yes RM and JTS were friends before migration.


permanent link
Sunil Kumar R (1.1k12743) | answered Feb 24 '15, 10:20 a.m.
JAZZ DEVELOPER
 Hi Chaitra, the issue you are seeing could be a defect, i.e., the finalizeApplicationMigration command failure, the bigger problem is if there is a rerun. See All Project Areas are deleted during upgrade to RDNG 5.0.2 if finalizeApplicationMigration is rerun following a failure

I suggest you create a PMR so that a thorough analysis is done..

Best Regards, Sunil

Your answer


Register or to post your answer.