Common problems encountered with configuration management operations

Here are some common problems that you might encounter with configuration management operations.

Unable to connect to SCC-Compliant configuration management tool (SCC mode)

When you install an SCC‑compliant configuration management tool, a tool‑specific DLL is installed on your PC. When invoking a configuration management operation, IBM Rational Rhapsody looks for an entry for this DLL in the system registry. If it finds one, it loads the DLL and executes the configuration management operation with that tool. If Rational Rhapsody cannot find the DLL for the correct SCC tool, it generates an error message. The ProviderRegKey value of the SourceCodeControlProvider key in the system registry (under HKEY_LOCAL_MACHINE\SOFTWARE) stores the location of the DLL for the default configuration management tool.

Note: The SCC interface is currently supported on Windows platforms only.

It is possible to have multiple SCC‑compliant tools installed on the same system. In this case, there are multiple entries under the InstalledSCCProviders key (under HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider). For example:

PVCS Dimensions: REG_SZ: Software\SQL Software\PcmcScc
Microsoft Visual SourceSafe: REG_SZ: Software\Microsoft\
                                    SourceSafe
ClearCase: REG_SZ: Software\Atria\ClearCase

If the ProviderRegKey value does not correspond to the configuration management tool you want, select one of the installed SCC‑compliant configuration management tools using a registry editor (for example, Regedt32) and edit the ProviderRegKey value of the SourceCodeControlProvider key with the information from InstalledSCCProviders for the SCC tool you want to use.

For example, to use PVCS Dimensions, edit the ProviderRegKey value with the following string:

   Software\SQL Software\PcmsScc

Unable to create process message (batch mode)

In some cases, there are problems with the standard echo command on the Windows 98/NT operating system.

If you receive an "Unable to create process" message while connecting to an archive because of an echo (either during a Connect operation or as a subtask of another configuration management operation), try to execute the same operation from a command prompt.

If the result is another message similar to "Unrecognized command," correct the PATH variable for your environment. The PATH variable must include the full path in which the command to be executed is located.


Feedback