Jazz Build Engine fails to connect to RTC after upgrade to 6.0.5
![]() We recently upgraded an RTC 4 instance to 5, and afterwards to 6.
An error response was received from the Jazz Team Server. Status=400. Message: CRJAZ1848E To perform the "Control The Build Lifecycle" operation, the user (userid="ADMIN") must have one of the following licenses that are installed on the server: Rational Team Concert.Developer-Floating, Rational solution for Collaborative Lifecycle Management.Practitioner. The server administrator can assign licenses.. The error description is: An error response was received from the Jazz Team Server. Status=400. Message: CRJAZ1848E To perform the "Control The Build Lifecycle" operation, the user (userid="ADMIN") must have one of the following licenses that are installed on the server: Rational Team Concert.Developer-Floating, Rational solution for Collaborative Lifecycle Management.Practitioner. The server administrator can assign licenses. The problem is the build engine is not started with the ADMIN user id specified in the error. We start it a user created specifically for builds, with the following license assigned: Rational Team Concert - Build System The command line used to start the jbe is: ./jbe -repository https://rtc-hostname:9443/ccm -userId Builduser -passwordFile /path/to/passwdfile -engineId Build_4 JBE version is 6.0.5, JTS and CCM is 6.0.5 as well. All servers involved are running on RHEL 7.4 Any ideas on what the problem would be? |
2 answers
![]()
Ralph Schoon (61.8k●3●36●43)
| answered Apr 17 '18, 4:40 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER There is something very wrong and confusing. Since you don't provide any thing in form of how you start the JBE there is no way we can tell.
Comments The command line used to start the jbe is:
What Java Version is used. Do you provide any VM in the JBE.ini? E.g. see https://rsjazz.wordpress.com/2015/04/07/the-day-the-jbe-stood-still/
I made progress by assigning a Rational Team Concert - Build System license to the ADMIN user, as it is a member of this project area even though the user is not in the user directory. I think this might be a miss-configuration from the old version. This project area is very old.
I agree. I don't understand that part with "Admin" either. The only Idea I have would be to try different -userId builduser -pass buildpassword combinations. I have been seeing ADMIN used in this context for quite a while now. As far as the OP goes, the addition of the Build license is insufficient as stated in the original message.
But if you set BuildUser as the user to run the JBE, you don't want and don't expect ADMIN to be used.
showing 5 of 6
show 1 more comments
|