Error in load file while deploying EPM Application View of HFM

Started Time : Friday, September 19, 2008 10:06:55 AM
Submitted Time : Friday, September 19, 2008 10:06:55 AM
Last Updated Time : Friday, September 19, 2008 10:45:02 AM
User Name : admin
Process Name :
Thread : 0
Server : DimServer
Detail : Errors occurred in load file
Status : Aborted
Progress : 100%
Can anyone help?

Hi,
This error will come when the services are not running properly.
When we encounter this error we normally restart the Hyperion Services and its gets resolved.
you may want to try the same.

Similar Messages

  • Error  in XML file while deploying in server

    Hi friends,
    I am Venkataramana . I am doing one small structs application with Validation . as usual in XML file i wrote validations but when i am deploying in server it is showing error as
    SEVERE: Parse Error at line 2 column 17: Document is invalid: no grammar found.
    org.xml.sax.SAXParseException: Document is invalid: no grammar found.
         at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
    and
    Jan 11, 2010 11:57:53 PM org.apache.commons.digester.Digester error
    SEVERE: Parse Error at line 2 column 17: Document root element "form-validation", must match DOCTYPE root "null".
    org.xml.sax.SAXParseException: Document root element "form-validation", must match DOCTYPE root "null".
    Kindly find the validation.xml file for your reference.
    <!DOCTYPE form-validation PUBLIC
    "-//Apache Software Foundation//DTD Commons Validator Rules Configuration 1.1.3//EN"
    "http://jakarta.apache.org/commons/dtds/validator_1_1_3.dtd">
    <form-validation>
    <formset>
    <form name="regFormForm">
    <field property="username"
    depends="required">
    <arg0 key="uname"/>
    </field>
    <field property="password"
    depends="required">
    <arg0 key="password"/>
    </field>
    </form>
    </formset>
    </form-validation>
    Please can any one help on this?

    I think your dtd entry - "http://jakarta.apache.org/commons/dtds/validator_1_1_3.dtd" is not compatible with your validation.jar file. If you have recently downloaded the these struts jar files then make sure this entry is matched with what they have provided in examples. Or download new set of jar files and copy the same doc-type tag as they have given in examples.

  • Error While deploy VC Application and Par file

    Hi Experts,
    The deployment of par or VC application worked fine, but last one week i am getting error while deploying par or VC application.
    I am getting pop-up window while deploy VC Application. That pop-up window shows Portal Request Failed. (com/sap/netweaver/bc/uwl/UWLException).
    I am getting Error like this, Please Check the user ID and password, while deploying par from NWDS.
    I have checked my userid and password, it is correct. I checked with admin userid and password, it shows the same error.  it is showing same for my team members userid also.
    I have checked logs and traces in server, nothing is logging regarding this deployment error.
    Where is the problem, please anybody help me.  I am using EP7 SP9.
    Thanks and Regards,
    Chinnadurai R

    Hi Detlev,
    I checked all the permission in the SECURITY ZONES, all the setting are correct in the portal.
    I informed to our BASIS Team, they found that problem is, one process always running in SDM. It didnt let to deploy another PAR file. They cann't able to open the SDM after gave the SDM username and password, its shows "still processing". So, how can we kill the process ? They restarted the SDM and also J2EE Engine, its still processing. After that they restarted the Machine also, still the process going on.
    How can we rectify the problem ?..
    Thanks & Regards
    Chinnadurai R

  • Error while deploying Webdynpro Application in CE 7.1.1

    Hi,
    Im developing Webdynpro DC application in CE 7.1.1. ( Composite Environment 7.1 Enhancement Pack 1)  While deploying the application im getting error saying ,
    Error: "Application error occurred during the request processing."
      Troubleshooting Guide https://sdn.sap.com/irj/sdn/wiki?path=/display/jsts/home
    Details: com.sap.tc.webdynpro.services.sal.core.DispatcherException: The requested deployable object 'demo.sap.com/firstdc' is not deployed on the server. Please check the used URL for typos.
    +     at com.sap.tc.webdynpro.clientserver.task.Task.getDeployableObject(Task.java:364)+
    +     at com.sap.tc.webdynpro.clientserver.session.RequestManager.initApplicationDeployableObjectPart(RequestManager.java:566)+
    +     at com.sap.tc.webdynpro.clientserver.session.RequestManager.initTask(RequestManager.java:504)+
    +     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doInitWdEnvironment(RequestManager.java:169)+
    +     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:230)+
    +     at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)+
    +     at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)+
    +     at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)+
    +     at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)+
    +     at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)+
    +     at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)+
    +     at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)+
    +     at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)+
    +     at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:54)+
    +     at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)+
    +     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)+
    +     at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)+
    +     at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)+
    +     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)+
    +     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)+
    +     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)+
    +     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)+
    +     at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)+
    +     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)+
    +     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)+
    +     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)+
    +     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)+
    +     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)+
    +     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)+
    +     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
    +     at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:425)+
    +     at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250)+
    +     at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)+
    +     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)+
    +     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)+
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create deployable object 'demo.sap.com/firstdc' since it is not a Web Dynpro object.
    +     at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:87)+
    +     at com.sap.tc.webdynpro.services.sal.deployment.core.DeployableObjectInternal.getDeployableObjectInternal(DeployableObjectInternal.java:37)+
    +     at com.sap.tc.webdynpro.clientserver.task.Task.getDeployableObject(Task.java:362)+
    +     ... 50 more+
    Caused by: com.sap.tc.webdynpro.spi.WebDynproRuntimeException: No Web Dynpro application (deployable object) with name demo.sap.com/firstdc exists.
    +     at com.sap.engine.services.webdynpro.WebDynproRuntimeServiceImpl.getDeployableObject(WebDynproRuntimeServiceImpl.java:264)+
    +     at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:85)+
    +     ... 52 more+
    Pls provide me the solution.
    thanks in advance,
    raji

    Hi Veera/Abhi
    I have installed MinDB and all the required files on the PDA. It is synchronizing with the middleware.
    On my NWDS PDA  Simulator , the application is appearing but when i click on the application there is no data and it is giving exception
    2009-02-11 13:02:40 ...  (com.sap.tc.mobile.cfs.pers.PersistenceManager:release resultset) Thread: Finalizer Error: java.sql.SQLException: Result set is closed
    Madhu--
    Please find my ans to the following points mentioned by you
    1) BASIS SWCV must be assigned in the Distribution Model Software Component Version tab of the device.
    It is assigned
    2) Activate the "DISTRIBUTE_USER_DETAILS" Rule in the admin.
    Rule is activated
    3) Activate the "DISTRIBUTE_USER_AUTHORIZATIONS" Rule in the admin.
    Rule is activated
    4) Make sure that you have installed the following components in the following sequence in the PDA
    - Creme
    - MinDB/DB2e
    - PDA_eswt_container
    - PDA Runtime.
    Client is  installed in this sequence only. I referrred to help.sap.com while installing
    the application should atleast work in the NWDS PDA simulator. My basic problem is it is not picking  up the data. giving the above mentioned error.
    Regards
    Priya

  • Error while deploying adf application using ant script or jdevloper IDE

    Hi All,
    While deploying adf application into cluster weblogic server I am getting strange error though my weblogic server is working fine as I checked it from weblogic console. Seems that there is some heap memory issue but don’t know the exact cause as it work perfectly if I restart the server.
    Same error i get when i try to deploy application from Jdeveloper IDE though it created the server connection successfully.
    Please help me by provided valuable tips to overcome this problem or any special tips to optimize weblogic server for ADF.
    Thanks in advance
    Error Reference:
    Buildfile: builddeploy.xml
    deploy:
    [wldeploy] weblogic.Deployer -debug -stage -verbose -upload -noexit -name admin -source W:\GRS\TEMP_RELEASE\ADFNEW\RSWG_PROJECTS\RSWGADMIN\GRSWEBAPPADMIN\deploy\admin.war -targets ADR_Cluster_1 -adminurl t3://WebServercom:7001 -user weblogic -password ******** -deploy
    [wldeploy] weblogic.Deployer invoked with options: -debug -stage -verbose -upload -noexit -name admin -source W:\GRS\TEMP_RELEASE\ADFNEW\RSWG_PROJECTS\RSWGADMIN\GRSWEBAPPADMIN\deploy\admin.war -targets ADR_Cluster_1 -adminurl t3://WebServercom:7001 -user weblogic -deploy
    [wldeploy] [WebLogicDeploymentManagerImpl.<init>():103] : Constructing DeploymentManager for J2EE version V1_4 deployments
    [wldeploy] [WebLogicDeploymentManagerImpl.getNewConnection():146] : Connecting to admin server at WebServercom:7001, as user weblogic
    [wldeploy] [ServerConnectionImpl.getEnvironment():286] : setting environment
    [wldeploy] [ServerConnectionImpl.getEnvironment():289] : getting context using t3://WebServercom:7001
    [wldeploy] [ServerConnectionImpl.getMBeanServer():237] : Connecting to MBeanServer at service:jmx:t3://WebServercom:7001/jndi/weblogic.management.mbeanservers.domainruntime
    [wldeploy] [ServerConnectionImpl.getMBeanServer():237] : Connecting to MBeanServer at service:jmx:t3://WebServercom:7001/jndi/weblogic.management.mbeanservers.runtime
    [wldeploy] [DomainManager.resetDomain():36] : Getting new domain
    [wldeploy] [DomainManager.resetDomain():39] : Using pending domain: false
    [wldeploy] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@1d27069
    [wldeploy] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@1d27069
    [wldeploy] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@200db9
    [wldeploy] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@200db9
    [wldeploy] [ServerConnectionImpl.initialize():169] : Connected to WLS domain: ADR_domain
    [wldeploy] [ServerConnectionImpl.setRemote():480] : Running in remote mode
    [wldeploy] [ServerConnectionImpl.init():159] : Initializing ServerConnection : [email protected]21b
    [wldeploy] [BasicOperation.dumpTmids():706] : Incoming tmids:
    [wldeploy] [BasicOperation.dumpTmids():708] : {Target=ADR_Cluster_1, WebLogicTargetType=cluster, Name=admin}, targeted=true
    [wldeploy] [BasicOperation.deriveAppName():140] : appname established as: admin
    [wldeploy] <23-Sep-2011 11:05:14 o'clock BST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, admin [archive: W:\GRS\TEMP_RELEASE\ADFNEW\RSWG_PROJECTS\RSWGADMIN\GRSWEBAPPADMIN\deploy\admin.war], to ADR_Cluster_1 .>
    [wldeploy] [ServerConnectionImpl.upload():849] : Uploaded app to /data/app/Oracle/Middleware/user_projects/domains/ADR_domain/servers/AdminServer/upload/admin
    [wldeploy] [BasicOperation.dumpTmids():706] : Incoming tmids:
    [wldeploy] [BasicOperation.dumpTmids():708] : {Target=ADR_Cluster_1, WebLogicTargetType=cluster, Name=admin}, targeted=true
    [wldeploy] [BasicOperation.loadGeneralOptions():623] : Delete Files:false
    [wldeploy] Timeout :3600000
    [wldeploy] Targets:
    [wldeploy] ADR_Cluster_1
    [wldeploy] ModuleTargets={}
    [wldeploy] SubModuleTargets={}
    [wldeploy] }
    [wldeploy] Files:
    [wldeploy] null
    [wldeploy] Deployment Plan: null
    [wldeploy] App root: \data\app\Oracle\Middleware\user_projects\domains\ADR_domain\servers\AdminServer\upload\admin
    [wldeploy] App config: \data\app\Oracle\Middleware\user_projects\domains\ADR_domain\servers\AdminServer\upload\admin\plan
    [wldeploy] Deployment Options: {isRetireGracefully=true,isGracefulProductionToAdmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=-1,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=false,libSpecVersion=null,libImplVersion=null,stageMode=stage,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=admin,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSubmoduleTargets=true,timeout=0,deploymentPrincipalName=null,useExpiredLock=false}
    [wldeploy]
    [wldeploy] [BasicOperation.execute():440] : Initiating deploy operation for app, admin, on targets:
    [wldeploy] [BasicOperation.execute():442] : ADR_Cluster_1
    [wldeploy] Task 5 initiated: [Deployer:149026]deploy application admin on ADR_Cluster_1.
    [wldeploy] dumping Exception stack
    [wldeploy] Task 5 failed: [Deployer:149026]deploy application admin on ADR_Cluster_1.
    [wldeploy] Target state: deploy failed on Cluster ADR_Cluster_1
    [wldeploy] java.lang.Exception: [DeploymentService:290036]Deployment for request id '1316772356780' is deferred since target 'ADR_ManagedServer_2' is disconnected.
    [wldeploy]      at weblogic.deploy.service.internal.adminserver.AdminRequestStatus.commitFailedDueToServerDisconnect(AdminRequestStatus.java:1870)
    [wldeploy]      at weblogic.deploy.service.internal.adminserver.AdminRequestStatus.access$600(AdminRequestStatus.java:51)
    [wldeploy]      at weblogic.deploy.service.internal.adminserver.AdminRequestStatus$CommitDisconnectListenerImpl.onDisconnect(AdminRequestStatus.java:2042)
    [wldeploy]      at weblogic.deploy.service.internal.transport.ServerDisconnectManager$ServerDisconnectListenerImpl.onDisconnect(ServerDisconnectManager.java:124)
    [wldeploy]      at weblogic.deploy.service.internal.transport.ServerDisconnectManager$ServerConnectDisconnectListenerImpl$2.run(ServerDisconnectManager.java:219)
    [wldeploy]      at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    [wldeploy]      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    [wldeploy]      at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    [wldeploy]
    [wldeploy]
    [wldeploy] Target Assignments:
    [wldeploy] + admin ADR_Cluster_1
    [wldeploy] weblogic.deploy.api.tools.deployer.DeployerException: Task 5 failed: [Deployer:149026]deploy application admin on ADR_Cluster_1.
    [wldeploy] Target state: deploy failed on Cluster ADR_Cluster_1
    [wldeploy] java.lang.Exception: [DeploymentService:290036]Deployment for request id '1316772356780' is deferred since target 'ADR_ManagedServer_2' is disconnected.
    [wldeploy]      at weblogic.deploy.service.internal.adminserver.AdminRequestStatus.commitFailedDueToServerDisconnect(AdminRequestStatus.java:1870)
    [wldeploy]      at weblogic.deploy.service.internal.adminserver.AdminRequestStatus.access$600(AdminRequestStatus.java:51)
    [wldeploy]      at weblogic.deploy.service.internal.adminserver.AdminRequestStatus$CommitDisconnectListenerImpl.onDisconnect(AdminRequestStatus.java:2042)
    [wldeploy]      at weblogic.deploy.service.internal.transport.ServerDisconnectManager$ServerDisconnectListenerImpl.onDisconnect(ServerDisconnectManager.java:124)
    [wldeploy]      at weblogic.deploy.service.internal.transport.ServerDisconnectManager$ServerConnectDisconnectListenerImpl$2.run(ServerDisconnectManager.java:219)
    [wldeploy]      at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    [wldeploy]      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    [wldeploy]      at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    [wldeploy]
    [wldeploy]
    [wldeploy]
    [wldeploy]      at weblogic.deploy.api.tools.deployer.Jsr88Operation.report(Jsr88Operation.java:542)
    [wldeploy]      at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:140)
    [wldeploy]      at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
    [wldeploy]      at weblogic.utils.compiler.Tool.run(Tool.java:158)
    [wldeploy]      at weblogic.utils.compiler.Tool.run(Tool.java:115)
    [wldeploy]      at weblogic.Deployer.run(Deployer.java:70)
    [wldeploy]      at weblogic.Deployer.mainWithExceptions(Deployer.java:62)
    [wldeploy]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [wldeploy]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [wldeploy]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [wldeploy]      at java.lang.reflect.Method.invoke(Method.java:597)
    [wldeploy]      at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy.java:419)
    [wldeploy]      at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:349)
    [wldeploy]      at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
    [wldeploy]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [wldeploy]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [wldeploy]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [wldeploy]      at java.lang.reflect.Method.invoke(Method.java:597)
    [wldeploy]      at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
    [wldeploy]      at org.apache.tools.ant.Task.perform(Task.java:348)
    [wldeploy]      at org.apache.tools.ant.Target.execute(Target.java:357)
    [wldeploy]      at org.apache.tools.ant.Target.performTasks(Target.java:385)
    [wldeploy]      at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
    [wldeploy]      at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
    [wldeploy]      at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
    [wldeploy]      at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
    [wldeploy]      at org.apache.tools.ant.Main.runBuild(Main.java:758)
    [wldeploy]      at org.apache.tools.ant.Main.startAnt(Main.java:217)
    [wldeploy]      at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
    [wldeploy]      at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
    [wldeploy] [ServerConnectionImpl.close():332] : Closing DM connection
    [wldeploy] [ServerConnectionImpl.close():352] : Unregistered all listeners
    [wldeploy] [ServerConnectionImpl.closeJMX():372] : Closed JMX connection
    [wldeploy] [ServerConnectionImpl.closeJMX():384] : Closed Runtime JMX connection
    [wldeploy] [ServerConnectionImpl.closeJMX():396] : Closed Edit JMX connection

    Well, I guess you have a problem here. Check http://multikoop.blogspot.de/2012/12/deploying-adf-applications-into-oracle.html and from this
    >
    Note: In its current stage Oracle Java Cloud Service runs WebLogic Server 10.3.6 with the appropriate Runtime ADF 11.1.1.6. Deployment of ADF 11gR2 Applications is currently not supported. Beside this limitation some ADF Features are not supported on the Oracle Cloud. According to the Oracle Cloud Documentation it is not supported to use the following ADF features
    ADF Desktop Integration
    ADF mBean
    ADF MDS (Seeded customizations or cross-session personalization)
    ADF Mobile
    ADF Active Data Services (=> No real-time ADF Web Apps in Oracles Cloud)
    ADF Business Components services interfaces (web services) or events
    ADF Data Controls for BI, Essbase, BAM, and JMX
    Further there are some restrictions which are good to know I think
    No Java Mail API (=>Sending Mails is prohibited)
    No File system access by deployed applications (=>Writing files is prohibited)
    No Direct use of Oracle JDBC Driver APIs
    No Java Message Service (JMS)
    Max Size for deployment archive 95MB
    >
    I hope for you that the information from the blog has changes in the meantime (blog is from end of last year). Check the current doc for the cloud ...
    Timo

  • Getting ConverterELTag error while deploying the application though jsf1.2 library is added

    Hi ADF Experts,
    I am using JDeveloper 11.1.1.7.0 and while deploying my application to weblogic server I am getting the below error.
    [Deployer:149193]Operation 'deploy' on application 'AppsSUI' [Version=0.5-SNAPSHOT]' has failed on 'DefaultServer'
    [07:19:01 AM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsSUI [Version=0.5-SNAPSHOT] on DefaultServer.: Failed to load webapp: 'AppsSUI'.
    [07:19:01 AM] Weblogic Server Exception: weblogic.application.ModuleException: Failed to load webapp: 'AppsSUI'
    [07:19:01 AM] Caused by: java.lang.ClassNotFoundException: javax.faces.webapp.ConverterELTag
    [07:19:01 AM]   See server logs or server console for more details.
    [07:19:01 AM] weblogic.application.ModuleException: Failed to load webapp: 'AppsSUI'
    [07:19:01 AM] ####  Deployment incomplete.  ####
    [07:19:01 AM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
    Caused by: java.lang.ClassNotFoundException: javax.faces.webapp.ConverterELTag
    Can you please help me, if anybody have faced this issue. Jsf 1.2 library is also added.
    Please help.
    Thanks,
    Roy

    Hi,
    normally it should not be required to deploy JSF 1.2 with the application as WLS has JSF 1.2 installed. So only make sure you deploy 11.1.1.7 to the WLS server it is supported with
    Frank

  • Error faced while deploying Dynpro application in SAP EP 7.0

    Dear All,
    I am getting the foll. error while deploying dynpro application from NWDS to SAP EP 7.0
    May 28, 2009 3:58:01 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [002]Deployment aborted
    Settings
    SDM host : EPTEST
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/nitesh/LOCALS1/Temp/temp25615pr_Bufferinfo.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/nitesh/LOCALS1/Temp/temp25615pr_Bufferinfo.ear
    Aborted: development component 'pr_Bufferinfo'/'local'/'LOKAL'/'0.2009.05.28.15.57.53'/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application local/pr_Bufferinfo.. Reason: Clusterwide exception: Failed to deploy application local/pr_Bufferinfo. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:      com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application local/pr_Bufferinfo. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment exception : The deployment of at least one item aborted
    Please help.
    Nitesh

    Nitesh,
    Please ensure you follow the note 701654 .
    Also refer to [SDM Deployment Fails|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/28/302c4142aef623e10000000a155106/content.htm]
    Good Luck!
    Sandeep Tudumu

  • Error while deploying my application

    Hi,
    I am getting the following error while deploying my application.
    com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'password' missing
        at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:457)
        at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1015)
        at com.sap.mw.jco.JCO$Client.connect(JCO.java:3255)
        at com.sap.dictionary.runtime.mdi.DataProvider.<init>(DataProvider.java:91)
    at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:319)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
         at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
    Thanks ,
    nadh

    Hi Nadh,
    This is the code to execute RFCst
    Z_Notification_Create_Input input = new Z_Notification_Create_Input();
    wdContext.nodeZ_Notification_Create_Input().bind(input);
    wdContext.currentZ_Notification_Create_InputElement().modelObject().addFlines(longText);
    wdContext.currentZ_Notification_Create_InputElement().modelObject().execute();
    Best regards,
    Chinnu

  • Error while deploying WC application: Unable to deploy EJB

    Hi All,
    we are getting the below error quite frequently, whenever we deploy the application to server:
    [03:35:14 AM] Weblogic Server Exception: weblogic.application.ModuleException: Exception preparing module: EJBModule(CAWrapperEJB.jar)
    Unable to deploy EJB: CAService from CAWrapperEJB.jar:
    [EJB:011055]Error deploying the EJB 'CAService(Application: CAPortal, EJBComponent: CAWrapperEJB.jar)', the JNDI name 'CAPortal-CAPModel-CAService2#com.lexisnexis.service.CAService' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
    [03:35:14 AM] Caused by: java.lang.Throwable: Substituted for missing class [EJB - 11055]Error deploying the EJB 'CAService(Application: CAPortal, EJBComponent: CAWrapperEJB.jar)', the JNDI name 'CAPortal-CAPModel-CAService2#com.lexisnexis.service.CAnService' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
    [03:35:14 AM] See server logs or server console for more details.
    -to solve this issue we just delete the cache and restart the Managed server.
    Please tell me what is the cause of this error and how can we fix it permanently, as restarting the server everytime is not very convenient.
    TIA,
    Bob

    The content of "weblogic-ejb-jar.xml" present in code is:
    <?xml version = '1.0' encoding = 'windows-1252'?>
    <weblogic-ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-ejb-jar http://www.bea.com/ns/weblogic/weblogic-ejb-jar/1.0/weblogic-ejb-jar.xsd"
    xmlns="http://www.bea.com/ns/weblogic/weblogic-ejb-jar">
    </weblogic-ejb-jar>

  • Problem while deploying the application

    Hi,
    My application is currently working fine on tomcat .
    I am trying to migrate it to Weblogic 8.1 SP4 in clustered environment.
    While deploying the application, I am getting the following error.
    <BEA-101249> <[ServletContext(id=19016735,name=test,context-path=/test)]: Servlet class com.ABC.EFG.services.QuartzInitializerServlet for servlet QuartzInitializer could not be loaded because the requested class was not found in the classpath.
    Please provide me the solutions.
    Thanks

    The workaround is to extract the ear file into war and jar files. Then open this war or jar file whatever you want to modify in the deployment tool. Save this modified war/jar file. Re-open the ear file and remove the previous war and jar files and add this new ones into the project.

  • Error in Embeded OC4J while deploying SessionBean

    I am using Jdeveloper version 9.0.5.1, since the project have brought to production at 2004, I have been using the same version.
    The workspace a number of project each contains a number of entity and session beans(EJB 2.0), lately I added a new project which contains a new session bean that references another session bean and an entity bean, when I attempt to run the application in the Jdeveloper the embedded OC4J returns the following errors messages:
    07/07/11 21:15:17 Copying default deployment descriptor from archive at D:\<Pathes>/META-INF/orion-ejb-jar.xml to deployment directory D:\TraineeCD\JDeveloper\jdev\system9.0.5.1.1605\oc4j-config\application-deployments\current-workspace-app\classes...
    07/07/11 21:15:18 Auto-deploying - file:/D:/TraineeCD/JDeveloper/jdev/mywork07/07/11 21:15:17 Copying default deployment descriptor from archive at D:\JDeveloper\jdev\mywork\<Pathes>classes/META-INF/orion-ejb-jar.xml to deployment directory D:\TraineeCD\JDeveloper\jdev\system9.0.5.1.1605\oc4j-config\application-deployments\current-workspace-app\classes...
    07/07/11 21:15:18 Auto-deploying - file:/D://JDeveloper/jdev/mywork/<Path>/classes/ (No previous deployment found)...
    07/07/11 21:15:19 Auto-deploying - file:/D://JDeveloper/jdev/mywork/<Path>/classes/ (No previous deployment found)...
    07/07/11 21:15:19 Auto-deploying - file:/D:/TraineeCD/JDeveloper/jdev/mywork/<Pathes>
    07/07/11 21:03:27 Auto-deploying - compiling and loading...
    07/07/11 21:03:53 SQL error: Io exception: The Network Adapter could not establish the connection
    07/07/11 21:04:21 Error creating table: Io exception: The Network Adapter could not establish the connection
    07/07/11 21:04:35 SQL error: Io exception: The Network Adapter could not establish the connection
    07/07/11 21:04:49 done.
    Ready message received from Oc4jNotifier.
    Embedded OC4J startup time: 101828 ms.
    07/07/11 21:04:53 Oracle Application Server Containers for J2EE 10g (9.0.4.0.0) initialized
    I dont know what is the meaning of this error, nor what is the cause as it never appeared before. Surprisingly the behaviour of the application seems to be behaving normally even though despite this error and when the Oc4J returns done does this mean it started successfully, this error is preventing me from deploying my application to production environment as I guess there's something abnormal going around.
    Note:When I get a fresh copy of the application without the new project which contain the session bean the OC4J starts with no errors.
    Any ideas what maybe the problem ?

    Is your new project trying to access the database?
    SQL error: Io exception: The Network Adapter could not establish the connection
    Seems to indicate that you have a problem accessing the database probably due to wrong settings of the database connection information.
    Also check your data-sources.xml file for any new entries.

  • Problem while deploying WD application thru SDM

    Hi friends ,facing problem while deploying webdynpro application on SDM.It takes much time deployment but for the past 1 or 2 day its not working properly ..i..e error is coming while deploying WD application................................................"Cannot login to the SAP J2EE Engine using user and password as provided in the Filesystem Secure Store. Enter valid login information in the Filesystem Secure Store using the SAP J2EE Engine Config Tool. For more information, see SAP note 701654.."
    If how know how to resolve this then waiting for ur response..
    Thanx in advance
    Hanif

    Hi Hanif,
    The SDM password should be reset if it is not the same as mentioned in your Filesystem Secure Store or vice versa.
    If you have changed your administrator password, kindly do change the same in secure store as well via the config tool.
    Use the Config Tool to change the entry in secure storage as follows:
    1. Start the Config Tool.
               (Go to  <drive>:\usr\sap\<SID>\<instance>\j2ee\configtool --> configtool.bat.)
    2. Select the secure store node.
               The configuration for the secure storage in the file system appears.
    3. Select the admin/password/<SID> entry.
    4. Enter the administrator user's new password in the "Value" field and choose "Add".
    5. Choose "File" --> "Apply" to save the data.
              Note: Contrary to the message that appears, you do not need to restart the server or cluster for this change to take effect.
    6. Finally restart SDM server.
    Regards,
    Anagha

  • Random SAXParseException while deploying web application

    Hi,
    We are using Weblogic 9.2 to host our web applications that are build with iBatis mapping to Oracle 10g backend.
    While deploying the applications, we keep getting the following error. The weird thing is that on redeploying the application multiple times, the error goes away eventually and the application runs fine.
    Any idea where/how to troubleshoot?
    regards,
    Rana
    ===================================================================
    ####<Aug 15, 2009 1:14:56 PM IST> <Error> <Deployer> <feloprbp1> <PROD_PSManagedServer1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1250338496964> <BEA-149265> <Failure occured in the execution of deployment request with ID '1250338493222' for task '52'. Error is: 'weblogic.application.ModuleException: '
    weblogic.application.ModuleException:
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:891)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:333)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
         at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:139)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:815)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1222)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:433)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    org.xml.sax.SAXParseException: Attribute "resultMap" must be declared for element type "parameter".
         at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
         at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(Unknown Source)
         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
         at org.apache.xerces.impl.dtd.XMLDTDValidator.emptyElement(Unknown Source)
         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
         at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
         at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
         at com.ibatis.common.xml.NodeletParser.createDocument(NodeletParser.java:150)
         at com.ibatis.common.xml.NodeletParser.parse(NodeletParser.java:50)
         at com.ibatis.sqlmap.engine.builder.xml.SqlMapParser.parse(SqlMapParser.java:45)
         at com.ibatis.sqlmap.engine.builder.xml.SqlMapConfigParser$11.process(SqlMapConfigParser.java:347)
         at com.ibatis.common.xml.NodeletParser.processNodelet(NodeletParser.java:112)
         at com.ibatis.common.xml.NodeletParser.process(NodeletParser.java:75)
         at com.ibatis.common.xml.NodeletParser.process(NodeletParser.java:93)
         at com.ibatis.common.xml.NodeletParser.parse(NodeletParser.java:63)
         at com.ibatis.common.xml.NodeletParser.parse(NodeletParser.java:51)
         at com.ibatis.sqlmap.engine.builder.xml.SqlMapConfigParser.parse(SqlMapConfigParser.java:78)
         at com.ibatis.sqlmap.client.SqlMapClientBuilder.buildSqlMapClient(SqlMapClientBuilder.java:62)
         at org.springframework.orm.ibatis.SqlMapClientFactoryBean.afterPropertiesSet(SqlMapClientFactoryBean.java:255)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1057)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1024)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:421)
         at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245)
         at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:140)
         at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242)
         at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:156)
         at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:270)
         at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:346)
         at org.springframework.web.context.support.AbstractRefreshableWebApplicationContext.refresh(AbstractRefreshableWebApplicationContext.java:156)
         at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:246)
         at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:184)
         at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:49)
         at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:376)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:82)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1608)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2750)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:889)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:333)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
         at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:139)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:815)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1222)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:433)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    >
    ####<Aug 15, 2009 1:14:57 PM IST> <Error> <Deployer> <feloprbp1> <PROD_PSManagedServer1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1250338497024> <BEA-149202> <Encountered an exception while attempting to commit the 7 task for the application 'fetacWIP'.>
    ===================================================================

    As the error message tells, did you make sure you have a correct/valid archive file? You might try deploying it from command line to make sure issue isn't at EM side.
    For 10.1.3 refer:
    http://download.oracle.com/docs/cd/B32110_01/web.1013/b28951/overview.htm#CJAJHJIA
    For 10.1.2 refer:
    http://download.oracle.com/docs/cd/B14099_19/core.1012/b13997/cmds.htm#BEIJGHDG
    http://download.oracle.com/docs/cd/B14099_19/core.1012/b13997/cmds.htm#BEICHFGJ
    Thanks
    Shail

  • Problem while deploying ADF application to standalone WLS server

    Hi,
    I am facing a problem while deploying ADF application to standalone WLS Server.
    Following is the error message that I am getting.
    [07:24:03 PM] ----  Deployment started.  ----
    [07:24:03 PM] Target platform is  (Weblogic 10.3).
    [07:24:07 PM] Retrieving existing application information
    [07:24:08 PM] Running dependency analysis...
    [07:24:08 PM] Building...
    [07:24:13 PM] Deploying 2 profiles...
    [07:24:14 PM] Wrote Web Application Module to D:\WorkSpace3\DashboardUi\deploy\Dashboard.war
    [07:24:14 PM] Wrote Enterprise Application Module to D:\WorkSpace3\deploy\Dashboard.ear
    [07:24:14 PM] Deploying Application...
    [07:24:22 PM] [Deployer:149191]Operation 'deploy' on application 'Dashboard' is initializing on 'msDevServer1'
    [07:24:27 PM] [Deployer:149193]Operation 'deploy' on application 'Dashboard' has failed on 'msDevServer1'
    [07:24:27 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application Dashboard on msDevServer1.: .
    [07:24:27 PM] Weblogic Server Exception: weblogic.application.ModuleException:
    [07:24:27 PM] Caused by: weblogic.common.ResourceException: DataSource DashboardDb already exists
    [07:24:27 PM]   See server logs or server console for more details.
    [07:24:27 PM] weblogic.application.ModuleException:
    [07:24:27 PM] ####  Deployment incomplete.  ####
    [07:24:27 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)Any suggestion how to fix this.
    Thanks
    Ajay

    I logged into console and browsed to 'Home >Summary of JDBC Data Sources' but not able to locate DashboardDb. Please let me know where to find DashboardDB on wls console.
    Also, please let me know how to configure the app to not to auto-deploy JDBC data sources

  • Java.io.IOException: Too many open files while deploying in soa 11g

    hi all,
    I am getting a strange error while deploying any composite .. it's a hello world kinda composite but while i am trying to deploy it i am getting "java.io.IOException: Too many open files" while deployment.. i have tried to deploy it in 2-3 ways but all of them resulted in the same error..bouncing the soa server might be an option but can someone give an insight as why it is happening and can it be resolved without restarting the server..
    Thanks

    yes..so this problem is with unix only ..coz i previously worked in Windows ..never got this problem..

Maybe you are looking for