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.asp

thanks 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

Similar Messages

  • PeopleSoft Web Services Connector Error – Failed to create a 'RequestMessageMemberType' . . .

    Hello all,
    I am new to FIM and am currently in the process of setting-up a PeopleSoft
    Web Services MA.  I am receiving the following error in the FIM Sync Manager in the Create Management Agent dialog in the Global Parameters section:
    “Test Connection failed with the following error: Failed
    to create a ‘RequestMessageMemberType’ from the text d:Find__CompIntfc__CI_PERSONAL_DATATypeShape’. Below is the information about configured endpoint address(es): http://<FQDN>:10320/PSIGW/PeopleSoftServiceListeningConnector/HR92DEV”.
    I had no issues with the discovery process in the Web Services Configuration tool.  The following parameters were supplied for the config file:
    WSDL: 
    http://<FQDN>:10320/PSIGW/PeopleSoftServiceListeningConnector/HR92DEV/PSCONNECTORWEBSERVICE.1.wsdl
    Namespace: 
    targetNamespace
    Basic authentication <user>, <password>; Interoperable:
    PasswordText
    Has anyone else received this error message or can anyone give me some advice on how to troubleshoot?  Any help would be greatly appreciated.
    Thanks.

    Hello all,
    I am new to FIM and am currently in the process of setting-up a PeopleSoft
    Web Services MA.  I am receiving the following error in the FIM Sync Manager in the Create Management Agent dialog in the Global Parameters section:
    “Test Connection failed with the following error: Failed
    to create a ‘RequestMessageMemberType’ from the text d:Find__CompIntfc__CI_PERSONAL_DATATypeShape’. Below is the information about configured endpoint address(es): http://<FQDN>:10320/PSIGW/PeopleSoftServiceListeningConnector/HR92DEV”.
    I had no issues with the discovery process in the Web Services Configuration tool.  The following parameters were supplied for the config file:
    WSDL: 
    http://<FQDN>:10320/PSIGW/PeopleSoftServiceListeningConnector/HR92DEV/PSCONNECTORWEBSERVICE.1.wsdl
    Namespace: 
    targetNamespace
    Basic authentication <user>, <password>; Interoperable:
    PasswordText
    Has anyone else received this error message or can anyone give me some advice on how to troubleshoot?  Any help would be greatly appreciated.
    Thanks.

  • 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?

  • Publish error: failed to create chr_book_op.gif

    I'm using RH10 as part of TCS4. Multiple projects that are routinely updatedfor the past 10 years suddenly (since the last update) now all fail during the Publish operation with an unhelpful error "Failed to create chr_book_op.gif." The projects generate without error so this is not a problem within TCS4. Since the error occurs in multiple projects, I assume it is a connectivity issue. To test, I verified that  I can manually (using Filezilla) FTP all files to the target Web site so I know the FTP settings are valid. I have verified that the Filezilla FTP settings are the same settings as defined in the project's Publish settings. The only thing that changed since the last update is that I swapped out a broadband modem. Everything works correctly with the new modem, and I assume that since I can successfully manually FTP, the modem is not the source of the problem.
    Has anyone seen this error before? I'm at a loss as to how to further troubleshoot.  It would be a nuisance if I cannot use RH's Publish functionality.

    Hello Anjaneai,
    I created a test project (as WebHelp). It generated correctly but again failed during Publish at the same file (chr_con_out.gif) that causes all of my other projects to fail. The .gif file is present in all of my projects and is part of the standard Chrisi skin. Here is a screenshot of the error:
    I generated the same test project as FlashHelp. It generated correctly but failed during Publish. I don't use FlashHelp, so I don't know how to interpret the error. Here is a screenshot of the error:
    There were no errors to indicate a problem with the FTP connection.
    Thank you for your help.
    Carol

  • 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

  • Query doesn't work in APD, Error: column store error: fail to create scenario: [340 2048

    Hi Experts,
    We got a problem here.
    We have a query ran without any problems in RSRT. But when I try to put it as data sources(infoprovider) in APD.
    I got following error:
    column store error: fail to create scenario: [340 2048
    We are in BW731006 & ABAP731006.
    Any advise?
    Thanks in advance!
    Tengran

    Hi,
    Can you check this part in error mentioned by clicking as highlighted in red box. It will give you a correct idea about the issue ::
    Also share the detailed error with us as well.
    Best Regards,
    Arpit

  • Xcode ERROR: Failed to create an alert for ID "enabled" based on defaults: 1

    I installed OX 10.8 and xcode 4.4 and when I run any simple application for simulator it generated error in console:
    Xcode[7808]: ERROR: Failed to create an alert for ID "enabled" based on defaults: 1
    I reinstalled with clean xcode, but it did not help.  I see the building freeze when "coping 2 of 2 resources to product
    Also, xcode freezes when I jusy click on Mainstoryboard.storyboard file.
    I found a few posts with the same ERROR but no clear fix.  Any help will be appriciated.

    Hi, i had the same problem yesterday and after searching I found no solution to this error.
    Today i just burned the original Mountain Lion.dmg to a portable hard driver then reinstall the OS. And it seemed that the os had been restored and the error had been fixed.
    And, i guess there's some app that changes some documents of the system. So when you rewrite the os, u get the bug fixed.
    Good luck to you guys.

  • SCCM 2012 Client Error Failed to create registration request body. Error: 0x80070057

    Hi,
    While installing sccm 2012 R2 Client on server 2008 R2 ClientManagerStartup.log shows below error
    Failed to create registration request body. Error: 0x80070057
    Kiran

    Torsten is right, please post the entire ccmsetup.log and client.msi.log.
    Daniel Ratliff | http://www.PotentEngineer.com

  • 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)

  • Any workaround to CDG-00071 SYSTEM ERROR:  Failed to create Forms API context

    Hi all,
    Is there a workaround to "CDG-00071 SYSTEM ERROR: Failed to create Forms API context" other than re-installing designer, then forms builder on the same ORACLE HOME directory? To do this will cause considerable downtime to our systems.

    Hi Diego,
    Do you have the correct, corresponding version of
    Developer installed? You must install Developer to
    be able to generate and run the Forms correctly.
    If so, is it in the same <ORACLE_HOME>?
    You normally get this error if you don't have Developer
    installed in the same ORACLE_HOME as Designer. Please
    see the relevant Designer installation guides for full details.
    Regards,
    Dominic
    Designer Product Management
    Oracle Corp

  • 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

  • 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 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.

  • ADT: Web Dynpro view/window error "Failed to create the part's controls"

    Hi, all
    Most of the things in my ADT work fine (e.g. programs, structures, domains), even the Web Dynpro Componentcontroller can be edited.
    However, with Web Dynpro view and window I get this error message: "Failed to create the part's controls".
    In SAP GUI everything works fine.
    Why could this happen and what can I do?
    My system details:
    32-bit Windows 7
    Eclipse Luna Release (4.4.0)
    ADT from https://tools.hana.ondemand.com/kepler, according to these instructions:  SAP Development Tools for Eclipse.
    SAP GUI 7.30, patch level 9.
    SAP_ALL authorizations
    Java: SE, version 7 update 60
    Activated services (SICF): wdy_aie_vd_preview, toolsdocu, docu
    The Java error log in Eclipse is quite long. It starts with:
    java.lang.IllegalStateException: java.lang.IllegalArgumentException: No enum constant com.sap.adt.wda.controller.semanticfs.common.ControllerFileServices.ControllerObjectTypeEnum.WDYNWZ
        at com.sap.adt.tools.core.ui.editors.AdtFormEditor.addPages(AdtFormEditor.java:222)
        at org.eclipse.ui.forms.editor.FormEditor.createPages(FormEditor.java:138)
        at com.sap.adt.tools.core.ui.editors.AdtFormEditor.createPages(AdtFormEditor.java:1251)
        at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:362)
        at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:140)
        at org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:99)
        at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:321)
        at sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
    As it is not popular to post long logs unnecessarily, I will skip the rest of it for the moment - let me know if it could help and I will post it.
    Thanks for help!
    KR,
    Igor

    Hi Ponraj,
    note applied without any problem.
    I'm still facing some difficulties accessing a WD component, maybe you could suggest me how to solve/proceed:
    in Eclipse Luna, I can access now a WD but "Layout" tab doesn't work - HTTP 403 Forbidden - Service cannot be reached. I guess it's a missing configuration, could you help me out on this?
    EDIT: This one is solved; I just missed to activate a service in SICF (WDY_AIE_VD_PREVIEW).
    That Eclipse module however seems not to be very stable; I tried to open a standard SRM WD view (wd component /SAPSRM/WDC_DO_SOCO_GAF_1, view V_AO_SOCO_GAF_1) and that resulted in the message:
    500 SAP Internal Server Error
    ERROR: Conversion of type C LENGTH 255 to type TABLE OF DEEP_STRUCTURE not supported. (termination: RABAX_STATE)"
    is there a way, from the Methods tab, to access directly to a particular method's implementation? The only way I found is going manually under the IMPLEMENTATION tab and CTRL+F with the method's name.
    is there any way to access to a particular enhancement made on the WD? Using SapGUI, there's a special "vortex" button to switch on a specific enhancement, but under Eclipse I can't find the alternative command.
    I know we're getting a bit OT with respect to the topic, anyway if there's a guide that could help clarifying my doubts please, share that documentation
    BR,
    M.

  • Runtime error: failed to create delegate view

    hi all,
    We have two applications in two separate projects. But we can deploy only one at a time. If we deploy the second application (or vice-versa)and try to access the first application, it throws up the following error.
    P.S. The problem is only with these two applications and they use Adaptive RFC models.
    We thought it was because of some Jco conections, but all of them test correctly from the WebDynpro administrator console. Any ideas?
    Error stacktrace:
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create delegate for view com.eac.vendorportal.DisplayNCRView. (Hint: Is the corresponding DC deployed correctly? Does the DC contain the component?)
         at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:110)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.<init>(DelegatingView.java:41)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.createUninitializedView(ViewManager.java:487)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:524)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
         at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:134)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:373)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:252)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
         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:392)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
         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:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         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:95)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
    Caused by: java.lang.ClassNotFoundException: com.eac.vendorportal.wdp.InternalDisplayNCRView
    Found in negative cache
    Loader Info -
    ClassLoader name: [local/ChangeNCR4]
    Parent loader name: [Frame ClassLoader]
    References:
       common:service:http;service:servlet_jsp
       service:ejb
       common:service:iiop;service:naming;service:p4;service:ts
       service:jmsconnector
       library:jsse
       library:servlet
       common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl
       library:ejb20
       library:j2eeca
       library:jms
       library:opensql
       common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore
       interface:resourcecontext_api
       interface:webservices
       interface:ejbserialization
       sap.com/tcwddispwda
       sap.com/tcwdcorecomp
       service:webdynpro
       service:sld
       library:tcddicddicservices
       library:com.sap.aii.proxy.framework
       library:tcgraphicsigs
       library:com.sap.mw.jco
       library:com.sap.lcr.api.cimclient
       library:sapxmltoolkit
       library:com.sap.aii.util.rb
       library:com.sap.util.monitor.jarm
       library:tcddicddicruntime
       library:com.sap.aii.util.xml
       library:tccolapi
       library:com.sap.aii.util.misc
       library:tc~cmi
       library:tccolruntime
    Resources:
       F:\usr\sap\PED\JC00\j2ee\cluster\server0\apps\local\ChangeNCR4\webdynpro\public\lib\app.jar
    Loading model: {parent,references,local}
         at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:348)
         at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:65)
         ... 33 more

    Hallo Vamsee,
    you wrote <i>"We use the same package naming conventions in both projects.Is that a problem"!</i> Does this mean that you have two different DCs sap.com/a/b/c/onedc and sap.com/a/b/c/anotherdc which both contain the same Web Dynpro component packages e.g. com.sap.a.b.c.mycomp? If this is true both Deployable DC units will collide on the serverside because the Web Dynpro classloader does not differ between the same Web Dynpro packages in different DCs. The DC namespace is not reflected by the classloader.
    Regards, Bertram

Maybe you are looking for

  • How to install Mac OSX on New Hard Drive (No Disk)

    I have a new Hard Drive that I just received and I'm looking to install it on my Early 2009 17 inch Macbook Pro. The problem is I dont have the original disk that came with my macbook. I do have a 2TB external HD so is there anyway I can back up Mave

  • MBP randomly crashes when in clamshell with external display

    Hi Mac people. As described in the "subject field" i have been encountering some random crashes after i startet using my MBP in clamshell with my newly pruchased 24" 16:10 NEC display . typically it occurs after about 10-20 minutes of playing world o

  • Exporting report to Excel messes up the graphs

    Hi All I am facing an issue and wanted to know if anyone has dealt with it before. I have data in tabular format as well as graphs (bar charts, pie charts etc). When I export the report and save it as PDF everything is excellent but when I export the

  • 0CUSTOMER_LKLS_HIER error when loading after addin class

    Hello, There has been added a class in R3 for customer.Ever since i can not load customer hierarchy in bw. I get the following error message "Node characteristic 0CLASS_NUM is not entered as hierarchy characteristic for 0CUSTOMER". In R3 i can run rs

  • Using custom color profiles....leica m8 on import

    Is it possible to use or assign a custom color profile like I would in capture 1? Thanks