Build Forge 7.1.3.3 with RTC 4.0 causing issues while creating the build engine.
Nanda Kumar (1●1●2●2)
| asked Sep 11 '12, 1:16 p.m.
edited Sep 11 '12, 5:19 p.m. by Seth Packham (1.4k●4●22●13)
I have BuildForge 7.1.3.3 on RHEL 5 server and RTC 4.0 on AIX server. The build engine "test connection" in RTC is success only for the first time. The ID, password that iam using in build engine tab (Build forge authentication fields) is being locked in BuildForge 7.1.3.3 console after the first successful attempt. Subsequent test connection attempt's in RTC fail's with the following error
"Testing, please wait... Result: Failed. A com.buildforge.services.common.api.APIException exception occurred testing the connection. Verify the user id and password specified and retry. The logs should have more detailed information about the exception" Can some body help on this ?? |
One answer
Create a new user id in BF and set RTC to use the new user. See if that user doesn't get locked out. Chances are that an engine in RTC is using a bad password and is locking out your BF id. RTC will retry the credentials every 15 seconds so it will lock an id in no time.
Use the URL <CCM server>/resource/virtual/build/engines?_prettyPrint=true to get a list of engines if you really want to save that old user id, and find the bad password.
|
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.