FIX: You receive a System.InvalidOperationException exception when a client proxy application that uses the xxxAsync methods calls an asynchronous Web service that is running on the .NET Framework 2.0 or on later versions

Article translations Article translations
Article ID: 976889 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario. You have a client application that uses a proxy class that is generated by the Web Services Description Language tool (Wsdl.exe) or by the Add Web Reference feature. The application calls an asynchronous Web service by using the xxxAsync methods. Then, the Web service returns a response that contains invalid XML. When the response is parsed, an exception is raised but is not handled. In this scenario, the application eventually crashes, and then you receive the following messages:
An unhandled exception occurred and the process was terminated.
Exception: System.InvalidOperationException
Message: There was an error during async processing.


Note The client application is based on the Microsoft .NET Framework 2.0 or on later versions.

CAUSE

This issue occurs because the try-catch statement in the client application is bypassed when an asynchronous response that contains invalid XML is parsed.

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have the .NET Framework 2.0 Service Pack 2 (SP2) or the .NET Framework 3.5 Service Pack 1 (SP1) installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix if no instance of the .NET Framework is being used.

Hotfix replacement information

This hotfix does not replace 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.
For all supported x86-based versions of Windows Server 2000, of Windows Server 2003, and of Windows XP
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
System.web.services.dll2.0.50727.4426839,68023-Nov-200920:26x86
For all supported x64-based versions of Windows Server 2000, of Windows Server 2003, and of Windows XP
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
System.web.services.dll2.0.50727.4426839,68023-Nov-200919:54x64
For all supported IA-64-based versions of Windows Server 2000, of Windows Server 2003, and of Windows XP
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
System.web.services.dll2.0.50727.4426839,68023-Nov-200919:54IA-64

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

WORKAROUND

To work around this problem, use the BeginXXX methods and the EndXXX methods instead of the XXXAsync methods in an asynchronous pattern.

Note "XXX" represents the name of the method that you want to expose.

MORE INFORMATION

For more information about server-side asynchronous Web methods, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn.microsoft.com/en-us/library/aa480516.aspx

Properties

Article ID: 976889 - Last Review: October 7, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft .NET Framework 3.5 Service Pack 1
  • Microsoft .NET Framework 2.0 Service Pack 2
Keywords: 
kbexpertiseadvanced kbsurveynew kbqfe KB976889

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com