SAP router it's not starting

Hi Guru's,
    I would like you too help me out here.  I did put the saproutab file and dev_rout.  Can you tell me what i am doing wrong here it's not starting the SAProuter.
1. SNC - connection from and to SAP
KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE"194.39.131.34 *
1. SNC - connection from SAP to local R/3-System for Support
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" * *
1. SNC - connection from SAP to local R/3-System for PcAnywhere
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" * 5631
1. SNC - connection from SAP to local R/3-System for saptelnet
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" * 23
1. SNC - connection from SAP to local R/3-System for WTS
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" * 3389
1. Access from the local Network to SAP R/3 Frontend (OSS)
P * 194.39.131.34 3299
P * 127.0.0.1 3299
P * 192.168.125.6 3299
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.168.1.6 3200
***********Beginning of data*************                                                                               
trc file: "dev_rout", trc level: 1, release: "710"                             
Tue Dec 28 18:28:46 2010                                                       
SAP Network Interface Router, Version 39.4                                                                               
command line arg 0: saprouter                                                  
command line arg 1: -r                                                         
main: pid = 53775, ppid = 53769, port = 3299, parent port = 0 (0 = parent is not
reading routtab: './saprouttab'                                                
ERROR => SNC field without SNC active, skip line 2 ¢nirout.cpp   9267!     
ERROR => SNC field without SNC active, skip line 5 ¢nirout.cpp   9267!     
ERROR => SNC field without SNC active, skip line 5 ¢nirout.cpp   9267!     
ERROR => SNC field without SNC active, skip line 8 ¢nirout.cpp   9267!     
ERROR => SNC field without SNC active, skip line 11 ¢nirout.cpp   9267!    
ERROR => SNC field without SNC active, skip line 14 ¢nirout.cpp   9267!    
ERROR => SNC field without SNC active, skip line 21 ¢nirout.cpp   9267!                                                                               
Tue Dec 28 18:33:10 2010                                                       
ERROR => NiBufIProcMsg: hdl 17 received rc=-94 (NIEROUT_PERM_DENIED) from pe
***********End of Data*******************

Hi,
Since you are using SNC connection to SAP, check below things:
1) SNC_LIB parameter should be set.
2) start your saprouter with below command:
saprouter -r -S <port> -K "p:<Your Distingushed Name>"
Thanks
Sunny

Similar Messages

  • SAP router service is not running.

    Hi Everyone.,
    Today I have tried to renew the certificate in windows system every thing went well till the end but after importing newly generated certificate sap router service failed to start. Below is the error message when i try to start the service.
    D:\usr\sap\SOL\SYS\exe\uc\NTI386>saprouter -r -S 3299 -K "p:CN=SOLMGR, OU=000086
    1986, OU=SAPRouter, O=SAP, C=DE"
    trcfile  dev_rout
    no logging active
    DEV_rout
    trc file: "dev_rout", trc level: 1, release: "700"
    Sat Dec 04 09:30:26 2010
    SAP Network Interface Router, Version 38.0
    command line arg 0:     saprouter
    command line arg 1:     -r
    command line arg 2:     -S
    command line arg 3:     3299
    command line arg 4:     -K
    command line arg 5:     p:CN=SOLMGR, OU=0000861986, OU=SAPRouter, O=SAP, C=DE
    SncInit(): Initializing Secure Network Communication (SNC)
          PC with Windows NT (mt,ascii,SAP_UC/size_t/void* = 16/32/32)
    SncInit(): Trying environment variable SNC_LIB as a
          gssapi library name: "D:\usr\sap\SOL\SYS\exe\uc\NTI386\sapcrypto.dll".
      File "D:\usr\sap\SOL\SYS\exe\uc\NTI386\sapcrypto.dll" dynamically loaded as GSS-API v2 library.
      The internal Adapter for the loaded GSS-API mechanism identifies as:
      Internal SNC-Adapter (Rev 1.0) to SECUDE 5/GSS-API v2
    main: pid = 7560, ppid = 0, port = 3299, parent port = 0 (0 = parent is not a saprouter)
    reading routtab: './saprouttab'
    When i tried to start the service manually then service is starting fine but when i tried to check OSS-001 connection in SM59 it says routtab permission failed rc-94.
    Please suggest if any one ever faced this issue.
    REgards,
    Vinod

    Hi Sunil,
    I have cross checked the orutab file. Please see below routab file and sugegst me incase if you find mistakes.
    SNC connection to and from SAP
    KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 194.39.131.34 *
    SNC-connection from SAP to your system SOL with SAPGUI
    KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 88.85.224.92 3200
    KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" solmgr 3200
    SNC-connection from SAP to your system SOL with WTS
    KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 88.85.224.92 3389
    SNC-connection from SAP to your system ECC DEV with SAPGUI
    KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 10.128.2.239 3200
    SNC-connection from SAP to local R/3-System for PCANYwhere
    KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" <R/3-Server> 5631
    SNC-connection from SAP to local R/3-System for saptelnet
    KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" <R/3-Server> 23
    Access from your local Network to SAP R/3 Frontend (OSS)
    P * 194.39.131.34 3299
    deny all other connections
    D * * *
    Also today i recieved a mail saying that client has chnaged the IP address of the saolution manager recently. Do they need to re register the IP with sap again. But i am able to telnet sapserv2 server IP using 3299 port and also able to ping the server. Please suggest.
    Regards,
    Vinod

  • SAP B1 License Manager not starting automatcially

    Dear All
    SAP Version : SAP 9.0 PL12
    Issue :
    1)SAP B1 License manager is not starting automatically even when the status is automatic in the Services.msc
    2)Also when logged from the client system its asks for the IP address/server name every time.
    3)Some times it connects with the Server name and sometimes with the IP address.
    And at cases it doesn't even connect at all throwing the error message "Connection to the license server failed" .
    and then when we replace the config files of SAP B1 to DI API it works fine at cases.
    This issue occurs on a random basis and at almost in all the systems(System connected in the morning is facing issue at afternoon).
    And it becomes an activity on a daily basis.
    So kindly let us know the exact cause for this issue and also a permanent solution for the same.
    Note : Firewall setting is turned off.
    Regards
    Shyam

    Hi Shyam..
    Have you Installed the License manager with the Admin Rights
    SAP Business One doesn't start and License Server Selection screen comes up
    SAP Business One generates this error message when logging on: "Connection with license server failed"
    On License Server Selection this error occurs: "Connection to license server failed; if license server address is invalid, correct it; if TAO NT Naming Service stopped, activate it and restart License Manager"
    On startup, the TAO NT Naming Service returns this warning: "The TAO NT Naming Service on local Computer started and then stopped...";
    TAO NT Naming Service is not running. To access this service,  right-click the My Computer icon and choose Manage -> Services
    Connecting to License Server brings warning: "Failed to connect to License Server"
    On startup, the SAP Business One License Manager returns this warning: "The SAP Business One License Manager on local Computer started and then stopped..."
    RSP: Logging on to Remote Support Platform (RSP) brings this Error:  "Agent service unavailable", RSP Agent Console cannot be accessed.  Nevertheless SAP Business One RSP Agent Service is running and restarts successfully
    check with the links
    TAO NT Naming Service Stop
    Check in Service Manager TAO_NT_Naming_Service does it has dependency with SAP B 1 License Manager.
    Check the above in the services... does it has got dependency
    check does it has set to restart on first failure and second failure in the TAO NT properties Recovery..
    Regards
    Kennedy

  • SAP Dialog Instance is not Starting - DISPATCHER EMERGENCY SHUTDOWN

    Hi All,
    We  are running on SAP ECC 6.0, Oracle 10, Windows 2003.
    We have One Central Instance an Two Dialog Instances, we shutdown the SAP system (  Jun 10 15:56:18 2008 ) to do an OFFLINE backup, now one of the Dialog Instances is no starting, we try to restart the system on Wed Jun 11 02:05:45 2008
    Oracle is Up and Open.
    The Central Instance and one of the Dialog Instances are Up, so you can login on the SAP System, and execute SAP transactions.
    I will Attach Our DEV_DISP, and DEV_W0 files:
    dev_dip
    trc file: "dev_disp", trc level: 1, release: "700"
    sysno      02
    sid        MIS
    systemid   562 (PC with Windows NT)
    relno      7000
    patchlevel 0
    patchno    133
    intno      20050900
    make:      multithreaded, Unicode, 64 bit, optimized
    pid        4008
    Wed Jun 11 02:05:45 2008
    kernel runs with dp version 232000(ext=109000) (@(#) DPLIB-INT-VERSION-232000-UC)
    length of sys_adm_ext is 576 bytes
    SWITCH TRC-HIDE on ***
    ***LOG Q00=> DpSapEnvInit, DPStart (02 4008) [dpxxdisp.c   1239]
         shared lib "dw_xml.dll" version 133 successfully loaded
         shared lib "dw_xtc.dll" version 133 successfully loaded
         shared lib "dw_stl.dll" version 133 successfully loaded
         shared lib "dw_gui.dll" version 133 successfully loaded
         shared lib "dw_mdm.dll" version 133 successfully loaded
    rdisp/softcancel_sequence :  -> 0,5,-1
    use internal message server connection to port 3900
    Wed Jun 11 02:05:50 2008
    WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds
    ***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  5371]
    MtxInit: 30000 0 0
    DpSysAdmExtInit: ABAP is active
    DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
    DpIPCInit2: start server >SAPPREC2_MIS_02                         <
    DpShMCreate: sizeof(wp_adm)          37008     (1480)
    DpShMCreate: sizeof(tm_adm)          56268128     (28120)
    DpShMCreate: sizeof(wp_ca_adm)          80000     (80)
    DpShMCreate: sizeof(appc_ca_adm)     160000     (80)
    DpCommTableSize: max/headSize/ftSize/tableSize=2000/16/2208064/2208080
    DpShMCreate: sizeof(comm_adm)          2208080     (1088)
    DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
    DpShMCreate: sizeof(slock_adm)          0     (104)
    DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    DpShMCreate: sizeof(file_adm)          0     (72)
    DpShMCreate: sizeof(vmc_adm)          0     (1864)
    DpShMCreate: sizeof(wall_adm)          (416064/346352/64/192)
    DpShMCreate: sizeof(gw_adm)     48
    DpShMCreate: SHM_DP_ADM_KEY          (addr: 000000000CCF0050, size: 59524432)
    ERROR => DpShMCreate: ShmCreate SHM_DP_CA_KEY(rc=4) [dpxxca.c     181]
    ERROR => DpIPCInit2: DpShMCreate [dpxxtool2.c  462]
    DP_FATAL_ERROR => DpSapEnvInit: DpIPCInit2
    DISPATCHER EMERGENCY SHUTDOWN ***
    NiWait: sleep (5000ms) ...
    NiISelect: timeout 5000ms
    NiISelect: maximum fd=1
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Wed Jun 11 02:05:55 2008
    NiISelect: TIMEOUT occured (5000ms)
    DpHalt: shutdown server >SAPPREC2_MIS_02                         < (normal)
    DpJ2eeDisableRestart
    Switch off Shared memory profiling
    ShmProtect( 57, 3 )
    ShmProtect(SHM_PROFILE, SHM_PROT_RW
    ShmProtect( 57, 1 )
    ShmProtect(SHM_PROFILE, SHM_PROT_RD
    call semaphore clean-up function ...
    ***LOG Q0E=> DpSigGenHandler, Exception (c0000005) [dpnttool.c   432]
    C-STACK -
    SAP (R) - R/3(TM) Callstack, Version 1.0
    Copyright (C) SAP AG. All rights reserved.
    Application exception occurred:
    Exception : c0000005 (Access Violation)
    App       : disp+work.EXE (pid=4008)
    When      : 6/11/2008 2:5:55.274
    Threads   : 2
    Computer Name       : SAPPREC2
    User Name           : SAPServiceMIS
    Number of Processors: 4
    Processor Type: EM64T Family 6 Model 15 Stepping 6
    Windows Version     : 5.2 Current Build: 3790
    State Dump for Thread Id 11ec
    --> (FAULT) Stack Back Trace <--
    FramePtr         ReturnAd         Param#1          Function Name
    0000000007d1f2e0 000000000041a395 0000000000000001 disp+work!DpVmcCheckDebugProxy [dpxxvmc.c (1211)]
    0000000007d1f3d0 000000000041d007 0000000005561401 disp+work!DpHalt [dpxxdisp.c (10016)]
    0000000007d1fc10 0000000000421a1b 0000000002671ab0 disp+work!DpFatalErr [dpxxdisp.c (17789)]
    0000000007d1feb0 000000000042d570 0000000000000000 disp+work!DpSapEnvInit [dpxxdisp.c (1388)]
    0000000007d1fee0 000000000040108d ffffffff00000002 disp+work!DpMain [dpxxdisp.c (1076)]
    0000000007d1ff10 00000000019c7dd1 0000000000000000 disp+work!nlsui_main [thxxanf.c (84)]
    0000000007d1ff70 0000000077d5966c 0000000000000000 disp+work!wmainCRTStartup [crtexe.c (498)]
    0000000007d1ffa0 0000000000000000 00000000019c7c60 kernel32!BaseProcessStart
    State Dump for Thread Id 1194
    --> Stack Back Trace <--
    FramePtr         ReturnAd         Param#1          Function Name
    000000000ccefe40 0000000077d5f651 0000000007d7bc60 ntdll!NtFsControlFile
    000000000ccefeb0 00000000018ae00f 0000000000000000 kernel32!ConnectNamedPipe
    000000000cceff40 000007ff7fc411c4 0000000000000000 disp+work!SigIMsgFunc [signt.c (679)]
    000000000cceff70 0000000077d6b69a 0000000077d6b660 msvcrt!endthreadex
    000000000cceffa0 0000000000000000 0000000000000000 kernel32!BaseThreadStart
    call clean-up function ...
    SigICallExitRoutine: call exithandler (DpHalt)
    DpHalt: shutdown server >SAPPREC2_MIS_02                         < (normal)
    DpJ2eeDisableRestart
    Switch off Shared memory profiling
    ShmProtect( 57, 3 )
    ShmProtect(SHM_PROFILE, SHM_PROT_RW
    DpShmPrfSwitch : State already set (OFF)
    ShmProtect( 57, 1 )
    ShmProtect(SHM_PROFILE, SHM_PROT_RD
    And our dev_w0
    this file was no modifued since we stop SAP System.
    M Tue Jun 10 15:56:18 2008
    M  *** WARNING => ThSndDelUser: delete client/user 020/RMENDOZA     (T60) on server SAPPREC1_MIS_01    
    S 
    S Tue Jun 10 19:07:40 2008
    S  server @>SSRV:SAPPREC1_MIS_01@< appears or changes (state 3)
    M 
    M Tue Jun 10 19:07:52 2008
    M  in_ThErrHandle: 1
    M  ThIErrHandle: new stat of W0 is WP_SHUTDOWN   
    M  ThIErrHandle: I'm during shutdown
    M  PfStatDisconnect: disconnect statistics
    M  Entering ThSetStatError
    M  ThCallDbBreak: use db_sqlbreak
    M  ThIErrHandle: don't try rollback again
    M  ThShutDownServer: shutdown server
    M  PfStatIndInit: Initializing Index-Record
    M  PfWriteIntoFile: copied shared buf (0 bytes) to local buf
    M  ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
    M  Entering ThReadDetachMode
    M  call ThrShutDown (1)...
    B  Disconnecting from ALL connections:
    B  Wp  Hdl ConName          ConId     ConState     TX  PRM RCT TIM MAX OPT Date     Time   DBHost         
    B  000 000 R/3              000000000 INACTIVE     NO  YES NO  000 255 255 20080610 144648 SAPPRECDB      
    C  Disconnecting from connection 0 ...
    C  Closing user session (con_hdl=0,svchp=000000000866D128,usrhp=0000000007D91058)
    C  Detaching from DB Server (con_hdl=0,svchp=000000000866D128,srvhp=0000000018D61918)
    C  Now I'm disconnected from ORACLE
    B  Disconnected from connection 0
    B  statistics db_con_commit (com_total=29203, com_tx=3253)
    B  statistics db_con_rollback (roll_total=494, roll_tx=0)
    M  ***LOG Q02=> wp_halt, WPStop (Workproc 0 2632) [dpnttool.c   327]
    Please Some Tips!
    Best Regards,
    Erick ILarraza

    Hi Deepak,
    Thanks  a lot for your reply, in this case the problem was with the Dialog Instance (Only SAP apps, not Oracle).
    We shutdown the instance with the Microsoft SAP Management Console (right  button -> Stop).
    In general to shutdown the SAP System we first:
    1. Shutdown The Dialog Instance. (SAP Management Console)
    2. Shutdown The Central Instance. (SAP Management Console)
    3. Shutdown Oracle (BR*Tools).
    4. Stop SAP and Oracle Services.
    Maybe is more a problem of Windows Memory Management.....
    Best Regards,
    Erick ILarraza

  • SAP Web Dispatcher does not start as windows service

    Hi,
    I have successfully installed and configured SAP Web Dispatcher. When I start the web dispatcher from command prompt, it works fine. I created a windows service for web dispatcher using the command
    ntscmgr install sapwebdisp -b "c:\program files\sap\sapwebdisp\sapwebdisp.exe"
    -p "service pf=sapwebdisp.pfl -cleanup -auto_restart"
    The command successfully created sapwebdisp service. The service also starts fine, but web dispatcher does not get started.
    Any ideas experts?

    Hi,
    Ok. Few suggestions.
    1. Can you review the SAP note:
    552286  Troubleshooting for the SAP Web Dispatcher
    2. When you said: "web dispatcher does not get started ", what error you got ? Can you be more details here ?
    3. Please check the trace file dev_webdisp" that generated in the work directory. If the log entries is not abvious, increase the trace level to 2 or 3, and reproduce and re-check the trace file.
    4. What is the output of the command "sapwebdisp -v"
    5. How about sapwebdisp.pfl ? Are those settings correct ?
    Hope this helps.
    Regards,
    Vincent

  • 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 Download Manager does not start after installation

    Hi,
    i justed tried to install sap download manager as described here:
    https://websmp102.sap-ag.de/~sapidb/002006825000000233132001D
    using java http://java.sun.com/products/archive/j2se/1.4.2_12/index.html
    installation itself was no problem but if I start the download manager only the color setings from windows
    change in blue and back to my own nothing else.
    Hope you can help me.
    Thanks in advance.
    Sebastian
    System is Win7 32bit

    > i justed tried to install sap download manager as described here:
    >
    > https://websmp102.sap-ag.de/~sapidb/002006825000000233132001D
    >
    > using java http://java.sun.com/products/archive/j2se/1.4.2_12/index.html
    >
    > installation itself was no problem but if I start the download manager only the color setings from windows
    > change in blue and back to my own nothing else.
    Are you intentionally using such an old JDK?
    Markus

  • SAP Router - Host did not respond 8 times

    Guys,
    I'm able to test OSS connection successfully in SM59. But in service connections, whenever i open connections, the connection failing to open with the "Host did not respond 8 times " error before changing to Cancel. Any suggestions please?

    There was a little glitch in the saprouttab file, which i fixed. But interesting to note that it didn't clear the error. I keep having the same error, but SAP was able to connect inspite of that. As i read elsewhere, often times this error is misleading. anyway, thanks.

  • Installation of TREX 7.0 on 64bit windows then SAP does not start

    I have implemented EP7 Portal (NW04s SP11) on a MS-SQL DB with windows 2003 64bit hardware.  I also want to install TREX which is version 7.0 on the same server.
    After installing TREX the http_server would not start. I followed OSS note 1008299 that instructed me to set IIS to run in 32 bit mode as TREX 7.0 really isn't a 64 bit application!!
    I performed this but now the service for my SAP Java instance will not start:
    error : "The dynamic link library librfc32.dll could not be loaded"  (SCS does start OK)
    Its obviously got something to do what I've just performed...
    any help anybody?
    thanks
    SB.

    Hi Simon,
    Actually trex was not released for a 64 bit component. But in the installation CD, it was printed mistakenly.
    For that only, SAP has given note 1008299 to run IIS in 32 bit mode instead of 64 bit mode, because although you have done the installation as a 64 bit machine, its for 32 bit platform only.
    Running the script will start your IIS on a 32 bit mode and also, change your executables, file folder as well.
    Previously, i also had the same problem and once i did as per the note, its working perfectly now.
    Thanks and Regards,
    Sailesh K

  • SAP does not start-gives error message

    This error has just started.
    When I click the SAP icon, it does not start and it gives the error message
    E - SAP - SAP Business One - SAP Business One
    The color palette file couldn't be properly loaded
    Thanks

    Hi.
    Have You installed something recently on that machine?
    Regards.

  • SAP router is shutting down automatically

    Hi All,
    I have configured SAP router and started SAP router service using command in command prompt and left command window unclosed. It is working for some time and after regular intervals automatically it is shutting down. So, I need to check and start manually. There is no SAP router service in services list. I guess this might be the problem.
    Can anyone please tell me the solution?
    Note: I have done all this in Solution Manager System.
    OS : Windows 2008
    DB: SQL Server
    Thanks in Advance
    Uday.

    Hi Varun,
    Thanks for helpful answer.
    Only SAP router is stopping not the window.
    I have tried installing SAProuter as NT service.
    After creating service should I need to reboot the system?
    Hi Sravanthi,
    Thanks for helpful answer.
    I have started SAProuter with 'saprouter -r &' command. Let me see the result.
    And also I installed a service as NT service( According to note 525751).
    Service was created successfully but when I select saprouter service and start(services.msc) it is getting terminated with the following error:
    Error 1067: The process terminated unexpectedly.
    Hi Siva,
    Thanks for your response.
    I have started SAProuter service using 'saprouter -r &' command, let me see this how long it works.
    Then I will start the service as you suggested.
    Thanks & regarda
    Uday

  • Saprouter could not start  "Error:1053"

    Hi!
    I have installed the SAP-Router service and cannot start it from "SERVICES".
    I get the error "Could not start the saprouter on the Local machine".
    I also implemented the recommendation from microsoft ot apply the new package
    from http://support.microsoft.com/kb/839174/en-us
    . But If I try to apply it, the popup tells me "no new packages found that are newer than on my OS".
    <b>How should I proceed?
    Is it possible to deinstall the service from "services"?</b>
    Thank you!
    regards

    Hello Peter,
    We started a survey to change our SAProuter acrhitecture to SAProuter
    7.0 version.
    As we overviewed all prerequisites, we require from SAP support
    confirmation on the 2 following points :
    1. As saprouter program will be installed on host which already exists
    and is located in DMZ, the existing Windows operating system version is
    W2003 Server Standard Edition in french version.
    Thus, we would like SAP support to confirm that SAProuter program can
    be installed and will run correctly on Windows 2003 Standard Edition in
    french version as SAP note 690432 'Windows 2003 Support' mentions that
    SAP supports such an hardware configuration if Windows Multilanguage
    User Interface (MUI) kit is installed and that W2003 Standard Edition
    is supported for 'test or small systems only' (only saprouter program
    will run on this host)
    2. One of the requirements of saprouter installation is to provide
    public @IP to SAP.
    As we get such an IP adress, we require SAP support to confirm that
    this IP adress will work properly as below :
    Saprouter will be installed on host which is located in DMZ (SAP
    requirement) what does mean 'between our 2 firewalls'
    Thus, connection from sap will be translated by first firewall which
    will redirect to public adress provided
    Question : Must the host on which saprouter will run have one and only
    one IP adress?
    As mentionned previously, host already exists and has already an IP
    adress : then, public @IP provided will have to be translated by
    firewall.
    Thanks for your response as my colleagues and I noted that you are 'reference guru' on several topics (you answered to us for customer message open ofr inquiry on ECC 6.0 upgrade with OS/DB migration)
    Rgds,
    Zulain

  • SAP system doesn't automatically start after restart (but manual start ok)

    Hi,
    We've got a new production line of SAP EP 7.0 systems, which have CI on HP-UX and DIs on windows. The version is NW2004s SPS09.
    What we see is that after a restart of the windows servers (usually because of windows patching), the SAP system doesn't automatically start up. It doesn't start up if I restart the SAP<SID>_<instance> service either. 
    However, I've got no problem starting the system with the MMC.
    Any idea what I am missing here? is it as simple as a profile parameter ?
    As far as I can see the profile used seem ok.
    After a restart of the windows server the following files have log entries in the c:\usr\sap\<SID>\J<instance>\work folder
    sapstartsrv.log
    trc file: "sapstartsrv.log", trc level: 0, release: "700"
    Fri Nov 17 15:51:26 2006
    <<- ERROR: SapSSLInit(read_profile=1)==SSSLERR_LIB_NOT_FOUND
    sapstart.log
    Starting WebService thread
    SapSSLInit failed => https support disabled
    Webservice named pipe thread started, listening on port
    .\pipe\sapcontrol_97
    Webservice thread started, listening on port 59713
    sapstart.trc
    Starting WebService thread
    SapSSLInit failed => https support disabled
    Webservice named pipe thread started, listening on port
    .\pipe\sapcontrol_97
    Webservice thread started, listening on port 59713
    The windows event log have the application events
    (first)SAP Service SAP<SID>_<instance> successfully started.
    (at the same time)
    Failed to update service environment from user (STATOIL-NET\<sid>adm) environment. [ntservmgr.cpp 201]
    (note that this doesn't happen for all systems which have this problem, for other there is no entry like this)
    I see no failed login attemps in the security event log, but see the that a login is performed for SAPService<SID>.
    Since it also fails to automatically startup when I restart the service, I am able to use filemon to see what happens at a file level. Here I see that it can access the shared file system without any problems, and can read the profile and everything.
    MOM is running on the server and gets some Access denied errors since it doesn't have access to the shared file system, but I don't think that matters.
    Cheers
    Dagfinn

    hi  we are using sap bw 3.5 . database is oracle 9i
    i applied a kernel patch and when i tried to start the services . there was no problem with the oracle services  and saposcol but the service sap<sid>_nr did not start .
    when i went to check the error in work folder ..
    it say " SapSSLinit failed => https support disabled  .
    then i tried to start sap from cmd pmt . din`t work .
    is there a way to statrt this ...
    thanks alot.
    arjun

  • Error in Fiori Launchpad "could not start the app due..."

    Hello everyone,
    I am having a previously unseen (well, at least for me) error which raises on a click on the tile "Track Purchase Orders" on the SAP Fiori Launchpad:
    "Could not start the app due to an internal error" (see the screenshot attached)
    I haven't found any help on this error on Google and SAP portals.
    The other applications work fine. So did this one before the implementation of SAP_UI 740 SP09 (before that it was SAP_UI 740 SP08). We applied all the notes specified in this post http://scn.sap.com/docs/DOC-56967
    Components needed for Track Purchase Orders are patched to their maximum levels (UIX01EAP 100 SP03 and SRA020 600 SP05). OData and UI5 services are activated.
    Plus, this error doesn't appear in the Gateway error logs (transaction /iwfnd/error_log) so troubleshooting is difficult.
    The issue is systematically reproducible and has been reproduced on several computers.
    Thanks a lot if you have any insight about this issue!
    Best regards,
    Guillaume

    Thank you for replying.
    I have inspected the element and clicked on the tile. The network tab is below:
    The status seems OK.
    The response for ResolveLink:
    {"d":{"results":[{"__metadata":{"id":"http://<server>:<port>/sap/opu/odata/UI2/INTEROP/NavTargets('PurchaseOrder-track~68')","uri":"<server>:<port>/sap/opu/odata/UI2/INTEROP/NavTargets('PurchaseOrder-track~68')","type":"INTEROP.NavTarget"},"id":"PurchaseOrder-track~68","shellType":"FLP","postParameters":"","text":"Track Purchase Order","applicationData":"SAPUI5.Component=ui.s2p.mm.purord.tracking","applicationAlias":"TrackPurchaseOrder","applicationType":"URL","url":"/sap/bc/ui5_ui5/sap/mm_purord_tpo"}]}}
    I'm surprised that gbapp_poapproval and sra001 OData services are called here (with an intriguing ";mo")... We have found these errors in our /iwfnd/error_log screen after the SAP_UI 740 SP09 patch. Seeing this, we have installed GBAPP002 600 SP6 and SRA001 600 SP4 and activated the OData services but have not tried to use the corresponding apps (meaning that we have not done any other app implementation tasks because we don't really intend to for the moment).
    In case the two problems are related, these are the responses to these requests:
    For gbapp_poapproval request
    {"error":{"code":"GBAPP_APV_MSG/013","message":{"lang":"en","value":"Workflow Task Type is not passed as filter criteria"},"innererror":{"transactionid":"53EB173F121613F0E1008000A87C135A","timestamp":"20140814124456.5404250","Error_Resolution":{"SAP_Transaction":"Run transaction /IWFND/ERROR_LOG on SAP NW Gateway hub system and search for entries with the timestamp above for more details","SAP_Note":"See SAP Note 1797736 for error analysis (https://service.sap.com/sap/support/notes/1797736)"},"errordetails":[{"code":"GBAPP_APV_MSG/013","message":"Workflow Task Type is not passed as filter criteria","propertyref":"","severity":"error"},{"code":"/IWBEP/CX_MGW_BUSI_EXCEPTION","message":"An exception was raised.","propertyref":"","severity":"error"}]}}}
    For gbapp_prapproval request
    {"error":{"code":"GBAPP_APV_MSG/013","message":{"lang":"en","value":"Workflow Task Type is not passed as filter criteria"},"innererror":{"transactionid":"53EB0B1112160FA0E1008000A87C135A","timestamp":"20140814124456.4449070","Error_Resolution":{"SAP_Transaction":"Run transaction /IWFND/ERROR_LOG on SAP NW Gateway hub system and search for entries with the timestamp above for more details","SAP_Note":"See SAP Note 1797736 for error analysis (https://service.sap.com/sap/support/notes/1797736)"},"errordetails":[{"code":"GBAPP_APV_MSG/013","message":"Workflow Task Type is not passed as filter criteria","propertyref":"","severity":"error"},{"code":"/IWBEP/CX_MGW_BUSI_EXCEPTION","message":"An exception was raised.","propertyref":"","severity":"error"}]}}}
    For sra001_pcapproval request
    {"error":{"code":"SRA001_CMN_MSG/013","message":{"lang":"en","value":"Workflow Task Type is not passed as filter criteria"},"innererror":{"transactionid":"53EB0E4512161140E1008000A87C135A","timestamp":"20140814124456.3244590","Error_Resolution":{"SAP_Transaction":"Run transaction /IWFND/ERROR_LOG on SAP NW Gateway hub system and search for entries with the timestamp above for more details","SAP_Note":"See SAP Note 1797736 for error analysis (https://service.sap.com/sap/support/notes/1797736)"},"errordetails":[{"code":"SRA001_CMN_MSG/013","message":"Workflow Task Type is not passed as filter criteria","propertyref":"","severity":"error"},{"code":"/IWBEP/CX_MGW_BUSI_EXCEPTION","message":"An exception was raised.","propertyref":"","severity":"error"}]}}}
    Regards,
    Guillaume

  • IPC Dispatcher not starting

    Hi All,
    The SAP IPC dispatcher and the SAP IPC Server are not starting. Message: "Couldn't start the SAP IPC Dispatcher service on local computer. The service didn't return an error. This could be an internal windows error or an internal service error. "
    Environment:
    1. Windows 2000 Server Service Pack 4.
    2. SAP:IPC:4.0 SP06
    Here are contents of properties file
    rfcEnabled=true
    rfcDispatcherProgId=IPC_RFC_DISPATCHER
    rfcServerCount=1
    rfcServerProgIdPrefix=IPC_RFC_SERVER_
    I searched OSS notes and this forum, but didn't have good luck.
    Looking forward to your help.
    CRM Installer

    Did you try note 842950?
    Regards,
    Kaushal

Maybe you are looking for

  • JDK1.2.2 and untrusted server chain and HELP

    Hi, I'm using JDK1.2.2 and I've downloaded and installed JSSE1.02. I have also installed the server cert in my own truststore. The server to whom I want to connect sends two certificates. One is valid and this is the one I need and I have and one tha

  • " User not authorized" error while deploying webdynpro application on WAS

    I am getting following error while deploying dyn pro application on WAS Error May 17, 2005 6:37:21 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR: [002]Deployment aborted Settings SDM h

  • HT1386 Ipod is not showing up in the itunes interface

    This is garbage

  • IWeb not accepting changes

    I started a website a few weeks ago from scratch using iWeb 08. I had some pages set up with headings for future pages which were all linked to a little "under construction" Flash animation. As I make each new page I simply replace the hyperlink to t

  • How to customize the Quick Launch with Security

    I would like to add links to the quick launch with security control - some menus only show to specific user groups. But I do not find any way to do that, either through configuration or custom codings. Would you please advise on that? Thanks. Kevin L