New nodes cannot join the mesh after a custom resolver uses the CustomPeerResolverService class in the .NET Framework 3.0

Symptoms

Consider the following scenario:

  • Some Windows Communication Foundation (WCF) peer channel clients use a custom resolver to obtain the IP addresses of the peer nodes in a mesh. The mesh has various peer nodes.

  • The custom resolver uses the CustomPeerResolverService class in the Microsoft .NET Framework 3.0.

  • An update operation occurs on a registered node. A new registration operation occurs on another peer node.


In this scenario, the custom resolver may stop responding. Therefore, the new nodes cannot join the mesh.

Cause

This issue occurs because of an issue in the CustomPeerResolverService class.

When the update operation occurs, it may be transformed into a registration operation. Therefore, two threads in the custom resolver try to obtain a read and write lock at the same time.

Resolution

Hotfix information

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

To resolve this problem, 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 website:

http://support.microsoft.com/contactus/?ws=supportNote 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

To apply this hotfix, you must have the Microsoft .NET Framework 3.5 Service Pack 1 (SP1) installed on a computer that is running Windows 7 or Windows Server 2008 R2.

Note The Microsoft .NET Framework 3.5 SP1 includes the Microsoft .NET Framework 3.0 Service Pack 2 (SP2).

Restart requirement



You do not have to restart the computer after you apply this hotfix if the affected files are not being used.

We recommend that you close all .NET Framework applications before you apply this hotfix.

Hotfix replacement information


This hotfix does not replace a previously released hotfix. 

File Information

The global 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 7

File name

File version

File size

Date

Time

Platform

Smdiagnostics.dll

3.0.4506.5691

110,592

25-May-2011

22:33

x86

Smsvchost.exe

3.0.4506.5691

128,848

25-May-2011

22:33

x86

System.identitymodel.dll

3.0.4506.5691

442,368

25-May-2011

22:33

x86

System.runtime.serialization.dll

3.0.4506.5691

970,752

25-May-2011

22:33

x86

System.servicemodel.dll

3.0.4506.5691

5,988,352

25-May-2011

22:33

x86

System.servicemodel.washosting.dll

3.0.4506.5691

32,768

25-May-2011

22:33

x86

Servicemodel.mof

Not Applicable

85,113

25-May-2011

22:33

x86

Servicemodel.mof.uninstall

Not Applicable

896

10-Jun-2009

21:14

x86

Servicemonikersupport.dll

3.0.4506.5691

17,256

25-May-2011

22:33

x86

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Servicemodel.mof

Not Applicable

85,113

25-May-2011

22:32

x64

Servicemodel.mof.uninstall

Not Applicable

896

10-Jun-2009

20:30

x64

Servicemonikersupport.dll

3.0.4506.5691

19,304

25-May-2011

22:32

x64

Smdiagnostics.dll

3.0.4506.5691

94,208

25-May-2011

22:32

x64

Smsvchost.exe

3.0.4506.5691

116,560

25-May-2011

22:32

x64

System.identitymodel.dll

3.0.4506.5691

401,408

25-May-2011

22:32

x64

System.runtime.serialization.dll

3.0.4506.5691

847,872

25-May-2011

22:32

x64

System.servicemodel.dll

3.0.4506.5691

5,328,896

25-May-2011

22:32

x64

System.servicemodel.washosting.dll

3.0.4506.5691

32,768

25-May-2011

22:32

x64

For all supported IA-64–based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Servicemodel.mof

Not Applicable

85,113

25-May-2011

22:25

IA-64

Servicemodel.mof.uninstall

Not Applicable

896

10-Jun-2009

20:35

IA-64

Servicemonikersupport.dll

3.0.4506.5691

33,640

25-May-2011

22:25

IA-64

Smdiagnostics.dll

3.0.4506.5691

94,208

25-May-2011

22:25

IA-64

Smsvchost.exe

3.0.4506.5691

116,560

25-May-2011

22:25

IA-64

System.identitymodel.dll

3.0.4506.5691

401,408

25-May-2011

22:25

IA-64

System.runtime.serialization.dll

3.0.4506.5691

847,872

25-May-2011

22:25

IA-64

System.servicemodel.washosting.dll

3.0.4506.5691

32,768

25-May-2011

22:25

IA-64

System.servicemodel.dll

3.0.4506.5691

5,328,896

25-May-2011

22:25

IA-64

Status

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

More Information

For more information about WCF peer channel, visit the following MSDN website:

General information about WCF peer channel

Нужна дополнительная помощь?

Совершенствование навыков
Перейти к обучению
Первоочередный доступ к новым возможностям
Присоединение к программе предварительной оценки Майкрософт

Были ли сведения полезными?

Спасибо за ваш отзыв!

Благодарим за отзыв! Возможно, будет полезно связать вас с одним из наших специалистов службы поддержки Office.

×