Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 988501, 1 year ago
Unhandled exception in lookup [Root exception is org.omg.CORBA.NO_PERMISSION: vmcid: 0x0 minor code: 0 completed: No] [java]
via Oracle Community by 711825, 1 year ago
Unhandled exception in lookup [Root exception is org.omg.CORBA.NO_PERMISSION: vmcid: 0x0 minor code: 0 completed: No]
via Oracle Community by 843830, 1 year ago
Unhandled exception in lookup [Root exception is org.omg.CORBA.BAD_OPERATION: vmcid: 0x0 minor code: 0 completed: No]
via Oracle Community by 843830, 1 year ago
Unhandled exception in lookup [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
via Oracle Community by 666705, 1 year ago
Unhandled exception in lookup [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 208 completed: Maybe]
via Stack Overflow by John Ament
, 2 years ago
Unhandled exception in lookup [Root exception is org.omg.CORBA.MARSHAL: vmcid: SUN minor code: 257 completed: Maybe]
javax.naming.NamingException: Unhandled exception in lookup [Root exception is org.omg.CORBA.NO_PERMISSION:   vmcid: 0x0  minor code: 0  completed: No]
[java]	at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:83)	at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:291)	at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:227)	at javax.naming.InitialContext.lookup(InitialContext.java:392)	at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:179)