Error: A communication failure occurred while attempting to obtain an initial context with the provider URL: "iiop://hostname:2825".
During the installation of the InfoSphere Information Server engine tier onto a separate server from the Domain/Repository tier, the following error occurred. This same also occur when DataStage clients attempt to login to DataStage server.
Error The following exception has occurred:
A communication failure occurred while attempting to obtain an initial context with the provider URL: "iiop://hostname:2825". Make sure that any bootstrap address information in the URL is correct and that the target name server is running. A bootstrap address with no port specification defaults to port 2809.
DataStage clients may also receive the related error message:
"Failed to authenticate the current user against the selected domain. You are attempting to connect to server[servername]. This server is configured to communicate with clients using hostname [hostname] on port . [servername]:2809] is not reachable. Ensure that the [servername] can be resolved and that communication on port  between this machine and the server is not blocked."
Resolving the problem
This error typically occurs for new installations of client and server. The most common cause is that the client is unable to fully resolve the hostname OR the host server is unable to resolve the hostname sent from client when used in loopback connection.
The hostname DataStage clients login to, as well as the hostname of each DataStage server must resolve to the same TCP/IP address on the client machine and on all server tiers.
You can test this by using the ping command on the client machine and each server machine to confirm that the hostname resolves to the same address on all machines. If the short hostname is used in some cases and fully qualified hostname in others, then confirm both formats for the hostname resolve to same address on all machines.
To resolve this problem, please check the following:
- Confirm that the hosts file on all tiers contains the hostname of each tier, defining both the short host name and also the fully qualified hostname (domain appended). For example:
126.96.36.199 hostname1 hostname1.ibm.com
188.8.131.52 hostname2 hostname2.ibm.com
On Unix systems, the hosts file is /etc/hosts . For Windows, the file is \windows\system32\drivers\etc\hosts .
- Ensure that the entries for the above hosts exists on each system and that the TCP/IP address is the same on each system. Ping the hostname (both shortname and fully qualified) from each server machine to confirm.
- Confirm the hosts file also has a "localhost" entry that points to 127.0.0.1
- Confirm the bootstrap port address used by WebSphere. This will typically be listed in the serverindex.xml file which defaults to the following location (for Information Server 8.5 and later, replace "default" with "InfoSphere" in path):
Browse that file and look for the line with keyword BOOTSTRAP_ADDRESS to find the assigned bootstrap port address (usually 2809).
Then use "netstat -na" command to confirm if any process other than WebSphere is using that port. (There should be no usage of that port if this is done when WebSphere is shut down).
- Verify that the DataStage client and server are the same version and release. For example, if a user with DataStage 8.0.1 client tries to connect to a DataStage 8.1 server, the login will fail with various communication errors.
Another possible cause of connection problems occurs when the DataStage server is behind a firewall. Please refer to the following technote for additional information on accessing a DataStage server behind a firewall:
DataStage: Designer client, Manager client, and Director clients cannot connect to DataStage server when the server is behind a firewall
|Information Management||InfoSphere DataStage||Not Applicable||AIX, HP-UX, Linux, Solaris, Windows||8.1, 8.0.1, 8.0|
More support for:
Software version: 8.0, 8.0.1, 8.1, 8.5, 8.7
Operating system(s): AIX, HP-UX, Linux, Solaris, Windows
Reference #: 1391139
Modified date: 13 February 2013
Translate this page: