Library > Articles >

Tip: Use a new command prompt for each application upgrade (CLM 2011)

Last Updated: June 13, 2011
Heather Sterling, IBM
Build basis: CLM 2011, Rational Team Concert 3.0.1, Rational Team Concert 3.0, Rational Requirements Composer 3.0.1, and Rational Quality Manager 3.0.1

Summary

If you are performing an upgrade with an upgrade script, you should always use a new command prompt window to avoid environment variable conflicts.

More Information

If you are running repotools commands or running multiple upgrades from a single command prompt, it is possible that the environment variables from a previous command will interfere with the upgrade script. Specifically, we have seen problems when issuing a 2.x repotools command to export data followed by a 3.0.1 upgrade script command. The problem is due to the fact that the 2.x repotools command does not reset all of the environment variables. In this case, the upgrade script will ultimately fail with the error:

“CRJAZ1834E Error provisioning the server.”

In general, it is good practice to use a new command prompt for each upgrade even if you are not running 2.x repotools commands first.

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.
Feedback
Was this information helpful? Yes No 0 people rated this as helpful.