FIX: The session fault notification does not carry the SoapFault object details, and the Connected Services Framework Server 2.5-based application cannot route the SessionFaultNotification object (917538)

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

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

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

No prerequisites are required.

Restart requirement

You do not have to restart the computer after you apply this 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.

File name	File version	File size	Date	Time	Platform
Microsoft.csf.connector.session.dll	2.5.0.1097	221,184	11-Apr-2006	04:02	x86
Microsoft.csf.session.dll	2.5.0.1097	53,248	11-Apr-2006	04:01	x86

Installation information

The Microsoft.Csf.Connector.Session.dll file and the Microsoft.Csf.Session.dll file in this hotfix are intended to replace the identically named files on the target system that has the session component installed. You must replace these files manually.

MORE INFORMATION

After you apply this hotfix, you experience the following functional behavior:

The Connected Services Framework Server 2.5-based application sends a ParticipantStateChangedNotification object in the following scenarios:
- An exception occurs when the application tries to send a one-way message to the participant. The exception occurs whether the participant is currently active or not.
- An exception that is not of the SoapException type occurs on a request call or on a response call.
- A call to dispatch a message succeeds, and the participant is currently inactive.
For asynchronous participants, SOAP faults are sent on a different channel to the appropriate session Web service front end. Additionally, SOAP faults are handled by using the regular routing logic. Any exception on the send call itself is treated as a participant state change and is handled. Therefore, the Connected Services Framework Server 2.5-based application sends a ParticipantStateChangedNotification object as necessary.

For synchronous participants, SOAP faults are sent as exceptions on the request call or on the response call. All exceptions that derive from the SoapException type are considered to result from a SOAP fault being sent on the wire from the other end. All other exception types are treated as a participant being down, and the Connected Services Framework Server 2.5-based application sends a ParticipantStateChangedNotification object as necessary. For the SoapException type, a session fault notification is created by using the information in the exception. Additionally, a session fault notification is routed by using the regular routing logic.
The Connected Services Framework Server 2.5-based application routes a session fault notification in the following scenarios:
- An issue occurs for the incoming SoapEnvelope objects on a synchronous call. For example, the objects are missing the required headers, an important element is not understood, or the policy requirements are not satisfied.
- A SoapFault object exception occurs because an exception is thrown by the service on a request synchronous call, on a response synchronous call, or on an asynchronous call.
Note A new SoapFaultElement property is added to the FaultNotification class that corresponds to the SessionFaultNotification field on the wire. The SoapFaultElement property is the XmlElement type. The SoapFaultElement property carries the SoapFault object details.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates