C# web service clients seem not to like the following construct that is part of e.g. any ObjectReferenceType:
<c:filter/>
and fail with the following exception:
System.InvalidOperationException was unhandled Message=No corresponding start element is open. Source=mscorlib
It is strange, because that XML fragment is fully conformant to the schema that is part of runtime WSDL, which is:
<xs:element minOccurs="0" name="filter"> <xs:complexType> <xs:sequence> <xs:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="lax"/> </xs:sequence> </xs:complexType> </xs:element>
(in the above case, there are zero elements matching xs:any, which is legal according to the schema)
A temporary fix for this situation is to omit the "filter" element of ObjectReferenceType if it's empty - see - MID-1603Getting issue details... STATUS .
However, there are more similar places, and it is likely that such problems would occur there. This has to be researched further and fixed if necessary.