Problems Running the Software Parts Manager (Windows)

The following items list the solutions for several problems commonly encountered when using SPM in the Windows environment

Unlocking Products From the partmgr executable:

• If you are unable to unlock a product, the most likely cause is an incorrect customer tracking number. Each unlock code is only valid with a specific customer tracking number. You can check the customer tracking number by selecting 'Customer Information' under the 'Misc' menu item.

Building Products From the partmgr executable:

The configuration process in the SPM dies with the error:

We will invoke the compiler like this: (.cpp may change if needed) 
     cl   -c something.cpp 
 ... and the link step like this: 
     cl  something.obj    
 We will start by trying to discover which file extension your compiler accepts.  This may take a few moments... 
 Trying suffix .cpp ...no Trying suffix .C ...no Trying suffix .cc ...no Trying suffix .cxx ...no 
   *** Something went wrong.  Probably one of the following:
   
 
 ***  o  cl does not exist;   
 ***  o  cl is not in your path;   
 ***  o  You do not have write permission in the current directory;   
 ***  o  Your compiler does not like any of the file suffixes I tried. 
   Here are the outputs from the attempts to compile: 
 Trying to compile with suffix .cpp cl: configCompile: rwsetup 2288: not found 
Trying to compile with suffix .C cl: configCompile: rwsetup 2288: not found 
Trying to compile with suffix .cc cl: configCompile: rwsetup 2288: not found 
Trying to compile with suffix .cxx cl: configCompile: rwsetup 2288: not found 
 exiting rwenv:  ERROR 1

This problem is caused by the directories containing the Microsoft C++ Compiler not being included in the current path. Microsoft provides a file called vcvars32.bat that will correctly configure your environment for the Microsoft C++ Compiler. You can find out the location of this file by performing a search in Windows Explorer. There are two ways to update your current path information.

• You can update your PATH system environment variable to include the directories that are set in the vcvars32.bat file. This will allow the Software Parts Manager to find the compiler even after the system has been rebooted.
• You can reinstall MSVC++. During the installation process, a check box will come up asking if you wish to add the VCVARS32.bat to your environment. Check the box and proceed with the installation.
• You can start a Command Prompt, change into this directory, and then execute the vcvars32.bat batch file. Once the batch file has run, change directories into the SPM directory and run the partmgr executable.

If you get errors about 'Out of Environment Space', you can fix these errors by starting another environment with enough environmental space as follows:

C:COMMAND.COM /E:8192