Article ID: 830789 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
When the name of your method includes a hyphen ("-"), the Remote Procedure Call (RPC) Web Service method ignores the RequestElementName property of the SoapRpcMethodAttribute class. Microsoft Visual Studio .NET 2003 does not permit a hyphen in the method name. Therefore, when the Microsoft .NET Framework 1.1 generates the proxy, it removes the hyphen. When your method is called, the requested element name does not have a hyphen and is not recognized by the Web Service. If you call the SoapRpcMethodAttribute class with the RequestElementName property, it does not have any effect.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
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.
The English version of this hotfix has the file attributes (or later) 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 tool in Control Panel.
Date Time Version Size File name ------------------------------------------------------------------------ 18-Oct-2003 02:16 1.1.4322.960 258,048 Aspnet_isapi.dll 18-Oct-2003 02:16 1.1.4322.960 20,480 Aspnet_regiis.exe 18-Oct-2003 02:16 1.1.4322.960 32,768 Aspnet_state.exe 18-Oct-2003 02:16 1.1.4322.960 32,768 Aspnet_wp.exe 18-Oct-2003 02:05 1.1.4322.960 94,208 Perfcounter.dll 20-Oct-2003 20:31 1.1.4322.960 1,216,512 System.dll 20-Oct-2003 20:31 1.1.4322.960 241,664 System.messaging.dll 20-Oct-2003 20:31 1.1.4322.960 323,584 System.runtime.remoting.dll 20-Oct-2003 20:30 1.1.4322.960 131,072 System.runtime.serialization.formatters.soap.dll 20-Oct-2003 20:31 1.1.4322.960 1,253,376 System.web.dll 20-Oct-2003 20:31 1.1.4322.960 819,200 System.web.mobile.dll 20-Oct-2003 20:31 1.1.4322.960 569,344 System.web.services.dll 20-Oct-2003 20:31 1.1.4322.960 1,335,296 System.xml.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 830789 - Last Review: January 17, 2015 - Revision: 2.2