weblogic.management.NoAccessRuntimeException

Access not allowed for subject: pr incipals=[], on ResourceType: ServerConfig Action: execute, Target: lookupServer Runtime

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web195

  • via Oracle Community by 3004, 1 year ago
    Access not allowed for subject: pr incipals=[], on ResourceType: ServerConfig Action: execute, Target: lookupServer Runtime
  • via Google Groups by Vasu, 3 weeks ago
    Access not allowed for subject: pr incipals=[], on ResourceType: ServerConfig Action: execute, Target: lookupServer Runtime
  • Access not allowed for subject: pr incipals=[], on ResourceType: ServerConfig Action: execute, Target: lookupServer Runtime
  • Stack trace

    • weblogic.management.NoAccessRuntimeException: Access not allowed for subject: pr incipals=[], on ResourceType: ServerConfig Action: execute, Target: lookupServer Runtime at weblogic.management.internal.Helper$IsAccessAllowedPrivilegeAction.run(Helper.java:2012) at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:721) at weblogic.management.internal.Helper.isAccessAllowed(Helper.java:1857) at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:918) at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:359) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313) at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:762) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:308) at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequestjava:30) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.