weblogic.management.DeploymentException: weblogic.application.ApplicationException: FRM-60104 Forms is not configured under Oracle Instance /TST/app/oracle/product/OFM_Middleware/asinst_1. Aborting deployment of Forms J2EE application formsapp.

Oracle Community | user6480399 | 7 years ago
  1. 0

    Deploying formsapp gives FRM-60104 Forms is not configured error

    Oracle Community | 7 years ago | user6480399
    weblogic.management.DeploymentException: weblogic.application.ApplicationException: FRM-60104 Forms is not configured under Oracle Instance /TST/app/oracle/product/OFM_Middleware/asinst_1. Aborting deployment of Forms J2EE application formsapp.
  2. 0

    Custom Managed Bean in OIM 11gR2PS2

    Oracle Community | 2 years ago | 2657125
    weblogic.management.DeploymentException: Cannot undeploy library Extension-Name: oracle.iam.ui.custom, Specification-Version: 11.1.1, Implementation-Version: 11.1.1 from server oim_server1, because the following deployed applications reference it: oracle.iam.console.identity.self-service.war, oracle.iam.console.identity.sysadmin.war
  3. 0

    Failed to start 'soa-infra'

    Oracle Community | 8 months ago | SivaBalan19
    weblogic.management.DeploymentException: [J2EE:160177]The application at "D:\Oracle\Middleware\Oracle_SOA1\soa\connectors\AqAdapter.rar" was not recognized as a valid application type. If this is an EAR file, please ensure the META-INF/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose name ends with "-jms.xml". A JDBC deployment should be an XML file whose name ends with "-jdbc.xml". For other application types, please consult the WebLogic Server documentation.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Failed to start 'soa-infra'

    Oracle Community | 8 months ago | SivaBalan19
    weblogic.management.DeploymentException: [J2EE:160177]The application at "D:\Oracle\Middleware\Oracle_SOA1\soa\connectors\JmsAdapter.rar" was not recognized as a valid application type. If this is an EAR file, please ensure the META-INF/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose name ends with "-jms.xml". A JDBC deployment should be an XML file whose name ends with "-jdbc.xml". For other application types, please consult the WebLogic Server documentation.
  6. 0

    Unable to deploy Mediator to soa_server

    Oracle Community | 3 years ago | Justin_Michael_Raj
    weblogic.management.DeploymentException: [J2EE:160177] The application at "C:\Oracle\orasoa11g\wls\Middleware\user_projects\domains\soa_domain\servers\soa_server1\stage\sca_mediator1_rev1\sca_mediator1_rev1.0.jar" was not recognized as a valid application type. If this is an EAR file, please ensure the META-INF/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose name ends with "-jms.xml". A JDBC deployment should be an XML file whose name ends with "-jdbc.xml". For other application types, please consult the WebLogic Server documentation.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. weblogic.management.DeploymentException

      weblogic.application.ApplicationException: FRM-60104 Forms is not configured under Oracle Instance /TST/app/oracle/product/OFM_Middleware/asinst_1. Aborting deployment of Forms J2EE application formsapp.

      at weblogic.deploy.event.DeploymentEventManager.sendVetoableDeploymentEvent()
    2. weblogic.deploy.event
      DeploymentEventManager.sendVetoableDeploymentEvent
      1. weblogic.deploy.event.DeploymentEventManager.sendVetoableDeploymentEvent(DeploymentEventManager.java:337)
      1 frame
    3. weblogic.deploy.internal
      DeploymentServiceDispatcher.prepare
      1. weblogic.deploy.internal.targetserver.operations.AbstractOperation.fireVetoableDeploymentEvent(AbstractOperation.java:781)
      2. weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:216)
      3. weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
      4. weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
      5. weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
      6. weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
      6 frames
    4. weblogic.deploy.service
      DeploymentReceiverCallbackDeliverer$1.run
      1. weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
      2. weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
      3. weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
      3 frames
    5. weblogic.work
      ExecuteThread.run
      1. weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
      2. weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
      3. weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
      3 frames