Ngo,
Glad to hear that it works now, however, this is something to worry about especially if it happens in production!
To my knowledge, there have been some changes to the webServices stack starting from webMethods 9.x.
The webservice provider you are testing now is one upgraded from an older webMethods version or a fresh new one?
In case the Provider webService has an operation with field name starting with xml in any of the following: the input signature, output signature, header or faults, then check extended property watt.server.xml.ncname.encode.backward.compatibility (via the GUI or in the config/server.cnf file); if this value is true, reset it to false. Regenerate afterwards the Provider webService.
Furthermore, if this is a new webService, check your fix level on IS and if it’s not up to date, check the fixes available and whether any of this cover the issue you are facing.
Otherwise, raise a ticket with SAG for further investigation.
I hope this helps,
Ana
#Integration-Server-and-ESB#webMethods