Article ID: 310835 - Last Review: April 24, 2003 - Revision: 3.2

FIX: .NET Profiling Service Remoting Callbacks Are Unreliable

View products that this article applies to.
This article was previously published under Q310835
Expand all | Collapse all

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.
Back to the top

CAUSE

Most of the callback functions do not work reliably.
Back to the top

RESOLUTION

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

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.
Back to the top

MORE INFORMATION

The remoting callbacks include:
  • RemotingClientInvocationStated
  • RemotingClientSendingMessage
  • RemotingClientReceivingReply
  • RemotingClientClientInvocationFinished
  • RemotingServerReceivingMessage
  • RemotingServerInvocationStarted
  • RemotingServerInvocationReturned
  • RemotingServerSendingReply
Back to the top

REFERENCES

For additional information on the CLR profiling service, click the article number below to view the article in the Microsoft Knowledge Base:
309551  (http://support.microsoft.com/kb/309551/EN-US/ ) INFO: CLR Profiling Services Problems
Back to the top
APPLIES TO
  • Microsoft Visual C++ .NET 2002 Standard Edition
  • Microsoft .NET Framework 1.0
Back to the top
Keywords: 
kbbug kbfix kbperformancetool kbpending KB310835
Back to the top
 

Get Help Now

Contact a support professional by E-mail, Online, or Phone

Article Translations

 

Related Support Centers