Unable to send AS2-MDN ack

Hi
We have configured an AS2 with one of our partner, we are able to send/receive 850 but our partner is unable to receive an MDN back from us for the 850, verified all the setups everything looks good..
I put in an SR also, but if anyone of you had experienced the similar issue before, please advise..
Thanks
Sri

hi all..
Im new to this technology and wanna learn and try to program some simple applications using Smart Card...
Reading thru all the topics above, Im wonderring is the Card Reader able write codes to the Smart Card, or maybe jux simply able to update the info inside the card??
I also heard about Card Decoder as well, I mean if the Card Reader can do the task.. why do we need Card Decoder ?!
Sorry if I stated something wrong... Im new and hope that someone could share some valuable knowledges here...
Thanks much much !!

Similar Messages

Sender AS2 MDN XML Channel error

Hi,
I am trying to configure a sender AS2 adapter to receive asynchronous MDN. But as soon as I create the channel ,it goes in error "Channel configuration is erroneous: java.nio.charset.UnsupportedCharsetException: The target charset iso885915 is not supported".
1. I don't see any other option to configure character set once AS2 MDN transport protocol is selected. Am I missing any configuration?
2. Also I am testing from mendelson and as per the mendelson log MDN is sent to PI system but I do not see any MDN in PI. We are using B2B addon SP1 on PI 7.11.
mendelson log :
[3:27:36 PM] mendelson_opensource_AS2-1407405456031-5@EDI_Partner_EDI_Partner: Outgoing MDN has not been signed.
[3:27:36 PM] mendelson_opensource_AS2-1407405456031-5@EDI_Partner_EDI_Partner: MDN created, state set to [processed].
[3:27:36 PM] mendelson_opensource_AS2-1407405456031-5@EDI_Partner_EDI_Partner: Sending async MDN to http://<PI_Host>:50000/AS2/AS2_Sender/mdn.
[3:27:36 PM] mendelson_opensource_AS2-1407405456031-5@EDI_Partner_EDI_Partner: Message sent successfully (HTTP 200); 791 Byte transfered in 353ms [2.19 KB/s].
[3:27:36 PM] 17ef0d18-1e19-11e4-c6b8-0000004bc76a@PI7: AS2 communication successful, payload 1 has been moved to "C:\Users\Pankaj\Desktop\mendelson\opensource\as2\messages\EDI_Partner\inbox\17ef0d18_1e19_11e4_c6b8_0000004bc76a@PI7".

Hi Pankaj,
This is what I did:
The most important parts of the configuration are
Receiver AS2 communication channel, requesting a synchronous MDN message
Sender AS2 communication channel processing the incoming MDN message
Receiver AS2 communication channel
Sender AS2 communication channel
Within the SAP PO monitoring tools, you see something like this:
Kind regards,
Dimitri

Unable to identify the exchange protocol of the message (sync AS2 MDN)

Hi,
We got the following error:
Description: Unable to identify the exchange protocol of the message
StackTrace:
Error -: AIP-50080: Exchange protocol identification error
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1367)
     at oracle.tip.adapter.b2b.msgproc.Request.postTransmit(Request.java:2370)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1813)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:968)
     at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1152)
     at oracle.tip.adapter.b2b.xmlgwIntg.XMLGWIntegration.raiseOutboundMessage(XMLGWIntegration.java:168)
     at oracle.tip.adapter.b2b.xmlgwIntg.Outbound.onMessage(Outbound.java:297)
     at oracle.jms.AQjmsListenerWorker.dispatchOneMsg(AQjmsListenerWorker.java:316)
     at oracle.jms.AQjmsListenerWorker.run(AQjmsListenerWorker.java:129)
     at java.lang.Thread.run(Thread.java:534)
Here is the Wire message (sync MDN)
=======================
Message-ID=<23033756.391232032071968.JavaMail.SYSTEM@INUBITTEST>
Subject=Your ORDERS AS2
[email protected]
Content-Length=1347
MIME-Version=1.0
Server=Apache
Date=Thu, 15 Jan 2009 15:07:52 GMT
Content-Type=multipart/mixed;      boundary="----=_Part_53998_23619909.1232032071968"
[email protected]
------=_Part_53998_23619909.1232032071968
Content-Type: text/plain; charset=UTF-8; name=test.txt
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename=test.txt
Message-ID: <17080722.371232032071906.JavaMail.SYSTEM@INUBITTEST>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=disposition-notification;
     boundary="----=_Part_53997_14786767.1232032071906"
AS2-Version: 1.1
AS2-From: test_AS2
AS2-To: as2me
------=_Part_53997_14786767.1232032071906
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
MDN for Message ID: <33156:4:0:137@as2me>
From: as2me
To: test_AS2
Received on: Thu, 15 Jan 2009 16:07:51 +0100
Status: processed
Comment: This is not a guarantee that the message has
been completely processed or unterstood.
------=_Part_53997_14786767.1232032071906
Content-Type: message/disposition-notification
Content-Transfer-Encoding: 7bit
Reporting-UA: inubit Integration Server
Original-Recipient: rfc822; test_AS2
Final-Recipient: rfc822; test_AS2
Original-Message-ID: <33156:4:0:137@as2me>
Disposition: automatic-action/MDN-sent-automatically; processed
Received-Content-MIC: 5kFOLMXOUurpm6DUTA8IMRj5gcs=, sha1
------=_Part_53997_14786767.1232032071906--
------=_Part_53998_23619909.1232032071968--
============================
The communication with our TP is going well, we are able to send, receive messages over AS2 and send back MDN, but we are not able
to receive their MDN.
Edit:
It seems that after the latest MLR patch, the error changed to [IPT_HttpSendError] HTTP encounters send error :. Premature EOF encounter but the roots seem to lead to the problem with MDN as B2B is sending the message a couple of times now and gives the mentioned EOF error.
Please advise,
Thank you
Edited by: Kamil Zadora on Jan 30, 2009 3:44 AM

Hi Ramesh,
Yes, agreement uses AS2 IDentifiers. Incoming messages are recognized correctly, and we send back sync MDN that is correctly received by our TP. They also recieve our messages correctly although Oracle B2B does not recognize the MDN from them. I think that this causes that, now after applying the latest MLR patch, B2B tries to send it around 6 times and gives the Unexpected EOF error.
Thank you for your help in advance,
Kind regards,

Send and Receive ACK 997 over AS2

Hi,
I have AS2/EDI setup in place and is working fine. The only thing remaining is sending and receiving Ack 997. How can I do that? What is the quickest way of doing it?
Please help. I need it urgently. I'm sure there must be some quick way of doing the same.
Thanks.

Hi Dipti,
If you have setup ready with parties then you need to add agreement
and in the agreement configure the acknowledgements section.
Go through following articles:
BizTalk Server EDI Scenario: Send an X12 Message and Receive an Acknowledgement
BizTalk Server EDI Scenario: Send an X12 Message Over AS2 and Receive an
Asynchronous MDN
If you not have parties added then first do that and then create agreement between them:
Create Trading Partners and Business Profiles
Create Trading Partner Agreement
Maheshkumar S Tiwari|User Page|Blog|BizTalk
Server : How Map Works on Port Level

Not able to generate AS2 MDN when receiving custom XML via AS2

Hi friends,
I have setup the trading partner and the corresponding TP certificate import for receiving the custom XML via AS2 channel.
I am receiving the custom xml properly to oracle b2b and able to receive the same to bpel as well. however in the oracle b2b console under reports tab i am seeing only one record for inbound document receive and i am not seeing the other record for the AS2 MDN going back to vendor. I have setup the AS2 channel under the external trading partner --> Channel using the vendor AS2 URL and selected all the security parameters while creating the Outbound AS2 channel.
1. Not able to generate AS2 MDN when receiving custom XML via AS2.
2. eventhough i am able to decrypt the inbound custom XML and ablr to recieve it in bpel also for processing, in the reports tab the inbound message state is changing to MSG_ERROR and it has the folloing error message:
Error Code
B2B-50037
Error Description
Machine Info: (***********) Description: B2B inbound message processing error
Error Level
ERROR_LEVEL_COLLABORATION
for AS2 MDN generation for custom XML receiving using As2 protocol, do we need to setup anything other than the outbound As2 Channel using the external vendor AS2 URL?
Can you please help me how can i generate the AS2 MDN for the inbound custom XML document i have received and also why the inbound message is failing even though i am receiving the custom XML properly to bpel?
Thanks,
Amirineni.

Hi Prasanna,
Vendor has enabled the ACK mode as SYNC.
Below are the headers for the inbound message to B2B. and we are able to receive the input message to bpel also.
Protocol Transport Binding
ChannelName=******** AS2-To=****AS2 TE=trailers, deflate, gzip, compress Date=Thu, 02 Oct 2014 14:26:31 GMT AS2-Version=1.2 Accept-Encoding=deflate, gzip, x-gzip, compress, x-compress AS2-From=****AS2 Disposition-Notification-Options=signed-receipt-protocol=optional, pkcs7-signature; signed-receipt-micalg=optional, sha1 Disposition-Notification-To=https://******/as2 Message-ID=<CLEO-20141002_142630452-31X54N@****_*****AS2.pcwbedi1-O> Content-type=application/pkcs7-mime; smime-type=enveloped-data; name=smime.p7m Content-length=747006 MSG_RECEIVED_TIME=Thu Oct 02 10:26:39 EDT 2014 Subject=EDI ECID-Context=1.005175bK7U^AXNJCAnf9Cx0002pW000yjX;kXjE1ZDLIPGIj2QCYV8QoKSSILRO_PQT_IS Proxy-Client-IP=****** Recipient-Address=https://******/b2b/httpReceiver User-Agent=RPT-HTTPClient/0.3-3I (Windows 2003) X-Forwarded-For=****** Content-Disposition=attachment; filename="smime.p7m" Host=****** EDIINT-Features=CEM, multiple-attachments, AS2-Reliability Connection=Keep-Alive X-WebLogic-KeepAliveSecs=30 X-WebLogic-Force-JVMID=-1497702782 From=****** Mime-Version=1.0
Message Digest
Message Digest
Digest Algorithm
sha1
Transport Protocol
HTTP
Transport Protocol Version
1.0
Url
http://******
security
Transport Headers
ChannelName=****** AS2-To=******AS2 TE=trailers, deflate, gzip, compress Date=Thu, 02 Oct 2014 14:26:31 GMT AS2-Version=1.2 Accept-Encoding=deflate, gzip, x-gzip, compress, x-compress AS2-From=****AS2 Disposition-Notification-Options=signed-receipt-protocol=optional, pkcs7-signature; signed-receipt-micalg=optional, sha1 Disposition-Notification-To=https://******/as2 Message-ID=<CLEO-20141002_142630452-31X54N@****AS2_*****AS2.pcwbedi1-O> Content-type=application/pkcs7-mime; smime-type=enveloped-data; name=smime.p7m Content-length=747006 MSG_RECEIVED_TIME=Thu Oct 02 10:26:39 EDT 2014 Subject=EDI ECID-Context=1.005175bK7U^AXNJCAnf9Cx0002pW000yjX;kXjE1ZDLIPGIj2QCYV8QoKSSILRO_PQT_IS Proxy-Client-IP=***** Recipient-Address=*******/b2b/httpReceiver User-Agent=RPT-HTTPClient/0.3-3I (Windows 2003) X-Forwarded-For=******* Content-Disposition=attachment; filename="smime.p7m" Host=***** EDIINT-Features=CEM, multiple-attachments, AS2-Reliability Connection=Keep-Alive X-WebLogic-KeepAliveSecs=30 X-WebLogic-Force-JVMID=-1497702782 From=***** Mime-Version=1.0
Thanks,
Amirineni

Sender AS2 to SAP PO; 403 forbidden error

Hello Experts,
I am using the AS2 adapter from the B2B Addon.
I am stuck in the scenario Sender AS2 -> SAP PO; with the 403 forbidden error.
Few queries;
1. Is virtual receiver mandatory ?
2. Is is mandatory to have party for sender and receiver. Currently I am having only Sender ( Party + Comm. Component ) and Receiver ( Comm. Component ( Partner Type = LS )).
Can you help please.
Thanks
Saurabh

Hi Harish,
Thanks for your quick response.
I have configured with the following details :
Sender Party : ABC ( 009 | GLN | 333333333 )
Sender Component : DEF
Receiver Party : PQR ( 009 | GLN | 111111111 )
Receiver Component : XYZ
Sender AS2 adapter :
Expected URL : http://10.194.35.20:8080/as2/HttpReceiver
Message ID Left : .*
Message ID Right : .*
Sender AS2 name : 333333333
Receivers AS2 name : 111111111
Expected subject : AS2 message
Partners in Mendelson :
Partner 1 :
( Local station )
1. Name : Mendelson_AS2
2. AS2 ID : 333333333
3. Email : [email protected]
MDN tab : http://<Mendelson desktop PC IP>:8080/as2/HttpReceiver
Parnter 2 :
1. Name : PQR
2. AS2 ID : 111111111
3. Email : [email protected]
Receipt URL : http://<PI-Host>:<PI-PORT>/AS2/.*
Payload subject : AS2 message
Error details :
[10:41:44 PM] mendelson_opensource_AS2-1398458504283-15@333333333_111111111: Transmission failed, remote AS2 server reports "Forbidden".
[10:41:44 PM] mendelson_opensource_AS2-1398458504283-15@333333333_111111111: HTTP 403
[10:41:44 PM] mendelson_opensource_AS2-1398458504283-15@333333333_111111111: Message payload stored to

Correlating AS2 MDN to Original IDoc?

Hi All -
I have got the following scenario:
1) Backend system (ECC) sends IDoc to SAP PI.
2) SAP PI maps IDoc to EDIFACT message and sends via AS2 to B2B Partner.
3) B2B Partner sends back AS2 MDN to acknowledge receiving of AS2 message.
__Question:__
How can I now correlate the AS2 MDN to the original IDoc and so forward the acknowledgement to the Backend system?
I was thinking to use the 'Correlation ID' which is contained in the AS2 MDN and is the same ID as the original SAP PI message.
However, how do I practically retrieve the IDoc number (part of original IDoc message and used as identifier in the ECC system) from the persisted messages of SAP PI?
Can I code an ABAP or JAVA program which is than called within a mapping to query the persisted messages and give back the correlating IDoc number?
Are there other ways to achieve this?
Thanks for your inputs.
Best Regards, Mathias.

Hi Mathias,
Approach1:
I would definately not consider using BPM overhead on a high volume scenario. As the Output file(that will be generated) will be a simple XML message with just the data required for corelating with the MDN. All MDN's are expected to received within 1 min or less than 5 min.(B'cos it is a System level Acknowledgement), Hence if the BPM is not closed within the specified time period(1min or 5 min), raise an exception.
The Corelation file that will be generated can look like
<MDN_Corr>
   <SenderAS1ID>        --> Will be used for Corelating the MDN
   <ReceiverAS2ID>      --> Will be used for Corelating the MDN
   <TimeStamp>
   <IDOCNumber>
   <EDI_ISA_Control_No> --> Will be used for Corelating the MDN
   <EDI_Message_Type>
</MDN_Corr>
Approach2:
It might be very resource intensive to perform payload search. (and in some cases, the messages are archived, hence might result in bad search). Hence, you can have Z-Table all the fields as mentioned in the XML message. 1:1 mapping b/n EDI_ISA control number & IDOC_Number will be your lookup key-value params
-SM

DtReport structure and Alerts Settings from sender AS2 Reports adapter

Hi,
I have imported DtReport for MDN's from SeeBurger AS2 adapter documentation as external definition into PI. However, in the mapping, when I select DtReport as source, I could see only the following structure:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:DtReport xmlns:ns0="http://uri.seeburger.com/dt/master/schema">
   <ns0:clientId/>
   <ns0:correlationId/>
   <ns0:category/>
   <ns0:state/>
   <ns0:finalReport/>
   <ns0:freeText/>
   <ns0:specificData/>
   <ns0:reportAttachment/>
   <ns0:archiving/>
</ns0:DtReport>
But when I import the test MDN message that we received it has key and value elements underneath the tag 'specificData'. How do I get these two elements from external definitation?? Anything that I should in External References??
How does the following 'Alerts Settings' work from sender AS2 Reports adapter:
Enable alerts
Negative transmission report alert
Negative delivery repot alert
Negative receipt report alert
Thanks,
Riya

Here is the XSD:
?xml version="1.0" encoding="ISO-8859-1"?
xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:att="http://uri.seeburger.com/bisas/message/schema" xmlns:tns="http://uri.seeburger.com/dt/master/schema" xmlns="http://uri.seeburger.com/dt/master/schema" targetNamespace="http://uri.seeburger.com/dt/master/schema" elementFormDefault="qualified" attributeFormDefault="unqualified"
     xsd:import namespace="http://uri.seeburger.com/bisas/message/schema" schemaLocation="attachments.xsd" /
     xsd:include schemaLocation="dtglobaltypes.xsd" /
     xsd:include schemaLocation="dtarchiving.xsd" /
     xsd:element name="DtReport" type="tns:DtReportType" /
     xsd:complexType name="DtReportType"
          xsd:sequence
               xsd:element name="clientId" default="000" type="tns:stringLength3Type"
                    xsd:annotation
                         xsd:documentation
                         Logical System ID
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
               xsd:element name="correlationId" type="tns:uuidType" /
               xsd:element name="category" type="tns:reportCategoryType" /
               xsd:element name="state" type="tns:reportStateType" /
               xsd:element name="finalReport" type="xsd:boolean"
                    xsd:annotation
                         xsd:documentation
                         True if this report is the last one for the given correlationId
                    E.g. if this report is a deliveryReport but there is also a remaining ReadReceipt, then finalReport would have the value 'false'
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
               xsd:element name="freeText" type="xsd:string" minOccurs="0" /
               xsd:element name="specificData" type="tns:keyValueType" minOccurs="0" maxOccurs="unbounded"
                    xsd:annotation
                         xsd:documentation
                         Optional report data specific to the components and protocols
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
               xsd:element name="reportAttachment" type="att:AttachmentRefType" minOccurs="0"
                    xsd:annotation
                         xsd:documentation
                         Optionally holds the report as attachment in its raw format.
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
               xsd:element name="archiving" type="tns:archivingType" minOccurs="0" maxOccurs="unbounded" /
          /xsd:sequence
     /xsd:complexType
     xsd:complexType name="responseReportHandlingType"
          xsd:annotation
               xsd:documentation
               Information in a DtResponse about the report handling of the sent payload.
               /xsd:documentation
          /xsd:annotation
          xsd:sequence
               xsd:element name="reportsExpected" type="xsd:boolean"
                    xsd:annotation
                         xsd:documentation
                         True if at least one report is pending (false if the one and only report is contained in response).
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
               xsd:element name="expectedReports" type="tns:expectedReportsType" minOccurs="0" maxOccurs="unbounded"
                    xsd:annotation
                         xsd:documentation
                         List of expected reports - also including the one optionally included in the response.
                        If reportsExpected is true then this list must contain at least one entry, else it must be empty.
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
               xsd:element name="dtReport" type="tns:DtReportType" minOccurs="0"
                    xsd:annotation
                         xsd:documentation
                         Optional report if it was synchronously received.
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
          /xsd:sequence
     /xsd:complexType
     xsd:complexType name="initiationReportHandlingType"
          xsd:annotation
               xsd:documentation
               Information in a DtRequestInitiation about the report handling of the received payload.
               /xsd:documentation
          /xsd:annotation
          xsd:sequence
               xsd:element name="reportsExpected" type="xsd:boolean"
                    xsd:annotation
                         xsd:documentation
                         True if at least one report was requested.
                         /xsd:documentation
                    /xsd:annotation
               /xsd:element
               xsd:element name="preparedReports" type="tns:preparedReportsType" minOccurs="0" maxOccurs="unbounded" /
          /xsd:sequence
     /xsd:complexType
     xsd:complexType name="expectedReportsType"
          xsd:sequence
               xsd:element name="category" type="tns:reportCategoryType" /
               xsd:element name="timeoutDate" type="xsd:dateTime" /
               xsd:element name="deliveryState" type="tns:deliveryStateType" /
          /xsd:sequence
     /xsd:complexType
     xsd:complexType name="preparedReportsType"
          xsd:sequence
               xsd:element name="category" type="tns:reportCategoryType" /
               xsd:element name="timeoutDate" type="xsd:dateTime" minOccurs="0" /
               xsd:element name="reportMessage" type="att:AttachmentRefType" /
          /xsd:sequence
     /xsd:complexType
     xsd:simpleType name="reportCategoryType"
          xsd:restriction base="xsd:NCName"
               xsd:enumeration value="DeliveryReport"
                    xsd:annotation
                         xsd:documentation
                         Report informing about the state of the delivery on a physical base
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
               xsd:enumeration value="ReceiptReport"
                    xsd:annotation
                         xsd:documentation
                         Report informing about the state of the receipt on a semantic base
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
               xsd:enumeration value="TransmissionReport"
                    xsd:annotation
                         xsd:documentation
                         Report informing about the state of the transmission on a physical base
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
          /xsd:restriction
     /xsd:simpleType
     xsd:simpleType name="deliveryStateType"
          xsd:restriction base="xsd:NCName"
               xsd:enumeration value="DELIVERED"
                    xsd:annotation
                         xsd:documentation
                         Delivery proceeded
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
               xsd:enumeration value="PENDING"
                    xsd:annotation
                         xsd:documentation
                         Delivery pending
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
          /xsd:restriction
     /xsd:simpleType
     xsd:simpleType name="reportStateType"
          xsd:restriction base="xsd:NCName"
               xsd:enumeration value="SUCCESS"
                    xsd:annotation
                         xsd:documentation
                         Positive report
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
               xsd:enumeration value="FAILURE"
                    xsd:annotation
                         xsd:documentation
                         Negative report
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
               xsd:enumeration value="EXPIRED"
                    xsd:annotation
                         xsd:documentation
                         No report received in time
                         /xsd:documentation
                    /xsd:annotation
               /xsd:enumeration
          /xsd:restriction
     /xsd:simpleType
/xsd:schema
Edited by: Riya Patil @SAP on Feb 4, 2010 9:05 PM
Edited by: Riya Patil @SAP on Feb 4, 2010 9:05 PM

How to configure alerts for sender AS2 reports channel?

Hi,
We have configured sender AS2 reports channel to receive MDN back from our partner. Scenario is working fine and we are receiving MDN. How does "Enable alerts" option under Alerts Settings in Sender AS2 Reports channel work?
I see following options, but dont know how to trigger an alert when we dont receive successful MDN back:
Negative transmissionreport alert
Negative delivery report alert
Negative receipt report alert
Has anyone trigger any kind of alrert and route them to an email for negative mdn?
Regards,
Riya Patil

Hi Riya,
I tried to use 'Enable alerts' option,but it didn't work.
Please let me know if you get a success in this.
Thanks.
Regards,
Shweta

HT3529 i am unable to send sms from my iphone 4s

i am unable to send sms from my iphone 4s

Try Settings > General > Reset > Reset Network Settings.
If that does not resolve, SMS is a carrier feature, contact the carrier.

HT1267 I am unable to send messages on my iPhone. I am getting an error when I send it. This just started this morning.

This is my first timeo n Apple Support. Suddenly this morning I am unable to send messages through my iPhone. I can send messages to one number, but all the other numbers I am sending to I receive an error message. Also, I can receive messages from the one number I can send to, but am unable to receive messages from any other number. What do I do to fix this?

Hi Steve,
No he has not turned iMessage off, infact when he sends me a message thru iMessage it says 'delivered'. I am at my wits end nd I don't know what to do anymore.

Unable to send the data entered in sap portal

Hi
All
i am trying to configure and test Leave Request from portal. When, we create the leave request and submit for the first time, it is giving the error/message Unable to send the data entered However, if do a submit for the second time, the same leave request, it sends the leave request.
Please share your valuable thoughts or solutions.Thanks in advance.
Tanks
Rafi Shaik

Hi Rafi,
We are also facing similar kind of issue.
When i select type of leave as annual it is giving an error message as
" Parameter missing in call of method BUILD_ACTOR_SELECT_CLAUSE in class CA_PT_REQ_ACTOR "
But when i select some other leave type and click review it is working fine, again if i click on previous step and change the leave type to annual it is working fine without giving any error message.
Please let us know how you have solved your issue?
Thanks.
-Suresh

Unable to send out emails via outlook express since 06/29/2010

Task '[email protected]" - Sending' reported error (0x80042109) : 'Outlook is unable to connect to your outgoing (SMTP) e-mail server. If you continue to receive this message, contact your server administrator or Internet service provider (ISP).' This is a copy/paste of error message from Office Outlook 2003
Our household has been unable to "send" outgoing emails since 06/29/2010. This includes a wireless laptop and a PC. We both lost the ability to send emails same day. We changed NOTHING and did not share emails with each other that would have corrupted our system. During this time I have had 2 Verizon techs dance around in the PC doing all the same things I did as well as what the automated assistant did. The last tech said the Outlook Express 6.0 was corrupted, and to unistall it and then reinstall; this time 2 hours later, I think he just gave up). That did not work either. I tried using the Outlook Office and still got an error message for outging. Everything is set up as it was when it was working until 06/29/2010. I was told that there was a new server being installed and that things wold be working by 07/02/2010... I have tried taking down the firewall, turning off virus protection (McAfee), changing from outgoing.yahoo.verizon.net to just outgoing.verizon.net, checking boxes, unchecked boxes. SMPT is set to 587. We get incoming fine. I hate using the "Verizon email site" as too much monkey motion to get to mail, but that's what we have been doing. I even tried setting up a GMail account, again got mail still could not send. Any ideas?

Thank you for your response! I even tried sending an email via dos prompt with Telnet, got past "HELO", but when trying to get a "RCPT TO" (using outgoing.yahoo.verizon.net) I got an "authorization required" response and then was dropped. I have been passed around without a solution. I am about ready to change ISP, but really hate to as most of the time (years now) this has been a decent ISP. If Verizon is having a problem just say so, I can handle it, honesty would be nice, refreshing and not wasting so much of my time as well as the techs!

We purchased a new iPad2 and registered it using a 'new' iCloud email/ID. We are unable to send email from the iPad and iPhone. The error is: Cannot send mail. The user name or password for iCloud is incorrect.

We purchased a new iPad2 and registered it using a 'new' iCloud email/ID. We are unable to send email from the iPad and iPhone. The error is:>> Cannot send mail. The user name or password for iCloud is incorrect.

About ~20 hours later, this ended up solving itself. We can send email using the '.icloud' email from both the iPad and iPhone. Advise would be 'wait' before you start seeking alteranatives like yahoo, hotmail, etc. This definitely is a convenient way to keep all your 'cloud' information in a centralized place, including the common email...

Unable to send any email from my brand new ipad 2 and my iphone 3gs lately

Lately I found that my Iphone & my brand new ipad2 are unable to send out any email. it keep mentioning about the outgoing setting.."the connection to the outgoing server"webmail..." failed.Additional Outgoing mail servers can be configures in setting, bla bla bla
.I try look for some advices from apple suport communities seems doesn't work for me...pls help...>_<

Anyone can help?

Unable to send AS2-MDN ack

Similar Messages

Maybe you are looking for