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

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.

Related Information

The following links point to related information:

• repotools-jazz -migration_qm_updateConfigurationFiles command looks for files in the wrong install directory (166638)
• Should be able to use 3.x upgrade batch files from same command window as 2.x repotools (167080)