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
Similar Messages
-
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 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 moreHi 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 -
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 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 !
seventyrosAccording 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 -
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
PoornimaFollowing 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) -
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,
YuHi 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 create Salience object and java.lang.NoClassDefFoundError
We are getting the below error while trying to use the text enrichment component in Endeca integrator clover server.
2015-01-26 10:11:59,880 INFO 1343495 [pool-7-thread-1] Creating new Salience object from data paths: '/app/oracle/ofm/TextEnrichment/salience-5.1.1.7349/data'.
2015-01-26 10:11:59,881 ERROR 1343495 [pool-7-thread-1] Failed to get Salience object from factory
java.lang.NoClassDefFoundError: com/lexalytics/salience/Salience
at com.endeca.clover.adapters.salience.SalienceFactory.createSalience(SalienceFactory.java:101)
at com.endeca.clover.adapters.salience.SalienceFactory.getSalienceInstance(SalienceFactory.java:41)
at com.endeca.clover.adapters.salience.SalienceRunnable.run(SalienceRunnable.java:92)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:680)
2015-01-26 10:11:59,891 ERROR 1343495 [WatchDog_1343495] Component [Customer Background:CUSTOMER_BACKGROUND] finished with status ERROR.
Failed to create Salience object.
2015-01-26 10:11:59,891 ERROR 1343495 [WatchDog_1343495] Error details:
org.jetel.exception.JetelRuntimeException: Component [Customer Background:CUSTOMER_BACKGROUND] finished with status ERROR.
at org.jetel.graph.Node.createNodeException(Node.java:535)
at org.jetel.graph.Node.run(Node.java:514)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:680)
Caused by: java.lang.RuntimeException: Failed to create Salience object.
at com.endeca.clover.adapters.salience.SalienceComponent.execute(SalienceComponent.java:166)
at org.jetel.graph.Node.run(Node.java:485)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
... 1 more
2015-01-26 10:11:59,930 INFO 1343495 [WatchDog_1343495] Execution of phase [0] finished with error - elapsed time(sec): 0
2015-01-26 10:11:59,930 ERROR 1343495 [WatchDog_1343495] !!! Phase finished with error - stopping graph run !!!
2015-01-26 10:11:59,930 INFO 1343495 [WatchDog_1343495] Post-execute finalization of connection:
2015-01-26 10:11:59,930 INFO 1343495 [WatchDog_1343495] DBConnection driver[org.jetel.connection.jdbc.driver.JdbcDriverImpl@103cdbdc]:jndi[null]:url[jdbc:oracle:thin:@gitvm000212.us.oracle.com:1521:upslstg]:user[upsell_winref] ... OK
2015-01-26 10:11:59,930 INFO 1343495 [WatchDog_1343495] -----------------------** Summary of Phases execution **---------------------
2015-01-26 10:11:59,931 INFO 1343495 [WatchDog_1343495] Phase# Finished Status RunTime(sec) MemoryAllocation(KB)
2015-01-26 10:11:59,930 INFO 1343495 [JobFinalizer_1343495] Finalisation
2015-01-26 10:11:59,931 INFO 1343495 [WatchDog_1343495] 0 ERROR 0 139976
2015-01-26 10:11:59,931 INFO 1343495 [WatchDog_1343495] ------------------------------** End of Summary **---------------------------
2015-01-26 10:11:59,931 INFO 1343495 [WatchDog_1343495] WatchDog thread finished - total execution time: 0 (sec)
2015-01-26 10:11:59,935 INFO 1343495 [JobFinalizer_1343495] RunTime: 296 ms
2015-01-26 10:11:59,935 ERROR 1343495 [JobFinalizer_1343495]
--------------------------------- Error details ----------------------------------
Component [Customer Background:CUSTOMER_BACKGROUND] finished with status ERROR.
Failed to create Salience object.
2015-01-26 10:11:59,935 INFO 1343495 [JobFinalizer_1343495] Finished Status: ERROR
This happens only on our stage and production instances. On our dev instance it works without problems. All 3 instances are setup the same, although our dev instance was created long time before the stage and prod instances. However, we cannot detect any differences between the machines.
I've tried the solutions mentioned in the other similar thread: Failed to create Salience object but this doesnt solve the issue since the directory and variables were already correct.
Anyone can help?Given that you are running this in Clover Server, one thing I can recommend is to shut that server down, move/truncate the logs, restart and retest, then look at the first error message you get when attempting to run the graph. Java classloaders sometimes cache failed class clinit and report future attempts to load that class as a simple NoClassDefFoundError, masking the original/actual root cause. With any luck you might find another, clearer error - maybe the native binary libraries are not being located.
-
Cisco Bars - Web Error : Failed to create ASP object
I have installed ;
Win2003
framework ASP .net2
IIS
MSDE 2000 serveur
Cisco BARS Version 4.0.12
When I go to http://IP/BARS
It ask for password, then I see the usual interface, but then I go and choose a backup option and I allways have this error
Windows Internet explorer
Failed to create ASP Object for : _RemoteScripts/rs_BARSconfig.asp
Firefox show that error :
Error:
Cannot locate proxy which supports Remote Scripting.
Was RSEnableRemoteScripting method invoked?
Second popup :
Failed to create ASP object for : _RemoteScripts/rs_BARSconfig.aspthanks a lot, it fix my problem verry well.
Another little one :)
have any idea of this one here ?
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
Timestamp: Sat, 4 Jul 2009 03:06:10 UTC
Message: Object doesn't support this property or method
Line: 269
Char: 3
Code: 0
URI: http://localhost/BARS/_ScriptLibrary/rs.htm
Message: 'rsConfig' is null or not an object
Line: 199
Char: 3
Code: 0
URI: http://localhost/BARS/BARSserverConfig.asp -
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 moreHI saket jha,
Refer the following thread
Error in "Who is Who" search
ESS Timesheet Error
Regards,
Manivannan P -
'Failed to create object' when trying to open PDF attachment in Dynamics GP 10 OLE notes
Microsoft Dynamics GP 10 users who updated to Adobe Reader X are getting errors when trying to open or create an OLE attachment on a note.
They get 'Failed to create object' when trying to open an existing and getting 'Failed to connect.
And " Link may be broken" when trying to create a new one.
PDF attachments work pretty fine with previous version of Acrobat reader 7,8,9 up tp 9.4
Now that we install Acrobat X, something has changed.
It only does this for PDF attachments, Other file types work fine.
I was able to remove Adobe Reader X and install a prior version to work around the issue.
Has Adobe developed any Fix for the integration of X and OLE objects.
regards,Hi Gestis,
What version of Adobe Reader are you using?
If its less that 10.1.2, please update it to 10.1.2 and then try to open PDF attachment inDynamcs GP OLE notes. -
I executed a simple query inside an execute SQL task -
SELECT col1, col2
from thetable
where code = ?
order by id asc
Exec sql task - ADO.NET connection
parameter "code" is an int32 in SSIS and int32 in parameter mapping of exec sql task.
It works fine in SQL server, but in SSIS it causes the error -
[Execute SQL Task] Error: Executing the query "SELECT col1, col2
from thet..." failed with the following error: "Failed to create an IDataAdapter object. This provider may not be fully supported with the Execute SQL Task. Error message 'Incorrect syntax near '?'.'.". Possible failure reasons: Problems with
the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
How do I fix this error ?Thanks. I think it was sqlclient. I changed it to OLEDB to avoid that issue. Btw, what is this "provider" ?
Hi blastoSO,
To check which provider is used by the current ADO.NET Connection Manager, you can open the “Configure ADO.NET Connection Manager” window, and check the “Managed Provider” option of each Data connection.
In an Execute SQL Task, if the managed provider is “System.Data.SqlClient”, we should use the rule for the ADO.NET connection type in the following table. If the managed provider is “System.Data.Oledb” or “System.Data.Odbc”, it actually uses the OLE DB provider
or ODBC provider, so we should use the rule for the OLE DB or OBC rule in the following table:
Reference:
http://technet.microsoft.com/en-us/library/cc280502.aspx
Regards,
Mike Yin
TechNet Community Support -
VBoxManage: error: Failed to create a session object!
When I run
vagrant up
I get the following output:
Bringing machine 'default' up with 'virtualbox' provider...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["list", "hostonlyifs"]
Stderr: VBoxManage: error: Failed to create a session object!
VBoxManage: error: Code NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) - Class not registered (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.
I tried directly running
VBoxManage list
and I get this output:
VBoxManage: error: Failed to create a session object!
VBoxManage: error: Code NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) - Class not registered (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.
VirtualBox (and vagrant) were both working earlier today, but I updated a bunch of packages via
yaourt -Syua
which I suspect is what caused the problem. Here's (what I think are) the relevant part of
/var/logs/pacman.log
[2013-10-22 15:53] [PACMAN] starting full system upgrade
[2013-10-22 15:55] [PACMAN] upgraded libpng (1.6.5-1 -> 1.6.6-1)
[2013-10-22 15:55] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2013-10-22 15:55] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2013-10-22 15:55] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> Starting build: 3.11.6-1-ARCH
[2013-10-22 15:55] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-10-22 15:55] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-10-22 15:55] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2013-10-22 15:55] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-10-22 15:55] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-10-22 15:55] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-10-22 15:55] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-10-22 15:55] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2013-10-22 15:55] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> Starting build: 3.11.6-1-ARCH
[2013-10-22 15:55] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-10-22 15:55] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-10-22 15:55] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-10-22 15:55] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2013-10-22 15:55] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-10-22 15:55] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-10-22 15:55] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2013-10-22 15:55] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-10-22 15:55] [PACMAN] upgraded linux (3.11.5-1 -> 3.11.6-1)
[2013-10-22 15:56] [ALPM] warning: /boot/syslinux/syslinux.cfg installed as /boot/syslinux/syslinux.cfg.pacnew
[2013-10-22 15:56] [ALPM-SCRIPTLET] Syslinux BIOS update successful
[2013-10-22 15:56] [ALPM-SCRIPTLET] If you used syslinux-install_update to install syslinux:
[2013-10-22 15:56] [ALPM-SCRIPTLET] ==> If you want to use syslinux with menu and all modules please rerun
[2013-10-22 15:56] [ALPM-SCRIPTLET] ==> # /usr/bin/syslinux-install_update -i -a -m
[2013-10-22 15:56] [ALPM-SCRIPTLET]
[2013-10-22 15:56] [ALPM-SCRIPTLET] If you manually installed syslinux:
[2013-10-22 15:56] [ALPM-SCRIPTLET] ==> Please copy or symlink all .c32 modules to your /boot/syslinux directory.
[2013-10-22 15:56] [ALPM-SCRIPTLET] ==> If (/ and /boot on seperate fs):
[2013-10-22 15:56] [ALPM-SCRIPTLET] ==> # cp /usr/lib/syslinux/bios/*.c32 /boot/syslinux
[2013-10-22 15:56] [ALPM-SCRIPTLET] ==> If (/ and /boot on same fs):
[2013-10-22 15:56] [ALPM-SCRIPTLET] ==> # ln -s /usr/lib/syslinux/bios/*.c32 /boot/syslinux
[2013-10-22 15:56] [PACMAN] upgraded syslinux (4.07-1 -> 6.02-3)
[2013-10-22 15:56] [ALPM-SCRIPTLET] In order to use the new version, reload all virtualbox modules manually.
[2013-10-22 15:56] [PACMAN] upgraded virtualbox-host-modules (4.2.18-7 -> 4.3.0-1)
[2013-10-22 15:56] [PACMAN] upgraded virtualbox (4.2.18-2 -> 4.3.0-1)
After merging in the changes from
/boot/syslinux/syslinux.cfg.pacnew
, I ran
/usr/bin/syslinux-install_update -i -a -m
, and then rebooted the system, and that's when I first discovered VirtualBox was no longer working.
I tried
sudo modprobe vboxdrv
sudo modprobe vboxnetadp
sudo modprobe vboxnetflt
and
sudo modprobe vobxpci
based on what I saw from https://bbs.archlinux.org/viewtopic.php?id=130317
I tried
chown root.root /tmp; chmod ug-s /tmp; chmod 1777 /tmp
based on what I saw from https://www.virtualbox.org/ticket/2335#comment:4
The output of
/bin/ls -ld /tmp
is
drwxrwxrwt 4 root root 80 Oct 22 16:46 /tmp
Not sure what to try next.
Last edited by Nebu (2013-10-22 21:33:35)I also can confirm the same issue as with previous posters, tried all stuff found on the net that seems related to this issue.
Nothing so far as solved it for me, I also had to downgrade to 4.2.18. Not optimal but atleasat i can work until this has been sorted out.
Last edited by loxan (2013-10-24 09:02:19) -
IMPDP Help needed please...ORA-39083: Object type PROCOBJ failed to create
OS=Win2003
DB=10gR2
Version = 102.0.4
Hi,
I am running a impdp on a 30gb file and well it seems to have gone fine (much faster then it normally does to be honest), but towards the end it fails, and when researching this error, it seems to be very vague and I was wondering if someone can help me. Below is the log, but I have taken parts out of it that are not relevant.
Import: Release 10.2.0.4.0 - Production on Wednesday, 16 April, 2008 15:22:18
Copyright (c) 2003, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Master table "SYSTEM"."IMPGEMDEV041608" successfully loaded/unloaded
Starting "SYSTEM"."IMPGEMDEV041608": system/********@iworksdb directory=DATA_PUMP_DIR dumpfile=expdpgemdev.dmp job_name=impgemdev041608 TABLE_EXISTS_ACTION=APPEND SCHEMAS=GEMDEV LOGFILE=IMPIWORKS_BOON.log REMAP_SCHEMA=GEMDEV:IWORKS REMAP_TABLESPACE=IWORKS_INDEX:IWORKS_IDX REMAP_TABLESPACE=IWORKS_IOT:IWORKS_IDX REMAP_TABLESPACE=IWORKS_TABLES:IWORKS_TABLES EXCLUDE=GRANT exclude=statistics STREAMS_CONFIGURATION=N
Processing object type SCHEMA_EXPORT/USER
ORA-31684: Object type USER:"IWORKS" already exists
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/TABLESPACE_QUOTA
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/TYPE/TYPE_SPEC
ORA-31684: Object type TYPE:"IWORKS"."T_NUMBER_TAB" already exists
ORA-31684: Object type TYPE:"IWORKS"."T_VARCHAR2_TAB" already exists
Processing object type SCHEMA_EXPORT/TABLE/TABLE
ORA-39152: Table "IWORKS"."SYS_TOKENTYPE" exists. Data will be appended to existing table but all dependent metadata will be skipped due to table_exists_action of append
ORA-31684: Object type PACKAGE:"IWORKS"."CONT_FEE_DEF_UC" already exists
ORA-31684: Object type PACKAGE:"IWORKS"."COPAYCALCFLAG" already exists
ORA-31684: Object type VIEW:"IWORKS"."VWTREE" already exists
ORA-31684: Object type VIEW:"IWORKS"."V_ROUTE_DTL_GROUP" already exists
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
Processing object type SCHEMA_EXPORT/TABLE/INDEX/FUNCTIONAL_AND_BITMAP/INDEX
Processing object type SCHEMA_EXPORT/POST_SCHEMA/PROCOBJ
ORA-39083: Object type PROCOBJ failed to create with error:
ORA-06550: line 2, column 11:
PLS-00103: Encountered the symbol "VARCHAR2" when expecting one of the following:
:= . ( @ % ;
The symbol ":=" was substituted for "VARCHAR2" to continue.
ORA-06550: line 3, column 12:
PLS-00103: Encountered the symbol "VARCHAR2" when expecting one of the following:
:= . ( @ % ;
The symbol ":=" was substituted for "VARCHAR2" to continue.
ORA-06550: line 4, column 19:
PLS-00103: Encountered the symbol "VARCHAR
ORA-39083: Object type PROCOBJ failed to create with error:
ORA-06550: line 6, column 16:
PLS-00103: Encountered the symbol "RAYSQLACCESS9889405" when expecting one of the following:
* & = - + ; < / > at in is mod remainder not rem
<an exponent (**)> <> or != or ~= >= <= <> and or like LIKE2_
LIKE4_ LIKEC_ between || multiset member SUBMULTISET_
The symbol "* was inserted before "RAYSQLACCESS9889405" to continue.
ORA-06550: line 7, column 17:
PLS-00103: Encountered the symbol "SQL" when expectin
Job "SYSTEM"."IMPGEMDEV041608" completed with 2831 error(s) at 15:30:37
Any help will be much appreciatedI can not seem to find any object named PROCOBJ.
As for the object called RAYSQLACCESS9889405...no idea what this is.
I checked the source for any invalid objects and none. -
ORA-39083: Object type TRIGGER failed to create with error:
i m getting these two error when i import data using impdp.
ORA-39083: Object type TRIGGER failed to create with error:
ORA-00942: table or view does not exist
i have exported (expdp) data from production db, when i importing (impdp) the dump file to the test db i m geting the above two errors.
example:
ORA-39083: Object type TRIGGER failed to create with error:
ORA-00942: table or view does not exist
Failing sql is:
CREATE TRIGGER "NEEDLE"."CC_BCK_TRG" BEFORE INSERT OR UPDATE
ON NIIL.cc_bck_mgmt REFERENCING NEW AS NEW OLD AS OLD FOR EACH ROW
DECLARE
w_date DATE;
w_user VARCHAR2(10);
BEGIN
SELECT USER,SYSDATE INTO w_user,w_date FROM DUAL;
IF INSERTING THEN
:NEW.cretuser :=w_user;
:NEW.cretdate :=w_date;
END IF;
IF UPDATING THEN
:NEW.modiuser :=w_user;
:NEW.modidate :=w_date;
END IF;
END;
status of the above trigger in pro db is valid. and source table also exist even though i m getting error when i import
please suggest me...perhaps you don't have table... (impdp created trigger before create table)
check about "NIIL.cc_bck_mgmt" table.
and then create it (trigger) manual ;)
Good Luck.
Maybe you are looking for
-
Follow up - DNS (internal domain has same name as external website)
Hi, I am following up with on previous blog entry about resolving an domain internal name to an external website found here: https://social.technet.microsoft.com/Forums/windowsserver/en-US/4d97325b-ff3a-4f46-ba6e-dc3f4ff978e1/dns-internal-domain-has-
-
Hey there:) since i updatet my iPhone 4s to ios7 the music synchronasation doesn't work! it takes a long time and it misses out many music pieces and i don't know why i also don't get any notificatations that not all the titles are synchronised and t
-
My ipod is exactly 2 years old, and it has nothing to do with the cable connecting it to the computer for all I know.
-
How to disable annoying photo sharing feature
Hi, when I exchange pictures via skype it converts file into link: To view this shared photo, go to: https://api.asm.skype.com/s... Also it decreases quality of picture significantly. Is there a way to disable this very annoying "feature"? I just wa
-
Communication type cannot be used.
when i try to issue an output type using va01/va02, (menu:->extra->header->output->edit)and assign the output to send it to mail,using cs01 communication type ,it gives an error communication type cannot be used