System Z Build: Versions Problems?
![]()
Hi,
I'm trying to do a compilation with RTC Enterprise Extensions in System Z. Get an error in the log: * fetch: * * BUILD FAILED * com.ibm.team.repository.common.TeamRepositoryException: Error logging in to repository https://192.168.38.120:9443/ccm/. Verify that the repository address and credentials to log in are correct. * at com.ibm.team.build.ant.task.AbstractTeamBuildTask.initializeRepositoryManager(AbstractTeamBuildTask.java:324) * at com.ibm.team.build.ant.task.AbstractTeamBuildTask.getTeamRepository(AbstractTeamBuildTask.java:270)*... * Caused by: com.ibm.team.repository.client.ServerVersionCheckException: El cliente es de la versión 4.0.1 y el servidor es de la versión 4.0.0.1. Estos servidores no son compatibles. However, looking through the versions Installation Manager, all are 4.0.0.1 I attached log and Installation Manager screens to verify it. Client: IBM Installation Manager - Ofertas instaladasIBM Installation Manager Versión 1.6.2 (1.6.2000.20130301_2248)
Server:
IBM Installation Manager - Ofertas instaladasIBM Installation Manager Versión 1.6.2 (1.6.2000.20130301_2248)
|
Accepted answer
![]()
The client here is your Build System Toolkit installed on the System z and it is at version 4.0.1, but your server is at version 4.0.0.1, which is not compatible. You either need to upgrade your server or install the 4.0/4.0.0.1 Build System Toolkit on System z.
Silvia Bosca selected this answer as the correct answer
|
5 other answers
![]()
Ralph Schoon (62.7k●3●36●43)
| answered Apr 04 '13, 7:31 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I can only guess, because just because IM lists what it had installed does not necessarily relate to the version that you are working against.
Caused by: com.ibm.team.repository.client.ServerVersionCheckException: El cliente es de la versión 4.0.1 y el servidor es de la versión 4.0.0.1. Estos servidores no son compatibles. However, looking through the versions Installation Manager, all are 4.0.0.1 I have seen this error coming up not only if the version is wrong, but also sometimes if the repository can not be reached e.g. due to a wrong public URI. I would check the connection for example with another client. * com.ibm.team.repository.common.TeamRepositoryException: Error logging in to repository https://192.168.38.120:9443/ccm/. Verify that the repository address and credentials to log in are correct.There is another thing that is most concerning.You should never, ever, ever use an IP address as public URI, nor should you use it in any automation for various reasons. One reason is that in most environments machines lease the IP address and might get a new one every now and then. |
|
![]()
I sent three images, but they are not visiable...
There are Build Engine (build Agent) and the started task... |
![]()
Hello Silvia.
You have to noticed that RTC has the URL fixed at installation time, for that it is not the same try to connect to server name or IP, sample: If you have the connection URL https://ladera20s.data.es:9443, yo cannot connect to https://192.168.38.120:9443. So I would try firstly to executed from your mainframe "TSO PING ladera20s.data.es". Maybe your mainframe system does not reach to RTC server. If this is the problem, it is easy, you will have to add the server in your IPNODES file inside TCPPARMS library and refresh TCP daemon. Good luck and regards. PD: ¿Como andas? ;-P |
Comments
Can you help me with this problem? Thanks in advance!! Silvia