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

Similar Messages

  • MDT 2012 - Failed to Run Action: Install Operating System Access is Denied (Error: 0000005; Source: Windows)

    Unable to deploy any image with WIM file. Vanilla or Custom Image gives the following error:
    ZTI Error – Unhandled error returned by LTIApply: invalid procedure call or argument (5)
    Litetouch deployment failed, Return code = -2147467259 0x80004005
    Failed to run action: Install Operating System.
    Access is denied (Error: 00000005; Source: Windows)
    Tried Giving Everyone Full rights to the deployment share
    Rebooted Server
    Updated Deployment Share
    Any ideas would be great!
    Thanks
    Rick
    Richard Ray

    https://skydrive.live.com/redir?resid=57E5397C8C507949!129&authkey=!AJDCfz7nGblrdQE&ithint=folder%2c.log
    Please try this link.
    Kris Da San Martino
    The SMSTS.log shows
    Expand a string: WinPEandFullOS TSManager 2/18/2014 1:35:48 PM 1508 (0x05E4)
    Executing command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf" TSManager 2/18/2014 1:35:48 PM 1508 (0x05E4)
    Process completed with exit code 5 TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    !--------------------------------------------------------------------------------------------! TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Failed to run the action: Install Operating System.
    Access is denied. (Error: 00000005; Source: Windows) TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Sending status message . . . TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Set a global environment variable _SMSTSLastActionRetCode=5 TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Clear local default environment TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Let the parent group (Install) decides whether to continue execution TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    The execution of the group (Install) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows) TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Failed to run the last action: Install Operating System. Execution of task sequence failed.
    Access is denied. (Error: 00000005; Source: Windows) TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Sending status message . . . TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,767) TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Task Sequence Engine failed! Code: enExecutionFail TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    **************************************************************************** TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Task sequence execution failed with error code 80004005 TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)

  • JInitiator 1.3 Fatal Error  Attachment to a running Virtual Machine failed

    We are running forms 9i from 9ias R2. We have an outside client trying to access the application from a machine with Windows XP. They receive the following errror after downloading the Jinitiator 1.3.1.9: JInitiator 1.3 Fatal Error - Attachment to a running Virtual Machine failed. As we are using Windows 2000, we have not come across this before and I find nothing on Metalink.
    Has anyone else had this problem? If so, do you have a solution?

    Hi,
    whatever browser you are running, during installation of the Browser (Netscape 7.x) or IE (postinstall) you decided to make teh Java Plugin 1.4 your default JVM. This means the VM is started when JInitiator loads which then leads to this collision. Disable Java Plugin as a default VM and it shoudl work fine.
    Frank

  • HT5945 Java has updated again today, i use a jave plug in to run my virtual software to access my work from home, today i have an error message saying security will not allow access to my website that i use to log in to work from, this is a JREdetection e

    Java has updated again today,
    i use a java plug in to run my virtual software to access my work from home,
    today i have an error message saying that security will not allow access to my website
    i use to log in to work from, this is a JREdetection error,
    my system runs off java and citrix, i tried chrome,firefox and safari - same issue, if my system cannot detect java it wont run, it runs on plug ins.
    How to i change my sec settings to allow access to this website, as i can only see that i can add apps not web addresses?

    If you get an error that says can't backup, try moving the existing backup file to a safe location and thry again. again. You can find the location of the backup file here:
    iPhone and iPod touch: About backups

  • VLAN RUNNING Config fetch Failed

    Hi;
    I have running Ciscowork LSM 3.2 with RME Ver 4.3 and Running SNMP V3 on all device. Out of 134 device 12-13 shows me Vlan running Config fetch failed. Please also find the dcmaservice.log in attachment.
    I already verify the Crediential number or times, I can access the devices from SSH and Telnet, on Cisco works RME shows Running and Startup Config success while VLAN Running Config fetch failed. and on some device it show following
    Protocol and Platforms passed = TELNET , RMEIOS
    trying for Telnet
    Failed to get CmdSvc from DeviceContext....
    Thanks,
    Best regards;
    Shoaib Ahmed

    HI Shoaib,
    Try  ssh\telnet into the device manually and issue the command copy flash:vlan.dat tftp: and
    enter the IP address of the LMS server? Does it work? If that works fine, try to increase
    the tftp timeout.
    This can be done under RME> Admin> System Preferences> RME Device Attributes.
    if it failed with an Error as below :
    %Error opening tftp: ............
    Then check if there any firewall in between these device and LMS blocking TFTP as TFTP is the only protocal
    that fetch the vlan.dat from the device.
    Thanks--
    Afroj

  • Fail to access SpecDictionary OneworldSpecDictionary

    Hi,
    I am getting an exception while trying to generate scehma in BizTalk for the JDE Enterprise Business Functions.
    E-JDE0010: JNI invocation method failed for the method GetMethodNames. JDEdwards error message : com.jdedwards.system.connector.dynamic.spec.SpecFailureException: Fail to access SpecDictionary OneworldSpecDictionary environment:JPY812:Fail to fetch ModuleInfo [INTERNAL_ERROR] Internal error.
    I have got the list of Business functions but this error comes up while generating schema for that.
    Thanks in advance.
    Regards,
    Faraz

    Hi
    impact for existing XI scenarios
    It will not affect your already configured and running scenario.
    To check SLD connection use transaction SLDCHECK, whether it works.
    If it doesn't work then check two RFC destination in transaction SM59 which are LCRSAPRFC and SAPSLDAPI, whether they are working fine.
    Also provide SLD access data in transaction SLDAPICUST.
    In transaction SXMB_ADM --> Integration engine configuration check whether entry for the coonected integration server is properly made.
    Regards
    Sami
    Reward points if helpful.

  • Operations Manager Failed to Access the Windows Event Log and management server is showing warning state

    Hi,
    I am monitoring AD server from SCOM 2012 R2. My management server goes into waning state. When i run Health explorer then it come back in the healthy state but after some time it again goes into warning state. After seeing alert i found that a alert is coming
    again and again i.e.  Operations Manager Failed to Access the Windows Event Log.The description of alert is mention below
    The Windows Event Log Provider is still unable to open the DhcpAdminEvents event log on computer 'nc2vws12ad5.corp.nathcorp.com'.
    The Provider has been unable to open the DhcpAdminEvents event log for 64080 seconds.
    Most recent error details: The RPC server is unavailable.
    Please suggest me how to resolve this so that my management server will again come back in healthy state.
    Thanks
    Abhishek

    Hi Abhishek,
    As i mentioned earlier the Alert resolution says the same points.
    Can you give details on the below ?
    Is there really a log named "Dhcpadminevents" in the MS's Event viewer ?
    Did you recently configure any new alert where you mentioned "Dhcpadminevents"
    as a event log location ?
    If yes then what is the target you selected for the rule / monitor there ?
    Can you post the results for analysis ?
    Gautam.75801

  • Distribution Manager Failed To Access The Source Directory

    Hello All,
    I have this issue distributing content to my Distribution Points for months now. I keep running into this error below:
    Distribution Manager Failed to Access the source directory (\\share\folder\file.wim)
    Possible Cause: Distribution Manager does not have sufficient rights to the source directory.
    Solution: Verify that the site server computer account has at least Read access to the directory you specify as the source directory.
    Possible Cause: There is not enough disk space available on the site server.
    Solution: Verify that there is enough free disk space available on the site server.
    I checked the distmgr.log file and received these messages: 
    GetTempFileNameA failed; 0x80004005    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)
    CFileLibrary::AddFile failed; 0x80004005    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)
    CContentDefinition::AddFile failed; 0x80004005    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)
    Failed to add the file. Please check if this file exists.    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)
    SnapshotPackage() failed. Error = 0x80004005    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)
    Failed to take snapshot of package CSU0006A    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)
    There is enough space on the site server and the site server has full control over the source directory. I wish I can give you more information but I'm hoping this is enough info to get some assistance. If more information is needed please let me know!

    We usually give the DP's computer account and the site server computer account read access to these shares in our environment.
    ... which is not enough for drivers and updates (as there will also files be added).
    Torsten Meringer | http://www.mssccmfaq.de
    ... And for capture Image too if your capture destination points on that share

  • SQL Developer fails to access update center via http proxy

    Hi,
    I've configured HTTP Proxy exactly like MS-IE. Anyway, sql developer fails to access web. This is the error message:
    java.io.IOException: Server returned HTTP response code: 407 for URL: http://htmldb.oracle.com/pls/otn/f?p=38606:2
         at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1149)
         at oracle.ideimpl.webupdate.CheckMasterListRunnable.run(CheckMasterListRunnable.java:131)
         at java.lang.Thread.run(Thread.java:595)
    Using the same URL in IE gives the following result:
    <?xml version="1.0" encoding="UTF-8" ?>
    - <centers xmlns="http://xmlns.oracle.com/jdeveloper/update/master">
    - <center id="oracle.sqldeveloper.webupdate.internal">
    <url>http://htmldb.oracle.com/pls/otn/f?p=raptor:internal</url>
    <name>Internal Update Cetner</name>
    <domain>.*\.us.oracle.com</domain>
    </center>
    - <center id="oracle.sqldeveloper.webupdate.otncenter">
    <url>http://htmldb.oracle.com/pls/otn/f?p=raptor:center</url>
    <name>Official Oracle Extensions</name>
    </center>
    </centers>
    What's wrong?
    I'm using sql developer 1.0.0.14.22.
    Martin

    Given that the update centre worked for me with proxy authentication in v1422 (and Production v1467 - I would recommend that you upgrade to this with a full download if you can't sort out your proxy issues), I would assume that it is not a SQL Developer bug.
    Are you still getting HTTP 407 errors when you have entered your username and password?
    Unfortunately, I don't know what username/password expectations a RADIUS based proxy authentication would expect. The only thing I can suggest to try is to explicitly put your username/password in your MS-IE proxy setup and see if you can still access the http://htmldb.oracle.com/pls/otn/f?p=38606:2 URL through IE. If this fails through IE, the username/password that you are supplying are not what the proxy is expecting.

  • SLDCHECK fails in XI - SLD running on Solman server

    Dear All,
    I have SLD configured on my solution manager system. All systems including XI are updating data in SLD -> Technical Systems.
    My problem
    When I execute SXMB_IFR, SLD web page opens up fine. But in transaction log I see following:
    Calling function LCR_LIST_BUSINESS_SYSTEMS
    Retrieving data from the SLD server...
    Function call returned exception code 4
    => Check whether the SLD is running!
    Also, when I try to execute Runtime Workbench, is throws following errors:
    5 Message(s) : SLD agent unable to specify domain - Error class com.sap.aii.rwb.exceptions.BuildLandscapeException: Error during communication with System Landscape Directory: User credentials are invalid or user is denied access - Attempt to create JCo connection object failed for domain domain.00.zonexid - Integration Server unable to specify a JCo client - No component names available from Integration Server -
    I have checked authorizations for all users, PIRWBUSER, PIAPPLUSER (used in SLDAPICUST) etc, but couldn't solve it.
    Post installation, I changed client setting for integration server after client copy and followed "Wizard-based basic configuration" for PI steps.
    Can anyone pls point out where I'm failing.
    regards, Sean

    Dear All,
    I'm finally able to access SLD from tools, but alas partially.
    I have new issues
    1) When I try to import s/w components through Integration Repository as PIREPUSER, it says not authorised. But, PISUPER can. I checked all default auth for PIREPUSER, both in XI and SLD server, passwords are same in SU01, Exchange profile yet nothing.
    2) In runtime workbench, I cannot go pass "Configuration". Message:
    Unable to read the current configuration for the selected XI domain because the system was unable to estable a connection to the monitoring server (possibly due to incorrect logon data). Error message: Unable to log on to system zonexid in language en with user PIRWBUSER
    When I can login using this user into RWB, how am I unable to proceed further??
    Any ideas??
    regards, Sean.
    P S: Our customer has not given us domain name to use, so we are performing local installations. Consequentially, I am not using any FQDN.

  • Portal failed to access remote resource due to network failures

    Hi,
    We have a portlet that allows users to upload files to a SQL Server database and make it available for other users to access. The portlet code is on our remote servers. Everything works fine in dev environment, but certain files fail in pre-prod and prod within the portal, but work fine when the code is executed outside the portal.
    I keep getting this error:
    Error - Portal failed to access remote resource due to network failures. Try again later or contact your portal administrator.     
    What could the problem be?
    Thank you for your help.
    Rad

    If the Studio service looks good on the remote server where Studio is installed (check that
    the service is started and look in the Studio logs for any warnings or errors), you should
    also verify the configuration settings in the Studio remote server object. Is it properly
    configured and pointing to the correct remote server?
    If so, check the portal servers access to the Studio server via the port specified in the remote
    server (default is 11935). You can test this by doing a telnet test on the portal server. In a cmd
    prompt (Windows) or on the CLI (Unix), type 'telnet [studioserver] 11935', where "<servername> is
    the name of your Studio remote server. The screen should just go blank, meaning that there is
    something accepting connections on that port on the given server. (We would hope it's the Studio
    app and not another service occupying that port.) If you get "Could not open connection to the host"
    or some such similar result, check that the network between the portal and the Studio remote server
    is open (ie, make sure there isn't any port blocking or a firewall in place that would hinder the
    communication between the two servers).

  • 3.0 Running in Circles - Can't access

    I've been using this new computer with all new install xp sp3 and AA3.0. This has worked for more than 6 months, no problems. I now have a UAD card installed and everything has worked. With this new system I haven't needed to lock any effects, no problems untill now. I'm working on a slightly bigger project and locked some effects and then the program stopped. The message I get is:
    Shutting down. To continue where you left off, you must restart Audition. And I select "OK" Now I get "Microsoft Visual C++ Runtime Library.  R6025 pure virtual function call" message. I can't get into Audition to undo what I've done.
    Some sessions are unreplaceable.
    I understand some kind of corrupted registry file or something like that.
    Any suggestions?
    Donnie

    My comp. guru fixed it in about 10 minutes. I had a bad file. It was deleated and automatically put back correctly. Works fine now.
    Date: Thu, 5 Aug 2010 15:55:10 -0600
    From: [email protected]
    To: [email protected]
    Subject: 3.0 Running in Circles - Can't access
    Hi Donnie,
    Do you recall the precise last steps you took before Audition stopped working?  Did it crash and start giving this error when you launched it again, or did this just occur at random after working fine the previous time?
    How far does the start-up process get before you receive this error?  Do you see the Audition splash screen?  Does it begin to show the UI before crashing?  Have you already installed the Audition 3.01 update patch?
    My first suggestion would be to wipe the application preferences and try launching it again.  To do this, rename the following "3.0" folder to "3.0.BAK" and then launch Audition
    XP: C:\Document and Settings\<your username>\Application Data\Adobe\Audition\3.0\
    Vista/Win7: C:\Users\<your username>\AppData\Roaming\Adobe\Audition\3.0\
    Renaming the folder instead of deleting it will retain your previous preferences and effects presets in case this is not the problem.
    >

  • Attachment to a running virtual machine failed

    I get the error message "Attachment to a running virtual machine failed" when trying to instantiate my active x bundled java bean.
    The steps I took to create it are:
    javac Person.java
    jar -cvfm PersonBean.jar person_manifest Person.class
    set JRE=D:\Applications\JavaSoft\JRE\1.3.1_01
    set classpath=%JRE%\lib\rt.jar;%JRE%\lib\jaws.jar
    java sun.beans.ole.Packager
    Then I answered the questions on the packager.
    When I try to create the bean from inside my application, I get an error dialog with the title "Java(TM) Plug-in 1.4 Fatal Error".
    When I try to create MSCal.Calendar in my application, all is well.
    Anyone know what is happening?

    If you run the packager, try not to register the
    newly created type library (*.TLB) immediately,
    but let the packager create the registry instructions
    (a *.REG file).
    Look at the *.REG file and check all references to
    virtual machines. Since you are using the packager
    from 1.3.1, probably the virtual machine (path for beans.ocx etc) points to the 1.3.1 JRE instead of the
    1.4 plugin.
    Make sure, all references to the virtual machine are
    linked correctly to 1.4 and reregister your TLB.
    Hope that helps and please let us know if you were
    successful, as this would indicate that indeed, beans
    packaged with the packager from 1.3.1 can run in the
    1.4 plugin. Sylvia

  • DTP runs endless and fails

    Hiii ,
    When I execute the DTP which loads data to ODS ,It runs endless and fails .
    I reactivated the ODS ,Retransported Still issue persists.
    Also i tried creating new DTP it also goes into endless and status remains Yellow and turns red after some time.
    Kindly help
    Regards.
    Akshay

    Hi Akshay,
    Please check in ST22 or SM21 for any errors raised by DTP failure. It might happen that it is due to partition max level reached.
    Please check free background processes in SM50 and data volume in DTP request. If possible change the DSO settings as Kodanda has suggested.
    Thanks
    Amit

  • Test Stand crashing when running ESS

    Test Stand is crashing when running ESS and one of the test fails.  I am able to run that same test alone and there are no issues.  I am seeing the following messege in the windows event log.
    Faulting application testexec.exe, version 13.0.0.0, stamp 4a9eca49, faulting module cvirte.dll, version 9.0.0.330, stamp 48dd23b1, debug? 0, fault address 0x000ac355.

    1) What is ESS?
    2) Are you calling a dll from TestStand? If so make sure the settings for passing parameters to the dll are exactly correct or it could cause memory corruption. If not, how exactly is teststand calling the test?
    -Doug

Maybe you are looking for