Problem receiving IDOC

Hi all,
I am trying to send an Idoc from XI to R/3, but I get an adaptor error:
"Unable to convert the sender service to an ALE logical system"
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
Any ideas, what could be wrong?
Thanks
/Thomas

Hi Thomas,
Think of it as this way...whenever XI's IDOC adapter receives an IDoc, it requires the metadata about the IDOC to operate on it and convert it to an IDOC-XML...
In a regular scenario..it is straight forward...If an SAP system is sending an IDoc, then in XI for that SAP system, there would be a port maintained using transaction IDX1 through whihc XI IDOC adapter downloads metadata dynamically...The download of metadata happens only the first time....The different metadata downloaded can be viewed using TCODE IDX2...(from here if we want we can forcefully import the metadata..)
Now coming to your scenario, the since the sending system is an FTP client and you have a made up ALE name in the business service, we need an entry for that ALE name in IDX1...Now the IDX1 entry should point to an SAP system which has the metadata regarding the IDoc being processed....You may or maynot download the IDOC metadata using IDX2(the system will do it automatically the first time)..
In effect we are telling XI to check for IDOC metadata from a different system and not the FTP clinet...
Hope this would make it a little bit clearer for you
Thanks.

Similar Messages

Problem with an Receiver Idoc adapter

Hi.
We have just went from XI 3.0 to PI.7.10.
The Receiver idoc adapter is set up in the same way as it was in XI.
The problem is when two different interfaces runs at the same time I got data into the DC40-record which not belongs too this idoc but from an another interface/idoc.
The idocs are different messagetypes.
In this case the field MESCOD which belongs to one of the idocs also appered in the idoc where the field MESCOD not should be used.
Any idea whats wrong ?
/Per-Arne

Thanks.
Checked sxmb_moni as you said.
In the OutboundBinding-node I can see the right idocadapter is used
where 'Apply Control Record Values from Payload' is enabled.
<SAP:ChannelName>IDOC_INBOUND_U01_110</SAP:ChannelName>
In the IdocOutbound-node I can see the message code 'EXT' which should'nt be there.
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>001</SAP:MANDT>
<SAP:DOCREL>710</SAP:DOCREL>
<SAP:DOCNUM>0000000000033474</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>OILLDD01</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>OILLDD</SAP:MESTYP>
<SAP:MESCOD>EXT</SAP:MESCOD>
Too be more specific about the interface.:
I got one file in from a file adapter and out of that file I produce two idocs into R3 whit
two different idocs-adapters.
I think you are right about that the configuration may be mixed up.
Any idea of what I can do?
It may be an PI 7.10 bug ?
Shall I delete all config objects and so set config up from scrach again ?
/Per-Arne

Problem with SAPServerHost - Receiver Idoc

Good afternoon!
I am using the component SAP.Net Connector to receive IDOC's from the SAP, for this I created a Windows Service and in the OnStart event I create the SAPServerHost object that will go to talk with the SAP (through the transaction sm59, for example).
It happens that some times the SAP does not obtain to see this object, thus being does not obtain to send the IDOC's for windows service.
Thank you.
Danilo Santos de Oliveira

The SAPServerHost itself doesn't register at the SAP gateway. The actual SAPServer-inherited instances do so. You create them and attach them to the SAPServerHost. The host can control the state of the servers that it hosts, e.g. it can stop, pause and continue them.

SP14 Multi-mapping - error in receiver idoc adapter

Hi,
I have a scenario where a business service should send some XML to SAP CRM. I get the file via a sender JMS adapter and try to post it to CRM via a receiver IDOC adapter.
I have created a multimapping (1:N - 1 XML file to many Idocs) as should in the repository.
In the configuration under Interface Determination, I have chosen 'RB_SPLIT' and selected the interface multimapping.
It should be pointed out, that when testing both interface and message mapping i get no error. All idocs seem to be created as they should.
When testing the setup 'real life' the message fails. The error message in the monitor says:
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>InterfaceCollection</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface InterfaceCollection</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Notice that the above error is when trying to send only 1 record, which in turn then should result in only 1 idoc.
If trying to send multiple XML records, i get the following error:
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">MMF_ENGINETYPE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>A system error occurred in the outbound binding</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In the monitor in the payload of 'Request message mapping' I see as many Maindocument, Submaindocument pairs as should be Idocs.
Now i really don't know how to interpret the error messages in both cases, so I'm a little lost here...
It should be pointed out that the idoc being used everywhere in this scenario, has not been modified - from all places it is being used (and only exists) in the 'Imported objects | Idocs' place.
Also the Idoc is also being used as Inbound interface - so no mistakes here either.
I really hope someone can help me here, as I'm otherwise pretty stuck in this case.
Best regards,
Daniel

Hi Daniel,
I have exactly the same type of scenario (under SPS14 and now also SPS15), sending an XML message over JMS to XI and trying a multi-mapping to many IDocs (actually a list of orders in XML is mapped to n ORDERS Idocs).
I also face problems doing so, when I use the IDoc Adapter as outbound in the Receiver Agreement. I receive the following error:
<i>CO_TXT_MMF_ENGINETYPE
Messages in multi message format can be sent to one adapter engine only</i>
However, I tested the same scenario by just changing the Receiver Agreement to a File Communication Channel and - surprise, surprise - it works. One file per IDoc is created.
Of course, this is not what we want to accomplish, but when I checked this piece of documentation (sorry another link
http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/content.htm
the IDoc adapter is not listed in the list of Adapters that are supported. Does that mean, that this feature is not supported for generating IDocs? Maybe that's a question for a SAP OSS Message?
I hope that helped you a little further - if you find out more I'd be happy to learn about it.
regards,
Peter

Receiving IDocs from non-SAP system ...

Hello guys,
I have problem with implementing IDoc-XI-IDoc scenario. The sender system is a subsystem (non-SAP system) sending IDocs but XI is not able to receive them. I thing the IDoc metadata can not be found.
Logical system name of the sender is IF6020DEV. I registered the system in SLD. In Integration Directory I imported the Bussines System IF6020DEV to my scenario and I created communication channel of type Sender IDoc Adapter in it.
In IDX2 I created new port called IF6020DEV and I copied needed metadata into the port. But it doesn't work. Probably I don't do it right because I'm beginner with SAP XI.
Could you give me any advice how to configure XI for receiving IDocs from non-SAP system?
Thank you in advance!
Regards
Zbynek

Thank you very much. The issue described in refered discussion is almost same issue what I'm solving. Unfortunetally the described solution dosn't work for me.
The sender system still returns following error. I know you probably won't understand it because you don't know the subsystem, but maybe you could get some idea what is wrong.
05/29/09 16:09:19.482 idoup2 Logon...
05/29/09 16:09:19.482 idoup2 RfcOpenEx (TRACE=1 CLIENT=110 USER=xxxxxx LANG=D LCHECK=1 GWHOST=xxxxxx GWSERV=3361 ASHOST=xxxxxxx SYSNR=61 PASSWD=<password>)
05/29/09 16:09:19.529 idoup2 Logon RfcOpenEx result=1
05/29/09 16:09:19.607 idoup2 Call to (IDOC_INBOUND_ASYNCHRONOUS) failed (3)
05/29/09 16:09:19.607 idoup2 Handle=1
05/29/09 16:09:19.607 idoup2 key............:
05/29/09 16:09:19.607 idoup2 status.........:
05/29/09 16:09:19.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
05/29/09 16:09:19.607 idoup2 internal status:
05/29/09 16:09:19.607 idoup2 idoc_upload failed with rc=(3), try(2)
05/29/09 16:09:20.607 idoup2 key............:IDoc-Adapter Eingang: Der Absend
05/29/09 16:09:20.607 idoup2 status.........:EXCEPTION SYSTEM_FAILURE RAISED
05/29/09 16:09:20.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
05/29/09 16:09:20.607 idoup2 internal status:
05/29/09 16:09:20.607 idoup2 idoc_upload failed with rc=(18), try(1)
05/29/09 16:09:21.607 idoup2 Logoff...

Problem sending IDOC DESADV /AFS/DELVRY03 to XI

Hi Gurus,
I have problems sending IDOCs DESADV (basic type /AFS/DELVRY03) created by function LSEND_IDOC to XI system. IDOC is correctly created by R3 system (AFS ECC 5.0) and correctly sent on the XI port (Status: Data passed to port OK - 03), but XI system doesn't receive IDOC.
If I resend the same IDOC by WE19 tcode goes ok!!
In R3 sending system nothing warnings/errors in syslog or sm58.
Any suggests? Thanks in advance.

Issue solved! It is necessary close the master idoc with a commit

Receiver IDoc Adapter - Outbound IDocs in IDX5 but stucked in SM58

Hi Gurus,
I have a Receiver IDoc issue with the above error.
My message is successful in the IE pipeline (but with error on outbound side)
I can even view the generated IDoc numbers for those messages in IDX5,   but when double-clicking on those IDX5 entries SM58 is called and there I see the error as follows:
Caller: PIAFUSER
FM: IDOC_INBOUND_ASYNCHRONOUS
Status Text: No Authorization to send IDocs with Message Type 0
The weird thing is why is the caller showing as PIAFUSER, when my RFC destination is using a custom RFC user id.
Shouldn't it be that the Caller be my custom RFC user id since this is the user used by the RFC destination i specified in the receiver idoc comm channel?
Would anyone of you know how to resolve this?
I have already implemented Note 837595 for (a) my custom RFC user id in the target system (b) PIAFUSER and PIISUSER in my Integration Server; and assigned SAP_XI_APPL_SERV_USER role to PIISUSER also as specified in http://help.sap.com/saphelp_nwpi711/helpdata/en/d4/d12940cbf2195de10000000a1550b0/content.htm
I am aware that IDoc should be sent to the receiving system by using the IDoc adapter and NOT by using the IDoc Interface (tRFC port)
Thanks in advance

Hi All,
I resolved this on my own.
The steps i specified in my 1st post (Note implementation & Role assignment) was not enough, we had to assign SAP_ALL & SAP_NEW to the rfc user.    The Note implementation & role assignment should have solved this problem, but strangely it was not enough.
As for the question on why PIAFUSER is showing up as the caller and not the RFC user id used in the rfc destination used by the port, it's because the original caller is what gets recorded in SM58, in this case Receiver IDoc adapter on the AE so PIAFUSER,   and not the RFC user id.   you can verify this in table ARFCSSTATE
Thanks to all answers

Problem with idoc DEBMAS

Hi everybody.
We have a problem with idoc DEBMAS.
This idoc is sent from R3 to PI throw change pointers then the idoc is field only with the data modified in the master custumer.
We need the information fill it in the segment /IDOC/E1KNA1M/E1KNVVM to determine the receiver determination but this segment is not always sent.
What can be done in R3 to send always this segment.
We dont want to sent the whole data but always this segment.
Any idea???
Thanks a lot!!!!!

Hi,
As E1KNVVM segement is not mandatory, when you are triggering IDoc based on change poitner data might not populted in the E1KNVVM segment until some sales data is changed.
if you need that segement always just copy the Idoc type and make it mandaotry field.
otherwise yoy can populate some fields like STDVRS with the reruried constant and can use in your receiver determination.
Regards,
Suresh

Problem importing idoc to XI integration repository

I have deleoped a custom IDOC and released in SAP/R3. Next I have imported it to XI using transaction IDX2 without problems.
However, when I try to import the metadata to the integration repository, I can't find it in the list of available IDOcs. I have tried to refresh the catches, and even restartet the XI server, but i doesn't help.
Any suggestions ?

Hi Henrik,
See if these threads help :
importing IDOC in XI for interface mapping
IDOC in IDX2 is not visible in while importing into XI Design Component.
Settings in XI side to receive IDOC from application server
Check this link to know minimum authorizations required for a user to import RFC/Idocs.
http://help.sap.com/saphelp_nw04/helpdata/en/2b/a48f3c685bc358e10000000a11405a/content.htm

Erros receiver (idoc)

HI GURUS...
I have the next problem:
25 idoc's (payext) was sended ,,, but only 24 arrieve correctly to his destination,
The messages flow is that:
    R3 SENDER           ->               XI                 ->           R3 DESTINATION
    25 idoc's                             24 idoc's                                24 idoc's
Was sending correct       Was sending correctly            Was received correctly
(TRANS..BD87)
in XI no mistakes appears it`s like if the last idoc was never sended,,,
so my question is, where I have to start looking for in order to find the lost idoc?,
cause I did't find any mistakes yet
THAKS...

First thanks for the answare
Well , I´m already check that you suggest me
But in tcode    we02 I saw every thing in green
                     sm58 no errors match with my user
in fact i already check this others tcode BD58,,, IDX55,,, SM21,,, etc

Is it possible to receive IDOCs from a non-SAP system?

Hi,
I'm facing a problem where I have to configure SAP MII (12.0) to receive IDOCs from a non-SAP client. Is it possible? I'm dealing with a system named Hydra (developed by MPDV) and I'd like to know what I should configure in Hydra systems in fields like: PROGID, GWHOST, GWSERV, SYSNR, CLIENT etc.
Anyone can help me?
Thanks a lot in advance

Unless Hydra emulates ECC sending IDOCS, then you just might want to use the WSMessageListener (http://help.sap.com/saphelp_xmii120/helpdata/en/45/6a86ac88130dece10000000a11466f/frameset.htm) and configure your message processing rules accordingly.

Send/Receive IDOCs (XML) from/to SAP R/3 with XI-SOAP without XI!

Dear SAP specialists,
(BACKGROUND) We are using the Microsoft BizTalk Adapter for SAP 1.0, developed on top of the SAP DCOM Connector (we are using the version 6.20 Patch Nr. 177), with Microsoft BizTalk Server 2002 SP1 in order to send and receive IDOC via the tRFC transport protocol. We are using the Microsoft BizTalk Adapter for SAP 1.0 since February 2002, and today we are exchanging more than 25,000 IDOC/day with this architecture.
When we migrate our SAP R/3 system to the version 4.7 with WAS 6.20, I was very enthusiastic about the possibility of sending the IDOC in XML via the standard HTTP transport protocol, because it would considerably simplify my architecture, i.e. no need of any (expensive) adapter any more! But, I had to realise that the quality of service exactly once will not be there anymore with HTTP as it exists with tRFC. Then, we carry on using the tRFC transport protocol with the adapter.
(QUESTION) But recently, I followed the SAP Course TBIT40 XI Foundations and I learn that:
1. On one hand, the XI-SOAP protocol supports the quality of service exactly once by the usage of a message GUID within the XI-SOAP envelope;
2. On the other hand, all mySAP solutions using WAS 6.20 (or higher) carry a small Integration Engine (with XI-SOAP as the native transport protocol).
Then, my question is: << Is it possible to exchange IDOC (XML) directly with an SAP R/3 4.7 (WAS 6.20) via the XI-SOAP transport protocol using the small Integration Engine embedded into it, with the quality of service exactly once? >>
Many thanks in advance and best regards,
Patrice Krakow

Hello Patrice
We have same issue. Is it possible to use IDoc (XML) directly with SAP 5.0 with SOAP (HTTP) without XI?
Since your que is three years old, I'm sure you must have found some method for this.
We'll highly appreciate your help.
Regards: Gaurave

I cannot send an email from my iPad 2? No problem receiving, why does this happen? Have tried the suggestions for setting up email and after doing the sync mail through iTunes receiving worked great but still cannot send? Any help would be great

I cannot send an email from my iPad 2? No problem receiving, why does this happen? Have tried the suggestions for setting up email and after doing the sync mail through iTunes receiving worked great but still cannot send? Any help would be great!

The fact that you can receive means you have a valid e mail address, and have established the connection to the incoming server, so all of that works. Since the send does not work, that means your outgoing server is rejecting whatever settings you used formthe outgoing set up. Try them again.
Google your particular isp, and ipad and many times you will find the exact settings needed for your isp. Or tell us here, and soneone else may be on the same isp. Some mail services need you to change a port, or have a unique name for the outgoing server.
Kep trying.

Problem receiving from sender, showing in SmtpReceive log but not Message Tracking

Our Exchange 2007 server (SBS2k8 really) has had problems receiving mail from a certain sender the last few weeks. With the SMTPReceive set to verbose, I can see the mail coming in but it never shows up in the message tracking logs.
Looking at similar issues, I thought maybe the content filtering agent might have been grabbing it, so I set up a transport rule to take any mail from this particular domain and set the SCL to 0 as well as bcc a copy of it to myself. But I just noticed
another entry in yesterday's smtpreceive log and that didn't do the trick (or forward a copy to me for that matter).
I'm including some samples from our SMTP log. I can see that when it works, after the 354 Start mail input line, our server sends a 250 2.6.0 code confirming the message has been queued for delivery, at which point the remote server sends a QUIT and
we close it. But when it fails, there's nothing after the 354 line.
Example of good transmission:
2014-04-23T15:00:49.636Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,0,10.0.100.3:25,50.xxx.xxx.xxx:9100,+,,
2014-04-23T15:00:49.636Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,1,10.0.100.3:25,50.xxx.xxx.xxx:9100,*,SMTPSubmit SMTPAcceptAnySender AcceptRoutingHeaders,Set Session Permissions
2014-04-23T15:00:49.636Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,2,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,"220 xxx.xxx.com Microsoft ESMTP MAIL Service ready at Wed, 23 Apr 2014 11:00:49 -0400",
2014-04-23T15:00:49.948Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,3,10.0.100.3:25,50.xxx.xxx.xxx:9100,<,EHLO other.domain.com,
2014-04-23T15:00:49.948Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,4,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250-xxx.xxx.com Hello [50.xxx.xxx.xxx],
2014-04-23T15:00:49.948Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,5,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250-SIZE 26091520,
2014-04-23T15:00:49.948Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,6,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250-PIPELINING,
2014-04-23T15:00:49.948Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,7,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250-DSN,
2014-04-23T15:00:49.948Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,8,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250-ENHANCEDSTATUSCODES,
2014-04-23T15:00:49.948Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,9,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250-STARTTLS,
2014-04-23T15:00:49.948Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,10,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250-AUTH,
2014-04-23T15:00:49.948Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,11,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250-8BITMIME,
2014-04-23T15:00:49.948Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,12,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250-BINARYMIME,
2014-04-23T15:00:49.948Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,13,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250 CHUNKING,
2014-04-23T15:00:50.026Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,14,10.0.100.3:25,50.xxx.xxx.xxx:9100,<,MAIL FROM:<[email protected]> SIZE=3497,
2014-04-23T15:00:50.026Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,15,10.0.100.3:25,50.xxx.xxx.xxx:9100,*,08D11000FE2BD02F;2014-04-23T15:00:49.620Z;1,receiving message
2014-04-23T15:00:50.026Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,16,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250 2.1.0 Sender OK,
2014-04-23T15:00:50.073Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,17,10.0.100.3:25,50.xxx.xxx.xxx:9100,<,RCPT TO:<[email protected]>,
2014-04-23T15:00:50.291Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,18,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250 2.1.5 Recipient OK,
2014-04-23T15:00:50.338Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,19,10.0.100.3:25,50.xxx.xxx.xxx:9100,<,DATA,
2014-04-23T15:00:50.338Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,20,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,354 Start mail input; end with <CRLF>.<CRLF>,
2014-04-23T15:00:50.525Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,21,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,250 2.6.0 <[email protected]> Queued mail for delivery,
2014-04-23T15:00:50.556Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,22,10.0.100.3:25,50.xxx.xxx.xxx:9100,<,QUIT,
2014-04-23T15:00:50.556Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,23,10.0.100.3:25,50.xxx.xxx.xxx:9100,>,221 2.0.0 Service closing transmission channel,
2014-04-23T15:00:50.556Z,SBS2k8srv\SBS Receive,08D11000FE2BD02F,24,10.0.100.3:25,50.xxx.xxx.xxx:9100,-,,Local
and an example of the message not being successfully received:
2014-04-24T11:57:37.236Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,0,10.0.100.3:25,50.xxx.xxx.xxx:10131,+,,
2014-04-24T11:57:37.236Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,1,10.0.100.3:25,50.xxx.xxx.xxx:10131,*,SMTPSubmit SMTPAcceptAnySender AcceptRoutingHeaders,Set Session Permissions
2014-04-24T11:57:37.236Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,2,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,"220 xxx.xxx.com Microsoft ESMTP MAIL Service ready at Thu, 24 Apr 2014 07:57:36 -0400",
2014-04-24T11:57:37.532Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,3,10.0.100.3:25,50.xxx.xxx.xxx:10131,<,EHLO other.domain.com,
2014-04-24T11:57:37.532Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,4,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250-xxx.xxx.com Hello [50.xxx.xxx.xxx],
2014-04-24T11:57:37.532Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,5,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250-SIZE 26091520,
2014-04-24T11:57:37.532Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,6,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250-PIPELINING,
2014-04-24T11:57:37.532Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,7,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250-DSN,
2014-04-24T11:57:37.532Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,8,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250-ENHANCEDSTATUSCODES,
2014-04-24T11:57:37.532Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,9,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250-STARTTLS,
2014-04-24T11:57:37.532Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,10,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250-AUTH,
2014-04-24T11:57:37.532Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,11,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250-8BITMIME,
2014-04-24T11:57:37.532Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,12,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250-BINARYMIME,
2014-04-24T11:57:37.532Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,13,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250 CHUNKING,
2014-04-24T11:57:37.579Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,14,10.0.100.3:25,50.xxx.xxx.xxx:10131,<,MAIL FROM:<[email protected]> SIZE=3481,
2014-04-24T11:57:37.579Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,15,10.0.100.3:25,50.xxx.xxx.xxx:10131,*,08D11000FE2BD40D;2014-04-24T11:57:37.220Z;1,receiving message
2014-04-24T11:57:37.579Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,16,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250 2.1.0 Sender OK,
2014-04-24T11:57:37.610Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,17,10.0.100.3:25,50.xxx.xxx.xxx:10131,<,RCPT TO:<[email protected]>,
2014-04-24T11:57:37.719Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,18,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,250 2.1.5 Recipient OK,
2014-04-24T11:57:37.750Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,19,10.0.100.3:25,50.xxx.xxx.xxx:10131,<,DATA,
2014-04-24T11:57:37.750Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,20,10.0.100.3:25,50.xxx.xxx.xxx:10131,>,354 Start mail input; end with <CRLF>.<CRLF>,
2014-04-24T11:57:37.875Z,SBS2k8srv\SBS Receive,08D11000FE2BD40D,21,10.0.100.3:25,50.xxx.xxx.xxx:10131,-,,Remote
Interestingly, we used to receive email from this sender in the past. When it stopped working, it didn't quite stop working outright - at some point after the deliveries stopped, 2 made it in, but nothing again since then.

Check the agent logs on the machine. The Exchange anti-spam agents log files are found here:
C:\Program Files\Microsoft\Exchange Server\TransportRoles\Logs\AgentLog
If you use Forefront, its agent log files are usually here:
C:\Program Files (x86)\Microsoft Forefront Protection for Exchange Server\Data\FSEAgentLog
Other software may have its log files elsewhere.
--- Rich Matheisen MCSE&I, Exchange MVP

Problems Receiving Emails and some data on WIFI since latest software update.

Problems Receiving Emails and some data on WIFI since latest software update.
My blackberry torch will not receive emails on wifi since the latest software update, I've tried numerous wifi networks and several handsets, even had them replaced and received a brand new. Still the same problem.
When turning off the wifi network on the torch, the phone will stall for 5-10min while it tries to communicate with the network (vodafone) to receive outstanding emails and data.
Can someone please inform Blackberry and get a quick fix on this

Sounds like you have Do NOt Disturb turned on.
settings - do not disturb - off

Problem receiving IDOC

Similar Messages

Maybe you are looking for