Messages are going to wrong Integration server

Hi,
In out SLD we have many servers like PD1(development) , PQ1, PQ2 etc.. somedays back basis team want to install some patch . so we moved to standbox for someday.. Pleaes note that we did client copy of PD1.. so all interface and we developed will point to PD1. now we have strange issue like when triggering the msg it getting appear in sandbox issue.. we chekced the ADM it was pointing the PD1 server. in the business systems too assigned to the PD1 integration server.. But how come the sandbox IS receiving the msg.. when we changed the related integration server to Sandbox server.. still the interface is working.. how come it is possible??
Regards
Balaji

Yes!! Web AS abap Systems.
I checked the SXMB_ADM , if pointing the PD1 server..
What the connection i should check in SM59.. apart from that any other things i should check??

Similar Messages

IDOCs are queued up In Integration Server

Folks ,
I am not able to process the iDOCS as they are choked up in Integration server with following trace , can anybody help me out
<i><b> <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>4445B42A-672D-40B8-E100-000064070151</SAP:MessageId>
<SAP:TimeSent>2006-04-19T18:43:47Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>BS_STG_R3_902_NA</SAP:Service>
<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">FIDCC2.FIDCCP01</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>BS_DEV_R3_950_CS</SAP:Service>
<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">FIDCC2.FIDCCP01</SAP:Interface>
- <SAP:Mapping notRequired="M">
<SAP:ObjectId>B4ydE1e/NPq9tEnsDcj7vA==</SAP:ObjectId>
<SAP:SWCV>U0Q4sKe1Edqe7daFZAcBUQ==</SAP:SWCV>
<SAP:SP>-1</SAP:SP>
</SAP:Mapping>
</SAP:Receiver>
<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">FIDCC2.FIDCCP01</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SystemAckRequested="false" SystemErrorAckRequested="true" ApplicationAckRequested="true" ApplicationErrorAckRequested="true" SOAP:mustUnderstand="1">
<SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <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="2006-04-19T18:43:47Z" wasRead="false">
<SAP:Engine type="IS" />
<SAP:Adapter namespace="http://sap.com/xi/XI/System">IDoc</SAP:Adapter>
<SAP:MessageId>44452091-7B42-40B7-E100-000064070151</SAP:MessageId>
<SAP:Info>FIDCC2.0000000018113400:20060419144347</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2006-04-19T18:43:47Z" wasRead="false">
<SAP:Engine type="IS">is.61.sun081</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>4445B42A-672D-40B8-E100-000064070151</SAP:MessageId>
- <SAP:Branch>
<SAP:MessageId>4445B42A-672D-40B8-E100-000064070151</SAP:MessageId>
<SAP:Service>BS_DEV_R3_950_CS</SAP:Service>
</SAP:Branch>
- <SAP:Branch>
<SAP:MessageId>4445B42B-672D-40B8-E100-000064070151</SAP:MessageId>
<SAP:Service>BS_DEV_R3_R1D_201_IE</SAP:Service>
</SAP:Branch>
<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>902</SAP:MANDT>
<SAP:DOCREL>31I</SAP:DOCREL>
<SAP:DOCNUM>0000000018113400</SAP:DOCNUM>
<SAP:DIRECT>1</SAP:DIRECT>
<SAP:IDOCTYP>FIDCCP01</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>FIDCC2</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPST4</SAP:SNDPOR>
<SAP:SNDPRN>ST4-902</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>A000000015</SAP:RCVPOR>
<SAP:RCVPRN>R3DCLNT950</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL>20060419144347</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>2006-04-19</SAP:CREDAT>
<SAP:CRETIM>14:43:47</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>20060419</SAP:Date>
<SAP:Time>144347</SAP:Time>
<SAP:Host>sun081</SAP:Host>
<SAP:SystemId>XID</SAP:SystemId>
<SAP:SystemNr>61</SAP:SystemNr>
<SAP:OS>SunOS</SAP:OS>
<SAP:DB>ORACLE</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>012</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>XIAPPL</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:LogSeqNbr>000</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
<SAP:PipelineElementId>5DC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
<SAP:PipelineService>PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:PipelineService>
<SAP:QIdInternal>XBTOD___0000</SAP:QIdInternal>
<SAP:CommitActor>A</SAP:CommitActor>
<SAP:ParentId ChildNo="0" ChildTotal="0">444520917B4240B7E100000064070151</SAP:ParentId>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="401">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID">6407015140B8444684E320CC</SAP:EOReferenceRuntime>
<SAP:EOReferenceInbound type="TID">6407015E1C50444684E39DF5</SAP:EOReferenceInbound>
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>18029</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>0</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>18029</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>IDOC</SAP:AdapterInbound>
<SAP:InterfaceAction>DEL</SAP:InterfaceAction>
<SAP:RandomNumber>24</SAP:RandomNumber>
<SAP:AckStatus>000</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="sun081">20060419184347.424552</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="sun081">20060419184347.443929</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="sun081">20060419184347.443977</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="sun081">20060419184347.613713</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="sun081">20060419184347.616273</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="sun081">20060419184347.625803</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="sun081">20060419184347.626241</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="sun081">20060419184347.634135</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="sun081">20060419184347.634561</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="sun081">20060419184347.645671</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="sun081">20060419184347.645716</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:DynamicConfiguration xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPOR">SAPST4</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPRN">ST4-902</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPRT">LS</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPOR">A000000015</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPRN">R3DCLNT950</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPRT">LS</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="MESTYP">FIDCC2</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="IDOCTYP">FIDCCP01</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="CIMTYP" />
</SAP:DynamicConfiguration>
- <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:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="IDX_INBOUND_XMB" />
- 
<Trace level="1" type="T">User: XIAPPL</Trace>
<Trace level="1" type="T">Language: E</Trace>
<Trace level="1" type="T">Correct Version from 2 to 3: 3.X-Data to 4.x-Data</Trace>
<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</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 SAPST4</Trace>
<Trace level="1" type="T">Convert Segment-Definitions to Types</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 = 401</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = XIAPPL</Trace>
<Trace level="1" type="Timestamp">2006-04-19T18:43:47Z EST</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 = 444520917B4240B7E100000064070151</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 : XBTI0003</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0003</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 = 401</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = XIAPPL</Trace>
<Trace level="1" type="Timestamp">2006-04-19T18:43:47Z EST</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: 2</Trace>
<Trace level="1" type="T">Multi-receiver split case</Trace>
<Trace level="1" type="T">Persisting initial (pre-split) message</Trace>
<Trace level="1" type="T">Persisting split messages (split kids)</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Splitting loop start</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTOD___0000</Trace>
<Trace level="1" type="T">Persisting split kid = 4445B42A672D40B8E100000064070151</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
- <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <SAP:Payload xlink:href="cid:[email protected]">
<SAP:Name>MainDocument</SAP:Name>
<SAP:Description />
<SAP:Type>Application</SAP:Type>
</SAP:Payload>
</SAP:Manifest>
</SOAP:Body>
</SOAP:Envelope></b></i>

Hi Manish,
but you have to register the queues
go to SXMB_ADM and register queues option
it's one of the installation/configuration steps
you have to do it for any kind of message message exchange (if the person who installed XI didn't do it)
register the queues and restart the messages
or F6 at the queue entry
Regards,
michal

Group messages are going through as texts instead of imessage

Usually when me and my friends have a group message it's fine, it's all going through iMessage and I've never had a problem but yesterday my messages were failing to send and today it says at the top 'Outgoing' instead of 'Group' like it usually does and also my messages are going through as a text not an iMessage but only on the group message? Help

If you have others that are receiving your imessaging but not the group you are attempting to send to then do this:
Click on your text messaging area using imessaging enabled and then type a message to yourself. Do this test to verify that your imessaging apple server is working properly. IF you get the messsage back to you in BLUE this indicates to you that both the outgoing and incoming text messaging is working as imessaging. With this piece of information verified that will indicate there are connectivity issues with individuals or all that are a part of the group you are attempting to contact. Please do not conclude that at a point in time this communication worked via imessaging that there may be some in the group that are now having conectiviity issues of their own.
Good luck, Friend.

TS2755 Receiving "Message Send Failure" notification, but messages are going through?

For the past few days, I have been receiving a "Message Send Failure" after every iMessage that I send. The messages are going through, but I still receive the notification every time. I have restarted my phone, signed out of and back into iMessage, and reset my network settings. Nothing seems to be working. Anyone have a solution? I'm having the same problem on my iPad, which leads me to believe it's a problem with iMessage at large as opposed to a device problem. Thanks!

If you have others that are receiving your imessaging but not the group you are attempting to send to then do this:
Click on your text messaging area using imessaging enabled and then type a message to yourself. Do this test to verify that your imessaging apple server is working properly. IF you get the messsage back to you in BLUE this indicates to you that both the outgoing and incoming text messaging is working as imessaging. With this piece of information verified that will indicate there are connectivity issues with individuals or all that are a part of the group you are attempting to contact. Please do not conclude that at a point in time this communication worked via imessaging that there may be some in the group that are now having conectiviity issues of their own.
Good luck, Friend.

Messages going to the wrong Integration Server

Hello All,
We saw a problem with few messages on the production XI server for a brief period of time. the following is the scenario.
1) An ORDERS05 IDoc comes out of the ECC, gets correlated and was sent out to conversion Agent for translation and was sent out to the vendor.
2) We get the response 997 from the vendor to the file port. This message has been picked up by the file adapter, got translated and was sent out to the XI Integration engine on the development box.
I could see this message on the RWB under the Adapter Engine component. This message did not reach the Integration engine on the Production box. A close look at the message details tells me that the message was sent to the Integration engine on the Development box. This happened to a few messages with in a minute time frame. All the messages before and after the minute time frame made just fine to the XI integration server.
We checked the SLD and found no reference of Production box pointing to the development XI IS.
I appreciate any pointers in this regard.
Thanks.

Hi Balu,
this could happen if your XI DEV system has a file adapter containing the same source directory where your response from vendor is coming for production.....this file adapter will be active....so it is pickng your response and triggering it to XI DEV before XI prod can pick it up.........it is also possibel that your XI PRD system file adapter is currently deactive or has some error in it now.......So just check the file adapters of XI DEV and XI PRD for your this scenario......
Thanks,
Rajeev Gupta

BPM Acknowledgement message reading the wrong integration server name

HI
I have a scenario where I have BPM which sends data to A MS SQL Server database and waits for a TRANSPORT Acknowledgement. The Mesage going to the Database is processed successfully but the acknowledgement messasge fails giving the following error when viewed in the message monitor.
IS_DETAILS_GET_ERROR
no_integration_server_found: Unable to find Integration Server is.XX.XXXXXXXX
Error while reading access data (URL, user, password) of Integration Server is.XX.XXXXXXXX
Actually the string "is.XX.XXXXXXXX" contains the name of the integration server.
Now my problem is the actual value contained in the above string is the name of the integration server . But this name is not correct , I mean it is not what the actual name should be. We are not able to find out from where this incorrect name is being picked up. Can anyone tell from where the actaul name and url of the integration server is read. Is it stored in different locations for inbound messages and acknowledgement msgs. Will refreshing any of the caches will help.
Please suggest.
regards
Nilesh Taunk.

Hi Nilesh,
your problem is very strange because your BPM is sending data correctly to SQL DB .....your db is processed.....but the ack msg when coming in bpm gives IS_DETAILS_GET_ERROR.
i think just see all the objects in IR and ID are activated.....after that by SXI_CACHE transaction do a cache refresh.........see the return code of BPM is zero or not......the retun code of BPM shuld be zero.......
again run your this scenario.......now please tell what happens......
Thanks,
Rajeev Gupta

Wrong Integration Server Data retrivied from Adapter

For unclear reasons the wrong URL to connect to Integration Server was retrieved by Adapter Framework.
This happened only once, and in this situation the xml message of a productive interface were sent to IS of an
other system (!).
As I can see in the default trace, during the call from AF
CPA cache service to SLD, the wrong host was retrieved.
In other circumstances, we have found that sometimes the IS hostname is filled with blank, causing the AF to not dispatch successfully the messages to IS. But in this case, thanks to the patch 14 of XI AF, the message are re-sent after the next polling sequence (15 min.).
I kindly need an help to discover which is the root cause of this kind of problem.
I red note 764176 about finding inconsistencies on sld, but I have some doubts on the correct implementation in my case. In the note it's discussed about the same domain written two times (for example one in fully-qualified host name and one with a short host name). In our productive SLD there are three domain that have the same name for the technical system point of view, but three definition as CIM data, since there are originally three XI instance on the same host. So, I don't know if we are in the same condition as reported in the note.
Does anyone have encountered a similar situation? Any workaround? For example, I view in the default traces that during the SLD Access performed by CPA service, there is no defualt value for Integration Server URL, but for default client yes (100). Is there a mode to force adapter framework to set the IS Url without asking it to sld, since I.S. url is always the same?
Thanks
Danilo

Hi,
The connection to the SLD is established by creating an RFC destination and The server program is called with the HTTP address as a parameter that is maintained with transaction SLDAPICUST.
Hope this link will be useful.
http://help.sap.com/saphelp_nw04s/helpdata/en/0b/8512417301ee6fe10000000a1550b0/frameset.htm
and 25th page of config guide.
https://websmp101.sap-ag.de/nw04installation
Regards,
Madhu

N9 IMAP4 messages are not deleted on the server

Emails deleted on N9 are not deleted (nor marked for deletion) in IMAP4 account on the server? I can see "unprocessed" emails in modest/evolution/thunderbird/webmail (after resync) which I have already deleted on the N9. I have deleted the account, set it up again on the N9, these deleted messages are there back (just like all other email clients and webmail show them). Need this feature working, otherwise email on N9 is useless. Paul

Hey Hey, I fixed my N9 IMAP mail!!!
First off, when I sent mail, I noticed it wasn't going to my primary Sent folder, but a legacy folder on my IMAP server called "Sent Messages".
Even after deleting this folder from the server, mail still was not captured to the correct "Sent" folder and I still got the connection error messages on every Sync.
So I cleaned house on my IMAP server and deleted all kinds of old folders like:
.INBOX/Sent
.INBOX/Trash
BadTrash
OldTrash
OldSent
Sent Messages
Then I removed and re-added the IMAP account on my N9, and BANG it works!
No more connection error messages, sent mail goes to the correct place, and deleted messages are deleted from the server.
Obviously, the problem as previously stated in this thread is when the N9 client initially connects to an IMAP account. It seems to latch onto the first Trash and Sent messages it finds, even if you don't use those folder.
In my case, it latched onto "Sent Message" for sent, and some invalid file for Trash (hence the connection error messages).
Much better now, but I can't help to wonder what kind of IMAP logic is lacking on the N9 that Modest had on the N900 to have these kinds of problems....

I iphone 4 is not sending texts to my friends and family with iphones. The blue messages are not going through. My green messages are going through. Help!

My Ipone is not sending text messages. i can recieve the messages, but my replies are not being sent.. this seems to only be an issue to sendin to other iphones. The blue messages are not being sent. if the box is green, the meessage is sent.this seems to ahve started after i down;oaded the latest operating system. HELP!!

Welcome to the Verizon family, ivpacks! I regret to learn that your alarms didn't work. I also regret that there is a problem with the messages. Have you tried the alarm again? Does it still not work? For instance, just set the alarm for a couple of minutes away to ensure that the alarm goes off.
When you send a text, do you get an error? If you power the phone off/on, do the messages send? This particular issue is expecting a software update to resolve the issue with texts and picture messages.
I believe that you have chosen a great device, but keep in mind that there is a 14 day exchange period. If you exchange for the same make/model, you will not pay the restocking fee.
If you do exchange for a different make/model, there is a $35.00 restocking fee.
TamaraH_VZW
Follow us on Twitter @VZWSupport

TS4268 my imessage was working fine on monday as of friday it stopped working and all my message are going to my ipad and not sure what to do i have tried the steps above

my imessage is not working all messages are being sent to ipad

Hello pinkyakabella,
Thanks for using Apple Support Communities.
For more information on this, take a look at:
iOS: Troubleshooting Messages
http://support.apple.com/kb/ts2755
Best of luck,
Mario

I get a message when going to any webpage "server not found" or "problem loading page". I click on try again and the page loads fine. This happens on bookmarked pages or manually entered urls. The issues started after I updated Firefox.

Server not found messages and problem loading page message since I updated to the latest version of Firefox. Usually will load the 2nd time after hitting the try again option.
Does not happen with Internet Explorer at all.

See:
*http://kb.mozillazine.org/Error_loading_websites

Calls, Messages, Facetime going to wrong Iphone?

Me and my mum both have an Iphone 4. Recently she has been recieving my calls, messages and facetimes? Any Ideas?
I have recently just downloaded IOS 7 but it seems to be working fine.

Settings>iMessage>uncheck your phoen number and email from her iphone

Messages not processed by integration server after SP09 to SP16

Operating System: Windows NT 2003 Standard edition Service Pack 1
Database: SQL_Server_8.00, DBSL:640.00 Patch Level: 100
ABAP Kernel: Non Unicode; Release: 640; Patch: 109;
XI: Version 3.0; Service Pack Stack:16
Host: PEARL; IPAddress: 10.1.1.13
We upgraded from service pack stack 09 to 16 and since then no messages
are getting routed to integration server. We tried a cache access
though TCODE: SXI_CACHE and it said "if_http_client receive
http_communication_failure". Then we went to ICM monitoring through
TCODE: SMICM and saw that the http service that runs on 8000 port is
inactive when we tried to activate it gave an error. Here is the
snapshot from the trace file.
[Thr 3492] *** ERROR => NiIBind: service '8000' (8000) in use
[nixxi_r.cpp 3845]
[Thr 3492] *** ERROR => NiIListen: NiBind (rc=-4) [nixxi_r.cpp
767]
[Thr 3492] *** ERROR => IcmBindService: NiBuf2Listen failed for host
PEARL:8000 (rc=-4): NIESERV_USED [icxxserv.c 1549]
When we tried to access runtime workbench through integration builder
webpage it says "page not found".
When we tried to login to the J2EE visual admin using the default
account(J2EE_admin) it gave the
error "http://pearl:8101/msgserver/text/logon returned empty list of
connection parameters."
In SAPMMC we looked at the system log and saw the error "SAP Basis
System: Operating system call gethostbyaddr failed (error no. 0 )".
We tried restarting the whole server but to no effect.

since your OS is Windows try following in command at prompt
C:>netstat -a
or
C:>netstat -an
one of the above will work in NT, the list shows the listening (Open) ports and ESTABLISHED (used)..check for the 8000 which is your HTTP port.
Also in SAP check the t-code "SMICM" and then goto services and see the HTTP services running without error or not?
Hint: Port names are defined in services file located at C:\WINDOWS\systemXX\drivers\etc\services file..

Mail 3, smtp, IMAP: sent messages are not saved on server

Hello,
I had problems using Mail 3 after I upgraded to Leopard, so I used Thunderbird for the time being. With the update 10.5.1 I tried again: most problems solved BUT: sent messages are not saved on the server in mailbox "Sent".
Some background: I deleted the folder "<User>/Library/Mail" and "<User>/Library/Preferences/com.apple.mail.plist" and configured Mail from scratch.
To be sure: I still have Thunderbird installed, and when I send with Thunderbird: a copy is placed in "Sent".
Another thing I noticed: it takes more than a minute to send from Mail 3 and a few seconds when I send from Thunderbird. I have another Macbook Pro with 10.5.0 installed: same problem with sending.
Any help is appreciated.
rene

Well, be stumped I did all that, but to be sure, I did it again:
I have a lot folders with subfolders and they are shown under my account name.
I created a new folder "test" in my IMAP account and designated it to be the new "Sent" folder. It replaces my previous Sent folder in the group Inbox, Drafts, Trash. My previous Sent folder now appears under my account name as a "normal" folder.
I send a message and the Activity monitor says: +"Delivering message: copying message"+. After a minute Mail is done. I check my (new) "Sent" folder and it's empty. I double check in webmail: it's empty.
So I go to the Finder and look in my IMAP folder: <user>/Library/Mail/<IMAP-account>/test.imapmbox and there is no folder "Messages", only Info.plist.
Then I try to move a message to the "Sent' folder: for a minute the Activity moinor says: Copying messages: copying message" and then Mail prompts: +"The message "testing" could not be+
+The connection to the server mail.hicetnunc.nl on port 143 timed out"+.
So it looks like Mail has a problem with the default "Sent" folder: it cannot copy messages to that folder at all! Aha!
But then I try to move a message to a "normal" IMAP folder: same thing! Mail cannot copy to any folder!
In both instances Mail says: +"The message "..." could not be be moved to the mailbox "..."+
+The connection to the server mail.hicetnunc.nl on port 143 timed out"+
Last thing: I try to move a message to a folder in the same account again. But in the process I quit Mail. I open Mail again and Mail is performing pending operations: copying message. After a while Mail prompts: +"Operation could not be completed. (MFMessageErrorDomain error 1028.)"+ and crashes... I open Mail again and it tries to peform pending operations. Again: an error message and Mail crashes. This keeps going on so I delete the whole account and set it up again. Nothing's changed...
I can receive and send, but sent messages are not copied to the "Sent" folder and I cannot move messages around within a IMAP account. But TADA!!!: I can move messages from account to account.

Messages going to wrong device

All of my messages are going to my wife's phone and vice versa

Go into your settings, Messages and turn on iMessage. It will then send messages that are iMessages to both your iPad and iPhone. You can also turn off this feature on the iPad if you do not want to receive messages on the iPad.

Messages are going to wrong Integration server

Similar Messages

Maybe you are looking for