SIP/2.0 400 Bad Request - 'Malformed/Missing Contact field'

I set up a trunk between Avaya and CUCM but when I call from Avaya to PSTN a receive the error "SIP/2.0 400 Bad Request - 'Malformed/Missing Contact field' (what does it mean????)
This is my scenario:
Avaya (SIP) -> CUCM -> (SIP) Voice Gateway
This the log extract from the CUCM:
INVITE sip:[email protected] SIP/2.0
From: "Test<Australia>" <sip:[email protected]>;tag=066f4f88a5ae31ddb84f9871ca00
To: sip:[email protected]
Call-ID: 066f4f88a5ae31deb84f9871ca00
CSeq: 1 INVITE
Max-Forwards: 71
Route: <sip:172.30.3.252;lr;phase=terminating;transport=tcp>
Record-Route: <sip:172.32.201.208;lr;transport=tcp>
Via: SIP/2.0/TCP 172.32.201.208;branch=z9hG4bK066f4f88a5ae31dfb84f9871ca00
User-Agent: Avaya CM/R015x.02.1.016.4
Supported: timer, replaces, join, histinfo, 100rel
Allow: INVITE, CANCEL, BYE, ACK, PRACK, SUBSCRIBE, NOTIFY, REFER, OPTIONS, INFO, PUBLISH
Contact: "Test<Australia>" <sip:[email protected];transport=tcp>
Session-Expires: 1200;refresher=uac
Min-SE: 1200
P-Asserted-Identity: "Test<Australia>" <sip:[email protected]>
Content-Type: application/sdp
History-Info: <sip:[email protected]>;index=1
History-Info: "435" <sip:[email protected]>;index=1.1
Alert-Info: <cid:[email protected]>;avaya-cm-alert-type=internal
Content-Length: 252
v=0
o=- 1 1 IN IP4 172.32.201.208
s=-
c=IN IP4 172.32.201.203
b=AS:64
t=0 0
m=audio 52284 RTP/AVP 18 0 8 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=ptime:30
INVITE sip:[email protected] SIP/2.0
From: "Test<Australia>" <sip:[email protected]>;tag=066f4f88a5ae31ddb84f9871ca00
To: sip:[email protected]
Call-ID: 066f4f88a5ae31deb84f9871ca00
CSeq: 2 INVITE
Max-Forwards: 71
Route: <sip:172.30.3.252;lr;phase=terminating;transport=tcp>
Record-Route: <sip:172.32.201.208;lr;transport=tcp>
Via: SIP/2.0/TCP 172.32.201.208;branch=z9hG4bK8066f4f88a5ae31e0b84f9871ca00
User-Agent: Avaya CM/R015x.02.1.016.4
Supported: timer, replaces, join, histinfo, 100rel
Allow: INVITE, CANCEL, BYE, ACK, PRACK, SUBSCRIBE, NOTIFY, REFER, OPTIONS, INFO, PUBLISH
Contact: "Test<Australia>" <sip:[email protected];transport=tcp>
Session-Expires: 1800;refresher=uac
Min-SE: 1800
P-Asserted-Identity: "Test<Australia>" <sip:[email protected]>
Content-Type: application/sdp
History-Info: <sip:[email protected]>;index=1
History-Info: "435" <sip:[email protected]>;index=1.1
Alert-Info: <cid:[email protected]>;avaya-cm-alert-type=internal
Content-Length: 252
v=0
o=- 1 1 IN IP4 172.32.201.208
s=-
c=IN IP4 172.32.201.203
b=AS:64
t=0 0
m=audio 52284 RTP/AVP 18 0 8 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=ptime:30
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 172.32.201.208;branch=z9hG4bK8066f4f88a5ae31e0b84f9871ca00
From: "Test<Australia>" <sip:[email protected]>;tag=066f4f88a5ae31ddb84f9871ca00
To: sip:[email protected]
Date: Fri, 08 Nov 2013 05:17:49 GMT
Call-ID: 066f4f88a5ae31deb84f9871ca00
CSeq: 2 INVITE
Allow-Events: presence
Content-Length: 0
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/TCP 172.30.3.252:5060;branch=z9hG4bK26a5845ec88e6
From: "Test<Australia>" <sip:[email protected]>;tag=286974~3b2f3ffb-a349-4309-b2d9-a3867e731109-17833990
To: <sip:[email protected]>
Date: Fri, 08 Nov 2013 05:17:49 GMT
Call-ID: [email protected]
Supported: timer,resource-priority,replaces
Min-SE:  1800
User-Agent: Cisco-CUCM9.1
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Cisco-Guid: 0447840768-0000065536-0000006291-4228062892
Session-Expires:  1800
P-Asserted-Identity: "Test<Australia>" <sip:[email protected]>
Remote-Party-ID: "Test<Australia>" <sip:[email protected]>;party=calling;screen=yes;privacy=off
Contact: <sip:[email protected]:5060;transport=tcp>" <sip:[email protected];transport=tcp>
Max-Forwards: 70
Content-Type: application/sdp
Content-Length: 214
v=0
o=CiscoSystemsCCM-SIP 286974 1 IN IP4 172.30.3.252
s=SIP Call
c=IN IP4 172.30.3.254
t=0 0
m=audio 24336 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
SIP/2.0 400 Bad Request - 'Malformed/Missing Contact field'
Via: SIP/2.0/TCP 172.30.3.252:5060;branch=z9hG4bK26a5845ec88e6
From: "Test<Australia>" <sip:[email protected]>;tag=286974~3b2f3ffb-a349-4309-b2d9-a3867e731109-17833990
To: <sip:[email protected]>;tag=C88DE7C0-313
Call-ID: [email protected]
CSeq: 101 INVITE
Reason: Q.850;cause=100
Content-Length: 0
ACK sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/TCP 172.30.3.252:5060;branch=z9hG4bK26a5845ec88e6
From: "Test<Australia>" <sip:[email protected]>;tag=286974~3b2f3ffb-a349-4309-b2d9-a3867e731109-17833990
To: <sip:[email protected]>;tag=C88DE7C0-313
Date: Fri, 08 Nov 2013 05:17:49 GMT
Call-ID: [email protected]
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence
Content-Length: 0
SIP/2.0 500 Internal Server Error
Via: SIP/2.0/TCP 172.32.201.208;branch=z9hG4bK8066f4f88a5ae31e0b84f9871ca00
From: "Test<Australia>" <sip:[email protected]>;tag=066f4f88a5ae31ddb84f9871ca00
To: sip:[email protected];tag=286973~3b2f3ffb-a349-4309-b2d9-a3867e731109-17833987
Date: Fri, 08 Nov 2013 05:17:49 GMT
Call-ID: 066f4f88a5ae31deb84f9871ca00
CSeq: 2 INVITE
Allow-Events: presence
Reason: Q.850;cause=100
Content-Length: 0
ACK sip:[email protected] SIP/2.0
From: "Test<Australia>" <sip:[email protected]>;tag=066f4f88a5ae31ddb84f9871ca00
To: sip:[email protected];tag=286973~3b2f3ffb-a349-4309-b2d9-a3867e731109-17833987
Call-ID: 066f4f88a5ae31deb84f9871ca00
Via: SIP/2.0/TCP 172.32.201.208;branch=z9hG4bK8066f4f88a5ae31e0b84f9871ca00
CSeq: 2 ACK
Max-Forwards: 70
Route: <sip:172.30.3.252;lr;phase=terminating;transport=tcp>
User-Agent: Avaya CM/R015x.02.1.016.4
Content-Length: 0

you are sending From:
Contact: "
,as the contact, towards your SIP voice gateway.  I dont know where that comes from but 092004131 is definitely not a Melbourne number (strip the 0 off).
There is a contact in there twice, with two IP addresses, the original one from avaya is:
sip:[email protected]
check this post out.
https://supportforums.cisco.com/message/3810453#3810453
=============================
Please remember to rate useful posts, by clicking on the stars below.
=============================

Similar Messages

  • SIP/2.0 400 Bad Request - 'Malformed/Missing URL'

    I have a problem with inbounds calls from an IP PBX to a callmanager 7.X. The call can not be stablished. This is the capture log of the call
    ***************************** SIP message buffer start *****************************
    INVITE sip:172.24.164.7 SIP/2.0
    Via: SIP/2.0/UDP 10.151.100.12:5060;rport;branch=z9hG4bKEPSVBUS863e8efa-5b23-4053-89c5-67c08916ac85
    To:
    From: ;tag=13946664875f3f5b48-2149-4cab-9f44-32090d7cf876
    CSeq: 487 INVITE
    Call-ID: [email protected]ygi-con...
    Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, NOTIFY, REFER, MESSAGE, UPDATE
    Contact:
    Content-Type: application/sdp
    Supported: replaces, norefersub
    User-Agent: Epygi Quadro SIP User Agent/v5.3.2 (MIDIGW)
    Max-Forwards: 70
    Content-Length: 390
    v=0
    o=- 170 395 IN IP4 10.151.100.12
    s=-
    c=IN IP4 10.151.100.12
    t=0 0
    m=audio 6052 RTP/AVP 0 8 96 97 2 98 18 102 101
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:96 G726-16/8000
    a=rtpmap:97 G726-24/8000
    a=rtpmap:2 G726-32/8000
    a=rtpmap:98 G726-40/8000
    a=rtpmap:18 G729/8000
    a=fmtp:18 annexb=no
    a=rtpmap:102 iLBC/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-15
    ***************************** SIP message buffer end ******************************
    13:57:05 Receive SIP message # (31/03/2014 18:57:05:315 GMT) # UDP # 494 bytes # buff size 1 # from: 172.24.164.7:5060 # to: 10.151.100.12:5060
    ***************************** SIP message buffer start *****************************
    SIP/2.0 400 Bad Request - 'Malformed/Missing URL'
    Reason: Q.850;cause=100
    Date: Mon, 31 Mar 2014 18:57:17 GMT
    From: ;tag=13946664875f3f5b48-2149-4cab-9f44-32090d7cf876
    Allow-Events: presence
    Content-Length: 0
    To: ;tag=1787501341
    Call-ID: [email protected]ygi-con...
    Via: SIP/2.0/UDP 10.151.100.12:5060;rport;branch=z9hG4bKEPSVBUS863e8efa-5b23-4053-89c5-67c08916ac85
    CSeq: 487 INVITE
    ***************************** SIP message buffer end ******************************
    13:57:05 TLayer::MsgToTU # Msg type: 400 # TID: 286 # DID: 285
    13:57:05 Try to send SIP message # (31/03/2014 18:57:05:316 GMT) # UDP # 459 bytes # buff size 1 # from: 10.151.100.12:5060 # to: 172.24.164.7:5060
    ***************************** SIP message buffer start *****************************
    ACK sip:172.24.164.7 SIP/2.0
    Via: SIP/2.0/UDP 10.151.100.12:5060;rport;branch=z9hG4bKEPSVBUS863e8efa-5b23-4053-89c5-67c08916ac85
    To: ;tag=1787501341
    From: ;tag=13946664875f3f5b48-2149-4cab-9f44-32090d7cf876
    CSeq: 487 ACK
    Call-ID: [email protected]ygi-con...
    User-Agent: Epygi Quadro SIP User Agent/v5.3.2 (MIDIGW)
    Max-Forwards: 70
    Content-Length: 0
    ***************************** SIP message buffer end ******************************
    13:57:05 SipSessDlg::Inc4xxProc # Got 400 message # OID: 285 # SID: 16249136886150664
    13:57:05 SipSessDlg::ErrorHandling # Error: Negotiation, Move to terminate state # OID: 285 # SID: 16249136886150664
    13:57:05 UA --> CM # ReportError # Error: Negotiation # Sip error: 400 # SID: 16249136886150664
    13:57:05 SipSessDlg::TerminateTransactions # OID: 285 # SIPID: [email protected]ygi-con... # SID: 16249136886150664
    Can anyone help me?

    Hello, did you edit the logs before posting it here? if not, then we are missing the fields in the incoming INVITE message from PBX.
    No phone numbers in the Invite header and From & To fields are also missing.
    Please check with the PBX.
    ***************************** SIP message buffer start *****************************
    INVITE sip:172.24.164.7 SIP/2.0 ----> Number missing here
    Via: SIP/2.0/UDP 10.151.100.12:5060;rport;branch=z9hG4bKEPSVBUS863e8efa-5b23-4053-89c5-67c08916ac85
    To: ----> Number missing here
    From: ;tag=13946664875f3f5b48-2149-4cab-9f44-32090d7cf876 ----> Number missing here
    CSeq: 487 INVITE
    Call-ID: [email protected]ygi-config.loc
    Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, NOTIFY, REFER, MESSAGE, UPDATE
    Contact:
    Content-Type: application/sdp
    Supported: replaces, norefersub
    User-Agent: Epygi Quadro SIP User Agent/v5.3.2 (MIDIGW)
    Max-Forwards: 70
    Content-Length: 390
    v=0
    o=- 170 395 IN IP4 10.151.100.12
    s=-
    c=IN IP4 10.151.100.12
    t=0 0
    m=audio 6052 RTP/AVP 0 8 96 97 2 98 18 102 101
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:96 G726-16/8000
    a=rtpmap:97 G726-24/8000
    a=rtpmap:2 G726-32/8000
    a=rtpmap:98 G726-40/8000
    a=rtpmap:18 G729/8000
    a=fmtp:18 annexb=no
    a=rtpmap:102 iLBC/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-15
    //Suresh
    Please rate all the useful posts

  • SIP 400 Bad Request

    I'm getting a bad request error when attempting to an outbound SIP call on a IP2IP gateway (H323 -> SIP).
    It's a slightly odd configuration as we will only be using this route for outgoing calls only. The only error message I get is:
    //-1/xxxxxxxxxxxx/SIP/Error/sipsdp_add_standard_lines: media_src_address is NULL; c-line is not added
    SIP Invite message:
    Sent:
    INVITE sip:[email protected]:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK11222C
    From: "anonymous" <sip:[email protected]>;tag=404CF30-282
    To: <sip:[email protected]>
    Date: Wed, 16 May 2007 13:09:44 GMT
    Call-ID: [email protected]
    Supported: 100rel,timer
    Min-SE: 1800
    Cisco-Guid: 15103203-2971783453-520093696-2887190163
    User-Agent: Cisco-SIPGateway/IOS-12.x
    Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER
    CSeq: 101 INVITE
    Max-Forwards: 70
    Remote-Party-ID: <sip:[email protected]>;party=calling;screen=yes;privacy=full
    Timestamp: 1179320984
    Contact: <sip:[email protected]:5060>
    Call-Info: <sip:192.168.1.1:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
    Expires: 180
    Allow-Events: telephone-event
    May 16 13:09:44.608 UTC: //-1/xxxxxxxxxxxx/SIP/Info/HandleUdpSocketReads: Msg enqueued for SPI with IP addr: 192.168.1.2:5060
    May 16 13:09:44.608 UTC: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportProcessNWNewConnMsg: context=0x00000000
    May 16 13:09:44.608 UTC: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
    Received:SIP/2.0 400 Bad Request
    Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK11222C
    From: "anonymous" <sip:[email protected]>;tag=404CF30-282
    To: <sip:[email protected]>
    Call-ID: [email protected]
    CSeq: 101 INVITE
    User-Agent: 2N StarGate V-02.20.47
    Allow: INVITE, BYE, ACK, CANCEL, OPTIONS
    Content-Length: 0
    Any ideas?

    For what its worth, I had the same problem from Callmanager to an IOS IPIPGW. I was getting the SIP/2.0 400 Bad Request - 'Malformed/Missing Contact field' error message. Turns out I had mistyped my caller id mask and was sending characters in place of numbers. By correcting it, my problem went away.
    Todd

  • How do I fix a 400 Bad Request or I'm I missing something to make it work.

    Every time I try to connect to Firefox (400 Bad Request). Now I even tried to disconnect and reconnect to Firefox again still the same 400 Bad Request.

    * "Clear the Cache": Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"
    * "Remove the Cookies" from sites causing problems: Tools > Options > Privacy > Cookies: "Show Cookies"
    See also:
    * http://kb.mozillazine.org/Error_loading_websites

  • "The request failed with HTTP Status 400: Bad Request." when running reports

    Hi,
    I installed reporting services and the install went fine.  The Reporting Services are located on a different server.  I can see all the reports in SCCM but when I try to run them I get the "400" error with the following details:
    System.Net.WebException
    The request failed with HTTP status 400: Bad Request.
    Stack Trace:
       at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
       at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.ReportExecutionService.LoadReport2(String Report, String HistoryID)
       at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.<>c__DisplayClass2.<LoadReport>b__0()
       at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.ProxyMethodInvocation.Execute[TReturn](RSExecutionConnection connection, ProxyMethod`1 initialMethod, ProxyMethod`1 retryMethod)
       at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID)
       at Microsoft.Reporting.WinForms.ServerReport.EnsureExecutionSession()
       at Microsoft.Reporting.WinForms.ServerReport.SetParameters(IEnumerable`1 parameters)
       at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ReportViewerWindowsForms.SetParameterValues_DoWork(Object sender, DoWorkEventArgs e)
    I can open the URL from the SCCM server but when I select a report I am unable to select any report options if available.  If no options are availble the report just doesn't run,  I don't get and error if I select "View Report" mutiple
    times.
    If I connect to the Reporting Services site on the computer where it is installed all the reports run fine.
    One thing I have noticed is that when I try to change or add a role assignment for Reporting Services the edited account always reverts back to the default settings and the added Domain user is dropped.
    Thanks

    I reviewed the topic and found a couple of steps I missed the first time around.  I had to "Configure Reports to Use Report Builder 3.0 and setting the "Log on Locally" permission. 
    I then uninstalled the role and reinstalled it.  I am still getting the 400 error.
    When I inspected the SmsAdminUI.log I noticed the Error on the last line 2151811598 (it repeats in the log).  I couldn't find anything specific related to it.  By reading a few "related" Internet posts I came accross a intial setup
    blog that noted some WMI firewall execptions (Async-in, DCOM-in and WMI-in) as require so I checked and they were not allowed on the SCCM server so I allowed them and tested with the same result.  I turned them off again. 
    Here is the tail end of the SmsAdminUI.log
    [19, PID:2684][01/24/2013 16:08:29] :[ReportProxy] - User-specified default Reporting Point [INC-SQL42.deccoinc.net] could not be found, [] is now the default Reporting Point.
    [4, PID:2684][01/24/2013 16:08:30] :[ReportProxy] - User-specified default Reporting Point [INC-SQL42.deccoinc.net] could not be found, [] is now the default Reporting Point.
    [15, PID:2684][01/24/2013 16:08:30] :[ReportProxy] - User-specified default Reporting Point [INC-SQL42.deccoinc.net] could not be found, [] is now the default Reporting Point.
    [1, PID:2684][01/24/2013 19:06:02] :System.Management.ManagementException\r\nNot found \r\n   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
       at System.Management.ManagementObject.Initialize(Boolean getObject)
       at System.Management.ManagementBaseObject.get_wbemObject()
       at System.Management.PropertyData.RefreshPropertyInfo()
       at System.Management.PropertyDataCollection.get_Item(String propertyName)
       at System.Management.ManagementBaseObject.GetPropertyValue(String propertyName)
       at System.Management.ManagementBaseObject.get_Item(String propertyName)
       at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.GetInstance(String objectPath)\r\nManagementException details:
    instance of SMS_ExtendedStatus
     Description = "Error retrieving object FileType=2";
     ErrorCode = 2151811598;
     File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\SspInterface.h";
     Line = 1208;
     Operation = "GetObject";
     ParameterInfo = "SMS_SCI_SysResUse.FileType=2,ItemName=\"[\\\"Display=\\\\\\\\INC-SQL42.deccoinc.net\\\\\\\"]MSWNET:[\\\"SMS_SITE=INC\\\"]\\\\\\\\INC-SQL42.deccoinc.net\\\\,SMS SRS Reporting Point\",ItemType=\"System Resource Usage\",SiteCode=\"INC\"";
     ProviderName = "ExtnProv";
     StatusCode = 2147749890;
    \r\n
    [1, PID:2684][01/24/2013 23:39:14] :System.NullReferenceException\r\nObject reference not set to an instance of an object.\r\n   at Microsoft.ConfigurationManagement.AdminConsole.SmsCustomDialog.get_LocaleIndependentIdentifier()
       at Microsoft.ConfigurationManagement.AdminConsole.ShowDialogTaskHandler.DoTask(NavigationModelNodeBase node, SccmTaskConfiguration sccmTask, PropertyDataUpdated dataUpdatedDelegate, Boolean readOnly)\r\n
    [1, PID:5008][01/25/2013 20:48:00] :System.Management.ManagementException\r\nNot found \r\n   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
       at System.Management.ManagementObject.Initialize(Boolean getObject)
       at System.Management.ManagementBaseObject.get_wbemObject()
       at System.Management.PropertyData.RefreshPropertyInfo()
       at System.Management.PropertyDataCollection.get_Item(String propertyName)
       at System.Management.ManagementBaseObject.GetPropertyValue(String propertyName)
       at System.Management.ManagementBaseObject.get_Item(String propertyName)
       at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.GetInstance(String objectPath)\r\nManagementException details:
    instance of SMS_ExtendedStatus
     Description = "Error retrieving object FileType=2";
     ErrorCode = 2151811598;
     File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\SspInterface.h";
     Line = 1208;
     Operation = "GetObject";
     ParameterInfo = "SMS_SCI_SysResUse.FileType=2,ItemName=\"[\\\"Display=\\\\\\\\INC-SQL42.deccoinc.net\\\\\\\"]MSWNET:[\\\"SMS_SITE=INC\\\"]\\\\\\\\INC-SQL42.deccoinc.net\\\\,SMS SRS Reporting Point\",ItemType=\"System Resource Usage\",SiteCode=\"INC\"";
     ProviderName = "ExtnProv";
     StatusCode = 2147749890;
    \r\n

  • Error: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request

    Hi Gurus,
    i am hardly fighting with this error in Communication Channel Monitoring:
    Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request
    SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request
    This is my scenario.
    I do a File to SOAP Scenario. in SXI_MONITOR everything is fine.
    My CommChan is a SOAP Receiver
    HTTP
    SOAP 1.1
    Central Adapter Engine
    Target URL is https --> i check url for correctness
    Configure User Authentication is checked and username and pw are given and are correct.
    Configure Certificate Authentication is checked are working
    Configure Proxy is checked and Host and port are povided.
    SOAP Action is provided
    In Tab Module
    if have this Processing Sequence
    1     localejbs/AF_Modules/MessageTransformBean     Local Enterprise Bean     transform
    2     sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean     Local Enterprise Bean     1
    and this Module configuration (and only this)
    transform     Transform.ContentType     text/xml;charset=utf-8
    (according to /people/sobhithalaxmi.kata/blog/2009/07/21/cost-free-edi-integration-using-message-transformation-bean)
    As far as i understand that my http header should have Content-Type: text/xml;charset=utf-8 now. I don't understand why Communication Channel Monitoring shows an error according to content TEXT/HTML.
    Can anyone help me with that?
    Is it possible that Transform.ContentType does not work for SOAP Receiver Adapter?
    is there any chance to view the HTTP-Header of the outgoing SOAP Request (with PI Transaction / Java Enironment) to convince myself that the HTTP Header is text/xml?
    Thank you in advance and Best Regards
    Udo

    Hi Thanks for your fast replies.
    The Provider of the Endpoint tells me that he needs text/xml as content-type. When I sent a message to the given Endpoint via SOAP UI I can see in the HTTP LOG of SOAP UI that the Endpoint is also sending text/xml back.
    Below you find the Details log out of the CommChan Monitoring.
    2011-04-29 11:37:45 Information The message status was set to TBDL.
    2011-04-29 11:37:45 Information Retrying to deliver message to the application. Retry: 3
    2011-04-29 11:37:45 Information The message was successfully retrieved from the receive queue.
    2011-04-29 11:37:45 Information The message status was set to DLNG.
    2011-04-29 11:37:45 Information Delivering to channel: getxxxxx_In  <---- name of my SOAP Receiver CommChan
    2011-04-29 11:37:45 Information Transform: using Transform.Class:  $identity
    2011-04-29 11:37:45 Information Transform: transforming the payload ...
    2011-04-29 11:37:45 Information Transform: successfully transformed
    2011-04-29 11:37:45 Information SOAP: request message entering the adapter with user J2EE_GUEST
    2011-04-29 11:37:46 Error SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request
    2011-04-29 11:37:46 Information SOAP: sending a delivery error ack ...
    2011-04-29 11:37:46 Information SOAP: sent a delivery error ack
    2011-04-29 11:37:46 Error SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request
    2011-04-29 11:37:46 Error Adapter Framework caught exception: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request
    2011-04-29 11:37:46 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request.
    2011-04-29 11:37:46 Error The message status was set to NDLV.
    What i am missing is a hint on the Message Transform Bean and a on a successfull sending process.
    What i also tried already:
    i also activated the checkbox "Do not use SOAP Envelop" in CommChan Configuration. The Result you see below (the last log entry is on first line - so read from bottom to top)
    Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request
    error in response
    call completed
    request entering
    Message processing started
    As you can see there is a "call completed" and "error in response" log entry. This is missing in in the first Log. So i guess the error is still in the sending process.
    Installing additional Software on the PI and use them to find out what the HTTP Request is is not possible as system access is very strict and limited :/

  • Invalid request in SOAP Scenario - "HTTP 400 Bad Request"

    Hi,
    By sending request to a Webservice thorugh XI ,I am getting an error as "HTTP 400 Bad Request" in MONI and the response payload looks like this
    "Request Error (invalid_request)
    Your request could not be processed. Request could not be handled 
    This could be caused by a misconfiguration, or possibly a malformed request. 
    For assistance, contact your network support team."
    I copy pasted the request payload in SOAP UI,  there its working fine.I don't know where it goes wrong.
    Please help me in that...
    Thanks & Regards,
    Yuga

    Hi Yugapreetha,
    Error: HTTP 400- Bad Request- ICM_HTTP_CONNECTION_FAILED
    Description: The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.
    Possible Tips: May be because of huge message flow. Related SAP Notes-824554, 906435, 783515, 910649, 706563 If it is because of Queue problems have a look into SMQ2 .
    And also here are a list of possible reasons for your problem with solutions.
    It could be that it cannot find your file adapter.
    1. Have you specified your hostname or IP address? Often the server cannot resolve the ip address for the hostname of your PC.
    2. Is the path and port in the directory the same as the path and port of your file adapter?
    3. Try question 14 (integration engine section)
    /people/mark.finnern/blog/2006/01/12/finally-best-of-sdn-2005
    4. also question 11 (in the same section)
    5. if the avove will not fix it open XI config guide and
    have a look at section
    "Connecting Business Systems with an Integration Engine to the Central Integration Server"
    6. Your error code is 400, so check this link,
    http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
    For http 400 - its a bad request.
    'The request could not be understood by the server due to malformed syntax.'
    If you have the XI trouble shooting guide see from page 54,and also try:
    1.Check that the port really is the ICM HTTP Port (transaction
    SMICM) and not the J2EE port
    2.If the port is wrong, change the pipeline URL in the SLD in
    the business system of the Integration Server
    3.Restart the J2EE Engine to reset the SLD buffer of the
    Adapter Engine
    Source- "XI troubleshooting guide"
    Check out this SAP Note- 824554
    Also this links
    ICM_HTTP_CONNECTION_FAILED
    Cache Refresh~
    https://websmp201.sap-ag.de/~sapdownload/011000358700003163902004E/HowTo_handle_XI_30_Caches.pdf
    Reprocessing failed XI messages:
    /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
    Regards,
    Vinod.

  • INVITE with display-name=""  in Contact header- 400 Bad request from occas

    Hi,
    When a UAC sends an INVITE to OCCAS
    with the Contact header in the form :
    Contact: "" <sip:user@domain>
    OCCAS rejects the message with 400 Bad request.
    The problem comes from display-name = ""
    (proven easily with sipp)
    In the 400 response : X-Bad-Request: Illegal header "Contact"
    It seems that the string "" as display name should be allowed according to rfc 3261:
    display-name = *(token LWS)/ quoted-string
    quoted-string = SWS DQUOTE *(qdtext / quoted-pair ) DQUOTE
    qdtext = LWS / %x21 / %x23-5B / %x5D-7E/ UTF8-NONASCII
    quoted-pair = "\" (%x00-09 / %x0B-0C / %x0E-7F)
    Has anyone encountered the problem?
    regards
    Christophe

    Hi LJ, you may want to post over on the new My Oracle Support Communications Community which is moderated by and responded to by Oracle Support and accessible by Oracle customers. Many new features will be developed for the Community in the coming months, please come and check it out at https://metalink.oracle.com/CSP/ui/index.html
    Regards
    Graham

  • XI's BC Adater (sender)-- 400 Bad Request

    Hi,
    I am trying to send data from SAP-BC to XI. XI will receive this data through XI's-BC Adapter(sender).
    I have defined a routing rule in BC as specified in help.sap.com.
    http://<hostname:50000/MessagingSystem/receive/BcAdapter/BC
    When i test this Flowservice from BC End, i get 400 Bad Request error.
    But when i specify the URL as http://hostname:50000 and test the service, the response code is 200 (success).
    I even tested the URL directly posting in a explorer page and i could see that the message servlet pertaining to BC is active.
    I am not able to understand why is XI-server not able to receive the request that has been posted to the URL
    http://<hostname:50000/MessagingSystem/receive/BcAdapter/BC
    Am i missing any configurations??
    Regards,
    siva Maranani

    hi,
    I was able to get the error details of "400:Bad Request."
    The error is :
    com.sap.aii.af.ra.ms.api.MessageFormatException: got no name/namespace for the payload of the XRFC_DOC_TYPE_ENVELOPE.
    org.xml.sax.SAXexception:got no name/namespace for the payload of the XRFC_DOC_TYPE_ENVELOPE.
    Below is the xmldata, that i am sent to XI:
    <?xml version="1.0" encoding="iso-8859-1"?>
    <sap:Envelope xmlns:sap="urn:sap-com:document:sap" version="1.0">
      <sap:Header xmlns:rfcprop="urn:sap-com:document:sap:rfc:properties">
        <saptr:From xmlns:saptr="urn:sap-com:document:sap:transport">BC</saptr:From>
        <saptr:To xmlns:saptr="urn:sap-com:document:sap:transport">XI</saptr:To>
      </sap:Header>
      <sap:Body>
        <rfc:ZSIVAINSERT xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
          <CARRID>AA<CARRID>
          <CONNID>0017<CONNID/>
          <FLDATE>20040417<FLDATE/>
        </rfc:ZSIVAINSERT>
      </sap:Body>
    </sap:Envelope>
    I do not understand the name/namespace it is looking for. Kindly help me out.
    Regards,
    Siva Maranani

  • Apache as reverse proxy - 400 Bad request

    Hi all,
    I'm configured apache as reverse proxy according to this blog:
    The Reverse Proxy Series -- Part 3: Apache as a reverse-proxy
    When I try to navigate http://testcomp/irj I get "400 - Bad request"
    See exception;
    <i>Message : User Guest, IP address
    Cannot parse the http request. Http error response [400 Bad Request] will be returned. Request is [Host: sapportal:50000
    Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, /
    Accept-Language: en,he;q=0.5
    Accept-Encoding: gzip, deflate
    User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322; FDM; .NET CLR 2.0.50727)
    Max-Forwards: 10
    Via: 1.1 localhost
    X-Forwarded-For: 10.0.0.4
    X-Forwarded-Host: 10.0.0.6
    X-Forwarded-Server: localhost
    Connection: Keep-Alive
    GET /irj HTTP/1.1
    Host: sapportal:50000
    Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, /
    Accept-Language: en,he;q=0.5
    Accept-Encoding: gzip, deflate
    User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322; FDM; .NET CLR 2.0.50727)
    Max-Forwards: 10
    Via: 1.1 localhost
    X-Forwarded-For: 10.0.0.4
    X-Forwarded-Host: 10.0.0.6
    X-Forwarded-Server: localhost
    Connection: Keep-Alive
    com.sap.engine.services.httpserver.exceptions.HttpIllegalArgumentException: Incompatible field content in the MIME header.
         at com.sap.engine.services.httpserver.lib.headers.MimeHeaderField.parse(MimeHeaderField.java:364)
         at com.sap.engine.services.httpserver.lib.headers.MimeHeaders.init(MimeHeaders.java:504)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.initialize(RequestAnalizer.java:196)
         at com.sap.engine.services.httpserver.server.Client.initialize(Client.java:84)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:143)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Severity : Error
    Category :
    Location : com.sap.engine.services.httpserver
    Application :
    Thread : SAPEngine_Application_Thread[impl:3]_32
    Datasource : 9332850:C:usrsapPD9JC00j2eeclusterserver0logdefaultTrace.trc
    Message ID : 000C29EFE9A300570000002D00000B9000043A81D3311894
    Source Name : com.sap.engine.services.httpserver
    Argument Objs :
    Arguments :
    Dsr Component :
    Dsr Transaction : 5359e85066e411dcbf6b000c29efe9a3
    Dsr User :
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 0
    Relatives :
    Resource Bundlename :
    Session : 2
    Source : com.sap.engine.services.httpserver
    ThreadObject : SAPEngine_Application_Thread[impl:3]_32
    Transaction :
    User : Guest</i>
    The lines I added to http.conf
    <i>#Enable reverse-proxying
    ProxyVia on
    ProxyTimeout 600
    #disable forward-proxying
    ProxyRequests Off
    #proxy /irj both ways
    ProxyPass /irj http://sapportal:50000/irj
    ProxyPassReverse /irj http://testcomp/irj
    #proxy /logon both ways
    ProxyPass /logon http://sapportal:50000/logon
    ProxyPassReverse /logon http://testcomp/logon</i>
    I tried with apache version 2.2.3 & 2.0.59 with no success.
    My J2EE/Portal version is 6.17.
    Since this is a testing environment the two computers are under the same workgroup (no domain).
    If I naviagte directly to the portal (without the reverse proxy) everything is working.
    How can I solve it?
    Regards,
    Omri

    Hi Jakub,
    Thanks for the answer.
    It's not working for me...
    I'm attaching my httpd.conf file.
    Also, what apache version do you use?
    Can you send me your post your httpd.conf file?
    Thanks,
    Omri
    httpd.conf
    This is the main Apache HTTP server configuration file.  It contains the
    configuration directives that give the server its instructions.
    See <URL:http://httpd.apache.org/docs/2.2/> for detailed information.
    In particular, see
    <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
    for a discussion of each configuration directive.
    Do NOT simply read the instructions in here without understanding
    what they do.  They're here only as hints or reminders.  If you are unsure
    consult the online docs. You have been warned. 
    Configuration and logfile names: If the filenames you specify for many
    of the server's control files begin with "/" (or "drive:/" for Win32), the
    server will use that explicit path.  If the filenames do not begin
    with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
    with ServerRoot set to "c:/apache" will be interpreted by the
    server as "c:/apache/logs/foo.log".
    NOTE: Where filenames are specified, you must use forward slashes
    instead of backslashes (e.g., "c:/apache" instead of "c:\apache").
    If a drive letter is omitted, the drive on which Apache.exe is located
    will be used by default.  It is recommended that you always supply
    an explicit drive letter in absolute paths, however, to avoid
    confusion.
    ThreadsPerChild: constant number of worker threads in the server process
    MaxRequestsPerChild: maximum  number of requests a server process serves
    ThreadsPerChild 250
    MaxRequestsPerChild  0
    ServerRoot: The top of the directory tree under which the server's
    configuration, error, and log files are kept.
    Do not add a slash at the end of the directory path.  If you point
    ServerRoot at a non-local disk, be sure to point the LockFile directive
    at a local disk.  If you wish to share the same ServerRoot for multiple
    httpd daemons, you will need to change at least LockFile and PidFile.
    ServerRoot "c:/apache"
    Listen: Allows you to bind Apache to specific IP addresses and/or
    ports, instead of the default. See also the <VirtualHost>
    directive.
    Change this to Listen on specific IP addresses as shown below to
    prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
    #Listen 12.34.56.78:80
    Listen 80
    Dynamic Shared Object (DSO) Support
    To be able to use the functionality of a module which was built as a DSO you
    have to place corresponding `LoadModule' lines at this location so the
    directives contained in it are actually available before they are used.
    Statically compiled modules (those listed by `httpd -l') do not need
    to be loaded here.
    Example:
    LoadModule foo_module modules/mod_foo.so
    LoadModule actions_module modules/mod_actions.so
    LoadModule alias_module modules/mod_alias.so
    LoadModule asis_module modules/mod_asis.so
    LoadModule auth_basic_module modules/mod_auth_basic.so
    #LoadModule auth_digest_module modules/mod_auth_digest.so
    #LoadModule authn_anon_module modules/mod_authn_anon.so
    #LoadModule authn_dbm_module modules/mod_authn_dbm.so
    LoadModule authn_default_module modules/mod_authn_default.so
    LoadModule authn_file_module modules/mod_authn_file.so
    #LoadModule authz_dbm_module modules/mod_authz_dbm.so
    LoadModule authz_default_module modules/mod_authz_default.so
    LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
    LoadModule authz_host_module modules/mod_authz_host.so
    LoadModule authz_user_module modules/mod_authz_user.so
    LoadModule autoindex_module modules/mod_autoindex.so
    #LoadModule cern_meta_module modules/mod_cern_meta.so
    LoadModule cgi_module modules/mod_cgi.so
    #LoadModule dav_module modules/mod_dav.so
    #LoadModule dav_fs_module modules/mod_dav_fs.so
    #LoadModule deflate_module modules/mod_deflate.so
    LoadModule dir_module modules/mod_dir.so
    LoadModule env_module modules/mod_env.so
    #LoadModule expires_module modules/mod_expires.so
    #LoadModule file_cache_module modules/mod_file_cache.so
    #LoadModule headers_module modules/mod_headers.so
    LoadModule imagemap_module modules/mod_imagemap.so
    LoadModule include_module modules/mod_include.so
    #LoadModule info_module modules/mod_info.so
    LoadModule isapi_module modules/mod_isapi.so
    LoadModule log_config_module modules/mod_log_config.so
    LoadModule mime_module modules/mod_mime.so
    #LoadModule mime_magic_module modules/mod_mime_magic.so
    <b>LoadModule proxy_module modules/mod_proxy.so</b>
    #LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
    #LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
    #LoadModule proxy_connect_module modules/mod_proxy_connect.so
    <b>LoadModule proxy_http_module modules/mod_proxy_http.so</b>
    #LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
    LoadModule negotiation_module modules/mod_negotiation.so
    #LoadModule rewrite_module modules/mod_rewrite.so
    LoadModule setenvif_module modules/mod_setenvif.so
    #LoadModule speling_module modules/mod_speling.so
    #LoadModule status_module modules/mod_status.so
    #LoadModule unique_id_module modules/mod_unique_id.so
    LoadModule userdir_module modules/mod_userdir.so
    #LoadModule usertrack_module modules/mod_usertrack.so
    #LoadModule vhost_alias_module modules/mod_vhost_alias.so
    #LoadModule ssl_module modules/mod_ssl.so
    'Main' server configuration
    The directives in this section set up the values used by the 'main'
    server, which responds to any requests that aren't handled by a
    <VirtualHost> definition.  These values also provide defaults for
    any <VirtualHost> containers you may define later in the file.
    All of these directives may appear inside <VirtualHost> containers,
    in which case these default settings will be overridden for the
    virtual host being defined.
    ServerAdmin: Your address, where problems with the server should be
    e-mailed.  This address appears on some server-generated pages, such
    as error documents.  e.g. [email protected]
    ServerAdmin @@ServerAdmin@@
    ServerName gives the name and port that the server uses to identify itself.
    This can often be determined automatically, but we recommend you specify
    it explicitly to prevent problems during startup.
    If your host doesn't have a registered DNS name, enter its IP address here.
    ServerName localhost:80
    DocumentRoot: The directory out of which you will serve your
    documents. By default, all requests are taken from this directory, but
    symbolic links and aliases may be used to point to other locations.
    DocumentRoot "c:/apache/htdocs"
    Each directory to which Apache has access can be configured with respect
    to which services and features are allowed and/or disabled in that
    directory (and its subdirectories).
    First, we configure the "default" to be a very restrictive set of
    features. 
    <Directory />
        Options FollowSymLinks
        AllowOverride None
        Order deny,allow
        Deny from all
        Satisfy all
    </Directory>
    Note that from this point forward you must specifically allow
    particular features to be enabled - so if something's not working as
    you might expect, make sure that you have specifically enabled it
    below.
    This should be changed to whatever you set DocumentRoot to.
    <Directory "c:/apache/htdocs">
    Possible values for the Options directive are "None", "All",
    or any combination of:
      Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    Note that "MultiViews" must be named explicitly --- "Options All"
    doesn't give it to you.
    The Options directive is both complicated and important.  Please see
    http://httpd.apache.org/docs/2.2/mod/core.html#options
    for more information.
        Options Indexes FollowSymLinks
    AllowOverride controls what directives may be placed in .htaccess files.
    It can be "All", "None", or any combination of the keywords:
      Options FileInfo AuthConfig Limit
        AllowOverride None
    Controls who can get stuff from this server.
        Order allow,deny
        Allow from all
    </Directory>
    DirectoryIndex: sets the file that Apache will serve if a directory
    is requested.
    <IfModule dir_module>
        DirectoryIndex index.html
    </IfModule>
    The following lines prevent .htaccess and .htpasswd files from being
    viewed by Web clients.
    <FilesMatch "^\.ht">
        Order allow,deny
        Deny from all
    </FilesMatch>
    ErrorLog: The location of the error log file.
    If you do not specify an ErrorLog directive within a <VirtualHost>
    container, error messages relating to that virtual host will be
    logged here.  If you do define an error logfile for a <VirtualHost>
    container, that host's errors will be logged there and not here.
    ErrorLog logs/error.log
    LogLevel: Control the number of messages logged to the error_log.
    Possible values include: debug, info, notice, warn, error, crit,
    alert, emerg.
    LogLevel warn
    <IfModule log_config_module>
    The following directives define some format nicknames for use with
    a CustomLog directive (see below).
        LogFormat "%h %l %u %t \"%r\" %>s %b \"%You need to enable mod_logio.c to use %I and %Oi\" \"%{User-Agent}i\"" combined
        LogFormat "%h %l %u %t \"%r\" %>s %b" common
        <IfModule logio_module>
          LogFormat "%h %l %u %t \"%r\" %>s %b \"%i\" \"%{User-Agent}i\" %I %O" combinedio
        </IfModule>
    The location and format of the access logfile (Common Logfile Format).
    If you do not define any access logfiles within a <VirtualHost>
    container, they will be logged here.  Contrariwise, if you do
    define per-<VirtualHost> access logfiles, transactions will be
    logged therein and not in this file.
        CustomLog logs/access.log common
    If you prefer a logfile with access, agent, and referer information
    (Combined Logfile Format) you can use the following directive.
        #CustomLog logs/access.log combined
    </IfModule>
    <IfModule alias_module>
    Redirect: Allows you to tell clients about documents that used to
    exist in your server's namespace, but do not anymore. The client
    will make a new request for the document at its new location.
    Example:
    Redirect permanent /foo http://www.example.com/bar
    Alias: Maps web paths into filesystem paths and is used to
    access content that does not live under the DocumentRoot.
    Example:
    Alias /webpath /full/filesystem/path
    If you include a trailing / on /webpath then the server will
    require it to be present in the URL.  You will also likely
    need to provide a <Directory> section to allow access to
    the filesystem path.
    ScriptAlias: This controls which directories contain server scripts.
    ScriptAliases are essentially the same as Aliases, except that
    documents in the target directory are treated as applications and
    run by the server when requested rather than as documents sent to the
    client.  The same rules about trailing "/" apply to ScriptAlias
    directives as to Alias.
        ScriptAlias /cgi-bin/ "c:/apache/cgi-bin/"
    </IfModule>
    "c:/apache/cgi-bin" should be changed to whatever your ScriptAliased
    CGI directory exists, if you have that configured.
    <Directory "c:/apache/cgi-bin">
        AllowOverride None
        Options None
        Order allow,deny
        Allow from all
    </Directory>
    Apache parses all CGI scripts for the shebang line by default.
    This comment line, the first line of the script, consists of the symbols
    pound (#) and exclamation followed by the path of the program that
    can execute this specific script.  For a perl script, with perl.exe in
    the C:\Program Files\Perl directory, the shebang line should be:
       #!c:/program files/perl/perl
    Note you mustnot_ indent the actual shebang line, and it must be the
    first line of the file.  Of course, CGI processing must be enabled by
    the appropriate ScriptAlias or Options ExecCGI directives for the files
    or directory in question.
    However, Apache on Windows allows either the Unix behavior above, or can
    use the Registry to match files by extention.  The command to execute
    a file of this type is retrieved from the registry by the same method as
    the Windows Explorer would use to handle double-clicking on a file.
    These script actions can be configured from the Windows Explorer View menu,
    'Folder Options', and reviewing the 'File Types' tab.  Clicking the Edit
    button allows you to modify the Actions, of which Apache 1.3 attempts to
    perform the 'Open' Action, and failing that it will try the shebang line.
    This behavior is subject to change in Apache release 2.0.
    Each mechanism has it's own specific security weaknesses, from the means
    to run a program you didn't intend the website owner to invoke, and the
    best method is a matter of great debate.
    To enable the this Windows specific behavior (and therefore -disable- the
    equivilant Unix behavior), uncomment the following directive:
    #ScriptInterpreterSource registry
    The directive above can be placed in individual <Directory> blocks or the
    .htaccess file, with either the 'registry' (Windows behavior) or 'script'
    (Unix behavior) option, and will override this server default option.
    DefaultType: the default MIME type the server will use for a document
    if it cannot otherwise determine one, such as from filename extensions.
    If your server contains mostly text or HTML documents, "text/plain" is
    a good value.  If most of your content is binary, such as applications
    or images, you may want to use "application/octet-stream" instead to
    keep browsers from trying to display binary files as though they are
    text.
    DefaultType text/plain
    <IfModule mime_module>
    TypesConfig points to the file containing the list of mappings from
    filename extension to MIME-type.
        TypesConfig conf/mime.types
    AddType allows you to add to or override the MIME configuration
    file specified in TypesConfig for specific file types.
        #AddType application/x-gzip .tgz
    AddEncoding allows you to have certain browsers uncompress
    information on the fly. Note: Not all browsers support this.
        #AddEncoding x-compress .Z
        #AddEncoding x-gzip .gz .tgz
    If the AddEncoding directives above are commented-out, then you
    probably should define those extensions to indicate media types:
        AddType application/x-compress .Z
        AddType application/x-gzip .gz .tgz
    AddHandler allows you to map certain file extensions to "handlers":
    actions unrelated to filetype. These can be either built into the server
    or added with the Action directive (see below)
    To use CGI scripts outside of ScriptAliased directories:
    (You will also need to add "ExecCGI" to the "Options" directive.)
        #AddHandler cgi-script .cgi
    For type maps (negotiated resources):
        #AddHandler type-map var
    Filters allow you to process content before it is sent to the client.
    To parse .shtml files for server-side includes (SSI):
    (You will also need to add "Includes" to the "Options" directive.)
        #AddType text/html .shtml
        #AddOutputFilter INCLUDES .shtml
    </IfModule>
    The mod_mime_magic module allows the server to use various hints from the
    contents of the file itself to determine its type.  The MIMEMagicFile
    directive tells the module where the hint definitions are located.
    #MIMEMagicFile conf/magic
    Customizable error responses come in three flavors:
    1) plain text 2) local redirects 3) external redirects
    Some examples:
    #ErrorDocument 500 "The server made a boo boo."
    #ErrorDocument 404 /missing.html
    #ErrorDocument 404 "/cgi-bin/missing_handler.pl"
    #ErrorDocument 402 http://www.example.com/subscription_info.html
    EnableMMAP and EnableSendfile: On systems that support it,
    memory-mapping or the sendfile syscall is used to deliver
    files.  This usually improves server performance, but must
    be turned off when serving from networked-mounted
    filesystems or if support for these functions is otherwise
    broken on your system.
    #EnableMMAP off
    #EnableSendfile off
    Supplemental configuration
    The configuration files in the conf/extra/ directory can be
    included to add extra features or to modify the default configuration of
    the server, or you may simply copy their contents here and change as
    necessary.
    Server-pool management (MPM specific)
    #Include conf/extra/httpd-mpm.conf
    Multi-language error messages
    #Include conf/extra/httpd-multilang-errordoc.conf
    Fancy directory listings
    #Include conf/extra/httpd-autoindex.conf
    Language settings
    #Include conf/extra/httpd-languages.conf
    User home directories
    #Include conf/extra/httpd-userdir.conf
    Real-time info on requests and configuration
    #Include conf/extra/httpd-info.conf
    Virtual hosts
    #Include conf/extra/httpd-vhosts.conf
    Local access to the Apache HTTP Server Manual
    #Include conf/extra/httpd-manual.conf
    Distributed authoring and versioning (WebDAV)
    #Include conf/extra/httpd-dav.conf
    Various default settings
    #Include conf/extra/httpd-default.conf
    Secure (SSL/TLS) connections
    #Include conf/extra/httpd-ssl.conf
    Note: The following must must be present to support
          starting without SSL on platforms with no /dev/random equivalent
          but a statically compiled-in mod_ssl.
    <IfModule ssl_module>
    SSLRandomSeed startup builtin
    SSLRandomSeed connect builtin
    </IfModule>
    <b>ProxyPreserveHost On
    ProxyVia on
    ProxyTimeout 600
    #disable forward-proxying
    ProxyRequests Off
    #proxy /irj both ways
    ProxyPass /irj http://sapportal:50000/irj
    ProxyPassReverse /irj http://sapportal:50000/irj
    #ProxyPassReverse /irj http://testcomp/irj
    #proxy /logon both ways
    ProxyPass /logon http://sapportal:50000/logon
    ProxyPassReverse /logon http://sapportal:50000/logon
    #ProxyPassReverse /logon http://testcomp/logon</b>

  • HTTP 400: BAD REQUEST IN WEBSTARTERAPPII

    Hi All;
    When accessing the WebStarterAppII on Oracle 10g Apps Server using the link "http://server:port/wsa2", after logging in using index.jsp, the "The page cannot be found" page is displayed along with the message "HTTP 400 - Bad Request" on the explorer's title bar.
    However, at that step if I manually write
    "http://server:port/wsa2/browseDirectory.do" on the address bar, I can see the browseDirectory page and continue us
    ing the WebStarterAppII. I debugged the code to see if it is really forwarding to the "/browseDirectory.do", I've seen in the strutsconfig.xml under logon action, the forward path is correct (forsuccess, /browseDirectory.do) and I debugged the logonAction.java, putting the
    line "debug(returnForward.getPath());" to see if it is actually forwarding to "/browseDirectory.do" and the answer is 'yes'.
    Thanks for youn kind help,
    Özgür
    It is really annoying as I cannot figure out what is wrong, everything seems OK except the "Bad Request" page

    Hi CB,
    Cause
    The 400 Bad Request error is an HTTP status code that means that the request you sent to the website server (i.e. a request to load a web page) was somehow malformed therefore the server was unable to understand or process the request.
    Resolution
    The most common reason for a 400 Bad Request error is because the URL was typed wrong or the link that was clicked on points to a URL with some kind of mistake in it.
    Though it's rare, the 400 Bad Request error could be an issue with the web site's server (mainly with the actual website name) that your users are trying to access.
    So in your Portal URL Iview, try to give the full URL with the actual website name (meaning the Portal Server name etc with port settings).
    Hope that helps.
    Ray

  • Incoming call 400 Bad request

    Hello,
    I have setup a test deployment of Lync server 2013 with collocated mediation server, which is working fine now. I am now trying to test with different SIP trunk providers. Two of them are working fine now, after some finetuning at the provider. The third
    and the most interesting provider for me, is not working properly:
    They are providing two trunk hostnames: sw1.sip.domain.com and sw2.sip.domain.com. I have filled both in at the topology. The result is that outgoing calls are working fine but incoming calls result in a 400 Bad Request. Lync Logger states
    "The host portion of the from header, sip.domain.com, arriving at MS listening port (5060) did not match any next hop peers' FQDN or IP Address".
    I have examined the INVITES with wireshark for all three providers and have found the following difference with the working providers:
    The CONTACT header does not match the same hostname/IP as the hostname in the FROM header (incoming call)
    Is it mandatory to be the same as the hostname in the FROM header? What else could be the cause of the error?

    Hi,
    1.  You must use a Microsoft certified service provider to ensure that your ITSP supports all of the functionality that traverses the SIP trunk
    Check if the issued ITSP is certified by Microsoft:
    http://technet.microsoft.com/en-us/office/dn788947
    2.  Please double check the settings on Lync Topology and make sure all Mediation configuration match Topology.
    3.  Check if CMS replicate status to be latest.
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Application Web Service Control Manager detected AWEBSVC is not responding to HTTP requests. The http status code and text is 400, Bad Request.

    Hi All,
    I am seeing the following error for SMS_AWEBSVC_CONTROL_MANAGER component with Message ID: 8100
    Application Web Service Control Manager detected AWEBSVC is not responding to HTTP requests.  The http status code and text is 400, Bad Request.
    awebsctl.log file has below errors:
    Call to HttpSendRequestSync failed for port 80 with status code 400, text: Bad Request
    SMS_AWEBSVC_CONTROL_MANAGER 12/22/2014 3:37:55 PM
    13920 (0x3660)
    AWEBSVCs http check returned hr=0, bFailed=1
    SMS_AWEBSVC_CONTROL_MANAGER 12/22/2014 3:37:55 PM
    13920 (0x3660)
    AWEBSVC's previous status was 1 (0 = Online, 1 = Failed, 4 = Undefined)
    SMS_AWEBSVC_CONTROL_MANAGER 12/22/2014 3:37:55 PM
    13920 (0x3660)
    Health check request failed, status code is 400, 'Bad Request'.
    SMS_AWEBSVC_CONTROL_MANAGER 12/22/2014 3:37:55 PM
    13920 (0x3660)
    Management point and Application Catalog Website Point are installed on the same Server where I am seeing the error for Application Catalog Web Service Point role. Management Point and Application Catalog Website Point are functioning properly. Application
    Catalog Website is working.
    Thanks & Regards, Kedar

    Hi Jason,
    Application Catalog Web Service Point and Application Catalog Website Point; both are installed as per below configuration on same Server:
    IIS Website: Default Web Site
    Port Number: 80
    with default value for Web Application Name configured.
    For SMS_AWEBSVC_CONTROL_MANAGER component, I am getting below error in Component Status:
    Application Web Service Control Manager detected AWEBSVC is not responding to HTTP requests.  The http status code and text is 400, Bad Request.
    Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which AWEBSVC is configured to communicate. 
    Solution: Verify that the designated Web Site is configured to use the same ports which AWEBSVC is configured to use.
    Possible cause: The designated Web Site is disabled in IIS. 
    Solution: Verify that the designated Web Site is enabled, and functioning properly.
    For more information, refer to Microsoft Knowledge Base.
    And awebsctl.log has the below error lines:
    Call to HttpSendRequestSync failed for port 80 with status code 400, text: Bad Request
    SMS_AWEBSVC_CONTROL_MANAGER
    12/23/2014 11:04:36 AM 16388 (0x4004)
    AWEBSVCs http check returned hr=0, bFailed=1
    SMS_AWEBSVC_CONTROL_MANAGER
    12/23/2014 11:04:36 AM 16388 (0x4004)
    AWEBSVC's previous status was 1 (0 = Online, 1 = Failed, 4 = Undefined)
    SMS_AWEBSVC_CONTROL_MANAGER
    12/23/2014 11:04:36 AM 16388 (0x4004)
    Health check request failed, status code is 400, 'Bad Request'.
    SMS_AWEBSVC_CONTROL_MANAGER
    12/23/2014 11:04:36 AM 16388 (0x4004)
    STATMSG: ID=8100
    What should I check from IIS side?
    Application Catalog Website is functioning properly.
    Thanks & regards,
    Kedar
    Thanks & Regards, Kedar

  • Content-Type is net being set in HTTP header. Server returns 400 Bad Request error.

    Hi,
    I am trying to access an XML WebService. This service requires the content type of the request to be set to "text/xml". As you can see in the source code, I am setting the req.ContentType property to "text/xml".
    However, this content type seems not to be added to the HTTP headers. The server returns a 400 Bad Request error as can be seen in the log.
    I've attached a System.Net.trace log and it states:
    [Public Key]
    Algorithm: RSA
    Length: 2048
    Key Blob: 30 82 01 0a 02 82 01 01 00 bc 09 30 8a 1e 03 4d 7a ea 16 d3 a8 5e d8 5b 00 c4 8a c5 9f 26 bd 7d d6 cb 8b d0 db bd 93 2d 2b 3b 84 f6 20 79 83 34 67 51 37 21 ea 56 5e 18 d8 a3 db 72 43 0e 14 77 e2 64 cb 07 b6 2a 81 c7 f5 16 dd 19 c7 d9 68 0b 3a 81 5c f0 05 c9 ed 2b 37 00 31 41 37 8b 3a 73 4a 4d ab d7 d8 87 79 35 82 01 97 e3 3c be bb 84 e5 94 bb 87 52 e3 9f b5 fb 3e 33 38 c3 eb 73 42 ee ba 1e c5 4a 33 18 a1 0d 8a d2 10 a8 c5 3....
    System.Net Information: 0 : [26780] SecureChannel#31884011 - Remote certificate was verified as valid by the user.
    System.Net Information: 0 : [26780] ConnectStream#26966483 - Sending headers
    API-VERSION: 1
    Host: test.myhost.com
    Content-Length: 329
    Expect: 100-continue
    Connection: Keep-Alive
    System.Net Information: 0 : [26780] Connection#3888474 - Received status line: Version=1.1, StatusCode=100, StatusDescription=Continue.
    System.Net Information: 0 : [26780] Connection#3888474 - Received headers
    System.Net Information: 0 : [26780] Connection#3888474 - Received status line: Version=1.1, StatusCode=400, StatusDescription=Bad Request.
    System.Net Information: 0 : [26780] Connection#3888474 - Received headers
    0: Content-type
    1: text/xml
    X-Debug-Token: a810dc
    X-Debug-Token-Link: /service/_profiler/a810dc
    Connection: keep-alive
    Content-Length: 3440
    Cache-Control: no-cache
    Content-Type: text/html; charset=UTF-8
    Date: Tue, 14 Apr 2015 11:07:11 GMT
    Server: Apache
    ...and here's the implementation of the web request:
    private void ButtonSend_Click(object sender, EventArgs e)
    WebHeaderCollection whCol = new WebHeaderCollection();
    whCol.Add("API-VERSION", "1");
    //whCol.Add("Content-Type", "text/xml; charset=UTF-8"); <-- That doesn't work in .NET. Content-Type has to be set on the ContentType-Property
    string msg = _textBoxReq.Text;
    HttpWebRequest req = (HttpWebRequest)WebRequest.Create(_textBoxURL.Text);
    byte[] data = Encoding.UTF8.GetBytes(msg);
    req.Method = "POST";
    req.ContentType = "text/xml; charset=UTF-8";
    req.ContentLength = data.Length;
    req.Headers = whCol;
    req.GetRequestStream().Write(data, 0, data.Length);
    string xml = "";
    try
    using (HttpWebResponse resp = (HttpWebResponse)req.GetResponse())
    using (System.IO.StreamReader sr = new System.IO.StreamReader(resp.GetResponseStream()))
    xml = sr.ReadToEnd().Trim();
    catch (WebException we)
    using (System.IO.StreamReader sr = new System.IO.StreamReader(we.Response.GetResponseStream()))
    xml = sr.ReadToEnd().Trim();
    _textBoxRes.Text = xml;
    Can anyone help?
    Thanks,
    MiRi

    Hi _MiRichter,
    Well Done!
    Thank you very much for sharing the solution to us.
    Best Regards,
    Amy Peng
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request

    Hi,
    We are doing File to WCF Scenario( SOAP ). I am trying to post the Data to WCf usingf SOAP Reciver Adapter.
    Getting the Following error.
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request
    Thanks in advance

    >>>  Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request
    Answer: Use the third party wsdl in SOAP UI or any soap client tool and send the request and see the response. The problem here is the message structure mismatch between your request to the webservice and webservice expecting... 
    Possible 2  reasons:
    1) You are not creating the target message based on the wsdl structure or not configured soap receiver properly.
        or
    2 ) Your wsdl is not latest or updated one or some changes have happened in the third party webservice hosting side.

Maybe you are looking for