ERROR: Unable to import binding 'ServiceBinding' from namespace

Technote (troubleshooting)


Problem(Abstract)

Attempts to generate a C# proxy using Microsoft .NET using the web services description language (WSDL) from WebSphere Studio Application Developer results in the error "ERROR: Unable to import binding 'ServiceBinding' ERROR: Unable to import binding 'ServiceBinding' from namespace 'http://www.myURL.com/definitions/ServiceRemoteInterface'.

Cause

A few of the more common reasons why the location URL may not be reachable are:

  1. The Service documents are being processed (by .NET) on a different host than the server and so the "localhost" in the location URLs are effectively pointing to the wrong system.
  2. The Web application server hosting the Service documents is not running.
  3. The Service documents have been renamed or removed.
  4. The web module name or context root has been changed.

Diagnosing the problem

The problem could have been caused by the location URL of Service-schema.xsd specified in the <import> element in Service-binding.wsdl could not be opened and read by Microsoft .NET.


To verify this, open your Web browser and enter the location URL from the <import> element:

http://localhost:8080/myURL/wsdl/Service-schema.xsd

If your browser is unable to load this document, then .NET will also be unable to load the document and will then be unable to locate the {class}.Query type.


Resolving the problem

In most of these cases, changing the value of the <import> location URL will solve the problem.


For example, in step 1, replace "localhost" by the true hostname of the server (or deploy the original service to a Remote WebSphere(R) instance instead of a Unit Test WebSphere instance, since remote yields the true hostname automatically).

For WebSphere Studio version 5.0.x, please consult the Web Services tool readme found in your installation directory of WebSphere Studio for interoperability issues under section 4.8 Interoperability.
(x:\WebSphere Studio\readme\ws\readme_webservice.html, where x: is your installation location of WebSphere Studio)

For WebSphere Studio version 5.1, please consult the Web Services tool readme found in your installation directory of WebSphere Studio for interoperability issues under section 4.3 Interoperability with IBM SOAP runtime.
(x:\WebSphere Studio\Application Developer\v5.1\readme\ws\readme_webservice_wsad_win32.html, where x: is your installation location of WebSphere Studio)

If these suggestions did not help, it is possible there is a defect in WSDL.EXE. Try contacting Microsoft for further assistance.


Cross reference information
Segment Product Component Platform Version Edition
Business Integration WebSphere Studio Application Developer Integration Edition Web Service Windows, Linux 4.1, 4.1.1, 5.0, 5.0.1 All Editions
Business Integration WebSphere Studio Enterprise Developer Web Service Linux/390, Windows 5.0, 5.0.1 All Editions

Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Studio Application Developer
Web Service

Software version:

5.0, 5.0.1, 5.1

Operating system(s):

Linux, Windows

Reference #:

1113231

Modified date:

2012-01-27

Translate my page

Machine Translation

Content navigation