cancel
Showing results for 
Search instead for 
Did you mean: 

connection error.

Former Member
0 Kudos

Hi,

I have an error when I click into one of our reports. The error message is shown below. I checked the RFC and users, all is working fine.

Please help.

====================================

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.1; SV1; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 2.0.50727), 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.4012.00.0000.20050509073444.0000 (release=630_VAL_REL, buildtime=2005-05-09:20:05:04[UTC], changelist=346209, host=PWDFM026)

Web Dynpro code generators of DC local/Hazard_Reporting:

SapDictionaryGenerationCore: 6.4012.00.0000.20050331142541.0000 (release=630_VAL_REL, buildtime=2005-05-22:19:57:15[UTC], changelist=339145, host=PWDFM026.wdf.sap.corp)

SapMetamodelWebDynpro: 6.4012.00.0000.20050121170001.0000 (release=630_VAL_REL, buildtime=2005-05-22:20:01:08[UTC], changelist=322883, host=PWDFM026.wdf.sap.corp)

SapMetamodelCore: 6.4012.00.0000.20050414173816.0000 (release=630_VAL_REL, buildtime=2005-05-22:19:49:19[UTC], changelist=342170, host=PWDFM026.wdf.sap.corp)

SapWebDynproGenerationTemplates: 6.4012.00.0000.20050509073444.0000 (release=630_VAL_REL, buildtime=2005-05-22:20:16:09[UTC], changelist=346209, host=PWDFM026)

SapWebDynproGenerationCTemplates: 6.4012.00.0000.20050509073444.0000 (release=630_VAL_REL, buildtime=2005-05-22:20:16:09[UTC], changelist=346209, host=PWDFM026)

SapGenerationFrameworkCore: 6.4012.00.0000.20041104141254.0000 (release=630_VAL_REL, buildtime=2005-05-22:19:48:34[UTC], changelist=298452, host=PWDFM026.wdf.sap.corp)

SapIdeWebDynproCheckLayer: 6.4012.00.0000.20050407155601.0000 (release=630_VAL_REL, buildtime=2005-05-22:20:04:47[UTC], changelist=340806, host=PWDFM026.wdf.sap.corp)

SapMetamodelDictionary: 6.4012.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2005-05-22:19:54:11[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)

SapMetamodelCommon: 6.4012.00.0000.20050414173816.0000 (release=630_VAL_REL, buildtime=2005-05-22:19:49:27[UTC], changelist=342170, host=PWDFM026.wdf.sap.corp)

SapWebDynproGenerationCore: 6.4012.00.0000.20050407155601.0000 (release=630_VAL_REL, buildtime=2005-05-22:20:05:16[UTC], changelist=340806, host=PWDFM026.wdf.sap.corp)

SapDictionaryGenerationTemplates: (unknown)

Web Dynpro code generators of DC sap.com/tcwddispwda:

No information available

Web Dynpro code generators of DC sap.com/tcwdcorecomp:

No information available

J2EE Engine:

6.40 patchlevel 92160.313

Java VM:

Java HotSpot(TM) Server VM, version: 1.4.2_07-b05, vendor: Sun Microsystems Inc.

Operating system:

Windows 2003, version: 5.2, architecture: x86

-


Error stacktrace:

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create delegate for component com.infosys.hazard.Hazard_Reporting_Component. (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.DelegatingComponent.<init>(DelegatingComponent.java:38)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doInit(ClientComponent.java:775)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:329)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:351)

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.reflect.InvocationTargetException

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

at java.lang.reflect.Constructor.newInstance(Constructor.java:274)

at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:74)

... 26 more

Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Unable to create connection for RFC Metadata Repository EHS_Metadata

at com.sap.tc.webdynpro.modelimpl.dynamicrfc.RFCMetadataRepository.getSingleton(RFCMetadataRepository.java:177)

at com.infosys.model.person.Zfm_Persongroups_Input.<init>(Zfm_Persongroups_Input.java:51)

at com.infosys.hazard.Hazard_Reporting_Component.<init>(Hazard_Reporting_Component.java:950)

at com.infosys.hazard.wdp.InternalHazard_Reporting_Component.<init>(InternalHazard_Reporting_Component.java:554)

... 31 more

Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed

Connect_PM TYPE=B MSHOST=s11i001e GROUP=PUBLIC R3NAME=AIE MSSERV=sapmsAIE PCS=1

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR partner not reached (host 127.0.0.1, service 3300)

TIME Tue Nov 20 11:59:44 2007

RELEASE 640

COMPONENT NI (network interface)

VERSION 37

RC -10

MODULE nixxi_r.cpp

LINE 8605

DETAIL NiPConnect2

SYSTEM CALL SiPeekPendConn

ERRNO 10061

ERRNO TEXT WSAECONNREFUSED: Connection refused

COUNTER 1

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:417)

at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:832)

at com.sap.mw.jco.JCO$Client.connect(JCO.java:3006)

at com.sap.mw.jco.JCO$Pool.initPool(JCO.java:4466)

at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:5844)

at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:5799)

at com.sap.mw.jco.JCO.getClient(JCO.java:8076)

at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.getClient(AbstractJCOClientConnection.java:393)

at com.sap.tc.webdynpro.modelimpl.dynamicrfc.RFCMetadataRepository.getSingleton(RFCMetadataRepository.java:172)

... 34 more

====================================

thanks,

kbas

Accepted Solutions (1)

Accepted Solutions (1)

raja_thangamani
Active Contributor
0 Kudos

Did you notice the error stack which has the below hint:

<i>Is the corresponding DC deployed correctly? Does the DC contain the component?</i>

Check out...

Raja T

Former Member
0 Kudos

Hi Raja,

Thanks for your reply. Im sorry im not familiar with Portal. What does it mean?

thanks,

kbas

Former Member
0 Kudos

Hi,

Redeploy the following component to the engine

"com.infosys.hazard.Hazard_Reporting_Component"

Check your JCO too as their some connection issues too...

Regards

Ayyapparaj

Answers (1)

Answers (1)

Former Member
0 Kudos

Thanks for your reply guys. I restarted the ECC server and now everything is working fine.

Will still award points for your effort.

KBas