FIX: VI 6.0 RTM Script Debugger Causes Internet Explorer to Crash with Active Desktop Turned On

View products that this article applies to.

This article was previously published under Q224938

Expand all | Collapse all

SYMPTOMS

When the Visual InterDev 6.0 debugger is enabled, Internet Explorer crashes on exit with the following message:

Access violation/OLEChannelWnd

This occurs under the following conditions:

When you have active Desktop turned on.
When you installed the script debugger from Visual InterDev/Visual Studio Setup.
When you run the attached page in Internet Explorer 4.

Internet Explorer will Access Violate when you close it or when the button is pressed on the test page.

Back to the top

Having a script control tag on a page with script that references the script control, even if the referencing script is not called through an event handler or other means, causes an Access Violation error 0xC0000005 in Explorer.exe if Visual InterDev 6.0 is installed with out other Visual Studio 6.0 components. An OLEChannelWnd error occurs if a full Visual InterDev 6.0 install is done versus just Visual InterDev 6.0 client.

Back to the top

STATUS

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

This bug was corrected in Visual Studio 6.0 Service Pack 3. For more information about Visual Studio service packs, please see the following articles in the Microsoft Knowledge Base:

194022 (http://support.microsoft.com/kb/194022/EN-US/ ) INFO: Visual Studio 6.0 Service Packs, What, Where, Why

194295 (http://support.microsoft.com/kb/194295/EN-US/ ) HOWTO: Tell That Visual Studio 6.0 Service Packs Are Installed

Back to the top