The information in this article applies to:
SYMPTOMSBuilding applications from the integrated development environment (IDE) may fail, with the following message subsequently displayed in the output window: The message does not identify why the build could not be performed. CAUSEThere are several known causes for this message:
RESOLUTIONThe following are four suggested resolutions: Resolution 1: Install or Re-Enable NULL Device (Windows NT Only)There are slight variations on the displayed error text. These variations can sometimes help to identify what is causing the problem. If the error text resembles the following, you may have problems opening the NULL device:Use the following steps to check on the NULL device:
Resolution 2: Correct the IDE EnvironmentIf you have the following error text variation, you probably have errors in the ComSpec definition or the IDE environment, which specifies where to find the tools:See Resolution 4 below for information about correcting the ComSpec definition. To correct the IDE environment:
Resolution 3: Use the System EnvironmentAn alternative way of specifying the executable paths is to use the /USEENV argument when starting MSDEV (Visual C++). The command line resembles the following:
This action forces Visual C to use the system environment settings rather than the directories specified in Options under the Tools menu. This will help if the system environment variables are all correct; for example, if you can build successfully from a command prompt.NOTE: Resolution 2 is usually recommended over using the /USEENV switch. For additional information about a bug that was fixed in Service Pack 3, please click the article number below to view the article in the Microsoft Knowledge Base: Q216854 FIX: Running msdev /useenv Once Causes Environment To Be Used Permanently Resolution 4: Correct the ComSpec Environment Variable DefinitionIf the paths look correct (see Resolution 2), the problem may be with the ComSpec environment variable. The ComSpec environment variable identifies the command prompt executable. On Windows NT, this usually resembles the following:
On Windows 95 or Windows 98, it typically resembles the following:
To check, set, or change the value of the ComSpec environment variable:
STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. REFERENCESFor additional information about this subject, please click the article numbers below to view the articles in the Microsoft Knowledge Base: Q189138 PRB: "error spawning empfile.exe" Building WINCE Application Q188720 PRB: Error Executing ~vcecho!Compiling Additional query words:
Keywords : kbVC600bug kbDSupport |
Last Reviewed: August 26, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |