Error consuming external webservice: <elements> violate "Unique Particle Attribution"

[erossing.26610 (Evelyn Rossing)]

When I try to create a web service descriptor from a WSDL in Designer 9.6 for IS 8.2.2, I get this error:

[ISS.0092.9001] Server Error: cos-nonambig: WC[##any] and table (or elements from their substitution group) violate “Unique Particle Attribution”. During validation against this schema, ambiguity would be created for those two particles. [null]
cos-nonambig: WC[##any] and table (or elements from their substitution group) violate “Unique Particle Attribution”. During validation against this schema, ambiguity would be created for those two particles. [null]
cos-nonambig: objectReferentId and WC[##any] (or elements from their substitution group) violate “Unique Particle Attribution”. During validation against this schema, ambiguity would be created for those two particles. [null]
cos-nonambig: options and WC[##any] (or elements from their substitution group) violate “Unique Particle Attribution”. During validation against this schema, ambiguity would be created for those two particles. [null]
cos-nonambig: WC[##any] and table (or elements from their substitution group) violate “Unique Particle Attribution”. During validation against this schema, ambiguity would be created for those two particles. [null]
cos-nonambig: WC[##any] and table (or elements from their substitution group) violate “Unique Particle Attribution”. During validation against this schema, ambiguity would be created for those two particles. [null]

The issue is that some of the complex elements in the WSDL have named elements followed by “any” elements. For example:

<xsd:sequence>
	<xsd:element name="objectReferentId" type="common:ObjectIdentifierType" nillable="true" minOccurs="0" maxOccurs="1"/>
	<xsd:element name="additionalRowInfo" type="AdditionalInfoType" nillable="true" minOccurs="0" maxOccurs="1"/>
	<xsd:any minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>

SOAPUI handles this WSDL without complaint. Is there anything I can do to convince webMethods to do the same?

[erossing.26610 (Evelyn Rossing)]

I submitted this question to SAG support also and got this response:

As of version 8.2.2 we added an additional level of validation to Integration Server. Apart from the internal IS validator, we also added Xerces.
This sometimes causes errors when generating Web Services Descriptors (WSD’s).

It’s is possible to turn off this additional level of validation by adding to following two settings in IS Admin > Settings > Extended > Edit Extended Settings and restarting IS:
watt.core.schema.validateIncomingXSDUsingXerces=false
watt.server.wsdl.validateWSDLSchemaUsingXerces=false

You should then be able to generate the WSD.

After following these instructions I was able to generate the WSD.