weblogic.ejb20.WLDeploymentException: The run-as principal 'portaladmin' for EJB 'MailService' is not a user in the current realm. The user must exist for the EJB to successfully deploy.

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 666705, 1 year ago
The run-as principal 'ProcessInjectorMessageBeanUser' for EJB 'com/OrchestratorMessageBean' is not a user in the current realm. The user must exist for the EJB to successfully deploy.
via Oracle Community by 3004, 1 year ago
The run-as principal 'portaladmin' for EJB 'MailService' is not a user in the current realm. The user must exist for the EJB to successfully deploy.
via Oracle Community by 3004, 4 months ago
The run-as principal 'portaladmin' for EJB 'MailService' is not a user in the current realm. The user must exist for the EJB to successfully deploy.
via wpthm.com by Unknown author, 2 years ago
The run-as principal 'portaladmin' for EJB 'MailService' is not a user in the current realm. The user must exist for the EJB to successfully deploy.
via Google Groups by andrew, 5 months ago
The run-as principal 'escappuser' for EJB 'JobSchedulerMDB' is not a user in the current realm. The user must exist for th e EJB to successfully deploy.
via Google Groups by andrew, 1 year ago
The run-as principal 'escappuser' for EJB 'JobSchedulerMDB' is not a user in the current realm. The user must exist for th e EJB to successfully deploy.
weblogic.ejb20.WLDeploymentException: The run-as principal 'portaladmin' for EJB 'MailService' is not a user in the current realm. The user must exist for the EJB to successfully deploy.
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.getRunAsPrincipal(MBeanDeploymentInfoImpl.java:1047)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeRunAsSettings(MBeanDeploymentInfoImpl.java:838)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.(MBeanDeploymentInfoImpl.java:246)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1262)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2962)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1534)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2602)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2552)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Know the solutions? Share your knowledge to help other developers to debug faster.