Ear Deploy Via Console Failure - ToolFailureException [J2EE:160111] ERROR - Appc can not write to the working directory

(Doc ID 1135483.1)

Last updated on FEBRUARY 11, 2017

Applies to:

Oracle Weblogic Server - Version: 9.2 and later   [Release: and later ]
Information in this document applies to any platform.

Symptoms

Customers have reported an issue with deploying an EAR file via the admin console. The customer has removed the older application version from the console and tried to deploy the new one. Customer has stopped managed servers, cleared cache, restarted managed server, then he tried to deploy the new ear via console. However it does not allow the customer to deploy the EAR and throws following error:

####<Jun 25, 2010 3:10:13 AM EDT> <Warning> <RMI> <unixs829> <ds1c2ms4> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1277449813168> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.corba.cos.naming.RootNamingContextImpl.resolve([Lorg.omg.CosNaming.NameComponent;)
org.omg.CORBA.NO_PERMISSION: User <anonymous> does not have permission on weblogic.management.mbeanservers to perform lookup operation. vmcid: 0x0 minor code: 0 completed: No.
org.omg.CORBA.NO_PERMISSION: User <anonymous> does not have permission on weblogic.management.mbeanservers to perform lookup operation. vmcid: 0x0 minor code: 0 completed: No
at weblogic.corba.cos.naming.NamingContextImpl.throwNamingException(NamingContextImpl.java:509)
at weblogic.corba.cos.naming.NamingContextImpl.resolve(NamingContextImpl.java:169)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms