FIX: .NET Profiling Service Remoting Callbacks Are Unreliable (310835)



The information in this article applies to:

  • Microsoft Visual C++ .NET (2002)
  • Microsoft .NET Framework 1.0

This article was previously published under Q310835

SYMPTOMS

The Microsoft .NET Framework profiling service remoting callbacks are unreliable. They may provide bogus information and may cause the application that is being profiled to fail.

CAUSE

Most of the callback functions do not work reliably.

RESOLUTION

To work around this problem, do not enable the remoting events to use remoting callbacks.

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 Microsoft Visual C++ .NET (2003), and Microsoft .NET Framework 1.1.

MORE INFORMATION

The remoting callbacks include:
  • RemotingClientInvocationStated
  • RemotingClientSendingMessage
  • RemotingClientReceivingReply
  • RemotingClientClientInvocationFinished
  • RemotingServerReceivingMessage
  • RemotingServerInvocationStarted
  • RemotingServerInvocationReturned
  • RemotingServerSendingReply

REFERENCES

For additional information on the CLR profiling service, click the article number below to view the article in the Microsoft Knowledge Base:

309551 INFO: CLR Profiling Services Problems


Modification Type:MinorLast Reviewed:4/24/2003
Keywords:kbfix kbbug kbpending kbPerformanceTool KB310835