SAP ESS WDA CATS Not Working
Hi Experts:
I got this dump when running CATs from the portal (7.3) or testing in the WD configuration.
"Syntax error in program CL_XSS_CAT_1_APPLICATION_CORE=CP"
I have the profile name assigned to CVR and have the relevant role assigned to my user. The profile works when executed in CAT2. I did some customization in CAC2 (hiding most of the fields). but nothing seems to work. Consistenly got the same error. Is this configuration or authorization issue?
Here is the dump:
The following syntax error occurred in program
"CL_XSS_CAT_1_APPLICATION_CORE=CP " in include
"CL_XSS_CAT_1_APPLICATION_CORE=CM00K " in
line 96:
""L_DISP1" is not type-compatible with formal parameter "IM_TEXT1"."
and where it happens in the code:
15 DATA:
16 l_cats_core TYPE REF TO cl_xss_cat_1_application_core.
17
18 CLASS cl_xss_cat_application DEFINITION LOAD.
19
20 IF cl_xss_cat_application=>instance IS INITIAL.
>>>> CREATE OBJECT l_cats_core
22 EXPORTING
23 im_scenario = im_scenario
24 im_pernr = im_pernr.
Any help is appreciated.
Here is source code dumnp: the exception occurs with CREATE OBJECT l_cats_core
The following syntax error occurred in program
"CL_XSS_CAT_1_APPLICATION_CORE=CP " in include
"CL_XSS_CAT_1_APPLICATION_CORE=CM00K " in
line 96:
""L_DISP1" is not type-compatible with formal parameter "IM_TEXT1"."
DATA:
l_cats_core TYPE REF TO cl_xss_cat_1_application_core.
CLASS cl_xss_cat_application DEFINITION LOAD.
IF cl_xss_cat_application=>instance IS INITIAL.
CREATE OBJECT l_cats_core
EXPORTING
im_scenario = im_scenario
im_pernr = im_pernr.
ENDIF.
erzeuge und initialisiere die Applikation
CALL METHOD cl_xss_cat_application=>get_instance
EXPORTING
im_core = l_cats_core
RECEIVING
result = ex_application
EXCEPTIONS
pernr_not_enqueued = 1
profile_not_found = 2.
IF sy-subrc = 1.
RAISE pernr_not_enqueued.
ELSEIF sy-subrc = 2.
RAISE profile_not_found.
ENDIF.
Similar Messages
-
CTI - SAP CRM & SAP BCM: ANI does not work in SAP standard
Hello Experts,
our customer wants to work with a CTI in SAP CRM WebUI Role (Non IC; CEBP).
For the CTI the SAP CRM 7.0 (on HANA) and SAP BCM where itegrated.
We are using the Slim Communication Toolbar as recommended by SAP.
The Problem ist that the ANI (Automatic Number Identification) does not work.
The Callers Number is not identified. Function Module BUPA_SEARCH2 is not called.
No Changes were made in this area. We are completely using the SAP standard.
Has anybody experienced issues related to this one?
It would be great if somebody could give me some help and/or information!
Thank you!
Kind Regards
Martin GaschkHello Andrei,
the issue was solved by SAP.
The relevant startup component for ANI in the CMS integration profile (Tx CRM_IC_FW_PROF) was inactive:
Component:
BUSINESS PARTNER IDENTIFICATION
Class:
CL_CRM_IC_FW_BP_SEARCH_SRV
Thanks for your support!
Kind regards
Martin -
SAP ESS/MSS CATS requirement Please Help
Hi SAP Gurus,
I am new to ESS/MSS , I have the following requirement from the client, please let me know how to start on this, appreciate if you could help me on how to start.
map and configure CA-TS business content including roles to be presented to users via ESS/MSS for time recording againist projects.
Points for help ful answers
JoHi Jo,
Try to checkout this post as we talk about CATS. We have some good links which can help you.
ESS/MSS CATS
Hope they help.
Ray -
SAP NetWeaver BW Connection not working for SBOP4.0
Hello Experts,
Following are the steps & current patches:
SBOP 4.0
Dashboard Design , version: 6.0.0.0
SAP Logon
Release : 720
Patch: 5
1. SAP BW & NetWeaver Portal are not SSO(Single Sign-on)
2. I open the Dashboard Designer
3. Click on "Manage Connection"
4. Select 'SAP NetWeaver BW Connection'
5. It pops-up the Log-on screen
6. Pass on the required information
7. Use the query browser & selected the query
8. it takes the query with no error message
Issue:
1. It is not showing the Input values & Output values
Not able to display the BW Bex Query element using Dashboard Designer - SAP NetWeaver BW Connection.
Please let me know if we are missing any config. or step.
Thanks
MahendraThanks Amit for your suggestions. I tried the below steps & still it is not working:
1. re-installed Adobe version 10.1
2. Tried to connect the BW Bex query using SAP NetWeaver BW connection.
3. I am getting no error but Dashboard designer is not able to display the Input values & Output values of the BW BEx query
As I had mentioned you earlier that when I open the Bex report using the designer using the IE, it calls the portal window & I have to enter the LDAP password then the report opens in the portal.
So I think as our BW & portal are not configured as SSO so when the Dashboard designer tried to load the query from the xml file it fails. It may be because it required my LDAP login credentials.
Please let me know your suggestions.
Thanks
Mahendra -
Additional Fields for ESS-Business Card Not Working for Certain Countries
Dear Experts,
We were trying to configure the additional fields to be displayed in Business Card - Overview Screen for all countries. We don't have problem configure and get the new fields display for Malaysia (Molga = 14) but having problem for the field to display for Hong Kong (Molga = 27) and Singapore (Molga - 25).
The strange thing is I am following the same steps as I configured for Malaysia. Somehow it is not working for Hong Kong and Singapore. As I understand, there is only 1 place to configure in SPRO for this requirement:
Personnel Management -> Employee Self-Service -> Service-Specific Settings -> Own Data -> Customizing of Personal Information Screens -> Determine Fields for Business Card on Overview Screen
Please help!Hi Siddhart,
Thank you for the information. We are currently in EhP3 with below Support Components installed.
Software Component: SAP_HR
Release: 600
Level: 60
Highest Support Package: SAPKE60060
Software Component: EA-HR
Release: 603
Level: 34
Highest Support Package: SAPK-60334INEAHR
The note 1159911 provided is within SAPK-60304INEAHR. Thus, I don't think this is the root cause of this inconsistency base on the Highest Support Package installed in our system.
Anymore hint? Anyone? Please... -
SAP FTP Binary Does not work after EHP 7 Upgrade
Hi All,
Since EHP 7, if I try to execute an external command through sm49, which has a shell script for ftp connection and fetching files, the 'binary' command after ftp connection is not working.
Result? I'm fetching corrupted files once in a while. The same was fine before the upgrade. The script runs fine at OS level. We are using AIX.
Did anyone see this issue before? Is there a solution?
Please help, it's quite urgent.
Thank you.
UdayHi Uday,
Since EHP 7, if I try to execute an external command through sm49, which has a shell script for ftp connection and fetching files, the 'binary' command after ftp connection is not working.
1) What is the exact error message you get ?
2) Did you check permission to the script . Ensure sidadm has full access to execute it.
3) Did you check Test Connection to TCP/IP RFC destinations SAPFTP and SAPFTPA are working fine in SM59 ?
Regards,
Deepak Kori -
SAP BeX WAD URL not working on Black Berry Emulator
Hi All,
I web report which is running successfully on Windows XP browsers. But when I am going to use same url for Black Berry emulator its not working for that. Can Some one please Help me on this?
I tried same url on Windows CE emulator also but was getting same error.
Regards,
Abhishek JainThe error that I was getting for above is "Something Didn't work quite right and we are unable to show the page you requested right now. Rest assured, Google Engineers are already springing into action to solve the problem."
Edited by: Abhi4SAP on Jan 12, 2010 8:06 AM -
MSS PCRs and ESS Adobe Forms not working
Hi Gurus,
Scenario: Portal system on a seperate box / Adobe system on a seperate box /R/3 on a seperate box . ADS is configured properly, From R/3 the forms are working fine all test programs are working great. But when I try to see thru the Portal MSS and ESS links then it gives me the following error. Please suggest what needs to be done. Points will be awarded..
500 Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
java.lang.Exception: Incorrect content-type found 'text/html'
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ClientMimeMessage.initDeserializationMode(ClientMimeMessage.java:120)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage(MimeHttpBinding.java:951)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1430)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:82)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:99)
... 52 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .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
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0008.20060517125535.0000 (release=645_VAL_REL, buildtime=2006-05-29:19:11:56[UTC], changelist=403424, host=pwdfm101), build date: Fri Oct 13 16:42:28 PDT 2006
J2EE Engine 7.00 patchlevel
Java VM Classic VM, version:1.4.2, vendor: IBM Corporation
Operating system AIX, version: 5.3, architecture: ppc64
Session & Other
Session Locale en_US
Time of Failure Tue Jan 30 11:01:46 PST 2007 (Java Time: 1170183706621)
Web Dynpro Code Generation Infos
sap.com/pb
SapDictionaryGenerationCore 7.0008.20060428175704.0000 (release=645_VAL_REL, buildtime=2006-06-10:14:30:12[UTC], changelist=400798, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0008.20060428175704.0000 (release=645_VAL_REL, buildtime=2006-06-10:14:30:21[UTC], changelist=400798, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0008.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-06-10:14:18:37[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0008.20060428190753.0000 (release=645_VAL_REL, buildtime=2006-06-10:14:35:47[UTC], changelist=400814, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0008.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-06-10:14:19:24[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0008.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-06-10:14:19:17[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0008.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-06-10:14:27:20[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0008.20060428190938.0000 (release=645_VAL_REL, buildtime=2006-06-10:14:32:41[UTC], changelist=400815, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0008.20060517125535.0000 (release=645_VAL_REL, buildtime=2006-06-10:14:52:10[UTC], changelist=403424, host=pwdfm101)
SapWebDynproGenerationCore 7.0008.20060428190753.0000 (release=645_VAL_REL, buildtime=2006-06-10:14:35:58[UTC], changelist=400814, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0008.20060517125535.0000 (release=645_VAL_REL, buildtime=2006-06-10:14:52:10[UTC], changelist=403424, host=pwdfm101)
sap.com/tcwddispwda
No information available null
sap.com/pb_api
SapDictionaryGenerationCore 7.0008.20060428175704.0000 (release=645_VAL_REL, buildtime=2006-06-10:14:30:12[UTC], changelist=400798, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0008.20060428175704.0000 (release=645_VAL_REL, buildtime=2006-06-10:14:30:21[UTC], changelist=400798, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0008.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-06-10:14:18:37[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0008.20060428190753.0000 (release=645_VAL_REL, buildtime=2006-06-10:14:35:47[UTC], changelist=400814, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0008.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-06-10:14:19:24[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0008.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-06-10:14:19:17[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0008.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-06-10:14:27:20[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0008.20060428190938.0000 (release=645_VAL_REL, buildtime=2006-06-10:14:32:41[UTC], changelist=400815, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0008.20060517125535.0000 (release=645_VAL_REL, buildtime=2006-06-10:14:52:10[UTC], changelist=403424, host=pwdfm101)
SapWebDynproGenerationCore 7.0008.20060428190753.0000 (release=645_VAL_REL, buildtime=2006-06-10:14:35:58[UTC], changelist=400814, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0008.20060517125535.0000 (release=645_VAL_REL, buildtime=2006-06-10:14:52:10[UTC], changelist=403424, host=pwdfm101)
sap.com/tcwdcorecomp
No information available null
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: Failed to UPDATEDATAINPDF
at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:371)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterApplicationModification(ClientApplication.java(Compiled Code))
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.afterApplicationModification(ClientComponent.java(Inlined Compiled Code))
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doRespond(WindowPhaseModel.java(Compiled Code))
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java(Compiled Code))
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java(Compiled Code))
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java(Compiled Code))
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java(Compiled Code))
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java(Compiled Code))
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java(Compiled Code))
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java(Compiled Code))
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java(Compiled Code))
at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java(Compiled Code))
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java(Compiled Code))
at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java(Compiled Code))
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java(Compiled Code))
at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java(Inlined Compiled Code))
at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java(Inlined Compiled Code))
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java(Inlined Compiled Code))
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java(Inlined Compiled Code))
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java(Compiled Code))
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java(Compiled Code))
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java(Compiled Code))
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java(Compiled Code))
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java(Compiled Code))
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java(Compiled Code))
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java(Compiled Code))
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java(Compiled Code))
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java(Inlined Compiled Code))
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java(Compiled Code))
at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java(Compiled Code))
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java(Compiled Code))
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Inlined Compiled Code))
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Compiled Code))
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java(Compiled Code))
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java(Compiled Code))
at com.sap.engine.services.httpserver.server.Client.handle(Client.java(Inlined Compiled Code))
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java(Compiled Code))
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java(Compiled Code))
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java(Compiled Code))
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code))
at java.security.AccessController.doPrivileged1(Native Method)
at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
Caused by: com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: PDFDocument Processor failed to process Render Request.
at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentProcessor.process(PDFDocumentProcessor.java:55)
at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentInteractiveFormHandlingContext.execute(PDFDocumentInteractiveFormHandlingContext.java:118)
at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:333)
... 46 more
Caused by: com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
java.lang.Exception: Incorrect content-type found text/html
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:366)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.render(PDFObject.java:3689)
at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRenderHandler.handle(PDFDocumentRenderHandler.java:154)
at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentProcessor.process(PDFDocumentProcessor.java:52)
... 48 more
Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
java.lang.Exception: Incorrect content-type found 'text/html'
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:89)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:99)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:359)
... 51 more
Caused by: java.lang.Exception: Incorrect content-type found 'text/html'
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ClientMimeMessage.initDeserializationMode(ClientMimeMessage.java:120)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage(MimeHttpBinding.java:951)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1430)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:82)
... 53 more
Regards,
Samar.Samar,
I am having the exact same problem. Can you please inform me on how you managed to resolve this issue?
Thanks,
Thomas -
SAP J2EE Engine : does not work !!!
Hi everyone,
I have installed SAP NW2004s Java SP9 Trial (on Windows XP and Sapdb as database). The installation finished without problems.
But when I start my SAP system, the SAP J2EE engine (process <b>jcontrol</b>) is still stopped
[... I have already searched in the forum, but I have not found a solution to my problem ...]
Here is the contents of files <b>dev_jcontrol</b> & <b>dev_sdm</b> :
File <b>dev_jcontrol</b> : *************************************
trc file: "D:\usr\sap\J2E\JC01\work\dev_jcontrol", trc level: 1, release: "700"
node name : jcontrol
pid : 1384
system name : J2E
system nr. : 01
started at : Mon Dec 03 15:23:56 2007
arguments :
arg[00] : D:\usr\sap\J2E\JC01\exe\jcontrol.EXE
arg[01] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_ahassaine
[Thr 2356] Mon Dec 03 15:23:56 2007
[Thr 2356] *** <b>ERROR => Can't open property file [D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties] [jstartxx.c 725]
[Thr 2356] *** ERROR => Can't open property file [D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties] </b>[jstartxx.c 1952]
[Thr 2356] *** ERROR => JStartupReadArgumentsEx: can't enumerate nodes [D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties;D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties] (rc = -1) [jstartxx.c 524]
File <b>dev_sdm</b> : *************************************
trc file: "D:\usr\sap\J2E\JC01\work\dev_sdm", trc level: 1, release: "700"
node name : sdm
pid : 1360
system name : J2E
system nr. : 01
started at : Fri Nov 30 10:38:29 2007
arguments :
arg[00] : D:\usr\sap\J2E\JC01\exe\jlaunch.exe
arg[01] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_ahassaine
arg[02] : -DSAPINFO=J2E_01_sdm
arg[03] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_ahassaine
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties]
-> ms host : ahassaine
-> ms port : 3900
-> OS libs : D:\usr\sap\J2E\JC01\exe
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
Instance properties
-> ms host : ahassaine
-> ms port : 3900
-> os libs : D:\usr\sap\J2E\JC01\exe
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
Worker nodes
-> [00] sdm : D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
[Thr 3544] Fri Nov 30 10:38:29 2007
[Thr 3544] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 3544] JLaunchRequestQueueInit: create pipe listener thread
[Thr 2240] JLaunchRequestFunc: Thread 2240 started as listener thread for np messages.
[Thr 3352] WaitSyncSemThread: Thread 3352 started as semaphore monitor thread.
[Thr 3544] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 3544] CPIC (version=700.2005.12.02)
[Thr 3544] INFO: Invalid property value [Debbugable=yes]
[Thr 3544] [Node: SDM] java home is set by profile parameter
Java Home: C:\Java\
[Thr 3544] <b>JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar</b>
JStartupIReadSection: read node properties [sdm]
-> node name : SDM
-> node type : sdm
-> node execute : yes
-> java path : C:\Java\
-> java parameters :
-> java vm version : 1.4.2_09-b05
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 512M
-> root path : D:\usr\sap\J2E\JC01\SDM\program
-> class path : D:\usr\sap\J2E\JC01\SDM\program\bin\SDM.jar
-> OS libs path : D:\usr\sap\J2E\JC01\exe
-> main class : SDMInternal
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
-> shutdown class : com.sap.sdm.jstartup.shutdown.InternalShutDown
-> parameters : server sdmhome=D:\usr\sap\J2E\JC01\SDM\program
-> debuggable : yes
-> debug mode : no
-> debug port : 50000
-> shutdown timeout : 120000
[Thr 3544] JLaunchISetDebugMode: set debug mode [no]
[Thr 2480] JLaunchIStartFunc: Thread 2480 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [SDM]
-> stack : 262144 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -Dsys.global.dir=D:\usr\sap\J2E\SYS\global
-> arg[ 4]: -Dapplication.home=D:\usr\sap\J2E\JC01\exe
-> arg[ 5]: -Djava.class.path=D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar;D:\usr\sap\J2E\JC01\SDM\program\bin\SDM.jar
-> arg[ 6]: -Djava.library.path=C:\Java
jre\bin\server;C:\Java
jre\bin;C:\Java
bin;D:\usr\sap\J2E\JC01\exe;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;D:\usr\sap\J2E\SYS\exe\uc\NTI386
-> arg[ 7]: -Dmemory.manager=512M
-> arg[ 8]: -Xmx512M
-> arg[ 9]: -DLoadBalanceRestricted=no
-> arg[ 10]: -Djstartup.mode=JCONTROL
-> arg[ 11]: -Djstartup.ownProcessId=1360
-> arg[ 12]: -Djstartup.ownHardwareId=G1610100576
-> arg[ 13]: -Djstartup.whoami=sdm
-> arg[ 14]: -Djstartup.debuggable=yes
-> arg[ 15]: -DSAPINFO=J2E_01_sdm
-> arg[ 16]: -DSAPSTARTUP=1
-> arg[ 17]: -DSAPSYSTEM=01
-> arg[ 18]: -DSAPSYSTEMNAME=J2E
-> arg[ 19]: -DSAPMYNAME=ahassaine_J2E_01
-> arg[ 20]: -DSAPDBHOST=ahassaine
-> arg[ 21]: -Dj2ee.dbhost=ahassaine
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude iaik/security/md/SHA a
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
[Thr 2480] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [SDM]
-> arg[ 0]: server
-> arg[ 1]: sdmhome=D:\usr\sap\J2E\JC01\SDM\program
[Thr 2240] Fri Nov 30 10:38:33 2007
[Thr 2240] JLaunchRequestFunc: receive command:17, argument:0 from pid:2600
[Thr 2240] JLaunchIShutdownInvoke: set shutdown interval (stop:1196419113/end:1196419233/TO:120)
[Thr 2240] JLaunchProcessCommand: Invoke VM Shutdown
[Thr 2240] JHVM_FrameworkShutdownDirect: invoke direct shutdown
[Thr 2240] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 2240] JLaunchISetState: change state from [Initial (0)] to [Stopping (5)]
[Thr 640] Fri Nov 30 10:38:34 2007
[Thr 640] JLaunchIExitJava: exit hook is called (rc = 0)
[Thr 640] JLaunchCloseProgram: good bye (exitcode = 0)
Thank you very much in advance for your help.
HassanHi!
If instance.properties is not there your installation has not finished correctly. This file is the central point of information for the bootstrap, which retrieves the info on how to connect to the database to collect the infos for the system startup (which will then overwrite your instance.properties file with the most recent values from the DB).
Please check if instance.properties has been deleted and can maybe be restored from tape or if there was an error in the installation.
Regards,
Jörg -
Data Services XI3.1 function module files for SAP R/3 is not working
Hi guys,
Thank you for the quick response so far. I am very grateful to you all.
I got an issue and will try to explain as detail as I could and
hope ur guys won't mind. :P
I pass the functions module to SAP tech guy to install to SAP using CTS
method, and using 900086.R63 file type because my chinese client is
running SAP on unicode environment.
My DS installed on my laptop client; job server plus db2 is on HP
unix. SAP is on another HP Unix server. The function module I used is
supplied from Data Services XI3.1.
Anyway, the installation is successfully done with GUI wizard windows of
SAP Workbench instead of tp command line method.
1)However, I checked the ZAW0 function group, I opened and can't see any functions
listed under it, although the table structures ZACTA, ZTAB2048 and other items
were created.
2)So I tried to create SAP Datastore, Transport Target, etc and tried to
extract file. It failed and log said "can't open file ---
/db2/temp/curcode.txt". I checked and SAP working directory /db2/temp didn't have
curcode.txt, because the result file supposed to be extracted and stored there.
The SAP tech guy checked SAP and cant find generated ABAP program of
ZCURCD is running anyway, although my local CURCD ABAP program is
created.
3)Is it the 900086.R63 not complete? Is my function installation correct? I could view data
on datastore, but just cant run job to extract. Another non-unidcode 900200.S08 group
has larger file sizes. Should I try to install also this 900200.S08 files? Will it corrupt SAP
and cause system errors?
4)After that, I had tried to install the functions manually into ZAW0
one by one using cut and paste, however after that, I cant view the data view anymore with
error. Besides, I tried to run Check on the functions and they all returned
syntax errors, so I cant Activate any of them with SAP. Maybe dependency is missing??
Then, I deleted the manually installed functions and can view data again, but just cant extract
data by job.
5)Another side issue is all these SAP datastore creation and viewing is
through DI 11.5 old installation. The new Data Services X3.1 unable to
create datastore with database error, although the function module
installed is came from Data Services. Does anyone know the issue?
Thank you very much to read it patiently. :PHi,
Thank you for the informative link. It did help a lot in solving the problem.
(1) to (4) --- The Sap tech guy didnt install the function programs correctly, and he redo the transport again using CTS. Now I can see all the functions inside the function group ZAW0. While for the problem of cannot generate extracted file to SAP working directory for downloading, it is due to unix directory access permission setting. And also have to include the ftp username into SAPSYS user group as the help link suggested.
(5) For this problem, I reinstalled again the DS with all required components like Server Manager. The network technical guy helped me with the first installation, and the installation was not complete. So now the issue is solved, I can create R/3 Datastore with DS. -
SAP Web Dynpro iView not working!
We are trying to run BI reports based on Web Dynpro ABAP in portal. I created a SAP Web Dynpro iView with following parameters
System : SAP_LocalSystem
Namespace : sap
Applicatioin Name : ZXXXXX_RRE (This is the template name)
When I try to preview the report I get portal runtime error with following error dump in log file
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template
'<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<ProducerInfo>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PARAMETER_MAPPING PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System: &#39;SAP_LocalSystem&#39;,
Attribute: &#39;client&#39;.
I have checked SAP_BW system object and tested the connections all connection test for SAP_BW is successful. BI Portal system is set up with SAP web dispatcher, ITS and WEB host names in system object are configured something like xxxx.hostname.com:443 since it's SSL.
Am I missing anything here?
Thanks
PraveenHello Pravin,
Currently i am also facing the same error. I am having set of Webdynpro-ABAP applications, and accessing from Portal.
I tested respective applications from SE80, all are working fine.But while accessing from Portal its giving Portal runtime error-Unable to parse etc....
I checked my system object.. both WAS and ITS connections are successful.but i mentioned its related to ITS, where can i test my ITS further level..
Though these are WDA applications , how these related to ITS..
I am also getting same error message.. Please suggest how can i go head
Thanks in Advance
Ganesh -
Sap adobe print preview not working
Hello,
I have installed Adobe Live Cycle Designer and developed a form. The form looks ok.
When I try doing a print preview of the form I get a message "initalization of font server module failed"(note: it is not a sap message but a windows system message) and i get kicked out of the SAP system.
I tried couple of things..Unstalling and Installing the SAP GUI 710 with patch level 11(latest). I checked with the basis team and seems like its working for them. Not sure what is the problem with my system.
Please let me know how to fix this issue.
Thanks,
RajeevHi,
It seems that the font you have used in form is not supported by the printer.
Please check it once.
Regards,
Raju. -
SAP router connection is not working
Dear Experts,
I cannot connect my systems to SAP, getting the below error.My router is not expired and port 3299 is reachable.
SAPRouter "dev_rout" log as follows:
trc file: "dev_rout", trc level: 1, release: "720"
Wed Apr 09 15:55:51 2014
SAP Network Interface Router, Version 40.4
command line arg 0: C:\saprouter\saprouter.exe
command line arg 1: -r
command line arg 2: -W
command line arg 3: 60000
command line arg 4: -R
command line arg 5: C:\saprouter\saprouttab
command line arg 6: -K
command line arg 7: p: CN=SOLMAR, OU=0000881026, OU=SAProuter, O=SAP, C=DE
SncInit(): Initializing Secure Network Communication (SNC)
PC with Windows NT (mt,ascii,SAP_UC/size_t/void* = 8/64/64)
GetUserName()="Administrator" NetWkstaUser="Administrator"
SncInit(): Trying environment variable SNC_LIB as a
gssapi library name: "C:\saprouter\nt-x86_64\sapcrypto.dll".
File "C:\saprouter\nt-x86_64\sapcrypto.dll" dynamically loaded as GSS-API v2 library.
SECUDIR="C:\saprouter\" (from $SECUDIR)
The internal Adapter for the loaded GSS-API mechanism identifies as:
Internal SNC-Adapter (Rev 1.0) to SAPCRYPTOLIB
Product Version = SAPCRYPTOLIB 5.5.5C pl36 (Jul 3 2013) MT,[aesni],NB
main: pid = 3656, ppid = 0, port = 3299, parent port = 0 (0 = parent is not a saprouter)
reading routtab: 'C:\saprouter\saprouttab'
Wed Apr 09 16:00:49 2014
NiHLGetHostName: to get 192.168.4.69 succeeded in 4660ms (tl=2000ms)
Wed Apr 09 16:00:50 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:03:12 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:03:13 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:03:24 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:03:25 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:03:27 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:08:16 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:11:42 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:20:08 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:10 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:11 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:12 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:28:04 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:55:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:20:08 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:20:08 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 04:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 04:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 04:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 04:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 04:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 05:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 05:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 05:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 05:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 05:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 06:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 06:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:20:08 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:56:37 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:56:38 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:56:39 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:58:15 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
SAPRoutab:
P * * *
P 192.168.0.96 194.117.106.129 3299
P 192.168.0.96 194.117.106.129 *
# SNC-connection from and to SAP
#KT "p:CN=sapserv1, OU=SAProuter, O=SAP, C=DE" 194.117.106.129 *
# SNC-connection from SAP to local R/3-System for Support
#KP "p:CN=sapserv1, OU=SAProuter, O=SAP, C=DE" 192.168.* 32*
P * 194.117.106.129 *
P 127.0.0.1 194.117.106.129 3299
P * * *
P sapserv1 192.168.0.165 3389
P sapserv1 192.168.0.96 3389
P sapserv1 192.168.0.162 3389
SAPOSS Screens:Hi Philip
This looks fine. Just click on change and save again , it will automatically create SAPOSS RFC, u can see that in TX; SM59,
seems you Public IP : 192.168.0.96
The entry that you maintained in the sapsouttab was:
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.168.0.96, 3200
you supposed to maintain the IP Address of the server that you opening the connection.not the router IP(192.168.0.96,)
make sure it looks like the below:
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" <IP Address of the server that you working with RFC>, 3200
Please follow this:
1.Maintain then correct entries in the saprouttab
2.restart the saprouter
3.Delete RFC: SAPOSS from TX:SM59
4. Recreate the RFC: SAPOSS from OSS1 after deleting that from SM59..
5.Go to TX: SM59 and open the RFC:SAPOSS and go to technical setting tab: and make sure that the string looks ok and make sence(if requied copy the string frm the anotherserver where the RFC:SAPOSS is workingalready) and go to log on security tab and reenter the password of the user:OSS_RFC as CPIC (all in Capital letters)
save it and test.
please send me the screen shots of saproutab and screen shot of the SAPOSS RFC from SM59 and error screen shot.
hope it clarifies the now.
Kind Regards,
Phaneendra kakani -
SAP BW Query iView not working.
Hi,
We have a WB Query iView which displays a Report correctly on the Portal. When the user right clicks and selects a menu (a dialog appears which changes the currency settings) and clicks ok he gets "Internet Explorer cannot display the web page" Error occurs. This particular report seems to work for some users and not for others.
Please Help.
Thanks
Rajendra P VenkataHello Prasad
I am reporting succesfully on WEBI 4.0 on BEx queries with Characteristic Restrictions (if I understand correctly SAP have changed the name back again to WEBI). My experience so far with BO4 is that you need to place a lot of calls to SAP to iron out some of the teething problems, so I suggest that you rairse a note with SAP to get direct support from them.
So I suggest develop in WEBI and get SAP involved to iron out the error messages.
Regards
Phillip -
Calling SAP Web Services does not work
Hi,
using this little program, I try to get a simple "Hello World" from a webservice in SAP.
require 'soap/rpc/driver'
s = SOAP::RPC::Driver.new('http://server:port/sap/bc/srt/rfc/sap/Z_WS_RUBY/', 'urn:sap-com:document:sap:soap:functions:mc-style')
s.add_method("Z_WS_RUBY", "StringIn" )
p s.Z_WS_RUBY("World")
Unfortunately there is an error:
in `parse_local': unknown namespace qualifier: xml (XSD::NS::FormatError)
from D:/rubyy/InstantRails/ruby/lib/ruby/1.8/soap/encodingstyle/soapHandler.rb:532:in `decode_attrs' ETC
In the WebService Recorder I find that the call is going through with request:
<?xml version="1.0" encoding="utf-8" ?>
- <env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <env:Body>
- <n1:Z_WS_RUBY xmlns:n1="urn:sap-com:document:sap:soap:functions:mc-style" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<StringIn xsi:type="xsd:string">World</StringIn>
</n1:Z_WS_RUBY>
</env:Body>
</env:Envelope>
but response ist like:
- <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
- <soap-env:Body>
- <soap-env:Fault>
<faultcode>soap-env:Client</faultcode>
<faultstring xml:lang="en">Operation not supported</faultstring>
</soap-env:Fault>
</soap-env:Body>
</soap-env:Envelope>
What am I mssing here ?
Any help is appreciated.
Regards
Marcus
Message was edited by:
Marcus SchifferHi,
I am using SAP WAS Rel. 7.0. SAPWAS is of 0.11.
Couldnt retype your exact example, but I hope it works with my simple program too.
I activated the trace, here the result:
ignored element: Feature
ignored element: useFeature
Wire dump:
= Request
! CONNECT TO myserver:myport
! CONNECTION ESTABLISHED
POST /sap/bc/srt/rfc/sap/Z_WS_RUBY?sap-client=800&sap-language=EN HTTP/1.1
SOAPAction: "urn:sap-com:document:sap:rfc:functions"
Content-Type: text/xml; charset=utf-8
Authorization: Basic gzhtfzu=
User-Agent: SOAP4R/1.5.5 (/146, ruby 1.8.6 (2007-03-13) [i386-mswin32])
Date: Thu, 14 Jun 2007 08:14:05 GMT
Content-Length: 332
Host: myserver:myport
<?xml version="1.0" encoding="utf-8" ?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Body>
<n1:ZTestWsRuby xmlns:n1="urn:sap-com:document:sap:rfc:functions">
<STRINGIN>dd</STRINGIN>
</n1:ZTestWsRuby>
</env:Body>
</env:Envelope>
= Response
HTTP/1.1 500 Internal Server Error
set-cookie: sap-usercontext=sap-language=EN&sap-client=800; path=/
set-cookie: sap-recorder_sid=%2cc%3dID6-95D8115601C54670F9E2221A00000000--1%2co%3jhggz; path=/; domain=mydomain
content-type: text/xml; charset=utf-8
content-length: 264
sap-srt_id: 20070614/101842/v1.00_final_6.40/466FCFE5847D01C50000000095D81156
server: SAP Web Application Server (1.0;700)
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"><soap-env:Body><soap-env:Fault><faultcode>soap-env:Client</faultcode><faultstring xml:lang="en">Operation not supported</faultstring></soap-env:Fault></soap-env:Body></soap-env:Envelope>
The call does not ecven go through to the Function Module in SAP.
Here is the call that worked from my VB Program:
<?xml version="1.0" encoding="utf-8" ?>
- <env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <env:Body>
- <n1:ZTestWsRuby xmlns:n1="urn:sap-com:document:sap:soap:functions:mc-style" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<STRINGIN xsi:type="xsd:string">wert</STRINGIN>
</n1:ZTestWsRuby>
</env:Body>
</env:Envelope>
Maybe you are looking for
-
If I know authority object is 'S_OC_SEND', how to check it in ABAP code ?
Can i find if people in other place check the authority 's_oc_send'. Best regards,
-
Urgent helep: socket write error
Hi All, My application is continuously writing the following error message to the domain log of WLS eventhough app is running ok javax.servlet.ServletException: Connection aborted by peer: socket write error
-
How Transportation of Adhoc Query is done through RSAQR3TR report.
Hi, How Transportation of Adhoc Query is done through RSAQR3TR report.i want to transport a new usergroup, new infoset and a query from Develpment to Quality and Production. I have gone through the documentation of the RSAQR3TR report and as well as
-
Bid approval workflow - adding approvers
Hi experts - We are implementing the n-level bid award approval workflow (WS14500044). We would like the approvers to be able to add approvers/users once the workflow has started. We can see that you can add approvers before the bid is awarded (ie:
-
Up to 10.10.1 have been successfully using external 3840x2160 TVs and monitors (Seiki and Philips) with my MacBook Pro (Retina, 13-inch, Late 2013) and Iris graphics. After the update to 10.10.2, when connected to my Seiki 4k TV the MBpro now produce