PRB: IIS 5.0 Stops Responding When You Call Application.Lock and Application.Unlock in WebClasses (273496)

The information in this article applies to:

Microsoft Internet Information Server 5.0
Microsoft Visual Basic Professional Edition for Windows 6.0
Microsoft Visual Basic Enterprise Edition for Windows 6.0

This article was previously published under Q273496

SYMPTOMS

When you debug a Visual Basic WebClass application within the Visual Basic Integrated Developer Environment (IDE) on a Microsoft Windows 2000-based computer, and you call the Application.Lock and Application.UnLock methods, the Web server may stop responding (hang).

CAUSE

With the introduction of COM+, Internet Information Server (IIS) 5.0 takes advantage of the Thread-Neutral Apartment (NA) when you access the Application object. As a result, when you explicitly call Application.Lock and Application.UnLock from a component, you encounter a deadlock scenario that causes the server to stop responding under certain situations.

RESOLUTION

Do not use Application.Lock and Application.UnLock in your WebClass code when you debug.

MORE INFORMATION

Steps to Reproduce Behavior

Start Visual Basic. In the New Project dialog box, select IIS Application, and then click Open.
In the Project window, click to expand the Designers folder. Right-click WebClass1, and then click View Code from the shortcut menu.

Add the following code to the WebClass_OnStart event:

Application.Lock
Application("myvar") = "hello world"
Application.UnLock

Save the WebClass.
On the Debug menu, click Start to run the WebClass. Internet Explorer stops responding, and the page is never displayed in the browser.

REFERENCES

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

271787 PRB: Application.Lock and Application.UnLock Causes Server to Hang in IIS 5.0

Modification Type:	Minor	Last Reviewed:	7/15/2004
Keywords:	kbASPObj kbprb kbWebClasses kbWebServer KB273496