com.ibm.rqm.asynchronous.migration.framework getMigrator Failed to instantiate migrator from plugin definition migratorId SuspectResultStatusMigratorForTCERs
When that was after configuration, go to https://elmtest.com:9443/jts/setup, when in the database configuration, process card, SystemOut. Log an error
Details are as follows:
000001c8 framework E com.ibm.rqm.asynchronous.migration.framework getMigrator Failed to instantiate migrator from plugin definition migratorId SuspectResultStatusMigratorForTCERs
com.ibm.team.repository.common.transport.TeamServiceRegistryException: CRJAZ1972E The "com.ibm.rqm.execution.service.migration.async.SuspectResultStatusMigratorForTCERs" service failed to activate because a service that it depends on, "com.ibm.rqm.planning.common.service.IManualExecutionScriptService", failed to be activated.
caused by "xxxService",failed to be activated
caused by "xxxService",failed to be activated
caused by "xxxService",failed to be activated
....
-------------------------------------------------------------------
db2 can connect to databases, such as JTS, normally. This environment setup is done on a redhat 8.2 VM, which is OK before. Why does this happen
One answer
This question fails to provide the minimum information such as versions etc. Please open a case with support to be guided how to collect the "Must Gather" information.
- The question also seems to not make a lot of sense. It is claimed in the JTS setup database connection step those ETM/RQM errors come up. This is inconsistent.
- It is also unclear if this is a fresh install or an upgrade or what the purpose of this is.
- The claim "db2 can connect to databases, such as JTS" does not make any sense since JTS would connect to the database, not the other way around.
- It is irrelevant if your environment was OK before, if you perform setup and install and you run into problems, the previous state of your system is changed.
Comments
