Last updated on SEPTEMBER 15, 2017
Applies to:Oracle Containers for J2EE - Version: 10.1.2.0.0 to 10.1.3.5.0 - Release: AS10gR2 to AS10gR3
Information in this document applies to any platform.
***Checked for relevance on 15-Apr-2010***
Failed at "Could not get DeploymentManager".
This is typically the result of an invalid deployer URI format being supplied, the target server
not being in a started state or incorrect authentication details being supplied.
Deploying the ear-file directly from the Oracle AS console is done without problems.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms