The errors still the same with new site.
According to XmlSpy, The WSDL in question is not well-formed which may indicate the problem.
Anyway, as I said befor, the problem is on the Web Service side.

>
>Thanks for your fast replies! I've confirmed that http://sp-s3g.iclp.com.au/ws/egapi/v1-0/egapi.cfc?wsdl is really difficult to acess at the moment. I've forward this to the company that is hosting the Web Service. Could you please test with http://sp-s3g-uat.iclp.com.au/ws/egapi/v1-0/egapi.cfc?wsdl, which is the user acceptance testing wsdl and seems that is working OK? Because I've tried with http://sp-s3g.iclp.com.au/ws/egapi/v1-0/egapi.cfc?wsdl when I could reach the wsdl and I wasn't able to consume the web service...