Hi Jabbs,
do you also have in the defaultTrace a similar entry like:
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: No port is available in client ...
If yes, then most likely this is related to the fact that the WSDL of the web service contains multiple porttypes (you can check the WSDL to see whether you have multiple instances of
"<wsdl:port name=..."
If yes, this is a limitation of the Java AS, and a workaround would be to split the multiple porttypes in separate WSDLs and use them for creating the WebDynpro models.
I hope this helps.
Best Regards,
Ervin