The client does not connect to server

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
Jorge Juillerat
Premium Member
Premium Member
Posts: 6
Joined: Thu Jun 01, 2006 11:29 am
Location: SANTIAGO, CHILE
Contact:

The client does not connect to server

Post by Jorge Juillerat »

Install the entire platform ISV8.1 on RedHat 4, to connect via the Web Server_Name: 9080 from the client I have no problems, but if I connect with the designer of DataStage gives me the following error:

Failed to authenticate the current user against the selected Domain
A communication failure occurred while attempting to obtain an initial context with the provider URL: "iiop://InfoServer:2810". 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. Possible causes other than an incorrect bootstrap address or unavailable name server include the network environment and workstation network configuration.
javax.security.auth.login.LoginException: A communication failure occurred while attempting to obtain an initial context with the provider URL: "iiop://InfoServer:2810". 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. Possible causes other than an incorrect bootstrap address or unavailable name server include the network environment and workstation network configuration.
at com.ascential.acs.security.auth.JAASAuthenticationService$WASServer.init(JAASAuthenticationService.java:584)
at com.ascential.acs.security.auth.JAASAuthenticationService.loginImpl(JAASAuthenticationService.java:321)
at com.ascential.acs.security.auth.JAASAuthenticationService.login(JAASAuthenticationService.java:160)
at com.ascential.acs.security.auth.client.AuthenticationService.doLoginImpl(AuthenticationService.java:879)
at com.ascential.acs.security.auth.client.AuthenticationService.doLogin(AuthenticationService.java:365)
Caused by: javax.naming.ServiceUnavailableException: A communication failure occurred while attempting to obtain an initial context with the provider URL: "iiop://InfoServer:2810". 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. Possible causes other than an incorrect bootstrap address or unavailable name server include the network environment and workstation network configuration. [Root exception is org.omg.CORBA.INTERNAL: initial and forwarded IOR inaccessible vmcid: IBM minor code: 58C completed: No]
at com.ibm.ws.naming.util.WsnInitCtxFactory.mapInitialReferenceFailure(WsnInitCtxFactory.java:1975)
at com.ibm.ws.naming.util.WsnInitCtxFactory.mergeWsnNSProperties(WsnInitCtxFactory.java:1179)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServer(WsnInitCtxFactory.java:727)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:650)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:497)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:113)
at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:428)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:144)
at javax.naming.InitialContext.lookup(InitialContext.java:363)
at com.ascential.acs.security.auth.JAASAuthenticationService$WASServer.init(JAASAuthenticationService.java:541)
... 4 more
Caused by: org.omg.CORBA.INTERNAL: initial and forwarded IOR inaccessible vmcid: IBM minor code: 58C completed: No
at com.ibm.rmi.corba.ClientDelegate.createRequest(ClientDelegate.java:1213)
at com.ibm.CORBA.iiop.ClientDelegate.createRequest(ClientDelegate.java:1320)
at com.ibm.rmi.corba.ClientDelegate.createRequest(ClientDelegate.java:1109)
at com.ibm.CORBA.iiop.ClientDelegate.createRequest(ClientDelegate.java:1286)
at com.ibm.rmi.corba.ClientDelegate.request(ClientDelegate.java:1816)
at com.ibm.CORBA.iiop.ClientDelegate.request(ClientDelegate.java:1242)
at org.omg.CORBA.portable.ObjectImpl._request(ObjectImpl.java:458)
at com.ibm.WsnBootstrap._WsnNameServiceStub.getProperties(Unknown Source)
at com.ibm.ws.naming.util.WsnInitCtxFactory.mergeWsnNSProperties(WsnInitCtxFactory.java:1162)
... 12 more




I do not understand this error message !!!
suryapkakani
Participant
Posts: 47
Joined: Wed Aug 20, 2008 7:31 am
Location: New jersey

Re: The client does not connect to server

Post by suryapkakani »

The topic says resolved..can you tell me what have you done to resolve this error.
sunny
sydphi
Premium Member
Premium Member
Posts: 13
Joined: Thu Mar 20, 2008 3:03 pm

Post by sydphi »

We had to add the ip of the server name to the /etc/hosts file on RedHat server on a separate line. The upgrade had matched 127.0.0.1 to our server name so our client couldn't connect to it.

Thanks
Post Reply