Error handling HTTP 400 in WCF-WebHttp adapter BizTalk 2013

Hi!
Does anyone knows how to catch HTTP errors when using WCF-WebHttp REST adapter in BizTalk 2013? I've looked into the article BizTalk
Server: REST Services Error Handling, but that is for BizTalk 2010 using the WCF-Custom adapter.
What I want is to catch the exception in an orchestration, and do some actions dependent on which HTTP error it is, i.e. HTTP 400.
Idar H.

Hi Idar,
Welcome to BizTalk forum.
From your description above, I don't have exact same scenario like yours, this scenario exposes a BizTalk Orchestration as a RESTful webservice using WCF-WebHttp, perhaps it will be good reference for you. See:
http://blog.tallan.com/2014/09/29/wcf-webhttp-and-custom-json-error-messages/
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.

Similar Messages

  • Biztalk 2013 WCF-WebHTTP Adapter - Outbound HTTP Headers

    Hi
    I have a requirement to connect to a service using the WCF-WebHTTP adapter that requires authentication to be passed in the Headers.
    A usercode and password is sent in the intial header and a security token is returned in the response header.
    This security token is then used in the header of each subsequent call to the service.
    I could not find anything in the documentation about getting and setting the "HTTP Header" data using maps or variables or using variables in the "Outbound HTTP Headers" on the adapter transport properties.
    Any help on this would be gratefully received.
    Malcolm

    You can set the outbound HTTP header in WCF-WebHTTP adapter by 2 ways
    1) At adapter level Change adapter properties
    2)Changing Message context property at Orchestration or at pipeline
    Its been well documented here
    http://blog.codit.eu/post/2013/04/30/Using-HttpHeaders-with-WCF-WebHttp-Adapter-on-Biztalk-2013.aspx
    Thanks
    Abhishek

  • WCF-WebHttp Adapter Substituting Nonstandard Characters In Address URI With Web Encoded Equivalent

    I’m using the WCF-WebHttp adapter to send an HTTP Get request to a REST API. The request has to be formatted as shown…
    http://xxx.xxx.xxx.xxx/HPRMServiceAPI/Record?q=title:test*&format=json
    Essentially this is searching for any records with “test” in their title and returning a JSON formatted response containing information on any records that match the search criteria. I don’t have any flexibility in how this request is formatted. It has to
    confirm to the syntax above.
    If I hardcode the above uri in the Address URI field in the WCF-WebHttp adapter configuration and put a request through my BizTalk application, BizTalk correctly sends that request and I get my expected response.
    So far so good.
    The problem is the query portion of the request string (“?q=title:test*” in the example above) needs to be created dynamically based on what is specified in an incoming request to my BizTalk application. It may contain many search criteria and is not limited
    to just record titles as in my example.
    This, I thought would be straight forward: I construct the query portion of the request string in a custom send pipeline and insert that value into a promoted property which is then used by the URL mapping mechanic of the WCF-WebHttp adapter.
    So now the uri in the Address URI field in the WCF-WebHttp adapter configuration simply contains…
    http://xxx.xxx.xxx.xxx/HPRMServiceAPI
    And the remaining part of the request is defined using a URL mapping…
    <BtsHttpUrlMapping>
    <Operation Name="DocumentSearchRequest" Method="GET" Url="/Record{searchquery}" />
    </BtsHttpUrlMapping>
    Where the {searchquery} variable is mapped to a promoted property.
    I can see that my custom send pipeline is correctly promoting the property and that it contains the correct value (e.g “?q=title:test*&format=json”). The problem is that the WCF-WebHttp adapter is now substituting the “?” with its web encoded equivalent
    (%3F). When I view the outgoing HTTP request in Fiddler it looks like this…
    http://xxx.xxx.xxx.xxx/HPRMServiceAPI/Record%3Fq=title:test*&format=json
    I have tried numerous ways of constructing the HTTP request, including hardcoding the offending “?q=” section into the URL mapping rather than having it in the promoted property…
    <Operation Name="DocumentSearchRequest" Method="GET" Url="/Record?q={searchquery}" />
    But this results in other characters (“:”, “&”, “=”) being web encoded in the outgoing HTTP request. Fiddler shows this…
    /HPRMServiceAPI/Record/?q=title%3atest*%26format%3djson
    Similarly, hardcoding the “/Record?q=” section in the Address URI field in the WCF-WebHttp adapter configuration like this…
    http://xxx.xxx.xxx.xxx/HPRMServiceAPI/Record?q=
    …and having the URL mapping contain just…
    <Operation Name="DocumentSearchRequest" Method="GET" Url="{searchquery}" />
    …results in the following outgoing HTTP request (Fiddler shows “?q=” portion now being placed at the end of the request string)…
    http://xxx.xxx.xxx.xxx/HPRMServiceAPI/Record/title:test*&format=json?q=
    So in summary it seems the WCF-WebHttp adapter is struggling to correctly assemble the HTTP request string when a portion of it is supplied in a promoted property and used by the URL mapping mechanic. Specifically when that portion contains nonstandard characters
    (“?”, “:”, “&”, “=” etc), the WCF-WebHttp adapter substitutes them for their web encoded equivalent.
    Any suggestions?

    Thanks Ravindar,
    Unfortunately, I don’t have control of the ‘receive side’. I can’t write a custom pipeline component at the receive side as it is not a BizTalk application, it’s a 3rd party web site exposing REST-like behaviour.
    I have however made progress. It occurred to me the WCF-WebHttp adapter isn't the problem. It's doing exactly what it should by URL encoding any potentially 'unsafe' characters that have been 'injected' into the URL via a promoted property. Potentially the
    promoted property could contain malicious content, especially if that content has been sourced directly from text in an incoming message to BizTalk.
    So the WCF-WebHttp adapter is URL encoding ‘?’ to ‘%3F’ which is probably good behaviour from a security point of view.
    http://xxx.xxx.xxx.xxx/HPRMServiceAPI/Record%3Fq=title:test*&format=json is a perfectly valid address.
    So I looked again at the actual error I was receiving from the 3rd party site. It was…
    HTTP/1.1 400 Bad Request
    System.Web.HttpException: A potentially dangerous Request.Path value was detected from the client (?).
    So, after some research, I edited the web.config of the 3rd party site so it no longer excludes any specific characters from the request.
      <system.web>
        <httpRuntime requestPathInvalidCharacters="" requestValidationMode="2.0" />
      </system.web>
    The 400 Bad Request has gone away and the 3rd party site is processing my request now. Unfortunately it still seems to have an issue with ‘%3F’ being used in place of ‘?’, but I think that will have to be resolved in IIS/web config on the receive side (maybe
    by using request filtering
    http://www.iis.net/configreference/system.webserver/security/requestfiltering) or by discussing with the sites developers.
    In summary, I now believe the WCF-WebHttp adapter is behaving correctly by substituting URL encoded values in place of potentially unsafe characters.
    Thanks for your help.

  • WCF-WebHttp Adapter issue?

    Hello guys
    I stumble on this problem while I was trying to develop a custom pipeline component that on runtime generates a GUID and affects it to the context and body of the message. That GUID is placed on Http Headers as a boundary (content type)
    and on the message body. What it happens is that, on the first message that I send, everything goes well (header GUID matches body GUID, the service response it’s not important here), after the first message all the following messages on the header will have
    the GUID from the first message that I send thought the port, although everything goes fine on the body. Like this:
    Request #1:
    Header: Content-Type: multipart/mixed; boundary=batch_bead1969-540e-4020-8b47-cf0fbcddef1c
    Body:
    bead1969-540e-4020-8b47-cf0fbcddef1ce
    Request #2:
    Header: Content-Type: multipart/mixed; boundary=batch_bead1969-540e-4020-8b47-cf0fbcddef1c
    Body:
    226dd0f5-501f-4da8-a871-b79e6ac512d0
    Request #3:
    Header: Content-Type: multipart/mixed; boundary=batch_bead1969-540e-4020-8b47-cf0fbcddef1c
    Body:
    98b7e6f9-c229-4a0b-a8f1-cd0c1f3e27e8
    As you can see in red, between multiple requests the GUID is always the same, and it shouldn’t be since on the body is changing correctly. After some analysis we realized that the problem was with the property “HttpHeaders” (WCF property
    schema), where we are writing the “content-type” in our custom pipeline component. It seems that for some reason the value of this property ain’t properly read after a first message went thought successfully.
    Why do I say successfully? Well…
    If there’s an error on send the message and the message gets dehydrated or suspended, the HttpHeaders seems to be “reseted” and read again, and everything goes as it should.
    If the message went to successfully regardless of the response, the issue that I describe will happen.
    Restarting the host instance seems to have no effect.
    Sometime after the first message went thought successfully, HttpHeaders seem to be “reseted” and read again. Although I don’t know how much time, at least something above 15min.
    Stop\Start the send seems to force an “reset” on the property.
    Just to make clear some eventual questions, HttpHeaders is correctly written into context before entering the adapter, after the message went thought the adapter, we can see on fiddler that the message isn’t as it should.
    I did some code to replicate this issue, and my Execute method on pipeline goes like this:
    public Microsoft.BizTalk.Message.Interop.IBaseMessage Execute(IPipelineContext pContext, Microsoft.BizTalk.Message.Interop.IBaseMessage pInMsg)
    Stream inMsgBodyStream = pInMsg.BodyPart.GetOriginalDataStream();
    pInMsg.Context.Write("HttpHeaders", "http://schemas.microsoft.com/BizTalk/2006/01/Adapters/WCF-properties",
    "content-type: multipart/mixed; boundary=batch_" + Guid.NewGuid().ToString());
    return pInMsg;
    I also try this behavior with the classic HTTP adapter, although another issues were raised, the fact is that Http Headers are correctly read between requests, so as far as we can tell this just happens with this adapter.
    Does anybody had similar issue? So far I haven’t found a solution.
    PS: I’m using Biztalk 2013 RTM
    Thanks

    Hey, someone else reported a similar issue with the WCF-WebHttp adapter for BizTalk 2013 - see this thread:
    http://social.msdn.microsoft.com/Forums/en-US/biztalkgeneral/thread/e477ad7a-505c-4f86-9556-8075d747e447. I will report your finding to Microsoft support.
    Thanks,
    If this answers your question, please use the "Answer" button to say so | Ben Cline

  • Biztalk 2013 Wcf-webhttp adapter Issue

    Hi
    I am trying to get WCF-WebHttp adapter working but it is ending  error.
    I created a service account with Bing api (can browse this url directly by providing login credentials)
    URL:
    https://api.datamarket.azure.com/Bing/SearchWeb/Web?Query='WA'
    These are my wcf-webhttp adapter settings
    URI
    https://api.datamarket.azure.com/Bing/SearchWeb
    http Method and URL Mapping
    <BtsHttpUrlMapping>
     <Operation Method="GET" Url="/Web?Query='WA'"/>
     </BtsHttpUrlMapping>
    it seems template matching is failing in wcf adapter as a result Outbound URL property is not getting promoted resulting below error.
    Can you please advice what is the missing piece in this configuration?
    Error Message:
    The Messaging engine failed to process a message submitted by adapter:WCF-WebHttp Source
    URL:https://api.datamarket.azure.com/Bing/SearchWeb. Details:The published message could not be routed because no subscribers were found. This error occurs if the subscribing orchestration or send
    port has not been enlisted, or if some of the message properties necessary for subscription evaluation have not been promoted. Please use the Biztalk Administration console to troubleshoot this failure.

    Hi
    Moreover I observed one more thing with another API if URI is brows able directly without Key it works
    Actual URL: https://ServerName/StoreMasterServices/Markets
    URI: https://ServerName/StoreMasterServices/
    Headers Info
    <BtsHttpUrlMapping>
    <Operation Method="GET" Url="/Markets" />
    </BtsHttpUrlMapping>
    This URI: https://ServerName/StoreMasterServices/    
    is brows able even without Key  (/Markets) and it is working fine.
    So Question is, is it mandatory to have URI brows able (with credentials if it needs)?

  • Custom headers are not exported correctly in the bindings for the WCF-WebHttp adapter

    I have an annoying issue with the bindings for the WCF-WebHttp adapter.
    As you know, the "Messages" tab of the WCF-WebHttp transport properties enables a developer to configure a number of static outbound HTTP headers. When I've entered two or more headers in the textbox, the CRLF between individual headers will be
    stripped after a bindings import. This means I cannot call RESTful services that require more than one custom HTTP header in a messaging-only scenario, because BizTalk goofs up the configuration.
    For example, when I enter the following headers in the textbox:
    Then export the bindings, and immediately import the bindings again (untouched), the textbox now shows:
    I did some brief analysis, and within the binding file's XML, the HttpHeaders property (contained in the TransportTypeData element) is not encoded/escaped in any way, so therefore the significant whitespace (in this case CRLF) that needs to be preserved
    is lost in the import process.
    Can anyone reproduce this and can anyone think of a workaround (without resorting to an orchestration)?

    I did some brief analysis, and within the binding file's XML, the HttpHeaders property (contained in the TransportTypeData element) is not encoded/escaped in any way, so therefore the significant whitespace (in this case CRLF) that needs to be preserved
    is lost in the import process.
    +1

  • Xml forms - Error handling HTTP request

    Hello,
    We have installed portal 6.0
    I've made some forms with the xml form builder, imported them into IViews (KM navigation IView) and assigned the IViews to a role
    The Iview shows the RenderListItem form
    Every Iview (RenderListItem form) has a "new item" button
    Every record of the iview has a edit-delete action
    When I press the "new item" button or the edit button (or save button) I get the following error:
    Error handling HTTP request. Check the log file for more information.
    java.lang.RuntimeException: Context is unavailable!
         at com.sap.pct.plm.dmsrmconnectorforkm.DMSRMConnection.(DMSRMConnection.java:83)
         at com.sap.pct.plm.dmsrmconnectorforkm.DMSRMR3FunctionCalls.getGenericValueList(DMSRMR3FunctionCalls.java:6532)
         at com.sap.pct.plm.dmsrmconnectorforkm.DMSRMR3FunctionCalls.getLaboratoryList(DMSRMR3FunctionCalls.java:6360)
         at com.sap.pct.plm.dmsrmconnectorforkm.DMSRMLaboratoryValueProvider.getAllowedValues(DMSRMLaboratoryValueProvider.java:79)
         at com.sapportals.wcm.service.propertyconfig.config.MetaName.getAllowedValues(MetaName.java:781)
         at com.sapportals.wcm.service.propertyconfig.config.MetaName.allowedValueIterator(MetaName.java:472)
         at com.sapportals.wcm.service.xmlforms.ResourceProperties.appendAllowedValues(ResourceProperties.java:713)
         at com.sapportals.wcm.service.xmlforms.ResourceProperties.mergeProperty(ResourceProperties.java:682)
         at com.sapportals.wcm.service.xmlforms.ResourceProperties.mergePropertiesIntoDom(ResourceProperties.java:611)
         at com.sapportals.wcm.service.xmlforms.transformation.HtmlGenerator.getHtmlStream(HtmlGenerator.java:116)
         at com.sapportals.wcm.service.xmlforms.transformation.Transformation.render(Transformation.java:391)
         at com.sapportals.wcm.service.xmlforms.transformation.Transformation.render(Transformation.java:336)
         at com.sapportals.wcm.service.xmlforms.transformation.Transformation.render(Transformation.java:188)
         at com.sapportals.wcm.app.xmlforms.EditServlet.doGetAction(EditServlet.java:165)
         at com.sapportals.wcm.app.xmlforms.XFBaseServlet.doGet(XFBaseServlet.java:241)
         at com.sapportals.wcm.app.xmlforms.XFBaseServlet.doPost(XFBaseServlet.java:261)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sapportals.wcm.app.xmlforms.XFBaseServlet.service(XFBaseServlet.java:134)
         at com.sapportals.wcm.portal.proxy.PCProxyServlet.service(PCProxyServlet.java:331)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sapportals.portal.prt.core.broker.ServletComponentItem$ServletWrapperComponent.doContent(ServletComponentItem.java:110)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java: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)
    This error doesn't always appear, there are times that the portal works correct and when I can add items, edit them and save my changes
    Does anyone have an idea where the error comes from? In what direction I have to search? How I can solve this problem?
    Thanks in advance, points will be distributed for helpfull answers

    Hi,
    I didn't place a save button on the RenderListItem but on the Edit form so this couldn't be the issue...
    I solved the error I got when I wanted to save my form
    The edit and delete buttons also work correct...
    I only get the error mentioned above when I press the "new form" button, I created that button with the CreateXMLForms action group that I added in my Collection Grid renderer settings (option collection command group)
    Then I changed my form availibility (System administration ->system configuration ->KM->CM->form based publishing->form availibility->folder settings)
    I created the following folder settings:
    foldername//priority//path//forms to exclude//forms to include
    library//10 //documents/testlibrary//Smarties, QnA,SAP_APP_News//library
    News //10 //documents/News//smarties, library, QnA// SAP_APP_News
    QnA //10 //documents/testQuestionAnswer// SAP_APP_News, smarties, library //QnA
    Smarties //10 /documents/testSmarties
    Did I do something wrong here? What can cause this error? In what direction should I search?

  • Sending an XML that contains CDATA to a SOAP service using wcf-webhttp adapter

    I've run into a rather unique problem when trying to send an xml that contains the <![cdata[]]> tag to a soap service.  Without the tag the xml sends through without issue.  However, when I add the cdata tag within the xml, BizTalk immediately
    fails without even attempting to send to the service.  I receive the following error:
    "The published message could not be routed because no subscribers were found. This error occurs if the subscribing orchestration or send port has not been enlisted, or if some of the message properties necessary for subscription evaluation have not
    been promoted. Please use the Biztalk Administration console to troubleshoot this failure. "
    I have ensured that the send adapter is enlisted and started. 
    This is on a BizTalk 2013 installation.
    Any and all help is appreciated!
    Thanks

    as per my understanding, if you use the
    <![cdata[]]> tag in sending message, BizTalk is not able to send the message as it is not matching with your send message schema that is why error  'The
    published message could not be routed because no subscribers were found.....' 
    Please compare the message format or configured schema in send shape and message which suspended when
    used <![cdata[]]> tag used.
    Regards
    Suman

  • Error code Http 400

    I am facing issue for Http 400 error

    Duplicate:
    http://supportforums.blackberry.com/t5/BlackBerry-Curve/Facing-issue-for-Http-400-amp-504/m-p/309630...
    Occam's Razor nearly always applies when troubleshooting technology issues!
    If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
    Join our BBM Channels
    BSCF General Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • Can Wcf-Custom Adapter implement Wcf-WebHttp Functionality?

    Can the Wcf-Custom adapter implement the same functionality as the Wcf-WebHttp adapter in BizTalk 2013? In particular, can it provide the same functionality as the operation map and the variable map? If not, is there any other way to provide Wcf-WebHttp
    functionality without hosting an adapter in IIS with an isolated host?
    Thanks!

    Yes, but...
    You can set the mappings on outgoing messages with some new Context Properties.  This describes how to do it on a Dynamic Port, but it should work the same on a static port. 
    http://masteringbiztalkserver.wordpress.com/2013/11/11/calling-restful-service-using-dynamic-send-ports-biztalk-2013/
    The receive side is a bit different since I'm 97% sure all the mapping happens in the BizTalk Adapter (WS-WebHttp) not any of the binding elements.
    However, you can essentially replicate that functionality with a Custom Pipeline Component.  In that case you would use the WCF-Custom Adapter with the webHttpBinding.

  • Http 400 error when accessing website on a browser

    My website which was formally working fine is now not!
    When I tried to look at my website on a browser yesterday all I got was error message http 400.
    So I figured I may have an error in my design somewhere due to recent changes so I then tried to upload a earlier version of my website (that I know contains no errors and functions correctly) and I get a 'timed out' error when trying to put it to the remote server
    Started: 20/09/2011 10:27 AM
    Analyt\analyt.html - Put operation successful
    Analyt\analyt_compost.html - Put operation successful
    Analyt\analyt_leaf.html - Put operation successful
    Analyt\analyt_leaf_clip_image002.gif - Put operation successful
    Analyt\analyt_leaf_clip_image004.gif - Put operation successful
    Analyt\analyt_leaf_clip_image006.jpg - Put operation successful
    Analyt\analyt_pathology.html - Put operation successful
    Analyt\analyt_soil.html - Put operation successful
    Analyt\analyt_water.html - Put operation successful
    Assets\AAS.jpg - Put operation successful
    Assets\analyt_compost_clip_image002.gif - Put operation successful
    Assets\Anna.JPG - Put operation successful
    Assets\Ash.jpg - Put operation successful
    Assets\BioLogo.jpg - Put operation successful
    Assets\Bio_980x150_Banner.swf - Put operation successful
    Assets\Bluetongue.jpg - Put operation successful
    Assets\BoreMonotor.jpg - Put operation successful
    Assets\Compost_Pile.jpg - Put operation successful
    Assets\Contamination.jpg - Put operation successful
    Assets\Contamination_Small.jpg - Put operation successful
    Assets\Culture.jpg - Put operation successful
    Assets\DeepRiver.jpg - Put operation successful
    Assets\Dieback.jpg - Put operation successful
    Assets\Drew.jpg - Put operation successful
    Assets\Driller1.jpg - Put operation successful
    Assets\Driller2.jpg - Put operation successful
    Assets\Driller3.jpg - Put operation successful
    Assets\Drilling3.jpg - Put operation successful
    Assets\Fig8-AAMGL.jpg - Put operation successful
    Assets\Fig8-AAMGL_samll.jpg - Put operation successful
    Assets\FloraRightSide.jpg - Put operation successful
    Assets\FloraRightSideA.jpg - Put operation successful
    Assets\FloraRightSideB.jpg - Put operation successful
    Assets\Genette.jpg - Put operation successful
    Assets\Glassware.jpg - Put operation successful
    Assets\GroundMod.jpg - Put operation successful
    Assets\Handdrill.jpg - Put operation successful
    Assets\hand_soil.jpg - Put operation successful
    Assets\HPLC.jpg - Put operation successful
    Assets\index.jpg - Put operation successful
    Assets\Kylie.jpg - Put operation successful
    Assets\Louise.jpg - Put operation successful
    Assets\Olivia.jpg - Put operation successful
    Assets\Peter_0000.jpg - Put operation successful
    Assets\PumpingTest.jpg - Put operation successful
    Assets\Sidebar_Background1.jpg - Put operation successful
    Assets\Sidebar_Background_Waste.jpg - Put operation successful
    Assets\Sidebar_Background_Water.jpg - Put operation successful
    Assets\Side_Background7.jpg - Put operation successful
    Assets\Small_Plant.jpg - Put operation successful
    Assets\Soilsamples.jpg - Put operation successful
    Assets\soil_profile.jpg - Put operation successful
    Assets\soil_reactivity.jpg - Put operation successful
    Assets\Sorter.jpg - Put operation successful
    Assets\thinking.jpg - Put operation successful
    Assets\UWMP.jpg - Put operation successful
    Assets\UWMS.jpg - Put operation successful
    Assets\Veg_Panorama2Small.jpg - Put operation successful
    Assets\Vindya.jpg - Put operation successful
    Assets\WaterDrop.jpg - Put operation successful
    Assets\WaterTestingEquip.jpg - Put operation successful
    Assets\Wetland.jpg - Put operation successful
    Assets\wetland2.jpg - Put operation successful
    Assets\Zebrafish.jpg - Put operation successful
    Operation timed out. Cancelling...
    Operation timed out. Cancelling...
    Operation timed out. Cancelling...
    Operation timed out. Cancelling...
    Operation timed out. Cancelling...
    The part where it is cancelling is my CSS folder I think.
    Anyone help?

    This is what I am seeing:
    Bad Request (Invalid Hostname)
    The other websites on the same IP are running OK:
    toowoombahonda.com
    www.accounting4u.com.au
    www.advancedmatting.com.au
    www.buyacres.com.au
    www.cgcinteriors.com.au
    www.equiaustralia.com.au
    www.firstbite.com.au
    www.gallbrosmedical.com.au
    www.groomersproducts.com.au
    www.robewaterfront.com.au
    Have you tried loading just a single page to test your server if it is misconfigured?  Alternatively, you may have to contact your host to see if there is anything wrong at their end.
    DW files do not create this problem.  even if you have some problems with your code they do not make your server go down.  DW files are simple text files and cause no problems.

  • 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.

  • BizTalk WCF-WebHttp Custom Headers per message

    Hi,
    I have a requirement to connect to a service using the WCF-WebHTTP adapter that requires add custom http Header "X-Auth: <Value varies for messageType>" per message.
    So am using dynamic Request-Response port to set HTTPHeaders dynamically per message. I am using following code to assign HttpHeaders in Message Assignment Shape.
    Msg_CogSrvReq(WCF.HttpHeaders)="X-Auth: "+<value that extracted from a another service>;
    However while testing these, am getting an error "X-Auth header not found in request" from the service.
    Why this HttpHeader not passing to the service while requesting? Is am missing anything?
    Thanks,
    Praveen
    Praveen

    Hi Praveen,
    I have seen this issue where when you try to set the HTTPHeader properties, the WCF-WebHTTP adapter
    ignores it and the outgoing message always goes without the custom HTTPHeader that’s been set in Orchestration.
    We had a similar situation like yours where I had to set a GUID as one of the properties in the HTTPHeader and needed to use WCF-WebHTTP
    adapter. Also if you use a static adapter and configure the properties, different GUIDs would not get generated per message instance, this is due to the way adapter initialize the message instances. So the only solution is to have dynamic GUID per message
    instance is using the dynamic port as you do.
    And for setting the dynamic HTTPHeader properties with WCF-WebHTTP adapter,
    I used a custom pipeline component with a code as below. Though you have the dynamic send port, your dynamic port need to have pipeline configured, in this case you can use a custom pipeline with a component in it will following code:
    public Microsoft.BizTalk.Message.Interop.IBaseMessage Execute(IPipelineContext pContext, Microsoft.BizTalk.Message.Interop.IBaseMessage pInMsg)
    pInMsg.Context.Write("HttpHeaders", "http://schemas.microsoft.com/BizTalk/2006/01/Adapters/WCF-properties", "X-Auth: "+<value that extracted from a another service>);
    return pInMsg;
    Check the following article in this context:
    http://www.codit.eu/blog/2013/04/30/using-httpheaders-with-wcf-webhttp-adapter-on-biztalk-2013/
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

  • WCF-WebHttp REST configuration

    I'm trying to configure the WCF-WebHttp adapter to retreive data from a REST endpoint, specifically a contact in CRM.  I need to include a filter to return only the contact that I want.  When I include a hardcoded value in the Uri it works fine:
    <BtsHttpUrlMapping>
      <Operation Name="Query" Method="GET" Url="?$filter=bsg_ProLicenseNumber eq '74309'" />
    </BtsHttpUrlMapping>
    However, I need to use a parameter here.  I have configured a parameter in the variable mapping section called PCCNUM.  When I include that in my Uri I get an error:
    <BtsHttpUrlMapping>
      <Operation Name="Query" Method="GET" Url="?$filter=bsg_ProLicenseNumber eq {PCCNUM}" />
    </BtsHttpUrlMapping>
    Error:  The Uri Template '?$filter=bsg_ProLicenseNumber eq {PCCNUM}' is not valid; each portion of the query string must be of the form 'name=value', when value cannot be a compound segment. 
    I have tried several ways of formatting {PCCNUM}, (single quotes, double quotes, parenthesis, encoding, etc.) but no luck.  Any ideas?
    Thanks,
    Frank

    Hi,
    The Variable Mapping options in the Send Port are limited. Another option is to use an Dynamic Send Port. In that case you have full control over the URI in the Orchestration.
    How to Configure a WCF-WebHttp Send Port
    http://msdn.microsoft.com/en-us/library/jj572853(v=bts.80).aspx
    Calling Restful Service using Dynamic Send Ports – BizTalk 2013
    http://masteringbiztalkserver.wordpress.com/2013/11/11/calling-restful-service-using-dynamic-send-ports-biztalk-2013/ 
    Kind regards,
    Tomasso Groenendijk
    Blog 
    |  Twitter
    MCTS BizTalk Server 2006, 2010
    If this answers your question please mark it accordingly

  • WCF-WebHttp dynamic URL and Dynamic Header/Behavior configuration.

    HI,
    I have an requirement to integrate with the REST Services in BizTalk Server 2013 R2, And This REST Service URL and HTTP Headers will differs per message. So I had created an Orchestration with the Dynamic Request-Response port and assign the properties in
    Message Assignment Shape. However while testing HTTP Headers were not added to service request message.
    I had tried with create Custom endpoint behaviour and assigned this behaviour to service request in Orchestration, however this property also not assigned from the Orchestration.
    Is this a bug for WCF-WebHttp Adapter? Is any other options to achieve my requirement?
    Thanks,
    Raj
    Praveen

    Hi Praveen,
    Its a known bug already
    reported to Microsoft. 
    BizTalk 2013 servers that have been upgraded from BizTalk 2010 are missing
    some of the new global properties including HttpHeaders properties because
    of this even in orchestration we cannot change the HttpHeaders on messages.
    As a workaround WCF behavior extension
    can be used to solve this problem.
    Which can be downloaded from here.
    For the detailed explanation, I would adivce you to follow the below link on how to dynamically change
    the WCF-HttpHeaders for WCF-WebHTTP adapter.
    Dynamic
    WCF-HttpHeaders for WCF WebHttp adapter
    There is already a discussion going on around this on another post. Ashwin has also recommend to use custom pipeline component as a work around .
    Refer: BizTalk WCF-WebHttp Custom Headers per message
    Rachit
    Please mark as answer or vote as helpful if my reply does

Maybe you are looking for

  • PRT's not printed on the SAP standard insp. instruction

    Dear forum, My client evaluates the possibility to use the insp. instruction program available in standard SAP, the pgm RQEEAS20, SAPScript INSP_INSTRUCTION. The client is generally satisfied with the layout, but unfortunately the PRT information fro

  • Can't send iMessage after update to IOS 7 on iPhone 5

    After I update to IOS 7 on iPhone 5 the iMessage function seems not working properly. when I trying to send iMassage the "sending" bar loads up to 90% (slowly) and then stops dead and doesn't move. It stays at that 90% mark until it either starts wor

  • [E2010] [EWSMA] [C#] [Windows]: How do I get Tasks to show up in the Calendar view

    When creating a task from EWS, the Owner field is empty.  I believe this causes my created Task to disappear when I am in the Calendar view (showing Tasks on the bottom).  The created Task still shows up in the Tasks view, but not the Calendar view (

  • Minis spin at restart or shut down

    I have 3 minis that just spin when you hit restart or shut down. You have to hard reboot... the old firmware update I found is not needed on that computer according to the computer. Running 10.4.11 on all. Any ideas?

  • SOAP Fault for Application errors

    Hi, I would like to know whether it is OK to raise a SOAP fault for Application or system level exceptions. For example, I'm searching for a user with an ID as request , If the ID is invalid(User is not found) is it OK to raise the SOAP Fault. Let me