HTTP_RESP_STATUS_CODE_NOT_OK -- 500 -- Timeout

Hi Guys,
There is 1 msg gone to error status with below error .
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!--  Call Integration Server
  -->
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30"     xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
  <SAP:Category>XIServer</SAP:Category>
  <SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
  <SAP:P1>500</SAP:P1>
  <SAP:P2>Timeout</SAP:P2>
  <SAP:P3 />
  <SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 500 with the description Timeout Error when sending by HTTP (error code: 500, error text: Timeout)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
This error happened only once and again all the msgs for the same interface processing successfully.
Scenario is: proxy --> XI --> IDoc(Asynchronous)
Could any one plz let me know wht could be the problem that time?
Thanx,
Kumar

Hi Kumar,
as far as I understood your problem, the Timeout error occurs when sending from
ABAP Proxy (?) to the Integratin Server, correct?
Please check with transaction SMICM on both sides the trace file and the parameter settings for the http protocol.
It could be that your message is quite large, and therefore the default values of 60 seconds are to small defined.
In general for Timeout settings, there is a nice unit called "Timeouts in XI" in the XI3.0/XI7.0 Troubleshooting Guide available at
<a href="http://service.sap.com/instguidesNW70">http://service.sap.com/instguidesNW70</a> > Operations
- Process Integration: <a href="http://Troubleshooting Guide - SAP XI 3.0/SAP NW 7.0">http://service.sap.com/~sapidb/011000358700005909032005E.PDF</a>
Extract from the guide, which should be also valid for your case:
ICM 402 timeout for http client calls (IS -> AF): ICM_HTTP_TIMEOUT
Value for all ports: icm/keep_alive_timeout (Default: 60 seconds)
Value for specific ports:
icm/server_port_0 = PROT=HTTP,PORT=<icmhttpport>, TIMEOUT=30, PROCTIMEOUT=900
PROCTIMEOUT not set > TIMEOUT is used > TIMEOUT not set >  icm/keep_alive_timeout is used
Default: TIMEOUT and PROCTIMEOUT not set –>icm/keep_alive_timeout is used
In the event of errors, increase the PROCTIMEOUT value for the HTTP/HTTPS ports used.
Do not increase icm/keep_alive_timeout or the TIMEOUT value as this would lead to a higher resource consumption.
For more information, see SAP Note 824554 - ICM timeout parameters.
Best regards,
Silvia

Similar Messages

  • RFC  Received HTTP response code 500 : Timeout error

    Hi All.
    I am getting the following error for the RFC sender:
    Transmitting the message to endpoint http://pocitmsprdxi.crisp.com:8000/sap/xi/engine?type=entry using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Timeout.
    The RFC sends the data to XI through RFC and at times the data is not entering XI and the error shown above occurs.
    How do i solve this?

    Hi Lavanya,
    For these kind of problem, you need to set proctimeout smicm as per SAP note - 824554 .
    Application threads in the J2EE engine might have got consumed in high load situations. Increase the count of application threads in config tool at location Config Tool -> cluster-data -> <configuration template> -> <instance-ID> -> managers -> ApplicationThreadManager -> MaxThreadCount.
    And also Increase the parameter ServletInputStreamTimeout.
    Hope this helps to you.
    Regards,
    P.Rajesh

  • Received HTTP response code 500 : Timeout

    Hi All,
    I have done the File to JDBC to File(Sync) with module concept. Every thing is working fine in Dev system, yes'day it was moved to Quality System while i am trying to test i am getting the error in Sender File communication chennal.
    Error: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Timeout
    I have chaged the SQL statment to fetch only 50 records at that time its working fine with out any error.
    While i am trying to collect 40,000 records its failing generally in Dev it use to take 4 to 6 min to gereate file.
    Pls let me know do i need to chage any paramaters in Visual admin.
    I have observed cm/keep_alive_timeout =60 (sec) but in dev the time is more? is this causing the problem?
    I DEV system i don't have any issues the scenario is working fine.
    Thanks,
    Venkat.

    Hi,
      Yes..you should increase the icm/keep_alive_timeout.If you increase the time then until the connection will wait for the response. For more details..
    [http://help.sap.com/saphelp_nw70/helpdata/EN/0b/1c7e7abbc311d5993a00508b6b8b11/content.htm]
    Regards,
    Prakasu.M
    Edited by: prakasu on May 13, 2009 6:31 PM

  • Error when sending message: 500 Timeout

    while sendin a message in the http to rfc scenario, im gettin this error message "Error when sending message: 500 Timeout".
    can any1 throw some light on this.

    Hi venu,
    you need to go to RZ10 and there select the profile instance and go with the extended maintance option in the change mode.
    there are two ways you can change it:
    1. check out note: 824554
    TCODE - rz10
    icm/server_port_0 = PROT=HTTP,PORT=8010,TIMEOUT=800,PROCTIMEOUT=800
    (for 800 seconds)
    8010 is my HTTP port so you have to change it:)
    2. SXMB_ADM -> configure integration server -> change specific identifiers
    runtime parameter:
    Parameter HTTP_TIMEOUT
    Meaning
    Specifies the timeout for http connections (time between two data packages at line level). This value overrides the system profile parameter icm/server_port_n (for example, icm/server_port_0 : PROT=HTTP, PORT=50044, TIMEOUT=900). If you do not set the parameter HTTP_TIMEOUT or if you set the parameter to 0, then the setting for the system profile parameter is used.
    Personally I only changed the one from the instance profile but the second one should work too
    My suggestion is change only PROCTIMEOUT to 600 or 900 but dont change TIMEOUT. Imp thing is u need to restart the XI, then onlychanges will take place.
    If these dosent work out go for changing TIMEOUT also. Just set the value for the instance and dont maintain the HTTP_Timeout in the sxmb_adm
    Let me know what u have done , if it works
    Thanks,
    srini

  • HTTP_RESP_STATUS_CODE_NOT_OK 500 error

    hi all,
    i am working on xi to LDAP connectivity,
    for this iam using java proxy, when iam executing the scenario, i am getting the follwing error in sxmb_moni
    can any one help me
    SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
      <SAP:P1>500</SAP:P1>
      <SAP:P2>Internal Server Error</SAP:P2>
    Thanks & Regards,
    Madhav Poosarla

    Hi madhav 
    HTTP_RESP_STATUS_CODE_NOT_OK 500 error
    error code 500 stands for Internal Server Error
    The server encountered an unexpected condition which prevented it from fulfilling the request. 
    Check whether you have given the right credentialsand also check the conditions which you have given whether any condition is false... If you are very sure that you have given right credentials then your problem will be solved by restarting J2EE engine
    steps to restart J2EE engine
    1) run transaction SMICM
    2) then in the tab administration => J2EE instance(local) =>send soft shutdown with restart
    by this java engine will restart and will be up in 5-10 minutes and your problem will be solved
    for more details on error code follow the link
    http://www.web-cache.com/Writings/http-status-codes.html
    http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
    http://www.helpwithpcs.com/courses/html/html_http_status_codes.htm
    Thanks
    sandeep sharma
    PS ; if helpful kindly reward points

  • CLIENT_SEND_FAILED 500 Timeout Error

    Hi Guys,
    i am getting below error in PI MONI, can any one please help me how to resolve this isuue.
    This interface is File to Proxy(ECC).
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
      <SAP:P1>500</SAP:P1>
      <SAP:P2>Timeout</SAP:P2>
      <SAP:P3>(See attachment HTMLError for details)</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Error while sending by HTTP (error code: 500 , error text: Timeout) (See attachment HTMLError for details)</SAP:Stack>
      <SAP:Retry>A</SAP:Retry>
      </SAP:Error>
    Thanks,
    Siva.

    Hi,
         Is your scenario synchronous?
    Did you get a chance to look at below links:
    Re: CLIENT_SEND_FAILED for sync calls
    INTERNAL CLIENT_SEND_FAILED Internal Server Error 500 Error while sending b
    Regards,
    Naveen

  • HTTP_RESP_STATUS_CODE_NOT_OK - 500

    All,
    The following error is displayed in the R3 environment when we check the message using SXMB_MONI the message never leaves SAP R3 to XI as it is only visible in R3.
    <SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
      <SAP:P1>500</SAP:P1>
      <SAP:P2>Soap document processing failed</SAP:P2>
    further down the XML the following detail message is displayed:
    SOAP Runtime Exception: CSoapExceptionDocumentFormat : document format error: XML kernel processor cannot read tag ( kernel rc=1 )
    Regards,

    Hi,
      I asked for sp as there was a fix, but its on and before sp12.
    In this case did you try this step,
    1.goto t code sxmb_adm.
    2.Configuration of intregation server.
    3.set the "Role of Business System" as LOC "Application system"
    Refer /people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
    Refer http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
    under
    <b>500 Internal Server Error</b>.
    Regards,
    Anirban.

  • HTTP Timeout 500

    Hello to all,
    we've got a sychronous szenario RFC <> XI <> JDBC.
    Sometimes I get the following exception:
    "com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Timeout."
    I've set the icm parameter to SAP recommandation.
    icm/server_port_1  PROT=SMTP, PORT=25, TIMEOUT=30, PROCTIMEOUT=600
    Any ideas to solve this?
    Regards Christian

    HI,
    Just take a look into SAP Notes – 804124, 807000
    Synchronous RFC HTTP Timeout---need urgent help

  • Timeout in ABAP Proxy

    Hi!
    In my scenario messages on CRM are created by a BADI calling an ABAP proxy class on the local Integraton Engine which then forwards the messages to the XI Integration Server and vice versa.
    We recently had the problem that the SAPSLDAPI SM59 destinations on XI and CRM ran into a timeout because the SAPSLDAPI service in the JCo RFC Provider Service of the J2EE Admin Tool was not working properly.
    While we experienced the SAPSLDAPI timeout problem in the XI Integration Server all messages which XI was supposed to forward to CRM failed in the Call Adapter step in SXMB_MONI with error status 500 (timeout).
    I would have assumed that the same happens also on the CRM side when the local Integration Engine was supposed to send messages to XI. However, there was a timeout when pressing the save button in the IC Web Client. The XML messages were not created at all and not visible in SXMB_MONI. Thus in production a call center agent would have not been able to update any customer or product information.
    If such a problem arises in my opinion the messages should always be created and queued up by the Integration Engine so that they can be reprocessed once the problem is solved. Does anybody have any idea why this did not happen on the CRM side and do you have any feedback how this problem could be resolved?
    Regards, Tanja

    Hi!
    > Please can you check in the SXMB_MONI of the CRM
    > system if there are any messages stcuk there if you
    > cannot see the same in the XI SXMB_MONI.
    There was a timeout when pressing the save button in the IC Web Client. Thus the XML messages were not created at all and not visible in SXMB_MONI on CRM.
    Regards, Tanja

  • HTTP_RESP_STATUS_CODE_NOT_OK 401 unauthorized

    Hi All
    my interface is File to proxy,
    i am getting this error ,HTTP_RESP_STATUS_CODE_NOT_OK
    when i checked the trace it is saying
    HTTP response contains status code 401 with the description Unauthorized Authorization error while sending by HTTP (error code: 401, error text: Unauthorized
    i needed to know what all the roles i need to have to have over come problem
    i hope this is only cause of roles problem has i dont have authorisation for all tracsation
    i should add in R/3 ECC 6.00 for my roles
    thankingyou
    Sridhar

    Hi
    use similar thread
    In SXMB_MONI i am gettin  error status 500
    Received HTTP response code 500..
    HTTP_RESP_STATUS_CODE_NOT_OK 500 error
    Re: Proxy error - HTTP status code 500

  • SOAP - XI - RFC / Problem with timeout-handle

    hi gurus
    B I G   U R G E N T problem. how can it be:
    - i've got an custom-bapi
    - in receiver-rfc-adapter 'commit-controller' is on
    when i force an time-out in sap ecc the soap-caller receives an system-error 'time-out...'.
    but: the custom-bapi becomes an commit and in ecc the document is booked!
    how can it be?
    thanks
    t

    hi Rajesh
    in sxmb_moni the message has the status 'log-version'.
    soap-adapter-log:
    2010-06-24 17:04:42 Erfolgreich calling the module processor for channel CC_SD01_WS_OUT
    2010-06-24 17:04:42 Erfolgreich MP: Tritt in den Modulprozessor ein
    2010-06-24 17:04:42 Erfolgreich MP: Lokales Modul localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean wird verarbeitet
    2010-06-24 17:04:42 Erfolgreich SOAP: request message entering the adapter with user KOMM
    2010-06-24 17:04:42 Erfolgreich SOAP: request message leaving the adapter (call)
    2010-06-24 17:04:42 Erfolgreich Die Anwendung versucht eine XI Message synchron zu senden über SOAP_http://sap.com/xi/XI/System
    2010-06-24 17:04:42 Erfolgreich Versuch die Message in die Call-Queue zu stellen
    2010-06-24 17:04:42 Erfolgreich Message erfolgreich in Queue gestellt
    2010-06-24 17:04:42 Erfolgreich Die Message wurde erfolgreich aus der Call-Queue abgerufen
    2010-06-24 17:04:42 Erfolgreich Der Status der Message wurde auf DLNG gesetzt
    2010-06-24 17:05:47 Fehler Rückgabe synchroner Fehlerbenachrichtigung an rufende Anwendung: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Timeout.
    2010-06-24 17:05:47 Fehler Die Übertragung der Message über http://szhm2179:8001/sap/xi/engine?type=entry ist fehlgeschlagen, weil: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Timeout
    2010-06-24 17:05:47 Fehler Der Status der Message wurde auf FAIL gesetzt
    2010-06-24 17:05:47 Fehler Zurück zur Anwendung. Ausnahme: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Timeout
    2010-06-24 17:05:47 Fehler SOAP: call failed: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Timeout
    2010-06-24 17:05:47 Fehler SOAP: call failed: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Timeout
    2010-06-24 17:05:47 Fehler MP: Ausnahme aufgetreten mit Grund com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Timeout: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Timeout
    rfc-adapter-log:
    2010-06-24 17:04:43 Erfolgreich Message wurde erfolgreich vom Messaging-System empfangen. Profil: XI URL: http://szhm2179.stzh.ch:50100/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
    2010-06-24 17:04:43 Erfolgreich Mit der Verbindung RFC_http://sap.com/xi/XI/System. Versuch die Message in die Request-Queue zu stellen
    2010-06-24 17:04:43 Erfolgreich Message erfolgreich in Queue gestellt
    2010-06-24 17:04:43 Erfolgreich Die Message wurde erfolgreich von der Request-Queue abgerufen
    2010-06-24 17:04:43 Erfolgreich Der Status der Message wurde auf DLNG gesetzt
    2010-06-24 17:04:43 Erfolgreich Liefert an Kanal: CC_SD01_RFC_IN
    2010-06-24 17:04:43 Erfolgreich MP: Tritt in den Modulprozessor ein
    2010-06-24 17:04:43 Erfolgreich MP: Lokales Modul localejbs/RfcAFBean wird verarbeitet
    2010-06-24 17:04:43 Erfolgreich RFC-Adapter hat synchrone Message erhalten. Versucht, sRFC für /STZH/SOZ_CD_F2_BELEG_CREATE zu senden
    2010-06-24 17:04:43 Erfolgreich RFC-Adapter hat synchrone Message erhalten. Versucht, sRFC für J2EE_GUEST zu senden
    2010-06-24 17:05:47 Fehler SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Timeout: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Timeout
    2010-06-24 17:08:43 Erfolgreich BAPI-Response war eine Struktur des Typs BAPIRET2
    2010-06-24 17:08:43 Erfolgreich TYPE='S', Message (ID:/stzh/messages, NUMBER:000): "I:/stzh/messages:000 Beleg wurde erfolgreich gebucht", LOG_NO:, LOG_MSG_NO:000000 (PARAMETER:, ROW:0, FIELD:, SYSTEM:D70450)
    2010-06-24 17:08:43 Erfolgreich BAPI erfolgreich ausgeführt
    2010-06-24 17:08:43 Erfolgreich Commit-Transaktion mit BAPI_TRANSACTION_COMMIT
    2010-06-24 17:08:43 Erfolgreich MP: Verlässt den Modulprozessor
    2010-06-24 17:08:43 Fehler Zustellung der Message an die Anwendung über RFC_http://sap.com/xi/XI/System ist fehlgeschlagen weil: com.sap.aii.af.ra.ms.api.MessageExpiredException: Sync application request expired.. Message wird auf 'fehlgeschlagen' gesetzt
    2010-06-24 17:08:43 Fehler Der Status der Message wurde auf FAIL gesetzt
    2010-06-24 17:08:43 Fehler Rückgabe der synchronen Fehler-Message an rufende Anwendung: com.sap.aii.af.ra.ms.api.MessageExpiredException: Sync application request expired..
    why does the rfc-adapter sends the bapi_transaktion_commit after an soap-error?
    thank you for your help.
    regards
    t.

  • Really Need Some Help with CME 8.6 using IOS as Firewall and Anyconnect VPN on Phones

    Hello,
    I have a 2911 Router with IOS Security and Voice enabled and we are using CME 8.6.  I am using a built-in Anyconnect VPN on 3 phones that are for remote users and thus I needed to enable security zones on the router which works because the remote phones will boot up, get their phone configs and I am able to call those remote phones from an outside line.
    The issue I am having is that when I try to dial a remote phone connected via the VPN through port g0/0 from and internal office phone, i.e., NOT involving the PSTN then there is no audio.  It's as if no audio is going back and forth.  When I take off the security zones from the virtual-template interface and the g0/0 interface then the audio works great and I can reach the phone from internal as I am supposed to.
    Could someone take a peek at my security config and see why audio would not be traveling through the VPN when I have my security zones turned on?
    clock timezone PST -8 0
    clock summer-time PST recurring
    network-clock-participate wic 0 
    network-clock-select 1 T1 0/0/0
    no ipv6 cef
    ip source-route
    ip cef
    ip dhcp excluded-address 192.168.8.1 192.168.8.19
    ip dhcp pool owhvoip
     network 192.168.8.0 255.255.248.0
     default-router 192.168.8.1 
     option 150 ip 192.168.8.1 
     lease 30
    multilink bundle-name authenticated
    isdn switch-type primary-ni
    crypto pki server cme_root
     database level complete
     grant auto
     lifetime certificate 7305
     lifetime ca-certificate 7305
    crypto pki token default removal timeout 0
    crypto pki trustpoint cme_root
     enrollment url http://192.168.8.1:80
     revocation-check none
     rsakeypair cme_root
    crypto pki trustpoint cme_cert
     enrollment url http://192.168.8.1:80
     revocation-check none
    crypto pki trustpoint TP-self-signed-2736782807
     enrollment selfsigned
     subject-name cn=IOS-Self-Signed-Certificate-2736782807
     revocation-check none
     rsakeypair TP-self-signed-2736782807
    voice-card 0
     dspfarm
     dsp services dspfarm
    voice service voip
     allow-connections h323 to h323
     allow-connections h323 to sip
     allow-connections sip to h323
     allow-connections sip to sip
     fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
     vpn-group 1
      vpn-gateway 1 https://66.111.111.111/SSLVPNphone
      vpn-trustpoint 1 trustpoint cme_cert leaf
     vpn-profile 1
      host-id-check disable
    voice class codec 1
     codec preference 1 g711ulaw
    voice class custom-cptone jointone
     dualtone conference
      frequency 600 900
      cadence 300 150 300 100 300 50
    voice class custom-cptone leavetone
     dualtone conference
      frequency 400 800
      cadence 400 50 200 50 200 50
    voice translation-rule 1
     rule 1 /9400/ /502/
     rule 2 /9405/ /215/
     rule 3 /9410/ /500/
    voice translation-rule 2
     rule 1 /.*/ /541999999/
    voice translation-rule 100
     rule 1 /^9/ // type any unknown plan any isdn
    voice translation-profile Inbound_Calls_To_CUE
     translate called 1
    voice translation-profile InternationalType
     translate called 100
    voice translation-profile Local-CLID
     translate calling 2
    license udi pid CISCO2911/K9 sn FTX1641AHX3
    hw-module pvdm 0/0
    hw-module pvdm 0/1
    hw-module sm 1
    username routeradmin password 7 091649040910450B41
    username cmeadmin privilege 15 password 7 03104803040E375F5E4D5D51
    redundancy
    controller T1 0/0/0
     cablelength long 0db
     pri-group timeslots 1-12,24
    class-map type inspect match-any sslvpn
     match protocol tcp
     match protocol udp
     match protocol icmp
    class-map type inspect match-all router-access
     match access-group name router-access
    policy-map type inspect firewall-policy
     class type inspect sslvpn
      inspect 
     class class-default
      drop
    policy-map type inspect outside-to-router-policy
     class type inspect router-access
      inspect 
     class class-default
      drop
    zone security trusted
    zone security internet
    zone-pair security trusted-to-internet source trusted destination internet
     service-policy type inspect firewall-policy
    zone-pair security untrusted-to-trusted source internet destination trusted
     service-policy type inspect outside-to-router-policy
    interface Loopback0
     ip address 192.168.17.1 255.255.248.0
    interface Embedded-Service-Engine0/0
     no ip address
     shutdown
    interface GigabitEthernet0/0
     description Internet
     ip address dhcp
     no ip redirects
     no ip proxy-arp
     zone-member security internet
     duplex auto
     speed auto
    interface GigabitEthernet0/1
     ip address 192.168.8.1 255.255.248.0
     duplex auto
     speed auto
    interface GigabitEthernet0/2
     no ip address
     shutdown
     duplex auto
     speed auto
    interface Serial0/0/0:23
     no ip address
     encapsulation hdlc
     isdn switch-type primary-ni
     isdn incoming-voice voice
     no cdp enable
    interface Integrated-Service-Engine1/0
     ip unnumbered Loopback0
     service-module ip address 192.168.17.2 255.255.248.0
     !Application: CUE Running on NME
     service-module ip default-gateway 192.168.17.1
     no keepalive
    interface Virtual-Template1
     ip unnumbered GigabitEthernet0/0
     zone-member security trusted
    ip local pool SSLVPNPhone_pool 192.168.9.1 192.168.9.5
    ip forward-protocol nd
    ip http server
    ip http authentication local
    no ip http secure-server
    ip http path flash:/cme-gui-8.6.0
    ip route 192.168.17.2 255.255.255.255 Integrated-Service-Engine1/0
    ip access-list extended router-access
     permit tcp any host 66.111.111.111 eq 443
    tftp-server flash:apps31.9-3-1ES26.sbn
    control-plane
    voice-port 0/0/0:23
    voice-port 0/3/0
    voice-port 0/3/1
    mgcp profile default
    sccp local GigabitEthernet0/1
    sccp ccm 192.168.8.1 identifier 1 priority 1 version 7.0 
    sccp
    sccp ccm group 1
     bind interface GigabitEthernet0/1
     associate ccm 1 priority 1
     associate profile 1 register CME-CONF
    dspfarm profile 1 conference  
     codec g729br8
     codec g729r8
     codec g729abr8
     codec g729ar8
     codec g711alaw
     codec g711ulaw
     maximum sessions 4
     associate application SCCP
    dial-peer voice 500 voip
     destination-pattern 5..
     session protocol sipv2
     session target ipv4:192.168.17.2
     dtmf-relay sip-notify
     codec g711ulaw
     no vad
    dial-peer voice 10 pots
     description Incoming Calls To AA
     translation-profile incoming Inbound_Calls_To_CUE
     incoming called-number .
     port 0/0/0:23
    dial-peer voice 20 pots
     description local 10 digit dialing
     translation-profile outgoing Local-CLID
     destination-pattern 9[2-9].........
     incoming called-number .
     port 0/0/0:23
     forward-digits 10
    dial-peer voice 30 pots
     description long distance dialing
     translation-profile outgoing Local-CLID
     destination-pattern 91..........
     incoming called-number .
     port 0/0/0:23
     forward-digits 11
    dial-peer voice 40 pots
     description 911
     destination-pattern 911
     port 0/0/0:23
     forward-digits all
    dial-peer voice 45 pots
     description 9911
     destination-pattern 9911
     port 0/0/0:23
     forward-digits 3
    dial-peer voice 50 pots
     description international dialing
     translation-profile outgoing InternationalType
     destination-pattern 9T
     incoming called-number .
     port 0/0/0:23
    dial-peer voice 650 pots
     huntstop
     destination-pattern 650
     fax rate disable
     port 0/3/0
    gatekeeper
     shutdown
    telephony-service
     protocol mode ipv4
     sdspfarm units 5
     sdspfarm tag 1 CME-CONF
     conference hardware
     moh-file-buffer 90
     no auto-reg-ephone
     authentication credential cmeadmin tshbavsp$$4
     max-ephones 50
     max-dn 200
     ip source-address 192.168.8.1 port 2000
     service dnis dir-lookup
     timeouts transfer-recall 30
     system message Oregon's Wild Harvest
     url services http://192.168.17.2/voiceview/common/login.do 
     url authentication http://192.168.8.1/CCMCIP/authenticate.asp  
     cnf-file location flash:
     cnf-file perphone
     load 7931 SCCP31.9-3-1SR4-1S.loads
     load 7936 cmterm_7936.3-3-21-0.bin
     load 7942 SCCP42.9-3-1SR4-1S.loads
     load 7962 SCCP42.9-4-2-1S.loads
     time-zone 5
     time-format 24
     voicemail 500
     max-conferences 8 gain -6
     call-park system application
     call-forward pattern .T
     moh moh.wav
     web admin system name cmeadmin secret 5 $1$60ro$u.0r/cno/OD2JmtvPq4w9.
     dn-webedit 
     transfer-digit-collect orig-call
     transfer-system full-consult
     transfer-pattern .T
     fac standard
     create cnf-files version-stamp Jan 01 2002 00:00:00
    ephone-template  1
     softkeys connected  Hold Park Confrn Trnsfer Endcall ConfList TrnsfVM
     button-layout 7931 2
    ephone-template  2
     softkeys idle  Dnd Gpickup Pickup Mobility
     softkeys connected  Hold Park Confrn Mobility Trnsfer TrnsfVM
     button-layout 7931 2
    ephone-dn  1  dual-line
     number 200
     label Lisa
     name Lisa Ziomkowsky
     call-forward busy 500
     call-forward noan 500 timeout 10
    ephone-dn  2  dual-line
     number 201
     label Dylan
     name Dylan Elmer
     call-forward busy 500
     call-forward noan 500 timeout 12
    ephone-dn  3  dual-line
     number 202
     label Kimberly
     name Kimberly Krueger
     call-forward busy 500
     call-forward noan 500 timeout 10
    ephone-dn  4  dual-line
     number 203
     label Randy
     name Randy Buresh
     mobility
     snr calling-number local
     snr 915035042317 delay 5 timeout 15 cfwd-noan 500
     call-forward busy 500
     call-forward noan 500 timeout 12
    ephone-dn  5  dual-line
     number 204
     label Mark
     name Mark McBride
     call-forward busy 500
     call-forward noan 500 timeout 10
    ephone-dn  6  dual-line
     number 205
     label Susan
     name Susan Sundin
     call-forward busy 500
     call-forward noan 500 timeout 10
    ephone-dn  7  dual-line
     number 206
     label Rebecca
     name Rebecca Vaught
     call-forward busy 500
     call-forward noan 500 timeout 10
    ephone-dn  8  dual-line
     number 207
     label Ronnda
     name Ronnda Daniels
     call-forward busy 500
     call-forward noan 500 timeout 10
    ephone-dn  9  dual-line
     number 208
     label Matthew
     name Matthew Creswell
     call-forward busy 500
     call-forward noan 500 timeout 10
    ephone-dn  10  dual-line
     number 209
     label Nate
     name Nate Couture
     call-forward busy 500
     call-forward noan 500 timeout 10
    ephone-dn  11  dual-line
     number 210
     label Sarah
     name Sarah Smith
     call-forward busy 500
     call-forward noan 500 timeout 10
    ephone-dn  12  dual-line
     number 211
     label Janis
     name Janis McFerren
     call-forward busy 500
     call-forward noan 500 timeout 12
    ephone-dn  13  dual-line
     number 212
     label Val
     name Val McBride
     call-forward busy 500
     call-forward noan 500 timeout 10
    ephone-dn  14  dual-line
     number 213
     label Shorty
     name Arlene Haugen
     call-forward busy 500
     call-forward noan 500 timeout 10
    ephone-dn  15  dual-line
     number 214
     label Ruta
     name Ruta Wells
     call-forward busy 500
     call-forward noan 500 timeout 10
    ephone-dn  16  dual-line
     number 215
     label 5415489405
     name OWH Sales
     call-forward busy 500
     call-forward noan 500 timeout 12
    ephone-dn  17  dual-line
     number 216
     call-forward busy 500
     call-forward noan 500 timeout 10
    ephone-dn  18  dual-line
     number 217
     call-forward busy 500
     call-forward noan 500 timeout 12
    ephone-dn  19  dual-line
     number 218
     call-forward busy 500
     call-forward noan 500 timeout 12
    ephone-dn  20  dual-line
     number 219
     call-forward busy 500
     call-forward noan 500 timeout 12
    ephone-dn  21  dual-line
     number 220
     call-forward busy 500
     call-forward noan 500 timeout 10
    ephone-dn  22  dual-line
     number 221
     call-forward busy 500
     call-forward noan 500 timeout 10
    ephone-dn  23  dual-line
     number 222
     label Pam
     name Pam Buresh
     call-forward busy 500
     call-forward noan 500 timeout 12
    ephone-dn  24  dual-line
     number 223
     call-forward busy 500
     call-forward noan 500 timeout 12
    ephone-dn  25  dual-line
     number 224
     call-forward busy 500
     call-forward noan 500 timeout 12
    ephone-dn  26  dual-line
     number 225
     label Elaine
     name Elaine Mahan
     call-forward busy 500
     call-forward noan 500 timeout 10
    ephone-dn  27  octo-line
     number 250
     label Shipping
     name Shipping
    ephone-dn  28  dual-line
     number 251
     label Eli
     name Eli Nourse
     call-forward busy 500
     call-forward noan 500 timeout 10
    ephone-dn  29  dual-line
     number 252
    ephone-dn  30  dual-line
     number 253
    ephone-dn  31  octo-line
     number 100
     label Customer Service
     name Customer Service
     call-forward busy 500
     call-forward noan 500 timeout 12
    ephone-dn  32  octo-line
     number 101
     label Sales
     name Sales
     call-forward busy 214
     call-forward noan 214 timeout 12
    ephone-dn  33  dual-line
     number 260
     label Conference Room
     name Conference Room
     call-forward busy 100
     call-forward noan 100 timeout 12
    ephone-dn  100
     number 300
     park-slot timeout 20 limit 2 recall
     description Park Slot For All Company
    ephone-dn  101
     number 301
     park-slot timeout 20 limit 2 recall
     description Park Slot for All Company
    ephone-dn  102
     number 302
     park-slot timeout 20 limit 2 recall
     description Park Slot for All Company
    ephone-dn  103
     number 700
     name All Company Paging
     paging ip 239.1.1.10 port 2000
    ephone-dn  104
     number 8000...
     mwi on
    ephone-dn  105
     number 8001...
     mwi off
    ephone-dn  106  octo-line
     number A00
     description ad-hoc conferencing
     conference ad-hoc
    ephone-dn  107  octo-line
     number A01
     description ad-hoc conferencing
     conference ad-hoc
    ephone-dn  108  octo-line
     number A02
     description ad-hoc conferencing
     conference ad-hoc
    ephone  1
     device-security-mode none
     mac-address 001F.CA34.88AE
     ephone-template 1
     max-calls-per-button 2
     paging-dn 103
     type 7931
     button  1:2 2:31
    ephone  2
     device-security-mode none
     mac-address 001F.CA34.8A03
     ephone-template 1
     max-calls-per-button 2
     paging-dn 103
     type 7931
     button  1:12
    ephone  3
     device-security-mode none
     mac-address 001F.CA34.898B
     ephone-template 1
     max-calls-per-button 2
     paging-dn 103
     type 7931
    ephone  4
     device-security-mode none
     mac-address 001F.CA34.893F
     ephone-template 1
     max-calls-per-button 2
     paging-dn 103
     type 7931
    ephone  5
     device-security-mode none
     mac-address 001F.CA34.8A71
     ephone-template 1
     max-calls-per-button 2
     username "susan"
     paging-dn 103
     type 7931
     button  1:6
    ephone  6
     device-security-mode none
     mac-address 001F.CA34.8871
     ephone-template 1
     max-calls-per-button 2
     paging-dn 103
     type 7931
     button  1:7 2:31 3:32
    ephone  7
     device-security-mode none
     mac-address 001F.CA34.8998
     ephone-template 1
     max-calls-per-button 2
     username "matthew"
     paging-dn 103
     type 7931
     button  1:9
    ephone  8
     device-security-mode none
     mac-address 001F.CA36.8787
     ephone-template 1
     max-calls-per-button 2
     username "nate"
     paging-dn 103
     type 7931
     button  1:10
    ephone  9
     device-security-mode none
     mac-address 001F.CA34.8805
     ephone-template 1
     max-calls-per-button 2
     paging-dn 103
     type 7931
     button  1:5
    ephone  10
     device-security-mode none
     mac-address 001F.CA34.880C
     ephone-template 1
     max-calls-per-button 2
     paging-dn 103
     type 7931
     button  1:14
    ephone  11
     device-security-mode none
     mac-address 001F.CA34.8935
     ephone-template 1
     max-calls-per-button 2
     paging-dn 103
     type 7931
     button  1:3
    ephone  12
     device-security-mode none
     mac-address 001F.CA34.8995
     ephone-template 1
     max-calls-per-button 2
     paging-dn 103
     type 7931
     button  1:8 2:31
    ephone  13
     device-security-mode none
     mac-address 0021.5504.1796
     ephone-template 2
     max-calls-per-button 2
     paging-dn 103
     type 7931
     button  1:4
    ephone  14
     device-security-mode none
     mac-address 001F.CA34.88F7
     ephone-template 1
     max-calls-per-button 2
     paging-dn 103
     type 7931
     button  1:23
    ephone  15
     device-security-mode none
     mac-address 001F.CA34.8894
     ephone-template 1
     max-calls-per-button 2
     paging-dn 103
     type 7931
     button  1:26
    ephone  16
     device-security-mode none
     mac-address 001F.CA34.8869
     ephone-template 1
     max-calls-per-button 2
     paging-dn 103
     type 7931
     button  1:28 2:27
    ephone  17
     device-security-mode none
     mac-address 001F.CA34.885F
     ephone-template 1
     max-calls-per-button 2
     paging-dn 103
     type 7931
     button  1:11
    ephone  18
     device-security-mode none
     mac-address 001F.CA34.893C
     ephone-template 1
     max-calls-per-button 2
     paging-dn 103
     type 7931
     button  1:27
    ephone  19
     device-security-mode none
     mac-address 001F.CA34.8873
     ephone-template 1
     max-calls-per-button 2
     paging-dn 103
     type 7931
     button  1:27
    ephone  20
     device-security-mode none
     mac-address A456.3040.B7DD
     paging-dn 103
     type 7942
     vpn-group 1
     vpn-profile 1
     button  1:13
    ephone  21
     device-security-mode none
     mac-address A456.30BA.5474
     paging-dn 103
     type 7942
     vpn-group 1
     vpn-profile 1
     button  1:15 2:16 3:32
    ephone  22
     device-security-mode none
     mac-address A456.3040.B72E
     paging-dn 103
     type 7942
     vpn-group 1
     vpn-profile 1
     button  1:1
    ephone  23
     device-security-mode none
     mac-address 00E0.75F3.D1D9
     paging-dn 103
     type 7936
     button  1:33
    line con 0
    line aux 0
    line 2
     no activation-character
     no exec
     transport preferred none
     transport input all
     transport output pad telnet rlogin lapb-ta mop udptn v120 ssh
     stopbits 1
    line 67
     no activation-character
     no exec
     transport preferred none
     transport input all
     transport output pad telnet rlogin lapb-ta mop udptn v120 ssh
    line vty 0 4
     transport input all
    scheduler allocate 20000 1000
    ntp master
    ntp update-calendar
    ntp server 216.228.192.69
    webvpn gateway sslvpn_gw
     ip address 66.111.111.111 port 443  
     ssl encryption 3des-sha1 aes-sha1
     ssl trustpoint cme_cert
     inservice
    webvpn context sslvpn_context
     ssl encryption 3des-sha1 aes-sha1
     ssl authenticate verify all
     policy group SSLVPNphone
       functions svc-enabled
       hide-url-bar
       svc address-pool "SSLVPNPhone_pool" netmask 255.255.248.0
       svc default-domain "bendbroadband.com"
     virtual-template 1
     default-group-policy SSLVPNphone
     gateway sslvpn_gw domain SSLVPNphone
     authentication certificate
     ca trustpoint cme_root
     inservice
    end

    I think your ACL could be the culprit.
    ip access-list extended router-access
     permit tcp any host 66.111.111.111 eq 443
    Would you be able to change the entry to permit ip any any (just for testing purpose) and then test to see if the calls function properly.  If they work fine then we know that we need to open som ports there.
    Please remember to select a correct answer and rate helpful posts

  • Problem in File to IDOC Scenario

    Hi,
    I am trying to test the demo example for Flight Booking using the "File Sender to IDoc" Scenario. I have done all the settings. As a last step after I copy the file in
    [XI-hostname]\sapmnt\trans\tmp\fileadapter\group[XX] as per the Demo example guide and activate the changes for File_Sender communication channel, no action is triggered.
    The file remains in the directory. When I want to see if my adapter is fine and I check the Adapter Lists in the Adapter Monitoring, it shows only JPR Adapter and that too in RED.
    Then I check the tracefiles and find this error.
    Date : 04/05/2006
    Time : 16:44:52:264
    Category : /Applications/ExchangeInfrastructure/Directory
    Message ID : 00B0D03E9B4F005A0000000D000001F4000410AB0985C603
    Severity : Error
    Location : XIDIR.com.sap.aii.ibdir.server.abapcache.ErrorHandler
    Source Name : /Applications/ExchangeInfrastructure/Directory
    Thread : SAPEngine_Application_Thread[impl:3]_3
    Message : Failure at Cache-Refresh data consumption !!!
    <?xml version="1.0" encoding="UTF-8"?>
    <CacheRefreshError>
      <EngineType>AE</EngineType>
      <EngineName>af.aba.singdemo1</EngineName>
      <RefreshMode>C</RefreshMode>
      <Channel>
        <PartyName></PartyName>
        <ServiceName>XI_LEGACY_BS_00</ServiceName>
        <ChannelName>File_Sender</ChannelName>
        <ChannelObjectId>838401f3335236bbadd7086c6711b070</ChannelObjectId>
        <ChannelError>
          <Message>
            Could not parse Channel 'File_Sender'(ObjectId: 838401f3335236bbadd7086c6711b070) AdapterType: File|http://sap.com/xi/XI/System|3b787a8035c111d6bbe0efe50a1145a5:
          </Message>
          <Trace>
            com.sap.aii.af.service.cpa.CPAException: Schema not available for File|3b787a8035c111d6bbe0efe50a1145a5|http://sap.com/xi/XI/System.
         at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataSAXHandler.endElement(DirectoryDataSAXHandler.java:262)
         at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler.endElement(SAXDocHandler.java:154)
         at com.sap.engine.lib.xml.parser.XMLParser.scanEndTag(XMLParser.java:1826)
         at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1722)
         at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2298)
         at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1719)
         at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2701)
         at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:162)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:126)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:136)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:209)
         at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:270)
         at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:331)
         at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
         at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
         at javax.xml.parsers.SAXParser.parse(SAXParser.java:143)
         at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataParser.updateCentralCache(DirectoryDataParser.java:54)
         at com.sap.aii.af.service.cpa.impl.cache.CacheManager.updateCacheWithDirectoryData(CacheManager.java:713)
         at com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(CacheManager.java:595)
         at com.sap.aii.af.service.cpa.impl.cache.CacheManager$CacheUpdateRunnable.run(CacheManager.java:440)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)
           </Trace>
        </ChannelError>
      </Channel>
    </CacheRefreshError>
    Datasource : 48696150:E:\usr\sap\ABA\DVEBMGS04\j2ee\cluster\server0\log\applications.log
    Application : sap.com/com.sap.xi.directory
    Argument Objs :
    Arguments :
    Dsr Component : singdemo1_ABA_48696150
    Dsr Transaction : 72d10590c48011da8a7100b0d03e9b4f
    Dsr User : Guest
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 0
    Relatives : XIDIR.com.sap.aii.ibdir.server.abapcache.ErrorHandler
    Resource Bundlename :
    Session : 3816
    Source : /Applications/ExchangeInfrastructure/Directory
    ThreadObject : SAPEngine_Application_Thread[impl:3]_3
    Transaction : SAP J2EE Engine JTA Transaction : [2ffffffe7b5600a31]
    User : XIAFUSER
    Any help will be great.
    Regards,
    Shubham

    Hi Manish,
    I updated the same and now when I activate the changes in my File_Sender communication channel its still not working.
    I checked the Message Monitoring and the message fails to get delivered.
    Here is the Message Audit Log.
    2006-04-11 13:21:51 Success Channel File_Sender: Send binary file "
    singdemo1\sapmnt\trans\tmp\fileadapter\group00\Booking00.xml". Size 526 with QoS EO
    2006-04-11 13:21:54 Success Application attempting to send an XI message asynchronously using connection AFW.
    2006-04-11 13:21:55 Success Trying to put the message into the send queue.
    2006-04-11 13:21:56 Success Message successfully put into the queue.
    2006-04-11 13:21:56 Success The application sent the message asynchronously using connection AFW. Returning to application.
    2006-04-11 13:21:56 Success Confirmation mode test found. File will be resent next time
    2006-04-11 13:21:56 Success The message was successfully retrieved from the send queue.
    2006-04-11 13:21:57 Success The message status set to DLNG.
    2006-04-11 13:23:01 Error Transmitting the message to endpoint http://singdemo1:8004/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500 : Timeout.
    2006-04-11 13:23:03 Success The asynchronous message was successfully scheduled to be delivered at Tue Apr 11 13:28:01 GMT+08:00 2006.
    2006-04-11 13:23:06 Success The message status set to WAIT.
    2006-04-11 13:28:02 Success Retrying to send message. Retry: 1
    2006-04-11 13:28:02 Success The message was successfully retrieved from the send queue.
    2006-04-11 13:28:02 Success The message status set to DLNG.
    2006-04-11 13:29:04 Error Transmitting the message to endpoint http://singdemo1:8004/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500 : Timeout.
    2006-04-11 13:29:04 Success The asynchronous message was successfully scheduled to be delivered at Tue Apr 11 13:34:04 GMT+08:00 2006.
    2006-04-11 13:29:04 Success The message status set to WAIT.
    2006-04-11 13:34:12 Success Retrying to send message. Retry: 2
    2006-04-11 13:34:12 Success The message was successfully retrieved from the send queue.
    2006-04-11 13:34:12 Success The message status set to DLNG.
    2006-04-11 13:35:15 Error Transmitting the message to endpoint http://singdemo1:8004/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500 : Timeout.
    2006-04-11 13:35:15 Success The asynchronous message was successfully scheduled to be delivered at Tue Apr 11 13:40:15 GMT+08:00 2006.
    2006-04-11 13:35:15 Success The message status set to WAIT.
    2006-04-11 13:40:15 Success Retrying to send message. Retry: 3
    2006-04-11 13:40:15 Success The message was successfully retrieved from the send queue.
    2006-04-11 13:40:15 Success The message status set to DLNG.
    2006-04-11 13:41:17 Error Transmitting the message to endpoint http://singdemo1:8004/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500 : Timeout.
    2006-04-11 13:41:17 Error The message status set to NDLV.
    What can be the problems?
    Regards,
    Shubham

  • Js query cycle, driving me round the bend

    Please can someone give their knowledge on what im doing wrong here. im trying to add a simple cycle fade using javascript.
    Im trying to add it to a dynamic site im updating previously written using php. The file im altering is a header (inc.php file) section included in a main.php file.
    Heres the code im editing.
    <?
    #  project           : PHPBazar
    #  filename          : header.inc
    #  last modified by  :
    #  e-mail            : [email protected]
    #  purpose           : Header File
    #  Processing Time Start
    $proctime_start=microtime();
    #  HTML Header Start
    ?>
    <!-- Header Start -->
    <html>
    <head>
      <title>Historic-Racer.com</title>
      <link rel="stylesheet" type="text/css" href="<? echo $STYLE;?>">
      <? echo "$lang_metatag\n"; ?>
      <meta http-equiv="Author" content="SmartISoft">
      <meta name="robots" content="index, follow">
      <meta name="revisit-after" content="20 days">
      <link rel="StyleSheet" href="mainstyle.css" type="text/css">
    <script type="text/javascript" src="js/jquery.cycle.all.js"></script>
    <script type="text/javascript" src="js/jquery.easing.compatibility.js"></script>
    <script type="text/javascript" src="js/jquery-1.6.4.js"></script>
    <script type="text/javascript">
    $(function() {
    $('.head').cycle((;
              fx: 'fade',                              
              speed: 500,
              timeout: 2000,
              pause: true
    </script>
      </head>
    <body>
    <div class="head">
    <img src="../images/logo.png" />
    <img src="../images/hrdm_logo.png" />
    </div>
    </body>
    <!-- Header End -->
    Any help is much appreciated
    Andy
    www.andybarrington.com

    Just report them and save yourself the hassle - that will get a quick response if you live in the USA and many other places I am sure.  The unsubscribe laws are pretty clear with no room for interpretation.
    I love my purple screen, 1/2 day battery, sketchy touch screen and $800 price tag - I call it my Lumia 900

  • HTTP time out Error in BPM.....

    Hi
    Error Description:
    We have created a Sync-Async Bridge BPM scenario in XI.
    In the BPM scenario we are calling the web service, and if the response from the web service is an error message then we have retry in a loop up to 24 times after wait for every 1 min.
    We are sending the data to the web service using a proxy created in the R/3 system.
    We are getting the time out error in the R/3 system. 
    We have changed the following parameters in XI.
    In SXMB_ADM of XI we have set the value for the following parameter.
    Category                      parameter                                                                    current value
    SA_COMM                    CHECK_FOR_ASYNC_RESPONSE_TIMEOUT                120
    In SXMB_ADM of R/3 we have set the value for the following parameter.
    Category                      parameter                                                                    current value
    RUNTIME                      HTTP_TIMEOUT                                                            120
    When we put the value as 120 for the above parameters and we try for 2 times in the BPM process, then it is sending the response back to the R/3 system after completing the whole BPM process.
    But when we increase the no of retries in the BPM process then it is not sending the response back to the R/3 system in the same way, at that time we are getting the error in SXMB_MONI of R/3 system as given below.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    -   <!--
        Inbound Message
      -->
    - <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
      <SAP:Context />
      <SAP:Code p1="500" p2="Timeout" p3="" p4="">HTTP.HTTP_STATUS_CODE_NEQ_OK</SAP:Code>
      <SAP:Text language="EN">HTTP status code 500 : Timeout</SAP:Text>
      </SAP:ErrorHeader>
    Please provide the solution for the same.
    Many Thanks
    Rinku Gangwani

    Hi Prateek,
    Thanks for your replay. I am able to open the URL from XI/PI.
    I tried by testing the same URL by using XI 3.0, its working fine and i am getting required data, but in PI 7.1 i am getting an error.
    Error is:
    In MONI:
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection refused: connect
    In RWB:
    Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out: connect
    What could be the reason?
    Regards,
    Venu

Maybe you are looking for

  • Please help --Error in insert into Statement

    Error in insert into statement while connecting to ms-access. import java.sql.*; public class stupid8      public stupid8()           try{                Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");                Connection con=DriverManager.getCo

  • LockBox - Not able to clear customer invoice with partial payment

    Importing LB data using FBL2. I can successfully clear full payment. I have tolerance group null for customer setup as below. When I try even a few cents below full invoice amount it posts, but doesn't clear. The account for Over/Underpayments and Un

  • Java.lang.NullPointerException at oracle.jbo.uicli.binding.JUCtrlListBinding.findOrCreateLOVDialogIteratorBinding

    Our application is developed using JDev Version 11.1.2.1.0.. We have an 'inputComboboxListOfValues' component with the following code: The source code from the page is hte follwoing:   <af:inputComboboxListOfValues id="TypeLOVId" autoSubmit="true"   

  • Database commit on each instance created

    Hi I am new to BPEL, and I have a requirement as follows: 1. Read a csv/text file through file adapter 2. For each row from the file, using the DB adapter, insert data into a tableA. 3. Select the data inserted in step2, and depending on the value, d

  • Sony XDCAM Viewer

    Is there a version of Sony XDCAM viewer that will work with a an iMac G5?