When you execute the Invoke Web Services object in Microsoft System Center Orchestrator or Opalis Integration Server, you receive one or more of the following errors in the "Error Summary Text" published data:
Unable to generate a temporary class (result=1).
error CS0029: Cannot implicitly convert type 'Opalis.WebServices.DynamicProxy.CustomType' to 'Opalis.WebServices.DynamicProxy.CustomType'
error CS0030: Cannot implicitly convert type 'Opalis.WebServices.DynamicProxy.CustomType' to 'Opalis.WebServices.DynamicProxy.CustomType'
A known issue with WSDL.exe can cause a proxy class to be generated incorrectly if an array of complex type includes an element that is also an array of complex type and for which only one element exists.Note
WSDL.exe is included in the Microsoft .NET Framework.
There is no resolution available at this point. However, three workarounds are available:
- You can generate the proxy class manually by using WSDL.exe and then change the proxy class in which the data type was inappropriately created as a two-dimensional array (for example, "CustomType") so that it is a single-dimensional array (for example, "CustomType").
- You can change the data type in the desired Web Services Description Language (WSDL) so that a second, optional element is included in the definition. You can do this by adding an element such as the following:
<xs:element minOccurs="0" name="dummyElement" nillable="true" type="xs:string"/>
- You can change the complex type in the desired WSDL so that the boundary attributes are part of the complex type instead of being part of the element. (That is, you can move the minOccurs and maxOccurs attributes to the complex type and then remove them from the element.)
Article ID: 2486643 - Last Review: December 30, 2013 - Revision: 4.0
- Microsoft System Center 2012 Orchestrator
- Opalis Integration Server
- Microsoft System Center 2012 Orchestrator Service Pack 1
- Microsoft System Center 2012 R2 Orchestrator