BUG: Web Service Endpoints Are Not Exposed If You Set SoapVRoot Property in a Managed ServicedComponent Class (312871)
The information in this article applies to:
- Microsoft Enterprise Services (included with the .NET Framework) 1.0
- Microsoft Windows XP Professional
This article was previously published under Q312871 SYMPTOMSNote The following .NET Framework Class Library namespaces are
referenced in this
article:
System.EnterpriseServices.ServicedComponent
When you
use the managed libraries to build a component in the EnterpriseServices namespace, you can use the SoapVRoot property to programmatically generate a virtual root. You can
then use this virtual root to expose the serviced component though Microsoft
Internet Information Services (IIS) remoting.
However, when you try
to use the SoapVRoot property to programmatically generate a virtual root on a
computer that is running Windows XP Professional, no endpoints are exposed for
the component. CAUSE This problem occurs because of a known bug in Windows XP
Professional. RESOLUTION To work around this problem, set the SoapVRoot property of the COM+ application manually by using the Component
Services snap-in. Alternately, if you already compiled the component
by using the programmatic attribute, and if you already used Regsvcs.exe to
register the component, follow these steps to work around this problem:
- In the Component Services snap-in, right-click the COM+
application, and then click Properties.
- On the Activation tab, clear the Users SOAP check box, and then click Apply.
- Select the Users SOAP check box, type the name of the virtual root in the SOAP VRoot text box, and then click OK.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft
products that are listed at the beginning of this article.
Modification Type: | Major | Last Reviewed: | 9/18/2003 |
---|
Keywords: | kbbug kbpending KB312871 kbAudDeveloper |
---|
|