BUG: "ExternalException: Cannot Execute a Program" Error Message When You Call WebServices from .aspx Page (315904)


The information in this article applies to:

  • Microsoft ASP.NET (included with the .NET Framework) 1.0
  • Microsoft Web Services (included with the .NET Framework) 1.0
  • Microsoft Web Services (included with the .NET Framework 1.1)
This article was previously published under Q315904

SYMPTOMS

If you use Simple Object Access Protocol (SOAP) to call the WebServices method from an .aspx page, the .aspx page may fail when you run the Microsoft Internet Information Services (IIS) Lockdown tool. In addition, you may receive the following error message:
[ExternalException (0x5): Cannot execute a program. The command being executed was "d:\winnt\microsoft.net\framework\v1.0.3408\csc.exe" /noconfig @"D:\WINNT\TEMP\eyrpuhyg.cmdline".]
This problem only affects Web applications or Web services that are clients of a Web service and that impersonate the Anonymous user account.

CAUSE

The IIS Lockdown tool denies execution access for the IUSR_COMPUTERNAME and the IWAM_COMPUTERNAME accounts to every executable file (*.exe) in the Windows directory (%windir%). This includes framework tools such as the Csc.exe file, which the XmlSerializer class uses. When a Web application or a Web service impersonates IUSR_COMPUTERNAME or IWAM_COMPUTERNAME, the Web application or the Web service cannot use XmlSerializer to serialize objects into Extensible Markup Language (XML) documents.

Note This problem does not affect the server side of a Web service because XmlSerializer is generated and compiled outside of the impersonation.

RESOLUTION

To resolve this problem, use one of the following methods:
  • Use a different, non-Anonymous account to impersonate. (This is the recommended method.)
  • Add sufficient permission for the executable files in the Windows directory.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Steps to Reproduce the Behavior

  1. Allow Anonymous access on the IIS application.
  2. Enable impersonation for the Web application in the local Web.config file as follows:
    <configuration>
  <system.web>	
	<identity impersonate="true" />
  </system.web>
</configuration>
  3. Run the IIS Lockdown tool, or deny access to the IUSR_COMPUTERNAME or the IWAM_COMPUTERNAME account on the Csc.exe file before you request the page.

REFERENCES

For additional information about impersonation in an ASP.NET application, click the following article number to view the article in the Microsoft Knowledge Base:

306158 INFO: Implementing Impersonation in an ASP.NET Application

For additional information about XmlSerializer, click the article number below to view the article in the Microsoft Knowledge Base:

315703 HOW TO: Serialize an Object to XML by Using Visual Basic .NET

For more information about Web services, refer to the following MSDN Web sites:

XML Web Services Developer Center
http://msdn.microsoft.com/webservices

XML Web Service-Enabled Office Documents (an Extreme XML column)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnexxml/html/xml03192001.asp

In addition, refer to the "Creating and Accessing Web Services Walkthroughs" topic in the Visual Studio .NET Online Help documentation for more information about Web services.
Modification Type:MinorLast Reviewed:7/6/2005
Keywords:kbbug kbpending kbSecurity kbWebForms KB315904 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.