FIX: Error PRJ0016 when you build a Visual C++ .NET project

View products that this article applies to.

This article was previously published under Q324153

SYMPTOMS

When you build or rebuild a Microsoft Visual C++ .NET project, you may receive the following error message:

Project : error PRJ0016 : The user's security settings prevent the process from being created. These settings are required for building.

Back to the top

CAUSE

This problem occurs because Visual Studio .NET incorrectly interprets the RestrictRun registry subkey.

Back to the top

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft Visual Studio .NET. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

837234 (http://support.microsoft.com/kb/837234/ ) List of bugs that are fixed in Visual Studio .NET 2002 Service Pack 1

Back to the top

Hotfix information

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

   Date         Time   Version         Size       File Name
   ------------------------------------------------------------------
   18-Jun-2002  14:18  7.0.9509.0      1,052,672  Vcprojectengine.dll

Back to the top

WORKAROUND

If you do not have to restrict the processes that a user can start, you can follow the steps in Microsoft Knowledge Base article Q313363 to work around this problem. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

313363 (http://support.microsoft.com/kb/313363/ ) PRB: Visual C++ .NET Project Build Error PRJ0016

If you must have this control, and if you want to build Visual C++ .NET projects, you must install the hotfix.

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Visual Studio .NET 2002 Service Pack 1.

Back to the top