Troubleshooting
Problem
Running Application Client, remotely connecting to WebSphere Application Server (WAS) version 8.0.0.3 (after migration from version 7) on the server side, getting error: 'javax.naming.NamingException: Error getting WsnNameService properties [Root exception is org.omg.CORBA.TRANSIENT: initial and forwarded IOR inaccessible vmcid: IBM minor code: E07 completed: No] at com.ibm.ws.naming.util.WsnInitCtxFactory.mergeWsnNSProperties(WsnInitCtxFactory.java:1482) at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServer(WsnInitCtxFactory.java:989) at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:909) at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:581) at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:124) at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:799) at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:165) at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:180) at javax.naming.InitialContext.lookup(InitialContext.java:436)
Cause
Server side has CSIv2 Transport Layer -> Transport set to SSL-Required, which is the default in WAS version 8, but client side was not set up for SSL.
Resolving The Problem
Go to the WAS Administrative Console and change the WAS Global Security settings, specify the CSIv2 inbound and outbound transports to "SSL-Supported", restart the server
Security -> Global security, then go to CSIv2 inbound communications (and outbound communications as well) -> CSIv2 Transport Layer -> Transport, change SSL-Required (the default in V8) to SSL-Supported
Common Secure Interoperability Version 2 transport inbound settings
http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=%2Fcom.ibm.websphere.nd.multiplatform.doc%2Finfo%2Fae%2Fae%2Fusec_inbound.html
Historical Number
PMR 07112;999;000
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21614221