It's all about the answers!

Ask a question

RTC 5.0.2 client and RBD 9.0.1


Ivan Bogovic (931311) | asked May 15 '15, 9:16 a.m.

On some workstations (Windows 7), after upgrade to RTC 5.0.2, on connect with RTC server, RBD returns a error: 

"CRJAZ6024E Cannot log into the server, 'rtc01.zbo', because that server cannot be contacted. Make sure that the server is running and available.

CRJAZ1371E The following URL cannot be reached: https://rtc01.zbo:9443/ccm/versionCompatibility?clientVersion=5.0.2. The server cannot be reached. The network could not connect to the server. Error details: Connection refused: connect.Connection refused: connect"


IBM Installation Manager Installed packages:

IBM Data Studio client Version 4.1.1 (4.1.1.20140731_1945)

IBM® Rational® Business Developer Version 9.0.1 (9.0.1000.RBDO901-I20131205_2314) 64 bit

Rational Team Concert - Client for Eclipse 4.2.x IDE Version 5.0.2 (5.0.2000.RTC-...   


Do you have any suggestions or could you point me in some direction?

Thank you,

Ivan Bogovic







Comments
Donald Nong commented May 17 '15, 9:53 p.m.

There are quite a few things to consider.
1. Is there a firewall between the said workstations and the RTC server?
2. How is the SSL connection implemented on the RTC server (default Tomcat, customized WAS, or something else)? In particular, does the SSL connection require a client certificate?
3. Is possible, do a network trace between a problematic workstation and the RTC server, and check why the SSL connection cannot be established.


Ian Wark commented May 18 '15, 3:51 a.m.

I think there may be an incompatibility between the RTC and RBD Eclipse client versions. Looking at RBD and RTC integration in the clarity reports, it suggests that RBD 9.1 can integrate with RTC 4.0.3 to 4.0.7, but to integrate with RTC 5.0.x you need to have RBD 9.1.1.

RBD and RTC integration


One answer



permanent link
Ivan Bogovic (931311) | answered May 18 '15, 6:14 a.m.
Thank you,
issue is resolved. There was issue with port 9443 in RTC server adress. After we removed port number from URL, everything works fine. We didn't investigate further.

Thank you all for your suggestions.

Regards, 
Ivan Bogovic   

Your answer


Register or to post your answer.