
	Search KbAlertz Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account

Already have an account?
[Click here to Login]

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Ads by Lake Quincy Media

FIX: A System.Runtime.InteropServices.COMException exception occurs when you use COM components in the .NET Framework 2.0 to access form data or querystring data that contains a TAB character

Article ID: 973746 - View products that this article applies to.

Expand all | Collapse all

SYMPTOMS

Consider the following scenario in the Microsoft .NET Framework 2.0:

You have a Microsoft ASP.NET Web page in which the AspCompat attribute is set to True.
You submit the form data or the querystring data by using a postback event. Additionally, the data contains a TAB character.
You try to access Active Server Pages (ASP) intrinsic objects by using COM components.

In this scenario, a failure occurs, and you receive the following error message:

Description: An unhandled exception occurred during the execution of the current Web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Runtime.InteropServices.COMException: Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))

Back to the top | Give Feedback

CAUSE

This problem occurs when the form data or querystring data is marshaled from the managed code to the native code. In this situation, the data is encoded as a string. Additionally, the TAB character is used to separate different entries. However, when the data already has entry values that contain a TAB character, the newly introduced TAB character corrupts the data in the native code during the decoding process.

Back to the top | Give Feedback

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

(http://support.microsoft.com/contactus/?ws=support)

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have the Microsoft .NET Framework 2.0 Service Pack 2 (SP2) installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix, assuming the affected DLLs were not being used when you applied the hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.