Status report 404 on tomcat

I have hit a bit of a wall with regard to deploying a servlet using tomcat.
I have followed and endless list of instructions I found on various web sites, but still I am having trouble.
The versions of tomcat I have is 5.0 with the j2sdk1.4.2_03.
My project allows for a user to enter a url in a form, which is then processed by a java servlet, and links within the url are validated. The problem I�m having is that when the form is submitted, tomcat returns the status report: 404 requested resource unavailable.
The url entered is http://localhost:8080/sitevalidation/INDEX.HTM - this works fine and the home page appears.
When the form is submitted, the url changes to http://localhost:8080/sitevalidation/SiteValidation - which I assume is then looking for the servlet declared in the web.xml file, this is when the problems start!
I think I have the correct file structure as I have included the application dir �sitevalidation� in the webapps directory of tomcat. Sitevalidation contains the web-inf dir, which in turn contains the web.xml file, and the classes dir, which contains SiteValidation.class.
my web.xml file reads:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC
"-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
<display-name>Site Validation</display-name>
<description>
This is the Site Validation Program Written in Java
</description>
<servlet>
<servlet-name>SiteValidation</servlet-name>
<servlet-class>SiteValidation</servlet-class>
</servlet>
          <servlet-mapping>
<servlet-name>SiteValidation</servlet-name>
<url-pattern>/SiteValidation</url-pattern>
</servlet-mapping>
</web-app>
Any suggestions to where I might be going wrong would be most appreciated.
Many thanks,
Dan Williams

Hello.
Uncomment the InvokerServlet in the $CATALINA_HOME/conf/web.xml.
<servlet>
<servlet-name>invoker</servlet-name>
<servlet-class>
org.apache.catalina.servlets.InvokerServlet
</servlet-class>
<init-param>
<param-name>debug</param-name>
<param-value>0</param-value>
</init-param>
<load-on-startup>2</load-on-startup>
</servlet>
and
<servlet-mapping>
<servlet-name>invoker</servlet-name>
<url-pattern>/servlet/*</url-pattern>
</servlet-mapping>
Then your target URL will http://localhost:8080/sitevalidation/servlet/SiteValidation .
Good luck.

Similar Messages

  • 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

  • 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

  • Sale Order Status Report

    Dear Expert.
    I want Sales Order Status report as below mentioned format required quarry base report from Date to To Date.
    Location-OrderSeries-OrderNo-CardCode-CardName-ItemCode-Item Descripotion-Inv.UOM-Order Qty-Allocated Qty-DeliverQty-Peniding Qty adn Pending Order Value.

    Hi,
    You can check this :
    select t3.location as 'Location',t0.series as 'Order Series',
    t0.docnum as 'Order No.',t0.cardcode as 'Business Partner Code',
    t0.cardname as 'Business Partner Name', t1.itemcode as 'Item',
    t1.dscription as 'Item Name', t2.invntryUom as 'Inventory UoM',t1.quantity as 'Order Qty',
    t1.QtyToship as 'Allocated Qty- Qty to Ship', t1.delivrdQty as 'Delivered Qty',
    t1.OrderedQty as 'Ordered Qty', t1.openCreQty as 'Pending Qty',
    t1.Opensum as 'Pending Order Row Value'
    from ORDR t0 inner join RDR1 t1 on t1.docentry = t0.docentry
    inner join OITM t2 on t2.itemcode = t1.itemcode
    inner join OLCT t3 on t3.code = t1.loccode
    where t0.docdate >= '2011.01.01' and t0.docdate <= '2011.12.31'
    Hope it helps.
    Kind Regards,
    Jitin
    SAP Business One Forum Team

  • Sales Order Status Report

    Hi,
    Can you please guide me for Sales Order status report extractors?whether some standard extractors would be used or customized or standard is available which can further be enhanced.
    Scenario is- I have to populate report columns like
    0-25000     25001-50000     50001-100000     100001-200000     200001-500000     500000>
    And analysis has to be shown in the report rows : Sales District. In Columns only number of sales order in each district would be entered as a number. Example- of for district ZMJT there are 3 order are in pending stage having quantities 35000 then entry 3 will come in first column and so on. Following are other columns for drill down purpose.
    Input Fields:
    Date Range
    Company Code
    Currency Type
    Sales District
    Sales Group
    Analytical Fields-
    Sales Org.
    Distribution Ch.
    Division
    Sales Order No.
    Sales Order Dt.
    Sales District
    Tube Dia
    Tube Length
    Laminate Structure
    Application Category
    Customer
    Customer Group
    Sales office
    Sales region
    Sales Order Qty
    Sales order Value
    Regards,
    Ritika

    Hi,
      We have standard extractor 2LIS_11_VASTI (Sales Document Item Status) for getting the status.
    Regards,
    Vamsi Krishna

  • What is table field name for order status report  of rate per unit and  bal

    hi  i want to make FS for order status report i almost get all table and field but i don't get only two field  rate per unit and balance value  table field didn't get please help me searching in field and table
      i want to develop my status report

    Hi,
    Check tables VBAK and VBAP wherein you will get all header and item details.
    VBUK and VBUP for header and line item statuses.
    KONV would give you rates/pricing details for each condition type determines in the sales order.
    VBAK-KNUMV = KONV-KNUMV is how you relate both of them.
    Hope that helps.
    Regards,
    Amit

  • Material Order status report - Closed PO's

    Hi,
    In my "Material Order status report" I got closed PO's. I dont want any closed PO's to be displayed in my report. How to set this?
    Regards
    P.Ramprakash

    Hi,
    This is your own doveloped report or you are talking about any standared report.
    Regards,
    Manish

  • PO - Line Items Payment Status Report

    Hi Friends,
    Is it possible to get a PO (Line Items wise) Payment Status Report.
    My client wants PO Line wise payment status as a MM report development.
    We have Down Payment, Residual & Retention money as a business practise with our vendors
    Following is the MM-FI flow in our company code..
    Create & Release PR u2013 MM - Creating PR
    Create & Release PO (ME21N) u2013 MM u2013 Creating PO
    F-47 Down Payment Request u2013 MM u2013 Creating DPR
    F-48 Post Vendor Down Payment u2013 FI - Posting DPR
    FBZ5 Print Check for Payment Document u2013 FI - For printing cheques for DP only
    MIGO/ML81N, GR u2013 MM u2013 SES/GR for PO
    MIR7/MIR6 IR - MM/FI u2013 Parking & IR
    F-44 Clear Vendor u2013 Linking advance with IR (as residual clearing)
    F-53/F-58 u2013 Posting Payments after deducting Retention
    F-04 Post with Clearing u2013 Clearing Outgoing account entries with Main account
    Thanks in advance.
    Regards,
    Vikrant Sood
    Moderator: This thread has been locked due to crossposting.
                       Please do not post the same question in different forums.

    hi
    there is no sap standard report available you have to develop your z report.

  • PO (Line Items wise) Payment Status Report

    Hi Friends,
    Is it possible to get a PO (Line Items wise) Payment Status Report.
    My client wants PO Line wise payment status as a MM report development.
    We have Down Payment, Residual & Retention money as a business practise with our vendors
    Following is the MM-FI flow in our company code..
    Create & Release PR u2013 MM - Creating PR
    Create & Release PO (ME21N) u2013 MM u2013 Creating PO
    F-47 Down Payment Request u2013 MM u2013 Creating DPR
    F-48 Post Vendor Down Payment u2013 FI - Posting DPR
    FBZ5 Print Check for Payment Document u2013 FI - For printing cheques for DP only
    MIGO/ML81N, GR u2013 MM u2013 SES/GR for PO
    MIR7/MIR6 IR - MM/FI u2013 Parking & IR
    F-44 Clear Vendor u2013 Linking advance with IR (as residual clearing)
    F-53/F-58 u2013 Posting Payments after deducting Retention
    F-04 Post with Clearing u2013 Clearing Outgoing account entries with Main account
    Thanks in advance.
    Regards,
    Vikrant Sood

    as per my knowledge you can configue a new Z table or prepare a Query using EKPO table you will your desired result.
    regards,
    Ninad Kshirsagar

  • Task status  report in cProject 3.1

    Hi,
    I want to extract task status report from cProject 3.1.
    Report should contain task name, status, start date,end date , effort etc.
    Thanks in advance
    Shiv

    Hi,
    Activate the form DPR_TASK_HIER for a particular Project type in SPRO screen. Now keep the cursor on any task in cProjects & click on Print pushbutton, this will generate a PDF Report which will contain Task name, Constraint dates, actual dates, administration details etc. In order to add more data to the Report, goto transaction SAMRTFORMS & edit the form DPR_TASK_HIER.
    Hope this will help you.
    Regards,
    Sujay G

  • Inventory Status Report issue

    Hello,
    Upon running the Inventory Status report for  item group    item no. 'A' shows 5,000 Ordered.   When I drilled  down on the 5,000, SAP B1 only shows 4,500 on open POs.   Please help  
    Using SAP B1 9.0 PL11
    Thanks,
    Jagriti

    Hi,
    Please refer SAP note:
    991077 - How to check 'Committed' and 'Ordered' values
    Thanks & Regards,
    Nagarajan

  • Approval Status Report, SBO v2007, current data or cumulative?

    I run the Approval Status Report while logged in as a superuser, selecting
    Document Status: 'Pending',
    no limits set in the To/From middle section,
    all document types ticked,
    and I get a list of document numbers.
    I immediately re-run the Approval Status Report while logged in as a superuser, selecting
    Document Status: 'Generated',
    no limits set in the To/From middle section,
    all document types ticked,
    and I get a list of document numbers that includes some of the 'Pending' status ones from the first run.
    How can the document be in both 'Pending' and 'Generated' status at the same time? Is this report supposed to show me the current status of documents, or all accumulated approval action taken on documents?

    Hi Cindy,
    Document number in approval is not unique.  Same number may refer to more than one document.  All draft documents will only be assigned a unique marketing document number until approved and created.
    That is probably you can see the same number in the 2 reports
    Thanks,
    Gordon

  • Claim status report - PC00_M40_REMS

    Hi experts
    Claims status report PC00_m40_rems is showing incorrect balance.  That is,  for example, eligibility is Rs. 50000
    Step1: Claim for the month for April is Rs.5000. Claim processed through PC00_M40_REMP. The claim status was successfull.
    After the above step, REMS report shows  Eligibility Rs.50, 000/- Claim payment - 0, claim due - Rs.5000/-, balance Rs.45000/- and no.of claim 1
    Step2: Claim was processed through offcycle payroll - PC00_m40_calc. After this process, the REMS report shows - Eligibility Rs.50000/-, claim payment - Rs.5000, claim due - Rs.5000/-, balance Rs.40,000/- and no. of claim 2
    Step3:  Then regular payroll was run. After the regular payroll, REMS is showing correct details i.e. Eligibility Rs.50,000/- Claim payment Rs.5000/-, Claim due - 0, balance Rs.45,000/- and no. of claim 1
    I suppose, the balance should show correct balance of Rs.45,000/- after the second step mentioned above.
    I have maintained bank details - Main bank and Main bank for offcycle.
    Kindly guide me.
    with regards

    hi Sikindar,
    In that table SMED has been assigned against my customised wagetype & also has been assigned aginst 00M0 wt;But In PC00_m40_REMP report it is showing calculation only against OOMO wt
    Thanks
    Sur

  • Database Status report.

    Hi Export,
    Currently i joined a company as a Oracle Dba. i am new to DBA world, My manager told me to prepare a database status report. Please suggest me how can i create the report.
    Regards...
    Asmit

    EdStevens wrote:
    marksmithusa wrote:
    That's an awesome idea - just one problem.
    If it's tall enough for all to see, this also includes management and if they notice the chicken, your cube will be instantly surrounded by various management types asking 'when will it be back up?'
    You're, almost literally, hoisting yourself with your own petard.True, but I think he had the understanding with mgmt that if the chicken was up, they'd best leave him alone until the chicken came down.Wow. I'm actually stunned - I didn't think that was possible within the physical laws of the universe that we occupy.
    He achieved 'DBA Hero' status.

  • Printer Status Report

    Printer: HP Photosmart 5515 on the label (but HP Photosmart 5510d B111h on the Printer Status Report).
    Operating system: Win 7
    Why does item 25 in my Printer Status Report show incorrect "Ink Install" dates? Depending on the colour, the date of installation of each ink cartridge is given as four or five days earlier than the actual date of replacement.  I would have thought that the date would be exactly as per my desktop computer to which the printer is connected via a USB cable.
    The printer is less than one year old and has given the incorrect dates from the moment the original set-up cartridges were replaced.

    HI LincsP,
    You are correct that the dates should in fact change and show the exact dates. This will not affect your ability to print or print quality at all. It may have something to do with you needing a product update. You can click here to find out how to check for a product update on your printer. 
    When it's time to change a cartridge next time print the Status report before you replace it and then again right after you replace it. If the same thing happens please scan the sheets and attach them to this thread for me to look at. 
    Let us know what happens.
    If I helped you at all it would be great if you clicked the blue kudos star!
    If I solved your post please mark it as solved to help others.
    I'm a printer tech with HP.

Maybe you are looking for

  • Doubt in data import from R3 to B1

    Hi , After many trails and errors we have successfully installed B1iSN and connected with both R3 and B1. But as of now the problem is the data transfer. I have did the following steps, 1.Installed B1iSN successfully with Event Sender. 2.In the Admin

  • How to Set File Handling on LIghtroom CC??

    I was watching a you tube on Lightroom CC and the person is using a mac - I am on WIndows.  The insructor selected the words "lightroom" to the left of "File" to get to catalogue settins.  I don't see that option so that I can set file handling etc f

  • MORE NANO PROBLEMS!!!!!!!!!!!!

    For the 4th time my nano wouldnt turn on and ive had to reset it everytime. This morning it stoped working and i got a sad ipod icon on the screen. I pluged it in to itunes and nothin happened the computer didnt pik it up. I letf it in whilst writing

  • Spinning Beach Ball and Startup Disc issue

    My friend has an IMAC and it has the latest updates and all... About once every day or two the mac just freezes and the rainbow beach ball spins... If she immediately restarts, she gets the question mark folder so her Imac is looking for a startup fo

  • Automatic inspection lot creation

    I am working in Pharma industry, For each material they have maintained certain validity period till date the material can be used or issued to production. now is there any way dat once the retest date is occured, the material should automatically cr