OSM WLS Server Failed With Error - principal name 'oms-internal' but a principal of that name could not be found. Please ensure a user with that name exists (Doc ID 1641753.1)

Last updated on FEBRUARY 16, 2017

Applies to:

Oracle Communications Order and Service Management - Version 7.2.2 to 7.2.4 [Release 7.2]
Information in this document applies to any platform.
Review relevance Sept 14, 2015
Review relevance Feb 16, 2017

Symptoms

<Mar 27, 2014 10:06:17 AM EDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'oms' due to error weblogic.management.DeploymentException: [J2EE:160204]The ApplicationLifecycleListener 'com.mslv.oms.j2ee.LifecycleListener' of application 'oms' has a run-as user configured with the principal name 'oms-internal' but a principal of that name could not be found. Please ensure a user with that name exists..
weblogic.management.DeploymentException: [J2EE:160204]The ApplicationLifecycleListener 'com.mslv.oms.j2ee.LifecycleListener' of application 'oms' has a run-as user configured with the principal name 'oms-internal' but a principal of that name could not be found. Please ensure a user with that name exists.
       at weblogic.application.internal.flow.HeadLifecycleFlow.getRunAsIdentity(HeadLifecycleFlow.java:245)
       at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:183)
       at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:281)
       at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648)
       at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
       at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
       at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59)
       at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
       at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
       at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:144)
       at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
       at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
       at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
       at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
       at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
       at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
       at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
       at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
       at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
       at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
       at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)


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