RQM 3.0.1.1 "upgrade" - falling at the first hurdl

Turns out this was a permissions issue. Of course, I have to run the command prompt as Administrator! Duh.

Upgrade of jts and qm successful. ccm failed. RQM now hosed. Glad I snap-shotted my VM before starting. Needless to say, I won't be trying to "upgrade" the production system.

Turns out this was a permissions issue. Of course, I have to run the command prompt as Administrator! Duh.

Upgrade of jts and qm successful. ccm failed. RQM now hosed. Glad I snap-shotted my VM before starting. Needless to say, I won't be trying to "upgrade" the production system.

David,

Glad to hear that you found the root cause of this error.

If possible, I would get your CLM installs out of "Program Files (x86)" ASAP. Recent Windows releases (7, 2008, 2008 R2, etc) impose all kinds of restrictions on virtualized folders. These can manifest in a bunch of "weird" issues whenever a process which was not explicitly invoked with the "run as administrator" context menu option attempts to read/write/execute any file within the virtualized folder. I have also sees issues when a process (example: an executable) running from a virtualized folder attempts to read/write/modify environment variables, the registry, etc.

My strong recommendation is to always install CLM (and all other IBM Rational QA products such as RFT, RPT, Robot, etc) in a non-virtualized folder. For example, install CLM here: C:\IBM\JazzTeamServer\. This will save you a lot of headaches now and down the road.

Regards,
Patrick

Thanks for the response Patrick.

I confess that I didn't really know what a virtualised directory was when I started on this. Anyway, both the production environment and the VM test bed are in "Program Files (x86)". With both working well, the prospect of a reinstall and resetup followed by moving all the data is not attractive.

I will try installing 3.0.1.1 to C:\IBM\JazzTeamServer\ and running the upgrade scripts on the VM and see how that goes.

Regards, Dave.