Why is script ccm_upgrade.bat failing while upgrading to 5.0.1?
We are currently upgrading our development environment from RTC 4.0.7 to 5.0.1 on a single server implementation. JTS upgraded successfully but CCM will not.
The error we get is as follows after we run the following command from
C:\Program Files (x86)\IBM\JazzTeamServer_5.0.1\server>upgrade\ccm\ccm_upgrade.bat -oldApplicationHome "C:\Program Files (x86)\IBM\JazzTeamServer_4.0.7\server\conf" -updateTomcatFiles no
The error:
\IBM\JazzTeamServer_4.0.7\server"\repotools-ccm.bat" was unexpected at this time.
The path to the old application home is set in double-quotes. We have been using this path to store all our server installs since RTC 3.X as show below:
Directory of C:\Program Files (x86)\IBM
09/15/2014 01:25 PM <DIR> .
09/15/2014 01:25 PM <DIR> ..
06/12/2014 02:33 PM <DIR> HTTPServer855
09/15/2014 02:13 PM <DIR> IBMIMShared
09/15/2014 12:50 PM <DIR> Installation Manager
09/15/2014 01:23 PM <DIR> JazzTeamServer
09/15/2014 01:23 PM <DIR> JazzTeamServer_1
09/15/2014 01:23 PM <DIR> JazzTeamServer_2
09/15/2014 01:23 PM <DIR> JazzTeamServer_3
09/15/2014 12:51 PM <DIR> JazzTeamServer_4.0.3
09/15/2014 12:51 PM <DIR> JazzTeamServer_4.0.5
09/15/2014 12:51 PM <DIR> JazzTeamServer_4.0.6
09/15/2014 01:25 PM <DIR> JazzTeamServer_4.0.7
09/15/2014 02:18 PM <DIR> JazzTeamServer_5.0.1
09/15/2014 12:51 PM <DIR> TeamConcert
06/12/2014 02:35 PM <DIR> WebSphere855
0 File(s) 0 bytes
16 Dir(s) 18,127,441,920 bytes free
Seems that it may perhaps have issues with parenthesis in the path. Any ideas?
One answer
I found a solution by using the short form to eliminate any spaces in my paths. So instead of running the command as follows
C:\Program Files (x86)\IBM\JazzTeamServer_5.0.1\server>upgrade\ccm\ccm_upgrade.bat -oldApplicationHome "C:\Program Files (x86)\IBM\JazzTeamServer_4.0.7\server\conf" -updateTomcatFiles no
I used
C:\PROGRA~2\IBM\JazzTeamServer_5.0.1\server>upgrade\ccm\ccm_upgrade.bat -oldApplicationHome "C:\ PROGRA~2\IBM\JazzTeamServer_4.0.7\server\conf" -updateTomcatFiles no
However, this used to work for past releases. I reported it to IBM.