Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 822411 - Last Review: April 20, 2007 - Revision: 1.8
FIX: XML Messaging with the .NET Framework 1.1 hotfix rollup
SYMPTOMS
This article contains fixes for the Microsoft .NET Framework
1.1 that affect XML Messaging. The following problems are in fixed in this
hotfix package:
- A client passes a marshal by reference object to a server,
and then the server calls the ThreadPool.QueueUserWorkItem method in a loop. As soon as the server sends about 600 requests,
it stops responding (hangs). This problem occurs when the available threads in
the client thread pool reaches 0. As the client continues processing, the
thread count increases, but the server still does not respond.
- When the Web Services Description Language (WSDL) imports a
schema that includes multiple schema by using the xsd:include element, and when these schemas include any command schema, the
WSDL tool (Wsdl.exe) cannot generate the proxy for the Web service.
- If the WSDL contains more than one binding, and if all the
bindings use SOAP headers, Wsdl.exe may generate an incorrect proxy. This
behavior occurs when you use the Wsdl.exe tool to create the Web service proxy.
The proxy must have the SOAP header field generated in all the classes.
Instead, the proxy has the SOAP header field generated only for the first
class.
Note You must install one of the following hotfixes together with this
hotfix, depending on your configuration:
For a Microsoft .NET Framework 1.1
without Visual Studio .NET 2003 version of this article, see
823641Â
(http://kbalertz.com/Feedback.aspx?kbNumber=823641/
)
.
For a Microsoft .NET Framework 1.1
with Visual Studio .NET 2003 version of this article, see
823639Â
(http://kbalertz.com/Feedback.aspx?kbNumber=823639/
)
.
RESOLUTION
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 Web site:
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.
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.
Date Time Version Size File name
------------------------------------------------------------------------
07-Jun-2003 06:52 1.1.4322.910 323,584 System.runtime.remoting.dll
07-Jun-2003 06:52 1.1.4322.910 569,344 System.web.services.dll
07-Jun-2003 06:52 1.1.4322.910 1,335,296 System.xml.dll
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, click the following article numbers to view the articles in the Microsoft Knowledge Base:
824684Â
(http://kbalertz.com/Feedback.aspx?kbNumber=824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
823640Â
(http://kbalertz.com/Feedback.aspx?kbNumber=823640/
)
FIX:
Microsoft .NET Framework 1.1 common language runtime hotfix rollup
APPLIES TO
- Microsoft .NET Framework 1.1
| kbhotfixserver kbqfe kbfix kbbug KB822411 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please