weblogic.management.NoAccessRuntimeException

Access not allowed for subject: principals=[], on ResourceType: ServerConfig Action: execute, Target: lookupServerRuntime

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 Google Groups by Vina Wang, 1 month ago
    Access not allowed for subject: principals=[], on ResourceType: ServerConfig Action: execute, Target: lookupServerRuntime
  • via Google Groups by Steven Ostrowski, 1 month ago
    Access not allowed for subject: principals=[], on ResourceType: ServerConfig Action: execute, Target: lookupServerRuntime
  • via Google Groups by Mark, 1 month ago
    Access not allowed for subject: principals=[system], on ResourceType: ServerConfig Action: execute, Target: lookupServerRuntime
  • Stack trace

    • weblogic.management.NoAccessRuntimeException: Access not allowed for subject: principals=[], on ResourceType: ServerConfig Action: execute, Target: lookupServerRuntime at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeAction.wlsRun(SecurityHelper.java:557) at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeAction.run(SecurityHelper.java:453) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118) at weblogic.management.internal.SecurityHelper.isAccessAllowed(SecurityHelper.java:347) at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:764) at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:404) at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

    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.