The Execute permissions for a Web application are unexpectedly set to the None setting after you use Visual Studio .NET 2003 to copy a Web application to the Web server

Consider the following scenario. You use the Copy Project feature in Microsoft Visual Studio .NET 2003 to copy a Web application to a Web server that is running Microsoft Internet Information Services (IIS) 6.0 and FrontPage 2002 Server Extensions from Microsoft. When you view the properties of the Web application in Internet Information Services Manager, you notice that the Execute permissions are set to the None setting. You expect the Execute permissions to be set to the default Scripts Only setting.

This issue may occur if one of the following conditions is true:

�	You run the Visual Studio .NET 2003 IDE as a user who does not have administrative credentials on the Web server.
�	You run the Visual Studio .NET 2003 IDE as a user who is not a member of the same domain as the Web server.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To work around this issue, turn on the NoMarkScriptable property. To do this, set the NoMarkScriptable registry entry in the following registry subkey to 1:Note <Number> is a number that indicates the instance of the Web application.

By default, the NoMarkScriptable registry entry for a Web application is set to 0 (zero). When you set the NoMarkScriptable registry entry for a Web application to 1, the scriptable attribute on folders in the Web application cannot be modified. To set the value of the NoMarkScriptable registry entry in the following registry subkey to 1, follow these steps:

1.	Click Start, click Run, type regedit, and then click OK.
2.	Locate the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions
3.	Expand Ports, and then expand Port /LM/W3SVC/<Number>.
4.	Double-click the NoMarkScriptable registry entry, type 1 in the Value data box, and then click OK. If the NoMarkScriptable registry entry does not exist, follow these steps to create it: a. Right-click Port /LM/W3SVC/<Number>, click New, and then click String Value. b. Name the new registry entry NoMarkScriptable, and then press ENTER.
5.	In the Value data box, type 1, and then click OK.
6.	On the File menu, click Exit to exit Registry Editor.

After you follow the steps in this article, the Allow scripts or programs to be run check box is unavailable (appears dimmed) when you view folders of the Web application in Microsoft FrontPage. However, when a new folder in the Web application is created, that folder inherits the permissions of the root folder. If the Execute permissions of the root folder are set to the Scripts only setting, the Execute permissions of the new folder will also be set to the Scripts only setting. To configure folders to store uploaded files, follow these steps:

1.	Right-click the folder, and then click Properties.
2.	Click to clear the Allow files to be browsed check box, and then click OK.
3.	Right-click the folder again, and then click Properties.
4.	Specify the upload settings that you want, and then click OK.

To enable the Allow scripts or programs to be run option for folders in the Web application, click to select the Allow authors to upload executables check box in FrontPage Server Extensions. Alternatively, turn off the NoExecutableCGIUpload property for the Web application.

For more information about the NoMarkScriptable property and the NoExecutableCGIUpload property, visit the following Microsoft Web site: For more information about how to set the NoMarkScriptable registry entry, visit the following Microsoft Web site: For more information about FrontPage 2002 Server Extensions, visit the following Microsoft Web site: For more information about FrontPage 2000 Server Extensions from Microsoft, visit the following Microsoft Web site: