Config SLD error on SAPNWCE71Trial_JavaEEServer

Hi all:
[step-1]After I successfully installed SAPNWCE71Trial_JavaEEServer(downloaded from SDN) on my laptop,
[step-2]goto: http://localhost:50000/sld
     error reported: System Landscape Directory(SLD)is not installed on this AS Java system
Question: How to reinstall SLD from SAPNWCE71Trial_JavaEEServer?
Thanks for any help and suggestion

Hello ,
As per my understanding you can not install SLD as single component .
SLD should be install at the time of Installation .
Hope I answer your Question !
Regards ,
Santosh

Similar Messages

  • Define system on portal J2ee server in SYSTEM CONFIG -- SLD error

    Hi,
    Can , any body tell me how to create a system on portal J2EE server in which bussiness package has implemented.
    WAS properties for the system as
    WAS host name:<j2ee name> : <port>
    WAS Path:/ webdynpro/dispatcher/
    wAS protocol :HTTP
    I have tried to create system in System admin--> System configuration --.>SLD .But it is showing following error
         SAP Web AS Connection
    Test Details:
    The test consists of the following steps:
    1. Checks the validity of system ID in the system object.
    2. Checks if the system can be retrieved from the PCD.
    3. Check whether a SAP system is defined in the system object
    4. Validate the following parameters: WAS protocol; WAS host name
    5. Checks if the host name of the server can be resolved.
    6. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
    7. Checks HTTP/S connectivity to the defined back-end application
    Results
    1. The system ID is valid
    2. The system was retrieved.
    3. The system object represents an SAP system
    4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (XX.XX.XX.XX:50000)
    5. The host name XX.XX.XX.XX was resolved successfully.
    6. The Web AS ping service http://XX.XX.XX:50000/sap/bc/ping was not pinged successfully. If the ping service is not activated on the Web AS, you can try to call the ping service manually.
    7. An HTTP/S connection to http://xx.xx.xx:50000/webdynpro/dispatcher/ was not obtained successfully; this might be due to a closed port on the Firewall.
    Why it is checking R/3 connection setup like sap/bc/ping and other connection . Iam creating WAS connection for java only.Even iam not define any related properties on this system.
    Regards,
    Eswar.

    Hi,
    in your ABAP system, open transaction SICF, F8, and go activating the required services :
    Default Host > sap > bc > ping. Right click on it and choose "Activate".
    This will normally solve your point 6 error.
    For point 7 I might think of a port error, can you tell us if your system is load balanced ? if yes, your port defined in your system in the PCD in the connector category hase to be 3600. If not load balanced : 3200.
    If implementing SSO, also check in the RZ10 transaction that your default profile contains those parameters :
    login/create_sso2_ticket = 2
    login/accept_sso2_ticket = 1
    icm/host_name_full = server_host_name.domain.com.
    Fabien.

  • Error while Running ESS - TypeBroker failed to access SLD: Error while obta

    Hi all,
    We try to run a WebDypro Application of ESS on 6.40 with mySAP ERP 2004:
    All the necessary JCO connections
    - SAP_R3_HumanResources
    - SAP_RE_HumanResources_MetaData
    are maintained and pinged and tested positive.
    Still, we get following error message. (see complete stack below):
    ...TypeBroker failed to access SLD: Error while obtaining JCO connection.
    Could anybody help, please?
    ERROR STACK
    An error has occurred:
    "Failed to process the request."
    Please contact your system administrator.
    Hide details
    Web Dynpro client:
    HTML Client
    Web Dynpro client capabilities:
    User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0), version: null, DOM version: null, client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
    Web Dynpro runtime:
    Vendor: SAP, Build ID: 6.4011.00.0000.20050217164947.0000 (release=630_VAL_REL, buildtime=2005-02-20:21:49:12[UTC], changelist=329752, host=PWDFM026)
    Web Dynpro code generators of DC sap.com/essarbank:
    SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:41[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:28:58[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:03[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapWebDynproGenerationCTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:17:08[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:25[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:21:50[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:14[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:44[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:46[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    Web Dynpro code generators of DC sap.com/pcui_gp~xssutils:
    SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:41[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:28:58[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:03[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapWebDynproGenerationCTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:17:08[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:25[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:21:50[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:14[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:44[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:46[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    Web Dynpro code generators of DC sap.com/ess~per:
    SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:41[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:28:58[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:03[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapWebDynproGenerationCTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:17:08[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:25[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:21:50[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:14[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:44[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:46[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    Web Dynpro code generators of DC sap.com/tcwddispwda:
    No information available
    Web Dynpro code generators of DC sap.com/pcui_gp~xssfpm:
    SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:41[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:28:58[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:03[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapWebDynproGenerationCTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:17:08[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:25[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:21:50[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:14[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:44[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:46[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    Web Dynpro code generators of DC sap.com/tcwdcorecomp:
    No information available
    Web Dynpro code generators of DC sap.com/ess~xx:
    SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:41[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:28:58[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:03[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapWebDynproGenerationCTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:17:08[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:25[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:21:50[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:14[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:44[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:46[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    J2EE Engine:
    No information available
    Java VM:
    Java HotSpot(TM) Server VM, version: 1.4.2_08-b03, vendor: Sun Microsystems Inc.
    Operating system:
    Windows 2000, version: 5.0, architecture: x86
    Error stacktrace:
    com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type com.sap.pcuigp.xssfpm.wd.model.types.Ext_Service could not be loaded: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:205)
         at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:485)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:771)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:756)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:433)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getController(Component.java:362)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.getPublicInterface(DelegatingComponent.java:142)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetBackendConnectionsController(InternalFPMComponent.java:199)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:171)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:105)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:95)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:346)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:349)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:599)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
         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:391)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)
         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:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:89)
         at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:408)
         at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:354)
         at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:215)
         at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)
         at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:87)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:73)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
         at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:234)
         ... 40 more

    Hi
    The type broker error indicates, issue with regard to your SLD. Check whether the SLD is configured properly. You need to do a initial level of SLD between your message server (SAp/back end) and your server. Check whether landscape has been created for the SAP server.
    landscape must be proper with your server configuration/installation number, SID and instance number...etc...
    After you have your SLD, recheck on your JCO for the model data and meta data connections..
    If you have any specific issues do let us know
    thanks
    sathya

  • Windows LV6.0 running on Linux Wine: config.cpp error (line 404)

    Have anyone tried to run LabView (Windows version) under Linux using the Wine "emulator"?
    Trying this on Debian Woody, with a Win98 install of LabView 6.0 returns:
    config.cpp error (line 404)
    I tried to search for such a file on both Win/Linux partitions: there's none.
    So how am i gonna check this line 404?
    Any clue would be strongly welcome!

    I agree with Labviewguru about getting Labview for Linux. The only
    problem is that you have to dish out $2000 or $3500. They don't have a
    Base package.
    I'm not sure if NI recomends a particular window manager but I do know it
    will run on any of them. In an extreme case I used it on a PII 233MHz,
    64MB ram, and a 300 MB disk. It was a Slackware distro using the fvwm2
    window manager. Ran great. Presently I run it with Gnome.
    My point is that if you have to buy a LV for Linux license, at least you
    can save money buy putting it on a machine that's been used as a paper
    weight for several years.
    -kevin
    In article <[email protected]>,
    "Labviewguru" wrote:
    > I don't believe you can run LabVIEW in an e
    mulation environment. There
    > is too much system control that LabVIEW needs a handle on to be able to
    > run on an emulator.
    >
    > The reason you are not able to find and troubleshoot that file is
    > because it is part of the source code for LabVIEW, and doesn't exist
    > except in a super secret vault which may or may not be located in Austin
    > Texas...
    >
    > Are you aware that there is a version of LabVIEW for Linux? I believe
    > that they recommend running KDE or similar GUI, but check on the support
    > website for that at ni.com/linux.
    >
    > I hope that was enough of a clue...

  • Aspnet_compiler web.config(132): error ASPCONFIG: Could not load type 'System.Data.Entity.Design.AspNet.EntityDesignerBuildProvider'

    My latest MVC 5 project built with VS 2013 compiled and works fine on my PC but can not be published to server using command line aspnet_compiler. I kept getting the web.config(132): error ASPCONFIG: Could not load type 'System.Data.Entity.Design.AspNet.EntityDesignerBuildProvider'
    In my web.config file, I have the following as suggested by many for solution:
    <add assembly="System.Data.Entity, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
     <add assembly="System.Data.Entity.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
    However, the error is persisting.  I have no clue how to fix this.  Hope someone can help.

    Hello FredVanc,
    As you mentions, it could work with your develop environment, so I am wondering it is that on the server machine, the assembly is not there actually. Here are some information I found which might be helpful:
    https://support.microsoft.com/en-gb/kb/958975?wa=wsignin1.0
    https://social.msdn.microsoft.com/Forums/en-US/1295cfa8-751b-4e9b-a7a7-14e1ad1393b6/compiling-error?forum=adodotnetentityframework
    By the way, since this issue is related with ASP.ENT project, I suggest that you could post it to the ASP.NET forum, there are web experts will help you:
    http://forums.asp.net/
    Regards.
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • SLD Error

    Hello All,
    I am trying to deploy a webdynpro app .The backend connection fails .
    I am able to test the Jco Connection on SLD and the test is sucessfull.
    Please help
    Root Cause
    The initial exception that caused the request to fail, was:
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'BERLIN_METADATA' in the SLD. No such JCO destination is defined in the SLD.
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:500)
    at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:229)
    at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:214)
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:111)
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:147)
    ... 45 more
    Stack Trace:
    com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type extern:com.sap.netweaver.mobile.emp.types.GetEmployeeTimeModel:com.sap.netweaver.mobile.emp.types.Bapicats2 could not be loaded: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
    at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:305)
    at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:229)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:654)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
    at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:429)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:345)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:668)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:268)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:40)
    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.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
    at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:90)
    at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:408)
    at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:354)
    at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:215)
    at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)
    at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:87)
    at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:73)
    at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
    at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
    at com.sap.dictionary.runtime.DdBroker.getStructure(DdBroker.java:180)
    at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:303)
    ... 32 more
    Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:149)
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:175)
    at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:62)
    at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:77)
    ... 42 more
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'BERLIN_METADATA' in the SLD. No such JCO destination is defined in the SLD.
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:500)
    at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:229)
    at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:214)
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:111)
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:147)
    ... 45 more
    Thanks

    Hi silpa,
    The exception came as your JCO connection is not defined in SLD; Login to the J2EE server as Administrator and configure the connection BERLIN_METADATA.
    Follow the steps
    Login as Administrator
    Select Button "maintain JCo Destinations"
    Find the Source
    Configure the MODEL_DATA as application data at the Datatype and RFC_METADATA_DEST as Dictionary meta data  .
    After configuring this test it and run the application.
    Regards
      - Vinod
    Rewards if found helpful.

  • SLD error after LDAP integration

    Hello All,
    I integrated Corporate LDAP with EP 7.0 ,after that I have SLD error when I click on the ESS tab which says:
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'SAP_R3_SelfServiceGenerics' in the SLD. No such JCO destination is defined in the SLD.
    When I go to content Admin->Webdynpro ,the SLD service is stopped and the 'Maintain Jco's' tab is greyed out.
    This keeps on happening regularly.
    When I go to the SLD log it says 'Server certificate rejected by ChainVerfier' ,I wonder if we need to implement SSL when we have the turned LDAP on.
    Any help would be really appreciated
    Thanks

    Hi Subhash,
    I think u didnt configure your SLD properly.
    open this link
    Configuring SLD in Sneak Preview SAP NetWeaver '04 Sneak
    which gives the porcedure to configure SLD
    for JCO destinations
    http://help.sap.com/saphelp_nw04/helpdata/en/77/931440a1c32402e10000000a1550b0/frameset.htm
    Administration manual->server administration->Administration/Configuration of Web Dynpro Runtime Environment ->Web Dynpro Content Administrator
    rgds
    srinivas

  • SLD Error : No host name defined in Exchange profile sld.SID.host

    Hi,
    I am trying to do the configuration for the pre built examples (Airlines, Agency ) using XI after installation.
    But when I installed XI and did the post install configuration, I had mentioned 000 as Integration server and configured the same using the SLD (URL) in business system configuration.
    But when I was doing the configuration for the example, I wanted to configure the client 100 as integration server on SLD (under business systems) , so I deleted the old business system pointing to client 000 (as it is defined as integration server) and now I am trying to add a new business system (client 100) on SLD and it is giving me an error saying that the integration server already defined.
    On the SLD error log it also shows tat No Host name defined in Exchange profile for sld.SID.host...
    Are the above two errors related and how do I add the client 100 as a business system on SLD and have it as my Integration server.....
    Please help..
    Thanks,
    Madhu

    Moorthy,
    Thanks for the reply...but all the checks were successful when I did the configuration in 000 and before I deleted the business system for client 000 in SLD...(See my post and problem above..)....I messed with my SLD and removed the business system for client 000 (which is configured as the integration server) and now when I try to add a new business system for client 100 (as integration server>..) I am not able to do as it gives me a error saying integration server already exists even though I deleted it from SLD Business system..
    Thanks,
    Madhu

  • System config network error while parsing /etc/hosts

    I am configuring RAC on Oracle Linux,i have configured /etc/hosts on both nodes,when ever i opened network, its displaying error message.
    system config network error while parsing /etc/hosts
    wrong ip on line 25
    wrong ip on line 26
    wrong ip on line 27
    here is my host entries.
    node1
    ====
    [root@racnode1 ~]# cat /etc/hosts
    # Do not remove the following line, or various programs
    # that require network functionality will fail.
    127.0.0.1 localhost.localdomain localhost
    #::1 localhost6.localdomain6 localhost
    #####Public#####
    192.168.1.101 racnode1.reg.com racnode1
    192.168.1.102 racnode2.reg.com racnode2
    192.168.1.103 racnode3.reg.com racnode3
    192.168.1.104 racnode4.reg.com racnode4
    ####Private######
    10.10.1.1 racnode1-priv.reg.com racnode1-priv
    10.10.1.2 racnode2-priv.reg.com racnode2-priv
    10.10.1.3 racnode3-priv.reg.com racnode3-priv
    10.10.1.4 racnode4-priv.reg.com racnode4-priv
    #####Virtual#####
    192.168.1.201 racnode1-vip.reg.com racnode1-vip
    192.168.1.202 racnode2-vip.reg.com racnode2-vip
    192.168.1.203 racnode3-vip.reg.com racnode3-vip
    192.168.1.204 racnode4-vip.reg.com racnode4-vip
    #SCAN
    #192.168.1.301 racdb-scan.reg.com racdb-scan
    #SCAN
    192.168.1.301 racnode1-scan.reg.com racnode1-scan
    192.168.1.302 racnode2-scan.reg.com racnode2-scan
    192.168.1.303 racnode3-scan.reg.com racnode3-scan
    [root@racnode1 ~]# hostname
    racnode1.reg.com
    [root@racnode1 ~]#
    node2 host entries
    ===========
    [root@racnode2 ~]# cat /etc/hosts
    # Do not remove the following line, or various programs
    # that require network functionality will fail.
    127.0.0.1 localhost.localdomain localhost
    #::1 localhost6.localdomain6 localhost
    #####Public#####
    192.168.1.101 racnode1.reg.com racnode1
    192.168.1.102 racnode2.reg.com racnode2
    192.168.1.103 racnode3.reg.com racnode3
    192.168.1.104 racnode4.reg.com racnode4
    ####Private######
    10.10.1.1 racnode1-priv.reg.com racnode1-priv
    10.10.1.2 racnode2-priv.reg.com racnode2-priv
    10.10.1.3 racnode3-priv.reg.com racnode3-priv
    10.10.1.4 racnode4-priv.reg.com racnode4-priv
    #####Virtual#####
    192.168.1.201 racnode1-vip.reg.com racnode1-vip
    192.168.1.202 racnode2-vip.reg.com racnode2-vip
    192.168.1.203 racnode3-vip.reg.com racnode3-vip
    192.168.1.204 racnode4-vip.reg.com racnode4-vip
    #SCAN
    #192.168.1.301 racdb-scan.reg.com racdb-scan
    #SCAN
    192.168.1.301 racnode1-scan.reg.com racnode1-scan
    192.168.1.302 racnode2-scan.reg.com racnode2-scan
    192.168.1.303 racnode3-scan.reg.com racnode3-scan
    [root@racnode2 ~]#
    i am not able to ping racnode1-priv or racnode2-priv.
    from node1:
    ========
    [root@racnode1 ~]# ping racnode2-priv
    PING racnode2-priv.reg.com (10.10.1.2) 56(84) bytes of data.
    From racnode1-priv.reg.com (10.10.1.1) icmp_seq=2 Destination Host Unreachable
    From racnode1-priv.reg.com (10.10.1.1) icmp_seq=3 Destination Host Unreachable
    From racnode1-priv.reg.com (10.10.1.1) icmp_seq=4 Destination Host Unreachable
    5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4002ms
    , pipe 3
    [root@racnode1 ~]#
    from node2:
    =======
    [root@racnode2 ~]# ping racnode1-priv
    PING racnode1-priv.reg.com (10.10.1.1) 56(84) bytes of data.
    From racnode2-priv.reg.com (10.10.1.2) icmp_seq=2 Destination Host Unreachable
    From racnode2-priv.reg.com (10.10.1.2) icmp_seq=3 Destination Host Unreachable
    From racnode2-priv.reg.com (10.10.1.2) icmp_seq=4 Destination Host Unreachable
    --- racnode1-priv.reg.com ping statistics ---
    4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2999ms
    , pipe 3
    [root@racnode2 ~]#
    any idea where configuration went wrong.
    Thanks

    here is output, i can see lot of additional characters.
    [root@racnode1 ~]# cat -vet /etc/hosts
    # Do not remove the following line, or various programs$
    # that require network functionality will fail.$
    127.0.0.1 localhost.localdomain localhost$
    #::1^I^Ilocalhost6.localdomain6 localhost$
    $
    #####Public#####$
    192.168.1.101 racnode1.reg.com racnode1$
    192.168.1.102 racnode2.reg.com racnode2$
    192.168.1.103 racnode3.reg.com racnode3$
    192.168.1.104 racnode4.reg.com racnode4$
    ####Private######$
    10.10.1.1 racnode1-priv.reg.com racnode1-priv$
    10.10.1.2 racnode2-priv.reg.com racnode2-priv$
    10.10.1.3 racnode3-priv.reg.com racnode3-priv$
    10.10.1.4 racnode4-priv.reg.com racnode4-priv$
    #####Virtual#####$
    192.168.1.201 racnode1-vip.reg.com racnode1-vip$
    192.168.1.202 racnode2-vip.reg.com racnode2-vip$
    192.168.1.203 racnode3-vip.reg.com racnode3-vip$
    192.168.1.204 racnode4-vip.reg.com racnode4-vip$
    #SCAN$
    #192.168.1.301 racdb-scan.reg.com racdb-scan$
    #SCAN$
    192.168.1.301^Iracnode1-scan.reg.com^Iracnode1-scan$
    192.168.1.302^Iracnode2-scan.reg.com^Iracnode2-scan$
    192.168.1.303^Iracnode3-scan.reg.com^Iracnode3-scan$
    [root@racnode1 ~]#
    from node2:
    ========
    [root@racnode2 ~]# cat -vet /etc/hosts
    # Do not remove the following line, or various programs$
    # that require network functionality will fail.$
    127.0.0.1 localhost.localdomain localhost$
    #::1^I^Ilocalhost6.localdomain6 localhost$
    $
    #####Public#####$
    192.168.1.101 racnode1.reg.com racnode1$
    192.168.1.102 racnode2.reg.com racnode2$
    192.168.1.103 racnode3.reg.com racnode3$
    192.168.1.104 racnode4.reg.com racnode4$
    ####Private######$
    10.10.1.1 racnode1-priv.reg.com racnode1-priv$
    10.10.1.2 racnode2-priv.reg.com racnode2-priv$
    10.10.1.3 racnode3-priv.reg.com racnode3-priv$
    10.10.1.4 racnode4-priv.reg.com racnode4-priv$
    #####Virtual#####$
    192.168.1.201 racnode1-vip.reg.com racnode1-vip$
    192.168.1.202 racnode2-vip.reg.com racnode2-vip$
    192.168.1.203 racnode3-vip.reg.com racnode3-vip$
    192.168.1.204 racnode4-vip.reg.com racnode4-vip$
    #SCAN$
    #192.168.1.301 racdb-scan.reg.com racdb-scan$
    #SCAN$
    $
    192.168.1.301^Iracnode1-scan.reg.com^Iracnode1-scan$
    192.168.1.302^Iracnode2-scan.reg.com^Iracnode2-scan$
    192.168.1.303^Iracnode3-scan.reg.com^Iracnode3-scan$
    Edited by: Endeca on Apr 7, 2013 10:13 AM

  • "Unable to open config file" Error when starting tomcat

    hi all,
    Here is the output from two of the log files when I start tomcat4 on my linux box. I have configured the mod_jk on the tomcat side.
    From the output of the second log file, it seems that the ajp13 worker I defined was started successfully. What I don't understand is the following:
    1) In catalina.out, where des the line 'Unable to open config file' come from? Which config file?
    2) Tomcat4 is supposed to generate a mod_jk.conf automatically, but I don't see any file generated in 'conf/auto/'.
    Content of 'catalina.out'
    Unable to open config file
    Starting service Tomcat-Standalone
    Apache Tomcat/4.0.4
    Unable to open config file
    Starting service Tomcat-Apache
    Apache Tomcat/4.0.4content of 'catalina_log.2002-08-16.txt'
    2002-08-16 01:05:22 HttpConnector Opening server socket on all host IP addresses
    2002-08-16 01:05:28 Ajp13Connector[8009] Opening server socket on all host IP addresses
    2002-08-16 01:05:28 Ajp13Connector[8009] Starting background thread
    2002-08-16 01:05:29 Ajp13Processor[8009][0] Starting background thread
    2002-08-16 01:05:29 Ajp13Processor[8009][1] Starting background thread
    2002-08-16 01:05:29 Ajp13Processor[8009][2] Starting background thread
    2002-08-16 01:05:29 Ajp13Processor[8009][3] Starting background thread
    2002-08-16 01:05:29 Ajp13Processor[8009][4] Starting background thread

    I have all those files too.
    I think the 'config file' mentioned in the error log is the mod_jk.conf.
    On Jason Hunter's tomcat4 guide, it says don't use the tomcat4 RPM to installed. What is the difference bettween the RPM version and the tar.gz version? The only difference I can think of is that in the RPM version, the conf directory is in the 'etc/tomcat4/conf'. Could it be the reason that tomcat4 cannot read the config file? But it has no problem reading the server.xml though.

  • SLD error - Please see my problem letter by letter.

    HI Masters,
    before see this error , first of all read my doubt line by line. then only You can understand.
    I have three doubts.
    first one is :
    when i am login to http://hostname:portno/sld browser , it showing error message in red color. Please check it .
    1) You do not have permission to view to SLD. Min required : UME role with permission com.sap.lcr.lcruser and j2ee role lcruser.see the sld post-installtion guide for details.
    2) SLD not configured. Configure SLD in Adminsitration First.
    It showing these above  two error messages.
    in go.bat file  after click on cim client test , i click on trigger sld data transfer, it showing error message.
    OPERATION FAILED ! FAILED TO COLLECT DATA . THERE IS NO PROCESS TO READ DATA  WRITTEN TO A PIPE..
    perform standard user group  to role assignment also failed.
    Second one is :
    I log in to go.bat file and gave correct host name , port no, userid- SLDDSUSER and password in area of cim client test and http settings tab:
    after then when i click on CIM CLIENT test . The test conection is failed.
    But with j2ee_admin user id in http setting tab and cim client test tab , then click on cim client test.
    the test is succeed.
    my doubt is generally by using user id - slddsuser in cimclient test and http settings tabs , even then also cim client test will succeed. but in my case with only j2ee_admin user id, only then cim client test is succeed.
    why it's happend with only j2ee_admin user only cim client test is succeed. why this one not succeed with SLDDSUSER.
    , i click on trigger sld data transfer, it showing error message.
    OPERATION FAILED ! FAILED TO COLLECT DATA . THERE IS NO PROCESS TO READ DATA  WRITTEN TO A PIPE..
    perform standard user group  to role assignment also failed.
    THIRD DOUBT IS :
    I am not finding the roles and users related to SLD and NWDI.
    Please give reply . reply will highly appreciated .
    Edited by: sujana mullapudi on Nov 4, 2009 1:21 PM

    Hi
    Please check documentation at System Landscape Directory (SLD) in particular the SLD Post Installation Guide
    chapter "Configuring SLD Security Roles"
    The SLD users may not be delivered with default authorizations - customers have to select the appropriate or as required roles
    Best regards
    Stuart

  • LaserJet P1102w: HTML Config page errors out

    I was using my LaserJet P1102w via wireless fine, until my wireless router died. When I replaced it, I tried to set up the printer on the new network but I get an error when I try to open the "HTML Config ..." utility. The page itself won't load.
    I've printed the config page on the printer, and it says it has an IP address, but it still thinks it's connected to the old network. Is there a way to reset the printer itself?

    Hi,
    Be sure to restore the Wireless Radio firs by turning the printer on while holding both the Wireless and Cancel buttons.. keep the buttons pressed till the lights between them start blinking.
    Next try usin HTML Config again and check for any difference.
    If the same persists, try clearing the browser history by clicking on Safari > Reset Safari.
    Be sure to remove any existing caches and cookies.
    Quit Safari to ensure it takes effect, then try alunching HTML Config once again.
    Hope that helps,
    Shlomi
    Say thanks by clicking the Kudos thumb up in the post.
    If my post resolve your problem please mark it as an Accepted Solution

  • How to Config Special Error Page for TIME OUT ONLY

    We can config our own error page for webdynpro applications by using
    transaction code SICF. thus the customizing error page will show when
    program meet some errors. these errors type include ABAP runtime
    dump/page time out etc.
    Here is my question, is there any configuration or enhancement can
    effect on ONLY ONE error type.which means the customizing error page
    shows only time out error occurred.for other errors show the standard
    error page.
    Thanks a lot for your help.

    I need to setup a situation, that is display a custom error page which say "under maintenance" if no back-end WebLogic Server instance reached.In the Apache HTTP Server v2.2 you can use the ErrorDocument directive: http://httpd.apache.org/docs/2.0/mod/core.html#errordocument
    For example in httpd.conf,
    ErrorDocument 503 /Test.html
    Test.html is placed in the DocumentRoot (http://httpd.apache.org/docs/2.0/mod/core.html#documentroot)
    Regards
    Fabian

  • SLD Error exporting technical system

    Hi,
    While trying to transport our first XI scenario for go-live, we have a error while trying to export a third-party technical system.
    The idea is to import the third party development technical/business system in the production SLD as well to setup a transport target for third party production technical/business system that was created directly in the production sld.
    We I click export, I do get a page with a link but this link does nothing and there is line with a red exclamation mark.
    The sld log shows
    #14599166 09/12/2006 14:25:03.402 [SAPEngine_Application_Thread[impl:3]_56] ERROR com.sap.sld.wd.technicalsystem.ExportView: null
    Thrown:
    java.lang.UnsupportedOperationException
    at java.util.AbstractCollection.add(AbstractCollection.java:216)
    at java.util.AbstractCollection.addAll(AbstractCollection.java:319)
    at com.sap.lcr.webui.admin.ImportExportControl.addAssociatorAndReferenceNames(ImportExportControl.java:1244)
    at com.sap.sld.wd.technicalsystem.ExportView.getBCSystemExportList(ExportView.java:285)
    at com.sap.sld.wd.technicalsystem.ExportView.getExport(ExportView.java:193)
    at com.sap.sld.wd.technicalsystem.wdp.InternalExportView.getExport(InternalExportView.java:137)
    at com.sap.sld.wd.technicalsystem.wdp.IPrivateExportView$IContextElement.wdGetObject(IPrivateExportView.java:208)
    at com.sap.tc.webdynpro.progmodel.context.AttributePointer.getObject(AttributePointer.java:158)
    at com.sap.tc.webdynpro.clientserver.data.DataContainer.getAndFormat(DataContainer.java:1092)
    at com.sap.tc.webdynpro.clientserver.data.DataContainer.getAndFormat(DataContainer.java:1064)
    at com.sap.tc.webdynpro.clientserver.uielib.standard.impl.FileDownload._getData(FileDownload.java:81)
    at com.sap.tc.webdynpro.clientserver.uielib.standard.uradapter.FileDownloadAdapter.getReference(FileDownloadAdapter.java:291)
    at com.sap.tc.ur.renderer.ie6.LinkRenderer.render(LinkRenderer.java:51)
    at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:435)
    This sounds like a sap problem
    Any suggestion for a workaround ?
    regards
    Dirk

    Hi ...
    at first U create a technical system in the development system..and that technical system belongs to development system....
    and after u tranport this stuff to the production system...the technical system differs...i.e.u should change the technical system according to ur production system....
    Cheers,
    Raghavesh

  • Portal "Start SLD"  error

    Dear Gurus,
    System : NW 7.31 EHP1
    I configured SLD in portal, as screen shot maintained below all neccesary RFC status is "Not Defined".
    By the way sld is running and configured
    When i "Check SLD Connection" Test connection is sucessfully, but seems port -1 and URL is strange(as screen shot) . i dont know it is true or not.
    When i "Start SLD" i am taking error like this
    What is wrong with that guys ?
    Regards

    The second screen shot you have attached should have the host name, URL.
    To properly configure this service, the following must be done. Use the Destinations Service to: 
    1. Set up the registration by creating a destination called "SLD_DataSupplier" of type HTTP. Enter the following configuration settings. (Note: The specified user must have the user role "SAP_SLD_DATA_SUPPLIER" or higher on the target SLD Server.)
    - Appropriate URL (http://<host>:<port>)
    - Authentication should be set to BASIC
    - Appropriate User Name and Password
    2. Set up the AS Java access to the SLD by creating a destination called "SLD_Client" of type HTTP. Enter the same configuration settings as in the SLD_DataSupplier destination. (Note: The specified user must have user role "SAP_SLD_GUEST" or higher. Aditional write access permissions may be required by certain applications. Refer to the corresponding application documentation for SLD access requirements.)

Maybe you are looking for

  • Hard drive not exist

    Took me ages to get this far on the site, too many loops holes to back where you started! Just strange why it gives you an option to email HP but you can't :/ Anyway... I clumsilly dropped a book on the trackpad of my HP Pavilion dv6-3123sa the hard

  • How to setup my BIOS to boot my PC from any key on keyboard

    Can somebody tell me how and what to setup in BIOS (Neo2-FX with bios 1.b) to boot my PC from any key on keyboard? Only thing that I see in this bios is option "S3 wake up by PS2/Keyboard" but this didn't help me.

  • How to test SQL query performance - realiably?

    I have certain queries and I want to test which one is faster, and how big is the difference. How can I do this reliably? The problem is, when I execute the queries, Oracle does it's caching and execution planning and whatnot, and results of the quer

  • Empty Events

    Man, this is the crappiest upgrade Apple has ever put out. I've solved a lot of issues by rebuilding the library, fixing permissions, etc. Importing photos is still flakey, and I've had to rebuild the library many times just to get newly imported pho

  • Slideshow - does not run! What have I done wrong?

    It's stuck on the first image, does not run to the next. Can't remember that I done any changes. What have I done wrong?