Failed to load deployable object part 'AmendAgrmntApp', type 'Application'

hi,
I have deployed a DC on server. I can run the application indepemdently. But when I try to create the URL of this application using WDURLGenerator.getApplicationURL (as I want to call this application from another application), i get the following exception
com.sap.tc.webdynpro.services.sal.deployment.api.WDDeploymentException: Failed to load deployable object part 'AmendAgrmntApp', type 'Application' of deployable object 'aramco.com/itcaesaleswebamndagrmnt'.
Failed to generate URL to deployable object 'aramco.com/itcaesaleswebamndagrmnt', application 'AmendAgrmntApp'
Please suggest a solution
Thanks !
seventyros

According to the API at http://help.sap.com/javadocs/NW04S/SPS09/wd/com/sap/tc/webdynpro/services/sal/url/api/WDURLGenerator.html
There must be a deployable object part of type WDDeployableObjectPartType.APPLICATION with the given applicationPartName within the deployable object with name deployableObjectName

Similar Messages

  • Web Dynpro Java : Failed to get deployable object part info for component

    Currently we have a web dynpro java project which connects to the ABAP backend with Web Services. Everything seems fine, and when we transport to the production server via NWDI, we have the following error. Everytime we try to access the application , the error is occurred.
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to get deployable object part info for component com.sie.attachmentcomp.AttachmentComp
        at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.getComponentDeploymentDescription(ClientComponent.java:784)
        at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:934)
        at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:177)
        at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149)
        at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:116)
    It is working properly in our development , and testing environment. Only production has this error. And one weird thing is that this particular error occurred only sometimes to some user. For example; I could not access to the application with this error yesterday but my friend can access. Today, I can access in the morning but my friend cannot. For another friend , Yesterday he can access by using IE but not by Firefox. But today Firefox is fine but not with IE. It seems crazy.
    For more information, in our J2EE engine for the production server, we have 3 server nodes (clusters). And we are not sure it is the source of the problem. Is there any solution , and any way to know from the application that we are on which server?
    We also go and check from the Content Administrator in Web Dynpro Console. Under our project name, in the list of Components, sometimes we can see AttachmentComp but sometimes not.
    Please help us as our project is about to go-live next week.
    Thanks,
    Yu

    Hi Meenge,
    Please check below document for finding root cause for "Failed to start deployable object part info for <development component> and application <application name>"
    http://help.sap.com/saphelp_nwce711core/helpdata/en/44/7716e1633a12d1e10000000a422035/frameset.htm
    OR http://help.sap.com/saphelp_nw04/helpdata/EN/f4/1a1041a0f6f16fe10000000a1550b0/frameset.htm
    Hope it helps
    Regards
    Arun

  • Failed to get deployable object part info for component

    We are getting the given error while accessing the leave request/approve application in the ESS overview page.
    The initial exception that caused the request to fail, was:
       com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to get deployable object part info for component com.sap.pcuigp.xssfpm.wd.FPMComponent
        at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.getComponentDeploymentDescription(ClientComponent.java:682)
        at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.<init>(ClientComponent.java:707)
        at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.<init>(ClientApplication.java:298)
        at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.createApplication(ClientApplication.java:285)
        at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.createApplication(WebDynproMainTask.java:748)
        ... 22 more

    HI saket jha,
    Refer the following thread
    Error in "Who is Who" search
    ESS Timesheet Error
    Regards,
    Manivannan P

  • Failed to create deployable object '********' since it is not a Web Dynpro object - Migration from 7.0 to 7.4

    I have installed NWDS 7.30 EHP1 SP 14 PAT000   with JVM 6 SAP AG
    to   migrate wedynpro development components from 7.0 to
    NW7.4 WAS SAP AG 1.6.0_85 on Windows Server 2008 R2 6.1  SP09 PAT000
    In track imported below SCAs of version  7.31 SP14 .
    Could able to migrate and build in NWDS, getting deployment errors.
    Followed   
    http://scn.sap.com/docs/DOC-55584 
    and   
    http://scn.sap.com/community/nwdi/blog/2014/03/26/nwdi-vs-nwdi-content 
    COMP_BUILDT
    ECM-CORE
    ENGFACADE
    ENGINEAPI
    ESCONF_BUILDT
    FRAMEWORK
    MOIN_BUILDT
    SAP_BUILDT
    WD-RUNTIME
    Deployment Errors:-
    com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
    Reason: ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed
        at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:862)
        at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
        at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:105)
        at com.sap.ide.tools.services.dc.EngineDcDeployService.deployFiles(EngineDcDeployService.java:257)
        at com.sap.ide.tools.services.dc.EngineDcDeployService.deploy(EngineDcDeployService.java:135)
        at com.sap.ide.dii05.ui.internal.actions.dc.DcDeployAction$5$1.run(DcDeployAction.java:282)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed
        at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:246)
        at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:67)
        at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:282)
        at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
        at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:100)
        at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
        at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
        at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
        at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] Operation [update] of [sdu id: [XXXXXXX.com_home~chgemail]
    sdu file path: [E:\usr\sap\SN3\J00\j2ee\cluster\server0\temp\tc~bl~deploy_controller\archives\111\XXXXXXX.com~home~chgemail.ear]
    version status: [HIGHER]
    deployment status: [Admitted]
    description: []
    ] failed
        at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:100)
        at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:141)
        at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
        at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:213)
        ... 8 more
    Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: ASJ.dpl_ds.006193 Operation [update] of [E:\usr\sap\SN3\J00\j2ee\cluster\server0\temp\tc~bl~deploy_controller\archives\111\XXXXXXX.com~home~chgemail.ear] failed
        at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:3370)
        at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:489)
        at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:74)
        ... 11 more
    Caused by: com.sap.engine.services.servlets_jsp.webcontainer_api.exceptions.WebContainerExtensionDeploymentException: Error during deployment of application {0}
        at com.sap.engine.services.webdynpro.WebDynproDeploymentHook.onDeploy(WebDynproDeploymentHook.java:52)
        at com.sap.engine.services.webdynpro.webcontainer.extension.ExtensionHandler.onDeployInternal(ExtensionHandler.java:169)
        at com.sap.engine.services.webdynpro.webcontainer.extension.ExtensionHandler.onDeploy(ExtensionHandler.java:129)
        at com.sap.engine.services.servlets_jsp.server.deploy.impl.WebContainerProvider.deploy(WebContainerProvider.java:334)
        at com.sap.engine.services.servlets_jsp.server.deploy.DeployAction.deploy(DeployAction.java:360)
        at com.sap.engine.services.servlets_jsp.server.deploy.UpdateAction.makeUpdate(UpdateAction.java:327)
        at com.sap.engine.services.servlets_jsp.server.deploy.WebContainer.makeUpdate(WebContainer.java:446)
        at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.makeUpdate(ContainerWrapper.java:409)
        at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:478)
        at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:183)
        at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:234)
        at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:421)
        at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:473)
        at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1836)
        at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:582)
        at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:487)
        ... 12 more
    Caused by: com.sap.tc.webdynpro.services.sal.deployment.core.DeploymentException: Failed to deploy application 'XXXXXXX.com/home~chgemail'.
        at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.notifyOnDeploy(DeployableObjectFactory.java:324)
        at com.sap.tc.webdynpro.services.sal.deployment.core.DeployableObjectInternal.notifyOnDeploy(DeployableObjectInternal.java:122)
        at com.sap.engine.services.webdynpro.WebDynproDeploymentHook.onDeploy(WebDynproDeploymentHook.java:49)
        ... 27 more
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
        at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:79)
        at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObjectFactory$1.getDeployableObject(AbstractDeployableObjectFactory.java:87)
        at com.sap.tc.webdynpro.services.sal.deployment.api.WDDeployableObject.getDeployableObject(WDDeployableObject.java:43)
        at com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.calculateVMOsOfDeployableObject(RepositoryContainerHook.java:264)
        at com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.onDeploy(RepositoryContainerHook.java:181)
        at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.notifyOnDeploy(DeployableObjectFactory.java:297)
        ... 29 more
    Caused by: com.sap.tc.webdynpro.spi.WebDynproRuntimeException: No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.
        at com.sap.engine.services.webdynpro.WebDynproRuntimeServiceImpl.getDeployableObject(WebDynproRuntimeServiceImpl.java:228)
        at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:77)
        ... 34 more
    Deployment Items status: [
    ----- Sorted Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
    ----- Deployment Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            Description:'1. Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
             -> No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.'.
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
            Time statistics( ms ):
                1.Check version:XXXXXXX.com_home~chgemail : 4
                2.validate : -1
                    2.1.Resolve dependencies : 3
                    2.2.deployment : 7055
                        2.2.1.Notify:Event triggered : 203
                        2.2.2.Bulk deployment : 6839
                            2.2.2.1.Stop : 73
                            2.2.2.2.Perform delivery : 6765
                                2.2.2.2.1.Application Deployer : 6615
                        2.2.3.Notify:Event performed : 9
                    2.3.Post process : 10
                        2.3.1.Starting : 9
    ]      [Error: com.sap.engine.services.tc~bl~deploy~api  Thread[Worker-444,5,main]]
    Deployment Items status: [
    ----- Sorted Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
    ----- Deployment Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            Description:'1. Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
             -> No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.'.
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
            Time statistics( ms ):
                1.Check version:XXXXXXX.com_home~chgemail : 4
                2.validate : -1
                    2.1.Resolve dependencies : 3
                    2.2.deployment : 7055
                        2.2.1.Notify:Event triggered : 203
                        2.2.2.Bulk deployment : 6839
                            2.2.2.1.Stop : 73
                            2.2.2.2.Perform delivery : 6765
                                2.2.2.2.1.Application Deployer : 6615
                        2.2.3.Notify:Event performed : 9
                    2.3.Post process : 10
                        2.3.1.Starting : 9
    ]      [Error: com.sap.engine.services.tc~bl~deploy~api  Thread[Worker-444,5,main]]
    [#6]: Deployment Items status: [
    ----- Sorted Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
    ----- Deployment Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            Description:'1. Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
             -> No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.'.
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
            Time statistics( ms ):
                1.Check version:XXXXXXX.com_home~chgemail : 4
                2.validate : -1
                    2.1.Resolve dependencies : 3
                    2.2.deployment : 7055
                        2.2.1.Notify:Event triggered : 203
                        2.2.2.Bulk deployment : 6839
                            2.2.2.1.Stop : 73
                            2.2.2.2.Perform delivery : 6765
                                2.2.2.2.1.Application Deployer : 6615
                        2.2.3.Notify:Event performed : 9
                    2.3.Post process : 10
                        2.3.1.Starting : 9
    ]      [Error: com.sap.ide.eclipse.deployer.dc.DVLog  Thread[Worker-444,5,main]]
    [#6]: Deployment Items status: [
    ----- Sorted Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
    ----- Deployment Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            Description:'1. Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
             -> No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.'.
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
            Time statistics( ms ):
                1.Check version:XXXXXXX.com_home~chgemail : 4
                2.validate : -1
                    2.1.Resolve dependencies : 3
                    2.2.deployment : 7055
                        2.2.1.Notify:Event triggered : 203
                        2.2.2.Bulk deployment : 6839
                            2.2.2.1.Stop : 73
                            2.2.2.2.Perform delivery : 6765
                                2.2.2.2.1.Application Deployer : 6615
                        2.2.3.Notify:Event performed : 9
                    2.3.Post process : 10
                        2.3.1.Starting : 9
    ]      [Error: com.sap.ide.eclipse.deployer.dc.DVLog  Thread[Worker-444,5,main]]
    Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed]      [Error: com.sap.engine.services.tc~bl~deploy~api  Thread[Worker-444,5,main]]
    Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed]      [Error: com.sap.engine.services.tc~bl~deploy~api  Thread[Worker-444,5,main]]
    [#6]: Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed]      [Error: com.sap.ide.eclipse.deployer.dc.DVLog  Thread[Worker-444,5,main]]
    [#6]: Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed]      [Error: com.sap.ide.eclipse.deployer.dc.DVLog  Thread[Worker-444,5,main]]

    C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear
    can you find this ear in your local drive?

  • Failed to start deployable object

    Hello friends!
    I get the following error very often after migrating from 7.1 sp5 to 7.1.1 Ehp1 sp4 NWDS.
    (Never faced this issue in 7.1 sp5 NWDS.)
    "Application error occured during the request processing
    com.sap.tc.webdynpro.services.sal.core.DispatcherException: Failed to start deployable object....."
    This Webdynpro Application goes down time and again when other application are working fine.
    On the NWA side : It says Webdynpro has implicilty stoped and EJB application failed to start.
    Please help.
    Regards
    Poornima

    Following is the entire stack trace
    com.sap.tc.webdynpro.services.sal.core.DispatcherException: Failed to start deployable object abcd.com/esswd.
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.initApplicationDeployableObjectPart(RequestManager.java:589)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.initTask(RequestManager.java:505)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doInitWdEnvironment(RequestManager.java:170)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:231)
         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.dispatchToDispatcherContext(ExecutionContextDispatcher.java:146)
         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.doPost(AbstractDispatcherServlet.java:61)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         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:486)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
         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:243)
         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:428)
         at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
         at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Caused by: com.sap.tc.webdynpro.services.sal.deployment.core.StartStopException: Failed to start the deployable object 'abcd.com/esswd'.
         at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.start(DeployableObject.java:226)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.initApplicationDeployableObjectPart(RequestManager.java:583)
         ... 50 more
    Caused by: com.sap.tc.webdynpro.spi.WebDynproRuntimeException: Cannot start application abcd.com/esswd
         at com.sap.engine.services.webdynpro.WebDynproRuntimeServiceImpl.start(WebDynproRuntimeServiceImpl.java:473)
         at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.start(DeployableObject.java:224)
         ... 51 more
    Caused by: com.sap.engine.services.servlets_jsp.server.deploy.impl.exceptions.WCEApplicationNotStartedException: Failed explicit start for application [abcd.com/esswd].
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.start(ApplicationManager.java:190)
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.analyseAppStatusMode(ApplicationManager.java:293)
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.WebContainerExtensionContext.getWebModuleContext(WebContainerExtensionContext.java:181)
         at com.sap.engine.services.webdynpro.WebDynproRuntimeServiceImpl.start(WebDynproRuntimeServiceImpl.java:471)
         ... 52 more
    Caused by: java.rmi.RemoteException: [ERROR CODE DPL.DS.6309] Error occurred while starting application in whole cluster and wait.; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: [server ID 4651950:Problem in appclient deployment. Cannot create application client environment into naming. Application "abcd.com/essappl" will not be deployed because of NamingException.
               -> Path to object does not exist at appclient-environment, the whole lookup name is appclient-environment/abcd.com/essappl/jxl.
    server ID 4651950:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application [abcd.com/esswd] cannot be started. Reason: it has hard reference to resource [essappl] with type [application], which is not active on the server.
    Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?
         at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:870)
         at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:847)
         at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:574)
         at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:488)
         at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:195)
         at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:160)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:587)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:213)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:374)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3430)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3416)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:551)
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.start(ApplicationManager.java:183)
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.analyseAppStatusMode(ApplicationManager.java:293)
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.WebContainerExtensionContext.getWebModuleContext(WebContainerExtensionContext.java:181)
         at com.sap.engine.services.webdynpro.WebDynproRuntimeServiceImpl.start(WebDynproRuntimeServiceImpl.java:471)
         at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.start(DeployableObject.java:224)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.initApplicationDeployableObjectPart(RequestManager.java:583)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.initTask(RequestManager.java:505)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doInitWdEnvironment(RequestManager.java:170)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:231)
         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.dispatchToDispatcherContext(ExecutionContextDispatcher.java:146)
         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.doPost(AbstractDispatcherServlet.java:61)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         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:486)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
         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:243)
         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:428)
         at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
         at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)

  • Failed to create deployable object 'local/Calendar' since it not a WD objec

    Hi
    I created a calendar application in Web dynpro,There iam getting this error .will any one please help me how to avoid this.
    com.sap.tc.webdynpro.services.sal.core.DispatcherException: The requested deployable object 'local/Calendar' and application 'CalendarApp' are not deployed on the server. Please check the used URL for typos.
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.getApplicationDeployableObjectPart(RequestManager.java:383)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.initTask(RequestManager.java:317)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:143)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create deployable object 'local/Calendar' since it is not a Web Dynpro object.
         at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.<init>(AbstractDeployableObject.java:106)
         at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.<init>(DeployableObject.java:56)
         at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:95)
         at com.sap.tc.webdynpro.services.sal.deployment.core.DeployableObjectInternal.getDeployableObjectInternal(DeployableObjectInternal.java:34)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.getApplicationDeployableObjectPart(RequestManager.java:380)
         ... 20 more

    Hi Sushma,
                     lot of new features have been added in CE EHP1 version .for more information refer this [link|http://help.sap.com/saphelp_nwce711/helpdata/en/26/b7fa511a964597a5d8c1b778508936/content.htm] and search in SDN for new features in EHP1 version.
    in CE EHP1, local web dynpro projects cannot be used as it is deprecated in this version.
    i believe this calendar is a local standalone project created in CE 7.1 version and conert this local project to development component.
    right click on ur local project --> Development component -->Convert Project to Development Component.
    After this, go ur NWDI --> select ur component --> right click --> Create project (& Sync ysed Dcs) ..
    finally deploy and run ur component .
    Hope this helps.
    Thanks and Regards

  • FRM - 18108 Failed to load following object

    when i am opening the forms in 10G suit , getting below error
    FRM - 18108 Failed to load following object
    source module : template.fmb
    source object: STANDARD
    please help me

    Sounds like you are working with the Enterprise Business Suite (EBS). The error you are getting is because Forms can't find a referenced object. This is because the directory where your TEMPLATE.fmb (and the objects the template.fmb form references) is not found in your FORMS_PATH. If you are using Windows, edit the registry and add the directory where you have your reference objects to the FORMS_PATH entry. Make sure you add it to the end of the existing value; not replace the existing value!
    Hope this helps,
    Craig B-)
    If someone's response is helpful or correct, please mark it accordingly.

  • Failed to create deployable object

    Hello All,
    We have upgraded my portal,web as and developer stuido from SP14 to SP12. All the web dynrpo applications on the portal pages have stopped functioning. I cannot click on any of the web dynpro application controls nor do these applications show
    images in caption fields. All the other portal components are working fine. The web dynpro application too work fine when I try to test them off the Web AS.Please advice.
    The error message i get is
    Failed to create deployable object resources/sap.com since it is not a webdynpro object
    Thanks

    HI Vijay,
    I guess when you upgraded your WAS server from SP14 to SP12 then you need to rebuild your all applications in NWDS SP12 and then deploy once again.
    Error says that those applications are not deployed on the server at this time. So, it means, when you have upgraded server all deployed applications were deleted.
    Just check in deploy service of visual administrator.
    Regards,
    Bhavik

  • Failed to create deployable object 'virsa/ccappcomp' since it is not a Web

    Hi All,
    As per 999858  I download VIRCC09_0-20001854.SAR and depolyed ( this is  fresh installation of Virsa Compliance Calibrator) it directly since in java stack you do not have to go incremental way  as per Virsa Compliance Calibratoru2122 Version 5.2 for SAP WAS 700  installation guide.
    Here are the components which I have deployed using SDM
    1. sap.comgrcccxsysdb.sda
    2. virsalib.sda
    3. sap.com~ccume.sda
    4. sap.comgrcccxsysbe
    5. sap.comgrcccxsysbehr
    6. sap.comgrcccappcomp
    7. sap.comgrcccxsysws 
    8. sap.comgrcccxsysbgear
    But when I take http://hostname:50200/webdynpro/dispatcher/virsa/ccappcomp/
    I am getting following error.
    Root Cause
    The initial exception that caused the request to fail, was:
       com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create deployable object 'virsa/ccappcomp' since it is not a Web Dynpro object.
        at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.<init>(AbstractDeployableObject.java:106)
        at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.<init>(DeployableObject.java:56)
        at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:95)
        at com.sap.tc.webdynpro.services.sal.deployment.core.DeployableObjectInternal.getDeployableObjectInternal(DeployableObjectInternal.java:34)
        at com.sap.tc.webdynpro.clientserver.session.RequestManager.getApplicationDeployableObjectPart(RequestManager.java:407)
        ... 20 more
    But I did deployed sap.comgrcccappcomp and still getting error tthat it is not deployed
    com.sap.tc.webdynpro.services.sal.core.DispatcherException: The requested deployable object 'virsa/ccappcomp' and application '' are not deployed on the server. Please check the used URL for typos.
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.getApplicationDeployableObjectPart(RequestManager.java:410)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.initTask(RequestManager.java:344)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:145)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create deployable object 'virsa/ccappcomp' since it is not a Web Dynpro object.
         at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.<init>(AbstractDeployableObject.java:106)
         at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.<init>(DeployableObject.java:56)
         at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:95)
         at com.sap.tc.webdynpro.services.sal.deployment.core.DeployableObjectInternal.getDeployableObjectInternal(DeployableObjectInternal.java:34)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.getApplicationDeployableObjectPart(RequestManager.java:407)
         ... 20 more
    But I am able to take the debug  window
    http://hostname:50200/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?debug=1
    Do you have any tips?

    Yes, try the correct URL for calling CC
    http://hostname:50200/webdynpro/dispatcher/sap.com/grc~ccappcomp/ComplianceCalibrator
    This is the URL since CC 5.2 SP05, before it was
    http://hostname:50200/webdynpro/dispatcher/virsa/ccappcomp/ComplianceCalibrator
    The first one should apply to you.
    Kind regards,
    Daniela

  • Failed to load following objects error

    --Thread moved from Forms
    Hi all,
    I am working on Form builder 10g and our Applications version is 12.1.3.I happen to develop a form by taking template.fmb from AU_TOP and worked on my requirement,everything works fine.Only thing missing is,when i open the form which i developed in applications i don't see Oracle logo,instead i get some other logo and some other functionalities are missing.
    My observation:
    when i open the .err file while compiling with frcmp_batch command i see the below errors.
    FRM-18108: Failed to load the following objects.
    Source Module:APPSTAND
      Source Object: STANDARD_PC_AND_VA
    Source Module:APPSTAND
      Source Object: STANDARD_TOOLBAR
    Source Module:APPSTAND
      Source Object: STANDARD_CALENDAR
    Compiling package specification APP_CUSTOM...
       No compilation errors.For the above things,i added Template.fmb & APPSTAND.fmb to the forms_path but still i am getting the same errors and i won't see my form with oracle logo.
    So,somehow i did a hunch and find the solution myself..
    instead of using Template.fmb i used APPSTAND.fmb which is working fine for me.However,my doubt is in every single tutorial i saw they mentioned to use Template.fmb while developing the form from scratch.
    Can anyone explain me why APPSTAND.fmb is working for me instead of Template.fmb
    Any help is appreciated,
    Thanks in advance!!

    Thanks all for your replies..I followed your suggestions,i saw the forms_path under registry editor.The path which is over there points to all the required pll's and .fmb files.There are like 1000 objects.So,now coming back to developing the form
    1.Using TEMPLATE.fmb(err file)
    FRM-18108: Failed to load the following objects.
    Source Module:APPSTAND
      Source Object: STANDARD_PC_AND_VA
    Source Module:APPSTAND
      Source Object: STANDARD_TOOLBAR
    Source Module:APPSTAND
      Source Object: STANDARD_CALENDAR
    Compiling package specification APP_CUSTOM...
       No compilation errors.
    Compiling package specification APP_CUSTOM...
       No compilation errors.
    Compiling package body APP_CUSTOM...
       No compilation errors.
    Compiling WHEN-WINDOW-RESIZED trigger on form...
       No compilation errors.
    Compiling FOLDER_ACTION trigger on form...
       No compilation errors.
    Compiling FOLDER_RETURN_ACTION trigger on form...
       No compilation errors.
    Created form file RHCCUSTALLOWANCEDET.fmxWhat's missing here when i open the form in applications is Oracle Logo and some standard functionalities.
    2.Using APPSTAND.fmb (err file)
    Compiling package specification APP_CUSTOM...
       No compilation errors.
    Compiling package specification APP_CUSTOM...
       No compilation errors.
    Compiling package body APP_CUSTOM...
       No compilation errors.
    Compiling EXPORT trigger on form...
       No compilation errors.
    Compiling CLOSE_THIS_WINDOW trigger on form...
       No compilation errors.
    Compiling WHEN-FORM-NAVIGATE trigger on form...
       No compilation errors.
    Created form file RHCCUSTALLOWANCEDET.fmxIn this case,everything works normal.
    As per your suggestions,TEMPLATE.fmb should work for me not APPSTAND.So,where am i doing wrong?
    @Srini:Yes,everything is as per the doc which you suggested
    @Hussein:Pls see the above explanation
    Kindly note that the above error report is while compilation using frmcmp_batch command and not in the Form Builder.
    My Observation:
    In the Object groups section,when using TEMPLATE.fmb STANDARD_PC_AND_VA,STANDARD_TOOLBAR,STANDARD_CALENDAR are missing.But when i use APPSTAND.fmb these object groups are present.
    Can i copy paste these object groups or doing like that damages my Applications?
    Edited by: sandy on Dec 21, 2011 11:29 AM

  • FRM-18108 Failed to load the  objects

    I have upgraded the forms from 4.5 to 6i and when I tried to open the form PCOECU20 it gives me error
    FRM-18108 Failed to load the following objects:
    Source Module: PCOEar10
    Source Object: STRUCTURE_NAME_QF_LOV
    Source Object: pc_object_Group1
    ... and several others...
    The form and libraries (pll, plx) are in the same directory.
    Can anyone help?

    Make sure you upgrade any object libraries or reference forms before the forms thta depend on them.
    Also set your Forms60_path explicitly so you know that you are using the correct versions

  • Acrobat fatal error: failed to load core dll

    Hi,
    I have a problem with acrobat reader on my laptop.
    My OS is Vista Home Premium.
    I had Master collection CS4 installed.
    When starting up acrobat reader; i got following error:
    failed to load core dll.
    I went to the log and this is the explenatoin written in there: (i'm dutch speaking)
    Kan activeringscontext voor 'C:\Program Files\Adobe\Reader  9.0\Reader\AcroRd32.dll' niet maken. Fout in manifest of beleidsbestand  '' op regel . Een onderdeelversie die nodig is voor de toepassing  conflicteert met een andere onderdeelversie die reeds actief is.  Conflicterende onderdelen zijn: Onderdeel 1:  C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt   _1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24  ad.manifest.  Onderdeel 2: C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt   _1fc8b3b9a1e18e3b_8.0.50727.762_none_10b2f55f9bffb  8f8.manifest.
    Kan activeringscontext voor 'C:\Windows\system32\BHOManager.dll' niet  maken. Fout in manifest of beleidsbestand '' op regel . Een  onderdeelversie die nodig is voor de toepassing conflicteert met een  andere onderdeelversie die reeds actief is. Conflicterende onderdelen  zijn: Onderdeel 1: C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt   _1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24  ad.manifest.  Onderdeel 2: C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt   _1fc8b3b9a1e18e3b_8.0.50727.762_none_10b2f55f9bffb  8f8.manifest.
    I simultaneously had a problem with Dreamweaver.
    I think all this is caused by an Side By Side configuration issue.
    I've tried to do following steps:
    -redistibrutable 2008 c++ package geinstall
    -system recoverage tool
    -reinstall cs4 master collection
    -uninstall master collection, clean up, install reeware acrobat reader
    -uninstall acrobat reader, ccleaner register issues resolver , also older than 24 uur , reboot,  install acrobat reader freeware
    -revo uninstall tool to remove acrobat
    none of the above actions were successful.
    What could u suggest or give as a solution.
    Atm i'm using an altarnative pdf-reader.
    But as i bought the master collection,
    i'd rather have my adobe acrobat reader pro and dreamweaver working.
    Thanks in advance,
    With friendly regards
    Anton

    Hi Anton
    I am sorry, I do not have an answer just a similar problem.
    I am no expert, but all these manifest files are to ensure that different developers can ensure that the appropriate versions of common libraries are used by particular versions of their software.
    Deatils are below. The original problem was a corrupted manifest file, probably due to a disk error. This resulted in several programs failing to run. In particular I was unable to access backup on my Windows Home Server. From the logs I was able to identify the manifest file in error and located a copy of a file with the same name on another of my computers. Using notepad I then changed the file causing the problem to match the file on the other computer.
    This appeared to resolve all my problems.
    When the Acrobat Reader updated itself, however, the"failed to load core DLL" message appeared. Simply uninstalling all adobe programs and re-installing makes no difference.
    If you have the solution please post.
    If not, I will continue to research this problem.
    Very best wishes
    Graham
    Details from error log and manifest files:
    Acrobat failed to load its core DLL
    Log Name:      Application
    Source:        SideBySide
    Date:          29/10/2010 23:30:07
    Event ID:      80
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      9GHASUSP5QSEx64
    Description:
    Activation context generation failed for "C:\Program Files (x86)\Adobe\Reader 9.0\Reader\AcroRd32.dll".
    Error in manifest or policy file "" on line .
    A component version required by the application conflicts with another component version already active.
    Conflicting components are:.
    Component 1: C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4927_none_d 08a205e442db5b5.manifest.
    Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_10 b2f55f9bffb8f8.manifest.
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
        <noInheritable></noInheritable>
        <assemblyIdentity type="win32" name="Microsoft.VC80.CRT" version="8.0.50727.4927" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
        <file name="msvcr80.dll" hash="b2cd2205044f7cfd822da03b5f8d329ac5f4fcde" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig:Transform></dsig:Tra nsforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>niXcYiF5k0Z3fQ7PBFMJuaYHWTU=</dsig:DigestValue></a smv2:hash></file>
        <file name="msvcp80.dll" hash="984100dac2591da1a03c5146fecc47eb5deabec7" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig:Transform></dsig:Tra nsforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>aW9cDm76mbaI14MUAAx8P0auVdE=</dsig:DigestValue></a smv2:hash></file>
        <file name="msvcm80.dll" hash="34d9d81de781f7566e20e2bd33e410bc80837703" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig:Transform></dsig:Tra nsforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>pyazDrJIgYvW/Y3vCJt/9hpimHA=</dsig:DigestValue></a smv2:hash></file>
    </assembly>
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
        <noInheritable></noInheritable>
        <assemblyIdentity type="win32" name="Microsoft.VC80.CRT" version="8.0.50727.762" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
        <file name="msvcr80.dll" hash="10f4cb2831f1e9288a73387a8734a8b604e5beaa" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig:Transform></dsig:Tra nsforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>n9On8FItNsK/DmT8UQxu6jYDtWQ=</dsig:DigestValue></a smv2:hash></file>
        <file name="msvcp80.dll" hash="b2082dfd3009365c5b287448dcb3b4e2158a6d26" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig:Transform></dsig:Tra nsforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>0KJ/VTwP4OUHx98HlIW2AdW1kuY=</dsig:DigestValue></a smv2:hash></file>
        <file name="msvcm80.dll" hash="542490d0fcf8615c46d0ca487033ccaeb3941f0b" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig:Transform></dsig:Tra nsforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>YJuB+9Os2oxW4mY+2oC/r8lICZE=</dsig:DigestValue></a smv2:hash></file>
    </assembly>

  • ArrayStoreException in WLS 8.1SP3: Object and inner type of array differs

    Has anyone seen this? We seem to get them from time to time, am running WLS 8.1 SP3 on JRockit 1.4.2.03. Stack trace follows.
              cheers
              dim
              <BEA-000802> <ExecuteRequest failed
              java.lang.ArrayStoreException: Object and inner type of array differs.
              java.lang.ArrayStoreException: Object and inner type of array differs
              at weblogic.rjvm.BasicOutboundRequest.sendReceive()Lweblogic.rmi.spi.InboundResponse;(BasicOutboundRequest.java:108)
              at weblogic.rmi.internal.BasicRemoteRef.invoke(Ljava.rmi.Remote;Lweblogic.rmi.extensions.server.RuntimeMethodDescriptor;[Ljava.lang.Object;Ljava.lang.reflect.Method;)Ljava.lang.Object;(BasicRemoteRef.java:137)
              at weblogic.cluster.replication.ReplicationManager_813_WLStub.update(Lweblogic.cluster.replication.ROID;ILjava.io.Serializable;)V(Unknown Source)
              at weblogic.cluster.replication.ReplicationManager.updateSecondary(Lweblogic.cluster.replication.ROID;Ljava.io.Serializable;Ljava.lang.String;)Ljava.lang.Object;(ReplicationManager.java:811)
              at weblogic.servlet.internal.session.ReplicatedSessionData.syncSession()V(ReplicatedSessionData.java:490)
              at weblogic.servlet.internal.session.ReplicatedSessionContext.sync(Ljavax.servlet.http.HttpSession;)V(ReplicatedSessionContext.java:184)
              at weblogic.servlet.internal.ServletRequestImpl.syncSession()V(ServletRequestImpl.java:2471)
              at weblogic.servlet.internal.WebAppServletContext.invokeServlet(Lweblogic.servlet.internal.ServletRequestImpl;Lweblogic.servlet.internal.ServletResponseImpl;)V(WebAppServletContext.java:3679)
              at weblogic.servlet.internal.ServletRequestImpl.execute(Lweblogic.kernel.ExecuteThread;)V(ServletRequestImpl.java:2630)
              at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
              at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
              at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
              Caused by: java.lang.ArrayStoreException: Object and inner type of array differs
              at java.io.ObjectInputStream.readObject(Unknown Source)
              at java.util.HashMap.readObject(Unknown Source)
              at java.io.ObjectInputStream.readSerialData(Unknown Source)
              at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
              at java.io.ObjectInputStream.readObject0(Unknown Source)
              at java.io.ObjectInputStream.readSerialData(Unknown Source)
              at java.io.ObjectInputStream.readObject(Unknown Source)
              at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:120)
              at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:117)
              at weblogic.cluster.replication.ReplicationManager_WLSkel.invoke(Unknown Source)
              at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
              at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
              at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
              at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
              ... 3 more

    You have to be careful how you define your complex elements, define complex elements outside of the root element or in a seperate file and reference them.
              While the following is syntactically correct, in weblogic you will result in the error you had previously
              <element>
              <complex type>
              </complex type>
              </element>
              Instead do
              <element type="ir:ComEx">
              <complex type name="ComEx"></complex type>
              outside of the root element
              Had this exact same problem today, this is how I fixed it

  • Hashtable insert failed. Load factor too high : Dot net 4.5

    I'm getting an exception “System.InvalidOperationException: Hashtable insert failed. Load factor too high.”
    My application is developed in VS2010 with 4.0 framework and it is working fine in our development environment (4.0 version ) (for 4.0 framework I'm able to find the hotfix and I've installed it in my development environment). In production environment
    framework is upgraded to 4.5 version and we often getting the mentioned exception.
    Application developed : windws 7 - 32 bit OS / vb.net 4.0
    Development environment (hotfix installed) :  windows server 2008 - 64 bit  / dotnet FW 4.0
    Prod Environment : windows server 2008 - 64 bit / dotnet FW 4.5 
    Kindly help me resolving this issue.
    Thanks.

    Hello,
    For this issue, we will focus on your new posted thread:
    https://social.msdn.microsoft.com/Forums/vstudio/en-US/a3feddfd-ff21-438c-9704-661375f096af/is-that-the-hot-fix-kb2803754-included-in-net-framework-451-version-4550938?forum=clr#a3feddfd-ff21-438c-9704-661375f096af
    >>Can you conform that the hot fix KB2803754 available in the version
    4.5.50938 (.NET Framework 4.5.1) ?
    You could do a test in the link above to check if the .NET 4.5.1 contians this KB(currently I do not have  an proper environment to test it).
    Regards.
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Failed to load value at index 22 with java object of type java.lang.String

    Hi all,
    As i am trying to open the notifications created from Administartor Workflow ,
    It throws a below error::
    oracle.apps.fnd.framework.OAException: oracle.jbo.AttributeLoadException: JBO-27022: Failed to load value at index 22 with java object of type java.lang.String due to java.sql.SQLException. at oracle.apps.fnd.framework.OAException.wrapperException(OAException.java:912) at oracle.apps.fnd.framework.OAException.wrapperException(OAException.java:886) at oracle.apps.fnd.framework.OAException.wrapperInvocationTargetException(OAException.java:1009) at oracle.apps.fnd.framework.server.OAUtility.invokeMethod(OAUtility.java:211) at oracle.apps.fnd.framework.server.OAApplicationModuleImpl.invokeMethod(OAApplicationModuleImpl.java:720) at oracle.apps.ap.oie.workflow.apexp.webui.NotifExpLinesCO.processRequest(NotifExpLinesCO.java:116) at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:600) at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.process
    java.sql.SQLException: Invalid column index
    at oracle.jdbc.driver.OracleResultSetImpl.getObject(OracleResultSetImpl.java:1042) at oracle.jbo.server.OracleSQLBuilderImpl.doLoadFromResultSet(OracleSQLBuilderImpl.java:1198) at oracle.jbo.server.AttributeDefImpl.loadFromResultSet(AttributeDefImpl.java:1633) at oracle.jbo.server.ViewRowImpl.populate(ViewRowImpl.java:2221).
    No extensions done in the page
    Please let me know the cause for this error ASAP
    Thanks
    Kash

    Problem solved. set the datatype as timestamp for that attribute in buissiness object.

Maybe you are looking for

  • Media encoder cs 6 and cuda  Ge Force gtx 780

    HI I have a new graphics card   it is the Gigabyte GeForce 780 I have CC and CC 2014  and also CS6    I notice that if encode using AME I can see Cuda enabled in the encoder window and the option to use software only as well. I don't see that option

  • Xcode project name

    If I make changes in a project and want to save it under a different name, the only option in the file menu seems to be to close the project with the same name. Is it possible to change the name of a project when it is open?

  • Records are not inserted into MTL_TXN_REQUEST_HEADERS,MTL_TXN_REQUEST_LINES

    Hi all, I am doing pick release thru API. For that , I have run following API successfully but my problem is that records are not inserted into MTL_TXN_REQUEST_HEADERS , MTL_TXN_REQUEST_LINES tables so that I cannot generate the move order. Can anyon

  • Problem loading a schema document using Java XDK

    I have an XSD file which I am attaching a portion of at the end of this message. If I use xmlns="http://www.w3.org/1999/XMLSchema" it will not recognize the "simpleContent" tag because I assume it did not exist in this version. If I use "http://www.w

  • Is that a good idea to put many things in /etc/rc.local?

    Hello, all: wiki told me that I could configure many files in /etc. However, sorry if sounds stupid, I think this is not KISS. I have to learn many different syntax to configure my computer. I think put things in /etc/rc.local if possible is a good i