Gen 8.6 Call External Fatal Error - wsdl has no complexType
search cancel

Gen 8.6 Call External Fatal Error - wsdl has no complexType


Article ID: 206030


Updated On:


Gen Gen - Workstation Toolset


All latest Gen 8.6 Toolset PTFs installed up to and including TSN86215.

Create a new CAB in a model and add a Call External statement.
On the "Select WSDL Method" dialog after the WSDL file is parsed select the displayed method and press the Add button.
The Toolset reports error "CA Gen Internal Fatal Error" with "Memory error: undefined record occurrence (type: 0, number: -1)." and crashes:

After the Toolset crashes also see this in Windows Event Viewer (Windows Logs > Application)
Faulting application name: TOOLSET.EXE, version:, time stamp: 0x5fd273bb
Faulting module name: ucrtbase.dll, version: 10.0.17763.719, time stamp: 0xa18cd287
Exception code: 0xc0000409
Fault offset: 0x000a522b
Faulting process id: 0xf738
Faulting application start time: 0x01d6e317b6b740ab
Faulting application path: C:\Program Files (x86)\CA\Gen86\gen\TOOLSET.EXE
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 1ba05206-8b73-4749-a8b8-41e410c338b0
Faulting package full name:
Faulting package-relative application ID:

With slightly different versions of the WSDL file, the same error message occurs with a different type value e.g. 44, 130.

Validating the WSDL file using Visual Studio 2017 shows 0 errors and warnings and 6 informational.

What is the cause of the error?


Release : 8.6
Component : Gen Workstation Toolset


In the WSDL file which causes the error there is a single element which is very simple and contains no complex types (no xsd:complexType) i.e.:
      <xsd:schema xmlns:xsd="">
         <xsd:element name="ELEMENT1" type="xsd:string" />

Previously a larger wsdl file containing complex types (xsd:complexType) was being loaded successfully.
After changing the above definition of element ELEMENT1 to be a complexType the error did not occur i.e.
      <xsd:schema xmlns:xsd="">
         <xsd:element name="ELEMENT1">
                  <xsd:element name="HEADER" type="xsd:string" minOccurs="0" />
                  <xsd:element name="HEADER2" type="xsd:string" minOccurs="0" />

Therefore there appears to be a limitation that Call External requires the use of xsd:complexType in element definitions.

Additional Information

** These problems were resolved by Gen Engineering in 2 PTFs **:
Toolset: TSN86216/LU00647
Generator: GEN86208/LU00648
Both are superseded by Gen 8.6.3 consolidation PTF WKS86300/LU06327