It's all about the answers!

Ask a question

RTC 4.0 upgrade issue: CRJAZ0683I - com.ibm.team.process


Vivek Iyer (15212527) | asked Jul 27 '12, 12:52 p.m.
retagged Nov 05 '12, 12:33 p.m. by Bo Chulindra (1.3k2718)
All,

Our admins ran into this issue upgrading to RTC 4.0.

It looks like a process configuration is failing an update because one of our sysadmins left and his account is archived. We unarchived his account and made a 2nd attempt, but that failed too. I wanted to bring this to the community's attention to ask if anyone has seen it before, and if IBM has any suggestions.

Thanks,

Vivek

CRJAZ0683I An error occurred during the post-import handler for the "com.ibm.team.process"
namespace. CRJAZ0698E The user with the user ID of "*****" and name "****, ****" cannot
be used to perform the attempted operation. For more details, open the help
system and search for CRJAZ0698E..
See the log file "****\RTC4-0\server\repotools-jazz_addTables.log"
for details.
CRJAZ1791E **ERROR** Migration completed with errors. The
imported database is in an inconsistent state and should not be used without
further analysis.
The ccm upgrade failed at step 1.  Correct the problem
and run the script again starting at step 1.
	
	
The "repotools-jazz_addTables.log" file has this snippet:
>
2012-07-27 10:49:51,513 Running post addTables for "com.ibm.team.foundation.wiki"...
2012-07-27 10:49:51,513 Post addTables for com.ibm.team.foundation.wiki took 0 ms.
2012-07-27 10:49:51,513 Running post addTables for "com.ibm.team.process"...
2012-07-27 10:50:08,061 CRJAZ0683I An error occurred during the post-import handler for the "com.ibm.team.process" namespace.	
com.ibm.team.repository.common.LoginFailureException: CRJAZ0698E The user with the user ID of "*****" and name "*****, *****" cannot be used to perform the attempted operation. For more details, open the help system and search for CRJAZ0698E.
at com.ibm.team.repository.service.internal.permission.ImpersonationService.pushImpersonation(ImpersonationService.java:198)
at com.ibm.team.repository.service.internal.permission.ImpersonationService.callAs(ImpersonationService.java:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:600)
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 $Proxy305.callAs(Unknown Source)
at com.ibm.team.process.internal.service.migration.ProcessMigrationHandlerTo21.userHasReadAccess(ProcessMigrationHandlerTo21.java:278)
at com.ibm.team.process.internal.service.migration.ProcessMigrationHandlerTo21.migrateProcessSharingRoleAssignments(ProcessMigrationHandlerTo21.java:228)
at com.ibm.team.process.internal.service.migration.ProcessMigrationHandlerTo21.postAddTables(ProcessMigrationHandlerTo21.java:387)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:600)
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 $Proxy1326.postAddTables(Unknown Source)
at com.ibm.team.repository.migration.internal.service.MigrationHandlerDispatcher.doPostAddTables(MigrationHandlerDispatcher.java:688)
at com.ibm.team.repository.migration.internal.service.MigrationHandlerDispatcher.postAddTables(MigrationHandlerDispatcher.java:680)
at com.ibm.team.repository.service.internal.rdb.DatabaseMaintenanceService.performPostAddTables(DatabaseMaintenanceService.java:1379)
at com.ibm.team.repository.service.internal.rdb.DatabaseMaintenanceService.performPostAddTables(DatabaseMaintenanceService.java:337)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:600)
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 $Proxy200.performPostAddTables(Unknown Source)
at com.ibm.team.repotools.commands.local.internal.AddTablesCommand$1.run(AddTablesCommand.java:84)
at com.ibm.team.repotools.commands.local.internal.AddTablesCommand$1.run(AddTablesCommand.java:1)
at com.ibm.team.repository.service.internal.TeamServiceContext.runAsAdmin(TeamServiceContext.java:141)
at com.ibm.team.repotools.commands.local.internal.AddTablesCommand.addTables(AddTablesCommand.java:59)
at com.ibm.team.repotools.commands.local.internal.AddTablesCommand.execute(AddTablesCommand.java:164)
at com.ibm.team.repotools.command.AbstractCommand.execute(AbstractCommand.java:66)
at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.run(RepositoryToolsApplication.java:768)
at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.start(RepositoryToolsApplication.java:843)
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:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:600)
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)
2012-07-27 10:50:08,076 Post addTables for com.ibm.team.process took 16563 ms.
2012-07-27 10:50:08,076 Running post addTables for "com.ibm.team.apt.resource"...
2012-07-27 10:50:08,076 Post addTables for com.ibm.team.apt.resource took 0 ms.
	
	
	
	
	
	
	

2 answers



permanent link
Martha (Ruby) Andrews (3.0k43951) | answered Jul 27 '12, 3:12 p.m.
JAZZ DEVELOPER
Hello Vivek,

This error occurs when:
 -- There is a user who cannot log into the repository
 -- The user is a member of a project area that is a process provider
 -- The process is consumed by one or more project areas that do not have public visibility.

I have filed defect 219632 (Error in migrating if member of a process provider project area no longer exists (219362)) for this issue. To workaround the issue, you can remove the user from the Members list of all project areas that provide process in your 3.x application, then run addTables again.

Martha (Ruby) Andrews
Jazz L3 Developer

Comments
Vivek Iyer commented Jul 27 '12, 3:20 p.m.

Thanks Martha. We just checked, but did not find this person's membership included any project areas that provided process. He was in project areas that inherited the process from another project area though. We removed him from all project areas and will give it another shot.

Thanks,

Vivek


Vivek Iyer commented Jul 27 '12, 3:23 p.m.

On a side note, do I need to worry about all archived users who are members of any project or team areas?

Thanks!

Vivek


Martha (Ruby) Andrews commented Jul 27 '12, 3:34 p.m.
JAZZ DEVELOPER

From my reading of the code, only members of the process provider should cause this error. Is it possible that there is an archived process provider project area that the user is still a member of? To answer your second question, you should only need to be concerned about archived users who are members of process provider project areas.


permanent link
Clement Liu (1.5k54149) | answered Sep 13 '12, 1:40 p.m.
We found out the database was actually corrupted...can't even log in JTS to remove the archived user from the project areas. We had to restore the database from a nightly backup first...

Your answer


Register or to post your answer.