Subscribe to Windows IT Pro

 

Get Newsletters

  • Get the Latest News
  • Product Updates
  • Helpful Tricks
  • Productivity Tips

Subscribe Now!

September 17, 2001 12:00 AM

Curing ASP-Run Executable Problems in IIS 5.0

Windows IT Pro
InstantDoc ID #22184
Rating: (1)

We use ServerObjects' AspExec ActiveX control to run an executable from Active Server Pages (ASP). This control has always worked for us under Microsoft Internet Information Server (IIS) 4.0 on Windows NT 4.0. However, the executable isn't working on our Windows 2000 server. The program is running in a hidden window, so we can't troubleshoot the problem. The executable won't terminate the process, and we can't kill it through Task Manager, which displays an Access denied error. The problem isn't specific to our executable. Do you know of another way to run executables from ASP, or can you tell us how to stop the executable or make the program run in a visible window?

Your problem relates to differences between the default application protection and isolation settings in Internet Information Services (IIS) 5.0 and in IIS 4.0. These settings control how applications run on the server. Applications can run in the same process as the Web server (Low setting), in a separate pooled process with other applications (Medium setting), or in an isolated separate process (High setting). You can configure these settings on the Home Directory tab of your IIS system's Web Site Properties dialog box, which Figure 1 shows.

The default setting under IIS 5.0 on Win2K servers is Medium (Pooled). When a site's Application Protection option is set to Medium (Pooled), IIS uses a program called dllhost.exe to execute DLLs, and you end up with an orphaned process. Your program probably requires a setting of Low (IIS Process), which is the default under NT 4.0 and IIS 4.0 and the reason the executable worked under those versions. You should be able to solve the problem by changing the Application Protection option to Low (IIS Process) for all sites on which ASP uses AspExec to call executables. (For more information about the differences between IIS 5.0 and IIS 4.0 and about IIS application settings, see Brett Hill, "Migrating from IIS 4.0 to IIS 5.0," September 2001, and Ken Spencer, "Introducing Internet Information Services 5.0," http://www.win2000mag.com, InstantDoc ID 8212.)

Related Content:

ARTICLE TOOLS

Comments
  • anne
    3 years ago
    Aug 24, 2009

    Sometimes working with legacy programs is a hassle. Who remembers all that asp stuff? The first line of this article was all I needed to get going again. Thanks!

You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

White Papers

Get your Windows 7 deployment off to the right start by implementing PC lockdown. A locked-down environment is easier and cheaper to support since users are less likely to make unnecessary changes to the core system configuration - read more here!

Essential Guides

Is your iSCSI "lossy"? The reality is that most off-the-shelf Ethernet hardware deployed for iSCSI can lose packets, resulting in slow performance or application downtime. Learn how to assess your current iSCSI infrastructure and engineer an advanced iSCSI SAN infrastructure.

Web Seminars

What's the best way to keep your network safe from malware? In this web seminar, security expert Greg Shields suggests an alternative method to the traditional blacklisting approach that is common with anti-virus and anti-malware solutions.

eLearning Series

We bring the experts direct to you to share their real-world perspective and expertise. During each event, three sessions stream in real time, so you can learn, ask questions, and get solutions.
Upcoming event: Getting the Most with Exchange 2010 with Paul Robichaux

Subscribe to Windows IT Pro!

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.