Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This section is a reference to the errors generated by the Project build tools. Project build errors and warnings have the form PRJxxxx, where xxxx is a four-digit number.
Important
The Visual Studio compilers and build tools can report many kinds of errors and warnings. After an error or warning is found, the build tools may make assumptions about code intent and attempt to continue, so that more issues can be reported at the same time. If the tools make the wrong assumption, later errors or warnings may not apply to your project. When you correct issues in your project, always start with the first error or warning that's reported, and rebuild often. One fix may resolve multiple subsequent errors.
To get help on a particular diagnostic message in Visual Studio, select it in the Output window and press the F1 key. Visual Studio opens the documentation page for that error, if one exists. You can also use the search tool at the top of the page to find articles about specific errors or warnings. Or, browse the list of errors and warnings by tool and type in the table of contents on this page.
Note
Not every Visual Studio error or warning is documented. In many cases, the diagnostic message provides all of the information that's available. If you landed on this page and think the error or warning message needs additional explanation, let us know by using the feedback buttons on this page. If you think the error or warning is wrong, or you've found another problem with the toolset, report a product issue on the Developer Community site. You can also send feedback and enter bugs within the IDE. In Visual Studio, go to the menu bar and choose Help > Send Feedback > Report a Problem, or submit a suggestion by using Help > Send Feedback > Suggest a Feature. Some compiler error topics were created that are not emitted by the compiler and now redirect to this page instead.
You may find additional assistance for errors and warnings in Microsoft Q&A C++ forums. Or, search for the error or warning number on the Visual Studio C++ Developer Community site. You can also search Stack Overflow to find solutions.
For links to additional help and community resources, see Visual C++ Help and Community.
Project build errors
| Error | Message |
|---|---|
| Project build error PRJ0002 | error result returned from 'command line'. |
| Project build error PRJ0003 | Error spawning 'command line'. |
| Project build error PRJ0004 | Could not generate command line for the 'tool' tool. |
| Project build error PRJ0005 | Unable to create a temporary file in directory 'directory'. |
| Project build error PRJ0006 | Could not open the temporary file 'file'. Make sure the file exists and that the directory is not write-protected. |
| Project build error PRJ0007 | Could not create output directory 'directory'. |
| Project build error PRJ0008 | Could not delete file 'file'. |
| Project build error PRJ0009 | Build log could not be opened for writing. |
| Project build error PRJ0013 | System resource could be critically low. Unable to create a pipe required to launch a build. |
| Project build error PRJ0014 | The job object used to control the spawned processes has failed. The build cannot continue. |
| Project build error PRJ0015 | The NULL device is missing from your system. We are unable to launch a build. |
| Project build error PRJ0016 | The user's security settings prevent the process from being created. These settings are required for building. |
| Project build error PRJ0017 | The current working directory is invalid. |
| Project build error PRJ0019 | A tool returned an error code from |
| Project build error PRJ0020 | Tool 'tool', Property 'property' contains invalid file name 'file'. |
| Project build error PRJ0021 | Tool 'tool', Property 'property' contains invalid file name. |
| Project build error PRJ0022 | Unknown Tool, Property 'property' contains invalid file name 'file'. |
| Project build error PRJ0023 | Tool 'tool', Unknown Property contains invalid file name 'file'. |
| Project build error PRJ0024 | Unicode path 'path' could not be translated to user's ANSI code page. |
| Project build error PRJ0025 | Batch file 'file' contains Unicode contents that could not be translated to user's ANSI code page. |
| Project build error PRJ0026 | Response file 'file' contains Unicode contents that could not be translated to user's ANSI code page. |
| Project build error PRJ0027 | Unicode log message 'contents' contains content that could not be translated to the user's ANSI code page. |
| Project build error PRJ0028 | Temporary file 'file' contains Unicode contents that could not be translated to user's ANSI code page. |
| Project build error PRJ0030 | Macro expansion error. Evaluate recursion exceeded 32 levels for $(macro). |
| Project build error PRJ0031 | The 'Outputs' property for the custom build step for file 'file' contained 'macro' which evaluates out to 'macro_expansion'. |
| Project build error PRJ0032 | The 'Outputs' property for the project-level custom build step contained 'macro' which evaluates out to 'macro_expansion'. |
| Project build error PRJ0033 | The 'Additional Dependencies' property for the custom build step for file 'file' contained 'macro' which evaluates out to 'macro_expansion'. |
| Project build error PRJ0034 | The 'Additional Dependencies' property for the project-level custom build step contained 'macro' which evaluates out to 'macro_expansion'. |
| Project build error PRJ0035 | XML file 'file' contains Unicode contents that could not be translated to user's ANSI code page. |
| Project build error PRJ0036 | The 'Additional Files' property for the Web Deployment Tool contained an invalid entry. |
| Project build error PRJ0040 | Internal error on build. Cannot continue. Please reload project and try again. |
| Project build error PRJ0044 | The 'Additional Dependencies' property for custom build rule 'rule' assigned to file 'file' is invalid. The property contained 'string' which evaluates to 'value'. |
| Project build error PRJ0046 | Could not spawn command line because the one specified was empty. |
| Project build error PRJ0047 | Could not resume the suspended process. The build has failed. |
| Project build error PRJ0050 | Failed to register output. Please ensure you have the appropriate permissions to modify the registry. |
Project build warnings
| Warning | Message |
|---|---|
| Project build warning PRJ0018 | The following environment variables were not found: |
| Project build warning PRJ0029 | The 'Outputs' property for the project-level custom build step is not set. The custom build step will be skipped. |
| Project build warning PRJ0041 | Cannot find missing dependency 'dependency' for file 'file'. Your project may still build, but may continue to appear out of date until this file is found. |
| Project build warning PRJ0042 | The 'Outputs' property for the custom build step for file 'file' is not set. The custom build step will be skipped. |
| Project build warning PRJ0049 | Referenced target '<Reference>' requires .NET Framework <MinFrameworkVersion> and will fail to run on this project's target framework |
See also
C/C++ Compiler and build tools errors and warnings
Visual Studio projects | C++