WSDL generated in TIBCO BW 5.9.3 is throwing SOAP Version mismatch when trying to get invoked from VB.NET

[Shunmuga Rajan]

Our requirement is to replace the existing dotnet webservice with TIBCO Webservice and the client is a VB.Net application.

The following error can be seen once the Endpoint url of the newly built TIBCO Webservice is invoked from VB.net and the below error is getting fixed only when the VB.net code is getting compiled, but we agreed to allow or do a config change of Endpoint url only in the existing VB.NET code but the below error is forcing a VB.net code compilation which is fixing the below error.

Possible SOAP version mismatch:

Envelope namespacehttp://schemas.xmlsoap.org/wsdl/was unexpected.

Expectinghttp://www.w3.org/2003/05/soap-envelope.

Can some one say is that the above error which is provoking for a code compilation ( for the definition to get downloaded as we invoke and mapped to VB.net code) is due to the non dot net technology build WSDL (TIBCO's WSDL) and as per my understanding TIBCO has build the WSDL in xml format which is usable for SOAP call and I dont understand why the VB.NET wasnt in sync with WSDL without compiling the code Please can some one share your experience