XYZ method cannot be reflected

Question

We used a third-party web service and are trying to call it from an ASP.NET web application. However, when creating the web service, the following System.InvalidOperationException is thrown:

The "ABC.XYZ" method cannot be reflected. System.InvalidOperationException: The method "ABC.XYZ" cannot be reflected. ---> System.InvalidOperationException: XML element "MyDoc" from the namespace ' http://mysoftware.com/ns ' of the reference method and type. Change the name of the message method using WebMethodAttribute or change enter the root element using XmlRootAttribute.

From what I can collect, there seems to be some ambiguity between the method and the type in the web service. Could someone clarify the likely reason for this exception, and is there anything I can do to fix this, or should I just contact the web service owners to fix it?

Edit: Visual Studio 2008 created a proxy class. Unfortunately, I cannot provide a link to wsdl, as it is a web service for a locally installed third-party application.

Answer 1

The problem seems to be related to data type issues between VS and the web service written in Java.

This was eventually fixed by manually editing the class and schema files created by VS.

Answer 2

Today I faced the same problem. The reason was that the class generated by Visual Studio and passed as a parameter to one of the methods did not have a constructor without parameters without parameters. As soon as I added it, the error disappeared.

Answer 3

I ran into the same problem when I consumed a third-party web service. The problem in this case was that the mustUndertand property in the link file was looking for a boolean, resulting in the namespace property looking for a string.

By browsing the link, I was able to identify the property of the violation and simply add “overrides” to the method signature.

Not perfect, as at any time when you update the service you need to do, but I could not find another way.

To find the link file, select "all files" from the solution explorer

Hope this helps

Answer 4

I assume that wsdl emitted or provided by a service is not in a form that wsdl.exe or serviceutil can understand - can you post wsdl or a link to it?

how do you create proxy classes?

You can also try and check wsdl on a wsdl schema to check if it is valid

Answer 5

In my case, I got the error "the method cannot be reflected" due to the fact that in the class returned by the method, I could not open the constructor without default parameters.

I worked in VB.NET. In my return class, I declared the "New (..)" method, which took a couple of parameters (because that’s how I wanted to use it in my code). But by doing this, I suppressed the default New () constructor (hidden) with no parameters, which VB adds behind the scenes. Apparently, the web service handler requires a constructor with no parameters. As soon as I added the task-free constructor New () back to my class, all this worked fine.

Answer 6

I received the same message, but mine was caused by the missing System.Runtime.Serialization.dll, since I tried to run 3.5 application on a computer with only .NET 2.0 installed.

Answer 7

I had the same problem, but I found that one of the WebMethod parameters has a member that is of type interface , so VS unable to serialize it. an exception occurs when trying to load a disco file

System.InvalidOperationException: Cannot serialize the element 'Leopard.JobDespatchParameters.SendingUser' of type 'Leopard.Interfaces.IUser', see internal exception for more details. ---> System.NotSupportedException: cannot serialize a Leopard.JobDespatchParameters.SendingUser element of type Leopard.Interfaces.IUser because it is an interface.

Answer 8

An old thread, but I had another problem, Maybe helping someone. referencing DLLs were mixed between the two versions at the data level and the service level, which caused the problem.

Answer 9

Another scenario in which this error can occur: I just had a different web method with the same name (but different parameters) in my web service that slipped during the code merge. After I deleted the old method, it worked.