Running migration script results in “Upgrade script failed: Not reading the teamserver.properties file properly” error
Frederic Fusier
Last Updated: December 6, 2011
Build Basis: Rational solution for Collaborative Lifecycle Management 2011
More Information
Attempts to run one of the IBM Rational Team Concert, Rational Quality Manager or Rational Requirements Composer upgrade scripts results in the error find: ‘/C’: No such file or directory.
Symptoms:Some unexpected error message(s) are raised by the find
command while running one of the migration scripts (such as jts_upgrade.bat, ccm_upgrade.bat, qm_upgrade.bat or rm_upgrade.bat).
Sample error:
find: '/C': No such file or directory
find: 'com.ibm.team.repository.server.webapp.url': No such file or directory
Missing operand
Refer to Jazz work item 177128 for other error message sample.
Upgrade scripts fails to read the CLM Server teamserver.properties
when find.exe command found on the Microsoft Windows system path is not the one in the default %SystemRoot%system32 directory (SystemRoot = C:Windows in common Windows installation). This can happen when another installed application (such as Cygwin from work item # 177128 issue) also have a find.exe command and has set its own path set before the Windows system 32 path during its installation. As the upgrade script calls the find.exe command without absolute path, it incorrectly uses the application (find) command instead of the Windows one.
Resolving the problem:
Change the PATH Windows environment variable so as to have C:Windowssystem32 at the beginning. This will enable the correct Windows find command to be called while running the migration scripts.
Note: The PATH variable can be reverted to its initial value after the upgrade.
Copyright © 2011 IBM Corporation