Error executing RDS command. Status Code:404

The following problem really made crazy. I worked it for a whole day and still didn't figure it out. could someone help me ? Thanks a million.
I created a project using this way:
and select a tomcat server 6.0.*
and my RDS configuration in my web.xml is this:
part of my web.xml
<servlet>
        <servlet-name>RDSDispatchServlet</servlet-name>
        <display-name>RDSDispatchServlet</display-name>
        <servlet-class>flex.rds.server.servlet.FrontEndServlet</servlet-class>
        <init-param>
            <param-name>useAppserverSecurity</param-name>
            <param-value>false</param-value>
        </init-param>       
        <load-on-startup>10</load-on-startup>
    </servlet>
    <servlet-mapping id="RDS_DISPATCH_MAPPING">
        <servlet-name>RDSDispatchServlet</servlet-name>
        <url-pattern>/CFIDE/main/ide.cfm</url-pattern>
    </servlet-mapping>
when I created my flex project, and added it to the server using the way of Add web module... . After that, I started my server, and changed to this view:
I clicked "Connect to Data/Service..." and selected the service type "BlazeDS". When the Flash  Builder popped up a Authentication window, I checked "No password required" and clicked the OK button, and then, the problem comes out.
Any clues for this problem? Thank you.

With all the problems people have with this error, you'd think there would be a FAQ about it. is this it? no answers?
no one knows why this happens with eclipse/FB4 on a windows xp system? is this the kind of support you get from Adobe?
this is EXTREMELY frustrating!!!!!!! please Adobe,HHHEELLPPP!!!!!

Similar Messages

  • Error executing RDS Command Status Code 504

    Hi,
    I'm new to the flex world & was trying out the testdrive application at http://www.adobe.com/devnet/flex/testdrive/articles/1_build_a_flex_app2.html
    I've installed Flex Flash builder 4 on top of my eclipse installation and I'm using Tomcat as the servlet container for deploying the testDrive WAR file (which contains the remote services).
    When I try to connect to the 'BlazeDS' from Data-> Connect to BlazeDS option; I get a Status code - 504, Reason: Connect Error.
    Can anyone please point me to the right direction, I've tried everything I could but no luck.
    Thanks in advance for your time.
    Cheers,
    J

    With all the problems people have with this error, you'd think there would be a FAQ about it. is this it? no answers?
    no one knows why this happens with eclipse/FB4 on a windows xp system? is this the kind of support you get from Adobe?
    this is EXTREMELY frustrating!!!!!!! please Adobe,HHHEELLPPP!!!!!

  • Error executing RDS command. Status Code : 503 , Reason : Service Unavailable

    Hi,
    I am being trying to connect a Flex desktop application with a Java application running in Tomcat (6.0.29), and I get this error message when trying to use the Data wizard to connect with Blaze DS.
    I have read all the tutorials and everything looks good from the server side. This is what appears in the server log:
    2011-01-27 16:02:33,030 [ INFO] - RemotingDestinationExporter - Created remoting destination with id 'accounts'
    2011-01-27 16:02:33,046 [ INFO] - RemotingDestinationExporter - Remoting destination 'accounts' has been started started successfully.
    2011-01-27 16:02:33,046 [ INFO] - RemotingDestinationExporter - Created remoting destination with id 'customers'
    2011-01-27 16:02:33,046 [ INFO] - RemotingDestinationExporter - Remoting destination 'customers' has been started started successfully.
    2011-01-27 16:02:33,061 [ INFO] - FrameworkServlet - FrameworkServlet 'flex': initialization completed in 3887 ms
    2011-01-27 16:02:50,813 [ INFO] - MessageBrokerHandlerAdapter - Channel endpoint my-amf received request.
    2011-01-27 16:43:42,897 [ INFO] - MessageBrokerHandlerAdapter - Channel endpoint my-amf received request.
    (The last two lines appears when I put the AMF channel's URI in a browser).
    Below is what appears in the Event log from Eclipse.
    java.lang.RuntimeException: java.lang.RuntimeException: RDS server message:
    Error executing RDS command. Status Code : 503 , Reason : Service Unavailable
    at com.adobe.flexbuilder.services.j2eeservice.J2EEServicePage.setVisible(J2EEServicePage.jav a:149)
    at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1171)
    at org.eclipse.jface.wizard.WizardDialog.access$2(WizardDialog.java:1149)
    at org.eclipse.jface.wizard.WizardDialog$5.run(WizardDialog.java:1138)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
    at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1136)
    at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:830)
    at com.adobe.flexbuilder.DCDService.ui.wizard.ServiceWizardDialog.nextPressed(ServiceWizardD ialog.java:93)
    at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369)
    at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3910)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3503)
    at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
    at org.eclipse.jface.window.Window.open(Window.java:801)
    at com.adobe.flexbuilder.DCDService.ui.wizard.ServiceWizard.show(ServiceWizard.java:190)
    at com.adobe.flexbuilder.DCDService.ui.wizard.ServiceWizard.createService(ServiceWizard.java :152)
    at com.adobe.flexbuilder.dcrad.views.ServiceExplorerView$1.handleEvent(ServiceExplorerView.j ava:528)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1012)
    at org.eclipse.swt.widgets.Link.wmNotifyChild(Link.java:1004)
    at org.eclipse.swt.widgets.Control.wmNotify(Control.java:4877)
    at org.eclipse.swt.widgets.Composite.wmNotify(Composite.java:1757)
    at org.eclipse.swt.widgets.Control.WM_NOTIFY(Control.java:4507)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:4000)
    at org.eclipse.swt.widgets.Display.windowProc(Display.java:4632)
    at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method)
    at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:2314)
    at org.eclipse.swt.widgets.Link.callWindowProc(Link.java:172)
    at org.eclipse.swt.widgets.Widget.wmLButtonUp(Widget.java:1917)
    at org.eclipse.swt.widgets.Control.WM_LBUTTONUP(Control.java:4301)
    at org.eclipse.swt.widgets.Link.WM_LBUTTONUP(Link.java:842)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:3982)
    at org.eclipse.swt.widgets.Display.windowProc(Display.java:4632)
    at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
    at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2411)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3501)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLau ncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.jav a:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
    Caused by: java.lang.RuntimeException: RDS server message:
    Error executing RDS command. Status Code : 503 , Reason : Service Unavailable
    at com.adobe.flexbuilder.services.j2eeservice.J2EEServicePage.initialize(J2EEServicePage.jav a:187)
    at com.adobe.flexbuilder.services.j2eeservice.J2EEServicePage.setVisible(J2EEServicePage.jav a:136)
    ... 61 more
    Any help wolud be appreciated.
    Thanks

    Hi There,
    I am getting the same error. can anyone tell me what could be problem?

  • Demo Error - HTTP response contains status code 404

    Dear all,
    While configuring the first demo on XI 3.0, I encountered the following errors when executing the scenario. The scenario is "Configuring Integration Scenarios for proxy-to-proxy communication" - Checking flight seat availability.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Integration Server
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
      <SAP:P1>404</SAP:P1>
      <SAP:P2>Not Found</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Error Report</title> <style> td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active </style> </head> <body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0"> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"><font face="Arial, Verdana, Helvetica" size="4" color="#666666"><b>  404 &nbsp Not Found</b></font></td> </tr> <tr bgcolor="#3F73A3"> <td height="23" width="84"><img width=1 height=1 border=0 alt=""></td> <td height="23"><img width=1 height=1 border=0 alt=""></td> <td align="right" height="23"><font face="Arial, Verdana, Helvetica" size="2" color="#FFFFFF"><b>SAP J2EE Engine/6.40 </b></font></td> </tr> <tr bgcolor="#9DCDFD"> <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td> </tr> </table> <br><br><br><br><br><br> <p><font face="Arial, Verdana, Helvetica" size="3" color="#000000"><b>  The requested resource does not exist.</b></font></p> <p><font face="Arial, Verdana, Helvetica" size="2" color="#000000"><table><tr><td valign="top"><b> Details:</b></td><td valign="top"><PRE>Go to <A HREF="/" target="_parent">main page</A> of this application!</PRE></font></td></tr></table></font></p> </body> </html></SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>HTTP response contains status code 404 with the description Not Found XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Any pointers on this is greatly appreciated!!
    Thanks,
    Cyanna

    Hi Michal,
    Thanks for your response! I followed the instruction on question 17, and recheck my configuration of the integration engines (for client 105/106/107 as stated in the SAp demo), and change the 'Corresponding Inte. Server" back to the format "dest://<RFC destination for inte. server>". I had that initially, and decided to try using the entire http path (http://<local_host:J2EE port>/sap/xi/engine/?type=entry). Neither of them worked.
    Do I need to restart or reactivate any components after I changed the corresponding integration server value after the configuration?
    Since the above did not work, so I went back to the possible root cause (Integration Server RFC destination). I have set up the integration server RFC destination in client 100, with the following parameters:
    Under Technical Settings:
    Host: <local_host>
    path prefix: /sap/xi/engine/?type=entry
    service no.: 5<instance>00
    Under Logon/Security:
    Logon Precedure: chose Basic Authentication
    Client: 100
    Login ID : XIAPPLUSER
    Afterwards, I did the "Test Connection", and it returns the 404 error.
    In addition, on the application systems side (in the demo, the case will be client 105/106/107), I have ensured the business systems are set to "application system".
    Any help is greatly appreciated!
    Thanks much!
    Regards,
    Cyanna

  • Error executing RDS command. Status Code : 404 , Reason : Not Found

    Anyone know how I would resolve this error?

    There can be any number of reasons. First would if the RDS feature is disabled on the server you’re connecting to. Second, that web server (if you are using one) could be configured to block RDS requests (or perhaps even all requests to url’s with CFIDE in them). You could address those, but before you do, please do share more about your use of CFB.
    To be clear, are you meaning to intentionally use the feature in CFB where you define a server (and optionally connect a project to that server), so that you can use features to allow you to access server resources (database info, CFC, and more) from within CFB? You would typically only do that in connecting to a development server. Just want to know what your intentions are before leading you to enable something on a server that you don’t really need.
    And while we await those answers, and whether the first paragraph may get you going to a solution, is this CF server something you’re connecting to (the RDS url) using the server’s external web server (like IIS or Apache, such as is typical if you have no port in the URL), or via CF’s built-in web server (such as is typical when you have a port like 8500 in the URL)? That may be important in helping to solve your problem.
    For instance, if the server (and the URL you’re using) uses IIS, then if you visited the URL for RDS in a browser on the server itself, you may get a much more clear explanation of the problem (since by default, IIS shows more details for requests made ON the sever itself than it does for requests from off the server). The RDS URL (which is generated by the RDS feature in CFBuilder, not something you normally type) is /CFIDE/main/ide.cfm, so append that to the domain or IP address of the server you have configured CFBuilder to use, and see what more detail you may get in your browser.
    /charlie

  • HTTP response contains status code 404 ...

    Hello,
    My system sceanrio is:
    R/3 -> idoc -> XI-1 -> xi adapter -> XI-2 -> idoc -> R/3.
    When the message sent, I get a red flag in SXMB_MONI transaction of "XI-1" system :
      'HTTP response contains status code 404 with the
      description Not Found'
    Here is the SOAP adapter of the Call Adapter:
    =============================================
    td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active </style> </head> <body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0"> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"><font face="Arial, Verdana, Helvetica" size="4" color="#666666"><b>  404 &nbsp Not Found</b></font></td> </tr> <tr bgcolor="#3F73A3"> <td height="23" width="84"><img width=1 height=1 border=0 alt=""></td> <td height="23"><img width=1 height=1 border=0 alt=""></td> <td align="right" height="23"><font face="Arial, Verdana, Helvetica" size="2" color="#FFFFFF"><b>SAP J2EE Engine/6.40 </b></font></td> </tr> <tr bgcolor="#9DCDFD"> <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td> </tr> </table> <br><br><br><br><br><br> <p><font face="Arial, Verdana, Helvetica" size="3" color="#000000"><b>  The requested resource does not exist.</b></font></p> <p><font face="Arial, Verdana, Helvetica" size="2" color="#000000"><table><tr><td valign="top"><b> Details:</b></td><td valign="top"><PRE>Go to <A HREF="/" target="_parent">main page</A> of this application!</PRE></font></td></tr></table></font></p> </body> </html></SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>HTTP response contains status code 404 with the description Not Found XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    - <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
    - <SAP:Hop timeStamp="2005-04-12T06:52:37Z" wasRead="false">
      <SAP:Engine type="IS">is.50.weaver</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">IDoc</SAP:Adapter>
      <SAP:MessageId>550806B7-DEED-FF42-96B1-6F33852373F1</SAP:MessageId>
      <SAP:Info>MATMAS.0000000000214059:20050412085231</SAP:Info>
      </SAP:Hop>
    - <SAP:Hop timeStamp="2005-04-12T06:52:37Z" wasRead="false">
      <SAP:Engine type="IS">is.50.weaver</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
      <SAP:MessageId>550806B7-DEED-FF42-96B1-6F33852373F1</SAP:MessageId>
      <SAP:Info>3.0</SAP:Info>
      </SAP:Hop>
      </SAP:HopList>
    - <SAP:IDocInbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <SAP:TABNAM>EDI_DC40</SAP:TABNAM>
      <SAP:MANDT>200</SAP:MANDT>
      <SAP:DOCREL>46C</SAP:DOCREL>
      <SAP:DOCNUM>0000000000214059</SAP:DOCNUM>
      <SAP:DIRECT>1</SAP:DIRECT>
      <SAP:IDOCTYP>MATMAS04</SAP:IDOCTYP>
      <SAP:CIMTYP />
      <SAP:MESTYP>MATMAS</SAP:MESTYP>
      <SAP:MESCOD />
      <SAP:MESFCT />
      <SAP:SNDPOR>SAPDEV</SAP:SNDPOR>
      <SAP:SNDPRN>LOGDEV200</SAP:SNDPRN>
      <SAP:SNDPRT>LS</SAP:SNDPRT>
      <SAP:SNDPFC />
      <SAP:RCVPOR>XI-TEST</SAP:RCVPOR>
      <SAP:RCVPRN>LOGXID700</SAP:RCVPRN>
      <SAP:RCVPRT>LS</SAP:RCVPRT>
      <SAP:RCVPFC />
      <SAP:TEST />
      <SAP:SERIAL>20050412085231</SAP:SERIAL>
      <SAP:EXPRSS />
      <SAP:STD />
      <SAP:STDVRS />
      <SAP:STATUS>30</SAP:STATUS>
      <SAP:OUTMOD>2</SAP:OUTMOD>
      <SAP:SNDSAD />
      <SAP:SNDLAD />
      <SAP:RCVSAD />
      <SAP:RCVLAD />
      <SAP:STDMES />
      <SAP:REFINT />
      <SAP:REFGRP />
      <SAP:REFMES />
      <SAP:CREDAT>2005-04-12</SAP:CREDAT>
      <SAP:CRETIM>08:52:31</SAP:CRETIM>
      <SAP:ARCKEY />
      </SAP:IDocInbound>
    - <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Date>20050412</SAP:Date>
      <SAP:Time>085237</SAP:Time>
      <SAP:Host>weaver</SAP:Host>
      <SAP:SystemId>XID</SAP:SystemId>
      <SAP:SystemNr>50</SAP:SystemNr>
      <SAP:OS>Windows NT</SAP:OS>
      <SAP:DB>MSSQL</SAP:DB>
      <SAP:Language />
      <SAP:ProcStatus>014</SAP:ProcStatus>
      <SAP:AdapterStatus>000</SAP:AdapterStatus>
      <SAP:User>ANNA</SAP:User>
      <SAP:TraceLevel>1</SAP:TraceLevel>
      <SAP:LogSeqNbr>002</SAP:LogSeqNbr>
      <SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
      <SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
      <SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
      <SAP:PipelineElementId>60C3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
      <SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
      <SAP:PipelineService>PLSRV_CALL_ADAPTER</SAP:PipelineService>
      <SAP:QIdInternal>XBTO3___0000</SAP:QIdInternal>
      <SAP:CommitActor>A</SAP:CommitActor>
      <SAP:SplitNumber>0</SAP:SplitNumber>
      <SAP:NumberOfRetries>0</SAP:NumberOfRetries>
      <SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
      <SAP:TypeOfEngine client="700">CENTRAL</SAP:TypeOfEngine>
      <SAP:PlsrvExceptionCode />
      <SAP:EOReferenceRuntime type="TID">DF010AB7129C425B7035011D</SAP:EOReferenceRuntime>
      <SAP:EOReferenceInbound type="TID">DF013D07020C425B70300B0A</SAP:EOReferenceInbound>
      <SAP:EOReferenceOutbound type="TID" />
      <SAP:MessageSizePayload>16517</SAP:MessageSizePayload>
      <SAP:MessageSizeTotal>0</SAP:MessageSizeTotal>
      <SAP:PayloadSizeRequest>16517</SAP:PayloadSizeRequest>
      <SAP:PayloadSizeRequestMap>16527</SAP:PayloadSizeRequestMap>
      <SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
      <SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
      <SAP:Reorganization>INI</SAP:Reorganization>
      <SAP:AdapterInbound>IDOC</SAP:AdapterInbound>
      <SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
      <SAP:RandomNumber>71</SAP:RandomNumber>
      <SAP:AckStatus>071</SAP:AckStatus>
      <SAP:SkipReceiverDetermination />
      </SAP:RunTime>
    - <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="begin" host="weaver">20050412065237.471</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="end" host="weaver">20050412065237.471</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="weaver">20050412065237.471</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="end" host="weaver">20050412065237.642</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="weaver">20050412065237.642</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="weaver">20050412065237.658</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="weaver">20050412065237.658</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="weaver">20050412065237.658</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="begin" host="weaver">20050412065237.658</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="end" host="weaver">20050412065237.674</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="weaver">20050412065237.674</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
      <SAP:Timestamp type="end" host="weaver">20050412065237.814</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="begin" host="weaver">20050412065237.814</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="end" host="weaver">20050412065237.939</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
      <SAP:Timestamp type="begin" host="weaver">20050412065237.939</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
      <SAP:Timestamp type="end" host="weaver">20050412065237.971</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
      <SAP:Timestamp type="begin" host="weaver">20050412065237.971</SAP:Timestamp>
      </SAP:RunTimeItem>
      </SAP:PerformanceHeader>
    - <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:TraceLevel>Information</SAP:TraceLevel>
      <SAP:Logging>Off</SAP:Logging>
      </SAP:Diagnostic>
    - <SAP:OutboundBinding xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    - <SAP:OutboundBindingEntry version="30">
      <SAP:OutboundBindingObjectId>B0E25658819A3AE888B48BAD55537C5E</SAP:OutboundBindingObjectId>
      <SAP:FromPartyName />
      <SAP:FromServiceName>DEV</SAP:FromServiceName>
      <SAP:ToPartyName />
      <SAP:ToServiceName>XIT</SAP:ToServiceName>
      <SAP:ToInterfaceName>MATMAS.MATMAS04</SAP:ToInterfaceName>
      <SAP:ToInterfaceNamespace>urn:sap-com:document:sap:idoc:messages</SAP:ToInterfaceNamespace>
    - <SAP:OutboundBindingAttributes>
      <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      </SAP:OutboundBindingAttributes>
    - <SAP:HeaderMapping>
      <SAP:FieldMapping xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      </SAP:HeaderMapping>
    - <SAP:ChannelEntry version="30">
      <SAP:PartyName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ServiceName xmlns:SAP="http://sap.com/xi/XI/Message/30">XIT</SAP:ServiceName>
      <SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">GeneratedReceiverChannel_XI</SAP:ChannelName>
      <SAP:AdapterName xmlns:SAP="http://sap.com/xi/XI/Message/30">XI</SAP:AdapterName>
      <SAP:AdapterNamespace xmlns:SAP="http://sap.com/xi/XI/Message/30">http://sap.com/xi/XI/System</SAP:AdapterNamespace>
      <SAP:AdapterSWCV xmlns:SAP="http://sap.com/xi/XI/Message/30">3B787A8035C111D6BBE0EFE50A1145A5</SAP:AdapterSWCV>
      <SAP:AdapterEngineType xmlns:SAP="http://sap.com/xi/XI/Message/30">IS</SAP:AdapterEngineType>
      <SAP:AdapterEngineName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:MessageProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">XI</SAP:MessageProtocol>
      <SAP:MessageProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30">3.0</SAP:MessageProtocolVersion>
      <SAP:TransportProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">HTTP</SAP:TransportProtocol>
      <SAP:TransportProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30">1.0</SAP:TransportProtocolVersion>
      <SAP:ChannelDirection xmlns:SAP="http://sap.com/xi/XI/Message/30">O</SAP:ChannelDirection>
      <SAP:FromPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:FromPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ToPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ToPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
    - <SAP:ChannelAttributes xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:Attribute>
      <SAP:Name>addressingMode</SAP:Name>
      <SAP:Value>url</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>authenticationModeBasicAnon</SAP:Name>
      <SAP:Value>anonymous</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>host</SAP:Name>
      <SAP:Value>victor</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>httpDestination</SAP:Name>
      <SAP:Value />
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>isMessageSecurity</SAP:Name>
      <SAP:Value>0</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>logonClient</SAP:Name>
      <SAP:Value />
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>logonLanguage</SAP:Name>
      <SAP:Value />
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>logonPassword</SAP:Name>
      <SAP:Value isPassword="true" encryption="hw">AQ==</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>logonUser</SAP:Name>
      <SAP:Value />
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>passHopList</SAP:Name>
      <SAP:Value>1</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>path</SAP:Name>
      <SAP:Value>/sap/xi/engine?type=entry</SAP:Value>
      </SAP:Attribute>
    - <SAP:Attribute>
      <SAP:Name>port</SAP:Name>
      <SAP:Value>56000</SAP:Value>
      </SAP:Attribute>
      </SAP:AdapterTypeData>
      </SAP:ChannelAttributes>
      </SAP:ChannelEntry>
      </SAP:OutboundBindingEntry>
      </SAP:OutboundBinding>
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="B" name="IDX_INBOUND_XMB" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
      <Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
      <Trace level="1" type="T">Syntax-Check-Flag X</Trace>
      <Trace level="1" type="T">IDoc-Tunnel-Flag</Trace>
      <Trace level="1" type="T">Queueid</Trace>
    - <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
      <Trace level="1" type="T">Get the Metadata for port SAPDEV</Trace>
      <Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
      <Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>
      </Trace>
      <Trace level="1" type="T">Set Receiver Routing-object</Trace>
      <Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
      <Trace level="1" type="T">COMMIT is expected by application !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="1" type="T">system-ID = XID</Trace>
      <Trace level="1" type="T">client = 700</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = ANNA</Trace>
      <Trace level="1" type="Timestamp">2005-04-12T06:52:37Z CET</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = 550806B7DEEDFF4296B16F33852373F1</Trace>
      <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
      <Trace level="1" type="T">Queue name : XBTI0010</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTI0010</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="1" type="T">system-ID = XID</Trace>
      <Trace level="1" type="T">client = 700</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = ANNA</Trace>
      <Trace level="1" type="Timestamp">2005-04-12T06:52:37Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
      <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">number of receivers: 1</Trace>
      <Trace level="1" type="T">Single-receiver split case</Trace>
      <Trace level="1" type="T">Post-split internal queue name = XBTO3___0000</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Persisting single message for post-split handling</Trace>
      <Trace level="1" type="T" />
      <Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="1" type="T">system-ID = XID</Trace>
      <Trace level="1" type="T">client = 700</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = ANNA</Trace>
      <Trace level="1" type="Timestamp">2005-04-12T06:52:37Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
    - <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
      <Trace level="1" type="T">Interface Mapping urn:XI_to_XI_Simulation MATMAS04_MATMAS04</Trace>
      <Trace level="1" type="T">*** APPLICATION TRACE TRUNCATED (for more details see LogViewer)***</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
      <Trace level="1" type="T">processing the outbound binding</Trace>
      <Trace level="1" type="T">search outbound bindings</Trace>
      <Trace level="1" type="T">outbound bindings found</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
      <Trace level="1" type="T">Sender: Header mapped to</Trace>
      <Trace level="1" type="T">Party =</Trace>
      <Trace level="1" type="T">Agency =</Trace>
      <Trace level="1" type="T">Scheme =</Trace>
      <Trace level="1" type="T">Service = DEV</Trace>
      <Trace level="1" type="T">Receiver: Header mapped to</Trace>
      <Trace level="1" type="T">Party =</Trace>
      <Trace level="1" type="T">Agency =</Trace>
      <Trace level="1" type="T">Scheme =</Trace>
      <Trace level="1" type="T">Service = XIT</Trace>
      <Trace level="1" type="T">Party denormalization: sender</Trace>
      <Trace level="1" type="T">Sender target scheme =</Trace>
      <Trace level="1" type="T">Sender target agency =</Trace>
      <Trace level="1" type="T">Sender party normalized =</Trace>
      <Trace level="1" type="T">Sender party external =</Trace>
      <Trace level="1" type="T">Party denormalization: receiver</Trace>
      <Trace level="1" type="T">Receiver target scheme =</Trace>
      <Trace level="1" type="T">Receiver target agency =</Trace>
      <Trace level="1" type="T">Receiver party normalized =</Trace>
      <Trace level="1" type="T">Receiver party external =</Trace>
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
      <Trace level="1" type="System_Error">HTTP-client: error response= <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Error Report</title> <style> td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active

    Hi,
    The 'Communication Channel' in Integration Builder was not configured right in the 'Service Number' field. There was a J2EE port instead of HTTP port.
    J2EE port: 5<instance number>00
    HTTP port: 80<instance number>
    Good luck to everyone,
    Dimitry

  • How to resolve HTTPS status code 404 using WinHTTP?

    I am getting status code 404 for the below code snippet.
    Note: please add `<HOSTNAME>` when you are trying to figure out the issue.
    HINTERNET m_hConnect;
    HINTERNET m_hSession;
    HINTERNET m_hRequest;
    m_hSession = WinHttpOpen(userAgent,
    WINHTTP_ACCESS_TYPE_NO_PROXY,
    WINHTTP_NO_PROXY_NAME,
    WINHTTP_NO_PROXY_BYPASS, 0);
    if (!m_hSession) {
    printf("WinHttpOpen:Error %d has occurred.",GetLastError());
    return 0;
    // connect to the IPP server on the given port
    m_hConnect = WinHttpConnect( m_hSession, <HOSTNAME>, 443, 0);
    if (!m_hConnect) {
    printf("WinHttpConnect: Error %d has occurred.",GetLastError());
    return 0;
    // Create an HTTP Request handle.
    m_hRequest = WinHttpOpenRequest(m_hConnect, L"POST" ,L"/ipp",
    L"HTTP/1.1", WINHTTP_NO_REFERER,
    WINHTTP_DEFAULT_ACCEPT_TYPES,WINHTTP_FLAG_SECURE);
    if (!m_hRequest) {
    printf("WinHttpOpenRequest:Error %d has occurred.",GetLastError());
    return 0;
    DWORD secureflags = SECURITY_FLAG_IGNORE_UNKNOWN_CA | SECURITY_FLAG_IGNORE_CERT_CN_INVALID |SECURITY_FLAG_IGNORE_CERT_WRONG_USAGE | SECURITY_FLAG_IGNORE_CERT_DATE_INVALID;
    BOOL bResult= WinHttpSetOption(m_hRequest, WINHTTP_OPTION_SECURITY_FLAGS, (LPVOID)&secureflags, sizeof(secureflags));
    if (!bResult) {
    printf("WinHttpSetOption:Error %d has occurred.",GetLastError());
    return 0;
    bResult = WinHttpSendRequest(m_hRequest, WINHTTP_NO_ADDITIONAL_HEADERS,0,WINHTTP_NO_REQUEST_DATA,0,0,0);
    if (!bResult) {
    printf("WinHttpSendRequest:Error %d has occurred.",GetLastError());
    return 0;
    if( !WinHttpReceiveResponse( m_hRequest, NULL ) )
    if( GetLastError( ) == ERROR_WINHTTP_CLIENT_AUTH_CERT_NEEDED )
    HCERTSTORE hMyStore = 0;
    PCCERT_CONTEXT pCertContext = 0;
    WCHAR szCertName[256]={0};
    //MY is the store the certificate is in.
    hMyStore = CertOpenSystemStore( 0, TEXT("MY") );
    if( hMyStore )
    pCertContext = CertFindCertificateInStore( hMyStore,
    X509_ASN_ENCODING | PKCS_7_ASN_ENCODING,
    0,
    CERT_FIND_SUBJECT_STR,
    (LPVOID) szCertName, //Subject string in the certificate.
    NULL );
    if( pCertContext )
    WinHttpSetOption( m_hRequest,
    WINHTTP_OPTION_CLIENT_CERT_CONTEXT,
    (LPVOID) pCertContext,
    sizeof(CERT_CONTEXT) );
    CertFreeCertificateContext( pCertContext );
    CertCloseStore( hMyStore, 0 );
    // NOTE: Application should now resend the request.
    bResult = WinHttpSendRequest(m_hRequest, WINHTTP_NO_ADDITIONAL_HEADERS,0,WINHTTP_NO_REQUEST_DATA,0,0,0);
    if (!bResult) {
    printf("WinHttpSendRequest:Error %d has occurred.",GetLastError());
    return 0;
    DWORD dwStatusCode = 0;
    DWORD dwSize = sizeof(DWORD);
    BOOL bResults = true;
    bResults = WinHttpQueryHeaders( m_hRequest, WINHTTP_QUERY_STATUS_CODE | WINHTTP_QUERY_FLAG_NUMBER, NULL, &dwStatusCode, &dwSize, NULL );
    Result: I am getting status code of 404. I am not able to figure out why it is happening.
    FYI, Using `WinINet`,  I have followed the same procedure, I am getting status code of 200, which is success. But my requirement is to use only `WinHttp`.
    Could any one please help me out to solve this issue. This is very urgent for me.
    SivaV

    Dear Henri,
    Thanks for your reply, it was really very helpful.
    I debugged
    HTTP session with Fiddler,
    I am getting certificate error.
    When I say 'Yes' in Fiddler, I am getting 200 success.
    Could you please help me out how to
    "Ignore certificate errors" using WinHTTP
    API's.
    Thanks in Advance.
    Best Regards,
    Siva
    SivaV

  • Java.rmi.RemoteException: HTTP Status-Code 404 Not Found  securesimple/Ping

    Hello!
    I'm testing interop and simple application for JWSDP and I get the following error in the context:
    build-client:
    run-sample:
    [echo] Running the simple.TestClient program....
    [java] Service URL=http://localhost:8080/securesimple/Ping
    [java] Nov 4, 2004 1:31:54 PM com.sun.xml.wss.filter.DumpFilter process
    [java] INFO: ==== Sending Message Start ====
    [java] <?xml version="1.0" encoding="UTF-8"?>
    [java] <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/".............
    [java] </env:Body>
    [java] </env:Envelope>
    [java] ==== Sending Message End ====
    So, after the client has send the message this error occurs:
    [java] java.rmi.RemoteException: HTTP Status-Code 404: Not Found - /secures
    imple/Ping; nested exception is:
    [java] HTTP Status-Code 404: Not Found - /securesimple/Ping
    [java] at simple.PingPort_Stub.ping(PingPort_Stub.java:96)
    [java] at simple.TestClient.main(TestClient.java:37)
    [java] Caused by: HTTP Status-Code 404: Not Found - /securesimple/Ping
    [java] at com.sun.xml.rpc.client.http.HttpClientTransport.checkResponse
    Code(HttpClientTransport.java:302)
    [java] at com.sun.xml.rpc.client.http.HttpClientTransport.connectForRes
    ponse(HttpClientTransport.java:252)
    [java] at com.sun.xml.rpc.client.http.HttpClientTransport.invoke(HttpCl
    ientTransport.java:88)
    [java] at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.
    java:92)
    [java] at simple.PingPort_Stub.ping(PingPort_Stub.java:80)
    [java] ... 1 more
    [java] Exception in thread "main"
    [java] Java Result: 1
    The application is running on localhost in a local network, so for accesing internet we're using a proxy. For this we tried to set up the proxy configuration and still the same error. We've also unplugged the network cable but it didn't help.
    We've done all the neccesary settings and we're using "org.bouncycastle.jce.provider.BouncyCastleProvider " as a JCE provider.
    Thank you!

    Just a guess, but if this is a secure web service shouldn't you be trying to connect to it using SSL? e.g.
    https://localhost:443/securesimple/Ping
    Have you tried hitting the web service via your browser and appending the ?WSDL to the URL
    http://localhost:8080/securesimple/Ping?WSDL
    https://localhost:443/securesimple/Ping?WSDL
    Can you telnet to http://localhost:8080

  • Status Code: 404 Not Found

    Hi,
    I have created simple REST Full services. It would validate the data and send it into a Queue. I have added a REST Client add-on's to my Mozilla browser . I got the following error when i test the rest full web services through Rest client .
    Status Code: 404 Not Found
    Content-Length: 1164
    Content-Type: text/html; charset=UTF-8
    Date: Mon, 08 Jul 2013 16:22:41 GMT
    X-ORACLE-DMS-ECID: a26c3ae948dcd922:28156ab0:13fbd9dc11f:-8000-00000000000001fc
    X-Powered-By: Servlet/2.5 JSP/2.1
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Draft//EN">
    <HTML>
    <HEAD>
    <TITLE>Error 404--Not Found</TITLE>
    </HEAD>
    <BODY bgcolor="white">
    <FONT FACE=Helvetica><BR CLEAR=all>
    <TABLE border=0 cellspacing=5><TR><TD><BR CLEAR=all>
    <FONT FACE="Helvetica" COLOR="black" SIZE="3"><H2>Error 404--Not Found</H2>
    </FONT></TD></TR>
    </TABLE>
    <TABLE border=0 width=100% cellpadding=10><TR><TD VALIGN=top WIDTH=100% BGCOLOR=white><FONT FACE="Courier New"><FONT FACE="Helvetica" SIZE="3"><H3>From RFC 2068 <i>Hypertext Transfer Protocol -- HTTP/1.1</i>:</H3>
    </FONT><FONT FACE="Helvetica" SIZE="3"><H4>10.4.5 404 Not Found</H4>
    </FONT><P><FONT FACE="Courier New">The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.</p><p>If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.</FONT></P>
    </FONT></TD></TR>
    </TABLE>
    </BODY>
    Can anyone Help me out. I was struck here
    Thanks,
    Viswas
    </HTML>

    Issue has been resolved. There is no tric. My suggestion is before going to test any rest full service over the browser, If we test at sb console level at least we can trace the error.
    you may get this fault when your web service has any syntax problem or validation problem or condition failing .so we can get this problem...
    Thanks,
    Viswas

  • MBAM 2.5 integration broke my Primary Site Server - Managment Point http status code 404, not found

    I uninstalled MBAM 2.0 and installed MBAM 2.5. During 2.5 installation there was this one section to enter "Web service application pool domain account", where I entered domain admin account. I don´t know if that has any effect on this problem.
    Though, situation now is that my site is now out of order because of Management Point cannot connect to IIS or something like that.
    In status messages I see "MP Control Manager detected management point is not responding to HTTP requests.  The HTTP status code and text is 404, Not Found. Message ID 5436".
    In mpcontrol.log I see Call to HttpSendRequestSync failed for port 80 with status code 404, text: Not Found
    I have tried:
    Bindings checked, that http uses port 80
    MP component is uninstalled and reinstalled succsessfully
    Primary site server has restarted several times
    In IIS, Default Site -> SMS_MP->Basic Settings I did "Test Settings". With pass-through authentification it cannot Access the D:\SMS_CCM path, I changed to the domain admin, and it succseed. I have no idea, does this have something to do
    with it.

    I have experienced all the above problems also and they can be a pain to fix. I guess the moral of the story is (as Andy says) leave the ConfigMgr server alone. If you want an MBAM server then build an MBAM server.
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson
    Hmm, I guess ConfMgr integration will not be the problem if your MP is using http(80) and MBAM will use https(443). If you then set spn to https, it will use 443 as-is, right? But other custom ports might be the problem?

  • Error Handler Returning 200 Status Code

    Greetings,
    I have a section of my site assigned to be an "Error Handler" however when a user is brought to this page, the status code is a 200. As you can imagine, this has the potential to cause a lot of problems for processes that rely on status codes to operate.
    I have found the following solution on another site, indicating to place this Idoc Script code at the top of the Page Template:
    <!--$setValue("#local", "ssChangeHTTPHeader", "true")-->
    Unfortunately, doing the above does not work. Am I missing something?
    Any help is appreciated. Thanks!
    Josh

    Hi Srinath,
    First of all, thanks for taking time to help. I removed the tag that I previously had inside of my Page Template and put yours in the body, however my page still returns a 200. I completely stripped the Page Template of all but the necessary markup.
    <!DOCTYPE html>
    <html lang="en">
    <head>
         <meta charset="UTF-8">
         <!--$include ss_layout_head_info-->
         <meta http-equiv="X-UA-Compatible" content="IE=edge" />
         <meta name="viewport" content="width=device-width, initial-scale=1">
         <script id="ssInfo" type="text/xml" warning="DO NOT MODIFY!">
              <ssinfo></ssinfo>
         </script>
    </head>
    <body>
         <!--$ssSet404Response("true")-->
    </body>
    </html>
    Thanks!

  • ERRORs executing CWM commands in SQL Plus

    Hi,
    I tried to execute following command in SQL Plus:
    execute cwm_olap_dimension.set_plural_name('olapdata', 'OLAP_APARAT_DIM', 'OLAP_APARAT_DIM');
    And in response I got following result:
    BEGIN cwm_olap_dimension.set_plural_name('olapdata', 'OLAP_APARAT_DIM', 'OLAP_APARAT_DIM'); END;
    ERROR at line 1:
    ORA-06510: PL/SQL: unhandled user-defined exception
    ORA-06512: at "OLAPSYS.CWM$UTIL", line 535
    ORA-06512: at "OLAPSYS.CWM$OLAP$DIMENSION", line 17
    ORA-06512: at line 1
    Can anyone explane me what am i doing wrong ?
    I would really appreciate any help!
    Thanks

    check SQL*Plus user's guide
    e.g column REMARK format a30
    set linesize 2243
    etc etc etc

  • Status code 404

    I've deployed a web application to a hosting provider. The application works on my local machine but when I try to run the application from the hosted server I see the 404 error page produced by Tomcat. ETA - I know that 404 means resource not found. Tomcat is unable to find the resource requested by the client.
    It's been a long time since I've wrestled with something like this and I'm wondering how to debug this. How should I investigate where I've gone wrong? What sorts of things should I look for? Feeling like a brain drain.
    Thanks in advance for any help.
    Edited by: nantucket on May 28, 2010 7:32 PM

    I managed to resolve this by simply redeploying my application. It turns out the war wasn't really being unpacked by Tomcat. So I deleted the original directory and redeployed the war file and it expanded properly and I no longer get a 404 code as response to the request.

  • CPIC error executing SNDDST command

    Hello All!
    We are using SNDDST command to send messages to user mailboxes for simple notification in a process. These are the steps that I did:
    - create an external OS command in SM49;
    - create an entry in WRKDIRE to user R3P02 (user SID+System number -> it starts R3 system);
    - change user profile R3P02 to limit capabilities -> *PARTIAL;
    I made a copy os user profile R3P02 to test sending messages from OS/400. From OS sends normally but when the command is called from R/3 occurs a timeout of connection. (by function module SAPXPG_START_XPG)
    I have extracted this portion of dev_rfc trace file:
    ======> CPIC-CALL: 'ThSAPCMRCV'                                                
    Excesso de tempo na estrutura de conexão (existe parceiro ?)                   
    ABAP Programm: SAPLSXPT (Transaction: ZME28A)                                  
    Called function module: SAPXPG_START_XPG                                       
    User: LOLIVEIR (Client: 400)                                                   
    Destination: %_TCPIP_%1 (handle: 2, convid , {464D7A0F-6E92-15A0-E100-0000800101
    Error RFCIO_ERROR_SYSERROR in /build/bas/46D/gen/opt/abrfcpic.c : 2963         
    CPIC-CALL: 'ThSAPCMRCV'                                                        
    Thanks for all help.
    Best Regards,
    André Koji Honma
    Support Analyst
    FUJIFILM da Amazônia Ltda.

    Hello André,
    A Question to determin where the problem lies.
    Is the SNDDST command working from a 5250 session command line ?
    If not please have a look at the following link:
    http://www-1.ibm.com/support/docview.wss?rs=0&context=SWG60&dc=DB520&dc=D900&dc=D800&dc=DA900&dc=DA800&q1=SMTPRTEANDAS400KBXXYYZZRCH&uid=nas134879f5e413aa5cd8625697b0053f36a&loc=en_US&cs=UTF-8&lang=all
    Regards, Rudi van Helvoirt

  • Error executing sudo command

    When I try to execute a sudo command I get the following message:
    "sudo: /etc/sudoers is mode 0644, should be 0440
    Segmentation fault"
    What does it mean?
    Thanks for all the help.

    When I try to execute a sudo command I get the following message:
    "sudo: /etc/sudoers is mode 0644, should be 0440
    Segmentation fault"
    What does it mean?
    It means someone has incorrectly modified the /etc/sudoers file, and as a side effect its permissions were changed to an insecure form, so sudo refuses to use the file. It is also possible that the /etc/sudoers file syntax is also invalid, which might also cause the segmentation fault.
    'visudo' should be used to edit the /etc/sudoers file, which would have properly preserved the permissions, as well as verified that the updated /etc/sudoers file contained valid syntax so that sudo would continue to work. See 'man visudo'.
    You now have a problem, in that you can no longer use sudo to fix the permissions.
    You should first try booting your installation DVD. Via the Menu, you can run Disk Utility and run Repair Permissions. Hopefully this will repair the /etc/sudoers file. You could try running Applications -> Utilities -> Disk Utility, however, if it wants to use sudo to elevate its privileges, that would fail, as a broken /etc/sudoers file is still a broken /etc/sudoers file.
    If you have by any chance enabled the 'root' account, you could try logging in as root and fixing the /etc/sudoers file's permissions.
    You should also run visudo, so that the file's syntax is valid.
    I think you can use the Installation DVD to enable the root account. that might be another way to login as root.
    If repair permissions does not work, then maybe you can put your Mac into firewire target mode, mount your Mac's disk on another Mac via firewire, and repair the /Volume/Macintosh HD/etc/sudoers permissions from the working Mac.
    If that failes, the next step is booting your Mac in Single User mode. Search for "Single User Mode" in the forums, and you should find instructions on both booting, as well as how to make the root file system writable so you can change the permissions from single user mode.
    And if that does not work, I think you are left with reinstalling the OS.
    Message was edited by: BobHarris

Maybe you are looking for