It's all about the answers!

Ask a question

Error when trying to finish RRC project migration after upgrade on CLM 4.0


Milan Krivic (98013176143) | asked Jul 17 '12, 4:41 a.m.
edited Jul 17 '12, 4:44 a.m.
Hi,

we have migrated CLM 3.0.1.2 to CLM 4.0. Everything completed well except one part, and that is RRC project migration.
Following the instructions from jazz.net, when I run this address:

https://clm_40_server:9443/rm/web/projects/migration

I clicked on Open the Upgrade Service Panel and proceeded next. After a few moments, I got this error message (look an attachment).

This is the error message:

A non-critical error was encountered that should be addressed before re-attempting this upgrade.

CRRS8084E Upgrade detected that there are no resources to upgrade. This may indicate that indices are invalid or that the RDMFrontingURL property in fronting.properties does not match the one stored in the repository being upgraded. This mismatch can occur if the repository has been copied from another environment. RRC4 upgrade specifically requires that these match.


Also, I have some logs from rm.log file:

2012-07-17 09:55:20,511 [           RRS-async-command-5]  INFO nting.server.rrs.migration.MigrationProgressRecord  - Tracking indexing status..
2012-07-17 09:55:20,791 [           RRS-async-command-5]  WARN om.ibm.rdm.fronting.server.util.ProjectAreaService  - OAuthHelper was unable to get the principal from the request
2012-07-17 09:55:20,947 [           RRS-async-command-5]  WARN gure.internal.ConfigureRegistrationServiceInternal  - CRRRS9646W  A license is already assigned to the functional user: rm_user
2012-07-17 09:55:21,181 [           RRS-async-command-5] ERROR ver.core.request.async.internal.RRSTrackingCommand  - Error executing command
com.ibm.rdm.fronting.server.rrs.migration.PreconditionFailedMigrationException: NO_TYPE_RESOURCES_FOUND
    at com.ibm.rdm.fronting.server.rrs.migration.command.RRC4000M7MilestoneUpgradeCommand.countTypeResources(RRC4000M7MilestoneUpgradeCommand.java:241)
    at com.ibm.rdm.fronting.server.rrs.migration.command.RRC4000M7MilestoneUpgradeCommand.checkPreconditions(RRC4000M7MilestoneUpgradeCommand.java:195)
    at com.ibm.rdm.fronting.server.rrs.migration.command.RRC4000M7MilestoneUpgradeCommand.preMigration(RRC4000M7MilestoneUpgradeCommand.java:108)
    at com.ibm.rdm.fronting.server.rrs.migration.command.BaseMigrationCommand.execute(BaseMigrationCommand.java:153)
    at com.ibm.rdm.fronting.server.core.internal.request.RRSCommandBase.call(RRSCommandBase.java:168)
    at com.ibm.rdm.fronting.server.core.internal.request.RRSCommandBase.call(RRSCommandBase.java:1)
    at com.ibm.rdm.fronting.server.core.request.async.internal.RRSTrackingCommand.call(RRSTrackingCommand.java:90)
    at com.ibm.rdm.fronting.server.core.request.async.internal.RRSTrackingCommand.call(RRSTrackingCommand.java:1)
    at com.ibm.rdm.fronting.server.concurrent.RRSConcurrency$1$1.call(RRSConcurrency.java:66)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
    at java.util.concurrent.FutureTask.run(FutureTask.java:149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
    at java.util.concurrent.ThreadPoolExecutor$Wor
ker.run(ThreadPoolExecutor.java:919)
    at java.lang.Thread.r
un(Thread.java:736)


2 answers



permanent link
Rosa Naranjo (2.9k11723) | answered Jul 18 '12, 1:38 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
Hello
This has been reported as a defect.  Look at the discussion here and join, if desired.
https://jazz.net/jazz03/web/projects/Requirements%20Management#action=com.ibm.team.workitem.viewWorkItem&id=61375

Your answer


Register or 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.