We are trying to create a provider Web Service Descriptor in webMethods 7.1 from a WSDL and get the following exception:

com.wm.util.LocalizedCharConversionException: [ISC.0042.9201] Incorrect character encoding (char=?; offset=1033)

The WSDL itself is well formatted in XMLSpy and can be imported into webMethods 6.1 server without any issues. We are also able to create WSDs from WSDLs from other sources on the 7.1.1 server just fine.

We are not sure what the problem/incompatibity is between webMethods 7.1.1 and these specific WSDLs. Per article
[URL]https://advantage.webmethods.com/advantage?targChanId=kb_home&oid=1614326880[/URL] some WSDLs might just not work in 7.1. Has anyone seen this or have a workaround for this?

Can you upload the wsdl here??

HTH,
RMG

Attached are the WSDLs and schema.
HGStatus_v1.7.wsdl (2.08 KB)
HGStatus_v1.7.xsd (10.5 KB)
HGSOAPHeader_v1.7.xsd (2.25 KB)
HGSOAPResponse_v1.7.xsd (670 Bytes)

A small advice in your xsd’s replace all xs: sequence tags with xs: all as In 711 while loading the xsd’s in the developer it choked the server due to sequence tags.I know this is outofscope of your issue.

Is this spl chars causing the issue?

xs:documentationAn Agency Financial Authorization / “Funds Obligation / Commitmentâ€? Number generated by agency’s financial system for a XYZHG.com Travel Plan Authorization.</xs:documentation>

HTH,
RMg

Seems like the problem is in the schema import statement in the WSDL

Is this spl chars causing the issue in the HGStatus_v1.7.xsd??
?

xs:documentationAn Agency Financial Authorization / “Funds Obligation / Commitmentâ€? Number generated by agency’s financial system for a XYZHG.com Travel Plan Authorization.</xs:documentation>

Yes, that was it. Removing the quotes from xs:documentationAn Agency Financial Authorization / “Funds Obligation / Commitment” Number generated by agency’s financial system for a XYZHG.com Travel Plan Authorization.</xs:documentation> fixed the problem.

But the WSDLs are not in our control, is there a way we can work with these characters (quotes in this case).

Also creating a document type from this XML schema doesn’t seem to be a problem nor is importing the WSDL into older IS servers. So I am hoping there is a way we can work around this in 7.1.1

In this can you escalate with SAG tech support on this issue as its related to IS711 only.

HTH,
RMG