Message stucked at O/B queue in ECC

Dear All,
We have a scenario - Purchase Order Data posted from ECC to SRM system through PI using Proxy.
Problem is when the message is triggered from ECC, it was stucked up at O/B queue in ECC in MCEXO2 queue and the entry was not found in SXMB_MONI in ECC.
Could you please suggest us resolution.
Thanks & Regards,
Soumya.

Dear All,
In SMQ1, select the Q, Unlock & Activate. When we click on activate system issues the message u201CLUWs in status NOSEND must be picked up by the application u2013Message No :: SR082 u201C.
What does that mean ? Can anybody suggest What are we missing ?
Regards,
Soumya.

Similar Messages

Messages stucked in moni with queue status as "RUNNING"

Hi All,
Few of messages stucked in moni with queue status as "RUNNING" from the past 6 to 7 hours. all the stucked messages running on same dialog instance app server 03 (ucobpi03_PIP_03). i checked PIP appserver its working fine.
Can any one please expalin me how to clean the queues..is there any effect of other queues ?
Thanks,
Siva.

Hi,
it can be due to multiple reasons....
check the interface logic built ...it can be either due to this or can be of large volume of data...
Also check the queues have been registered or not...
HTH
Rajesh

Messages stuck in SMQ2 Inbound Queue.

Scenario: File->XI->Proxy
When I put 50 files at the same time in a directory, channel is configured Exactly Once in Order and we have created queue with the name GATQUEUE. The messages are picked up from directory and sent one by one to BPM process. 31 messages out of 50 poccesed succesfully but 19 of them get stuck in the queue always. Though GATQUEUE is released lately but they are stuck in 'XBQO$PE_WS90000013' queue. This is seen in SMQ2 Inbound Queue.
Could you please tell me how to release this message which are already stuck and what bit of configuration required so that it works for 1000s of files/messages at a time?
Thanks
K

Hi Kiran,
Just add the below parameter in XI tcode : SXMB_ADM
Execure Integration Engine and Configuration.
Click on Specific Configuration, go to change mode
Click on New entries
Category : MONITOR
Parameter :QRFC_RESTART_ALLOWED
Current Value : 1
Save.
Regards,
Venu.

Message stuck in Adapter Engine queue with status "Delivering"

Hi All,
I have a File to File EOIO scenario. The messages are sucessfully delivered from IE to AE. All entries have a chequered flag in SXMB_MONI. No messages are stuck in IE queue (SMQ2). But the message is stuck in AE queue with status "Delivering". I can not resend or cancel the message coz the status is "delivering".
The reason it is in "delivering" status is due to some config error that I made in Communication Channel FTP parameters. Now it is corrected. But how do I deal with this message now?
Restart of server is not an option here. Is there are place I can delete the message from AE queue?
Thanks
Jaishankar

You can see the queues status (and number of stuck entries etc) through the link:
http://<host>:<port>/MessagingSystem/monitor/systemStatus.jsp
There, you can maintain the queues.
There is also a link for the EOIO Sequence Monitor:
http://<host>:<port>/MessagingSystem/monitor/sequenceMonitor.jsp
There you can see the stuck messages and maintain these.
Make sure to handle the proper message IDs.
All of these are acessible through the Messaging System main page:
http://<host>:<port>/MessagingSystem/
Regards,
Henrique.

How to check the messages stuck up in the queues.

hi experts,
i have implemented the message queues in the EOIO form. if any message is stuck up in the inbound or the outbound queue. where would i will be able to check it.
i have the answers of checking it up in SXMB_MONI and runtime workbench.
is there any other way where i can get info about where the message has stuck up
regards,
Alpa.

Hi,
you could use transactions SMQ1 and SMQ2.
For more information:
XI Asynchronous Message Processing: Understanding XI Queues -Part I
http://help.sap.com/saphelp_nw04/helpdata/en/7b/94553b4d53273de10000000a114084/frameset.htm
Regards
Patrick
Edited by: Patrick Koehnen on Oct 22, 2008 2:51 PM

Messages stuck in queue AFWRecv of Adapter Framework

Hello,
Messages stuck in queue AFWRecv of Adapter Framework in our production system(trace in RWB: "to be delivered")
in URL http://xxxxxxx:50000/MessagingSystem/monitor/systemStatus.jsp we can see:
Queue Info
Queue Name isStarted QueueSize ThreadCount (working) MaxThreads
AFWCall true 0 0 (0) 20
AFWRecv true 954 10 (10) 10
AFWRqst true 0 0 (0) 20
AFWSend true 0 0 (0) 10
We have tried to resend the first message but that´the result:
Time Stamp Status Description
2010-10-09 11:24:06 Success The message was successfully received by the messaging system. Profile: XI URL: http://xxxxxxxxx:8100/MessagingSystem/receive/AFW/XI
2010-10-09 11:24:06 Success Using connection AFW. Trying to put the message into the receive queue.
2010-10-09 11:24:06 Success Message successfully put into the queue.
2010-10-11 00:01:46 Success Recovering from loss of connection to database; message loaded into queue by recover job: System Job (Failover Recovery)
2010-10-11 02:48:16 Success System Startup: Message successfully loaded into queue: AFWRecv.
2010-10-13 11:03:19 Success Admin action: Trying to redeliver message.
2010-10-13 11:03:46 Success Admin action: Trying to redeliver message.
Since then it stucks there...
Any help would be apreciated....

Hi,
Go to the runtime workbench --> Message Monitoring --> Click on the 'Configure Table Columns' > Check Sequence ID, Serialization Context & Sequential Number options.> and then click 'Apply'.
Then in the 'Serialization Context' column you will get the queue ID for the stcuk message.
Take that value and click on the 'Show additional Criteria' option on the top and put this value in the 'Serialization context' parameter. Also,select the start/end date as 'This year' --> start.
You will get all the messages stuck in that particular queue for this yoear, try to rectify them, so that your message will be processed.
-Supriya.

Messages stuck in Java Queues

I am running PI7.0 SP10 on a MCOD system running ECC6.0 and EP.
We had an issue last week on our Production system where the Java Stack went down, and when the system came back up, we cleared the issues in SMQ1, SMQ2 and SM58 and now we have over two hundred messages stuck in the java queues.
There is nothing locked in SM13, in sxmb_moni all the messgaes are successfully processed... In the RWB the status of the messages are "To be delivered".
I have tried reactivating the adapters but this has not worked.
The queues can be seen in the http://host.fqdn:5<SYSNO>00/MessagingSystem/monitor/systemStatus.jsp
specifically : File_http://sap.com/xi/XI/SystemRecv
and
SOAP_http://sap.com/xi/XI/SystemRecv
where the "isStarted" is set to false, where all the others are true...
How can I go about starting these and processing the backlog of messages??
I have searched OSS, SDN and SAPFans but had not luck!
I have subsequently done a full cache refresh and CPACache refresh but this has not helped.
There are no locked users (XI/PI users) holding this up!

Ok,
It seems to be ok, the return can be http 200 or http 500.
The Soap and File are destinations, ok.
The messages are with status "delivering" on rwb... really, increasing the number of threads will not solve this...
I don't have access to visual admin (only basis team can access it here). I thought it could be something wrong with destination (but you already checked it)... so, the only thing can be done is to find in visual admin somewhere about system properties, conection parameters searching for something wrong there... here are our parameters if you would like to find something (sorry for the size of message)...
AFW.Call.maxConsumers 10
AFW.Recv.maxConsumers 5
AFW.Rqst.maxConsumers 10
AFW.Send.maxConsumers 5
BC_http://sap.com/xi/XI/System.Call.maxConsumers 20
BC_http://sap.com/xi/XI/System.Recv.maxConsumers 10
BC_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
BC_http://sap.com/xi/XI/System.Send.maxConsumers 10
BcAdapter.Call.maxConsumers 10
BcAdapter.Recv.maxConsumers 5
BcAdapter.Rqst.maxConsumers 10
BcAdapter.Send.maxConsumers 5
CIDXAdapter.Call.maxConsumers 10
CIDXAdapter.Recv.maxConsumers 5
CIDXAdapter.Rqst.maxConsumers 10
CIDXAdapter.Send.maxConsumers 5
CIDX_http://sap.com/xi/XI/System.Call.maxConsumers 20
CIDX_http://sap.com/xi/XI/System.Recv.maxConsumers 10
CIDX_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
CIDX_http://sap.com/xi/XI/System.Send.maxConsumers 10
EOIO.lockTimeout 5
File_http://sap.com/xi/XI/System.Call.maxConsumers 20
File_http://sap.com/xi/XI/System.Recv.maxConsumers 10
File_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
File_http://sap.com/xi/XI/System.Send.maxConsumers 10
JDBC_http://sap.com/xi/XI/System.Call.maxConsumers 20
JDBC_http://sap.com/xi/XI/System.Recv.maxConsumers 10
JDBC_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
JDBC_http://sap.com/xi/XI/System.Send.maxConsumers 10
JMS_http://sap.com/xi/XI/System.Call.maxConsumers 20
JMS_http://sap.com/xi/XI/System.Recv.maxConsumers 10
JMS_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
JMS_http://sap.com/xi/XI/System.Send.maxConsumers 10
JPR.Call.maxConsumers 10
JPR.Recv.maxConsumers 5
JPR.Rqst.maxConsumers 10
JPR.Send.maxConsumers 5
MPA.Call.maxConsumers 10
MPA.Recv.maxConsumers 5
MPA.Rqst.maxConsumers 10
MPA.Send.maxConsumers 5
Mail_http://sap.com/xi/XI/System.Call.maxConsumers 20
Mail_http://sap.com/xi/XI/System.Recv.maxConsumers 10
Mail_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
Mail_http://sap.com/xi/XI/System.Send.maxConsumers 10
Marketplace_http://sap.com/xi/XI/System.Call.maxConsumers 20
Marketplace_http://sap.com/xi/XI/System.Recv.maxConsumers 10
Marketplace_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
Marketplace_http://sap.com/xi/XI/System.Send.maxConsumers 10
RFC_http://sap.com/xi/XI/System.Call.maxConsumers 20
RFC_http://sap.com/xi/XI/System.Recv.maxConsumers 10
RFC_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
RFC_http://sap.com/xi/XI/System.Send.maxConsumers 10
RNIF11Adapter.Call.maxConsumers 20
RNIF11Adapter.Recv.maxConsumers 10
RNIF11Adapter.Rqst.maxConsumers 20
RNIF11Adapter.Send.maxConsumers 10
RNIF11_http://sap.com/xi/XI/System.Call.maxConsumers 20
RNIF11_http://sap.com/xi/XI/System.Recv.maxConsumers 10
RNIF11_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
RNIF11_http://sap.com/xi/XI/System.Send.maxConsumers 10
RNIFAdapter.Call.maxConsumers 10
RNIFAdapter.Recv.maxConsumers 5
RNIFAdapter.Rqst.maxConsumers 10
RNIFAdapter.Send.maxConsumers 5
RNIF_http://sap.com/xi/XI/System.Call.maxConsumers 20
RNIF_http://sap.com/xi/XI/System.Recv.maxConsumers 10
RNIF_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
RNIF_http://sap.com/xi/XI/System.Send.maxConsumers 10
SOAP_http://sap.com/xi/XI/System.Call.maxConsumers 20
SOAP_http://sap.com/xi/XI/System.Recv.maxConsumers 10
SOAP_http://sap.com/xi/XI/System.Rqst.maxConsumers 20
SOAP_http://sap.com/xi/XI/System.Send.maxConsumers 10
bulkCommit.threshold 100
cluster.timeout 60000
connection.0.ackListener null
connection.0.exceptionListener localejbs/AFWListener
connection.0.jms.messageSelector null
connection.0.jms.profile null
connection.0.jms.provider null
connection.0.jms.queue null
connection.0.messageListener localejbs/AFWListener
connection.0.name AFW
connection.0.pollAttempts 60
connection.0.pollInterval 60000
connection.1.ackListener localejbs/MarketPlaceAdapterListener
connection.1.exceptionListener localejbs/MarketPlaceAdapterListener
connection.1.jms.messageSelector null
connection.1.jms.profile null
connection.1.jms.provider null
connection.1.jms.queue null
connection.1.messageListener localejbs/MarketPlaceAdapterListener
connection.1.name MPA
connection.1.pollAttempts 60
connection.1.pollInterval 60000
connection.2.ackListener null
connection.2.exceptionListener localejbs/JPR
connection.2.jms.messageSelector null
connection.2.jms.profile null
connection.2.jms.provider null
connection.2.jms.queue null
connection.2.messageListener localejbs/JPR
connection.2.name JPR
connection.2.pollAttempts 60
connection.2.pollInterval 60000
connection.3.ackListener null
connection.3.exceptionListener localejbs/RNIFMessageListener
connection.3.jms.messageSelector null
connection.3.jms.profile null
connection.3.jms.provider null
connection.3.jms.queue null
connection.3.messageListener localejbs/RNIFMessageListener
connection.3.name RNIFAdapter
connection.3.pollAttempts 60
connection.3.pollInterval 60000
connection.4.ackListener null
connection.4.exceptionListener localejbs/CIDXMessageListener
connection.4.jms.messageSelector null
connection.4.jms.profile null
connection.4.jms.provider null
connection.4.jms.queue null
connection.4.messageListener localejbs/CIDXMessageListener
connection.4.name CIDXAdapter
connection.4.pollAttempts 60
connection.4.pollInterval 60000
connection.5.ackListener localejbs/BcAdapterListener
connection.5.exceptionListener localejbs/BcAdapterListener
connection.5.jms.messageSelector null
connection.5.jms.profile null
connection.5.jms.provider null
connection.5.jms.queue null
connection.5.messageListener localejbs/BcAdapterListener
connection.5.name BcAdapter
connection.5.pollAttempts 60
connection.5.pollInterval 60000
connection.6.ackListener null
connection.6.exceptionListener localejbs/TestListener
connection.6.jms.messageSelector null
connection.6.jms.profile null
connection.6.jms.provider null
connection.6.jms.queue null
connection.6.messageListener localejbs/TestListener
connection.6.name test
connection.6.pollAttempts 60
connection.6.pollInterval 60000
connection.7.ackListener null
connection.7.exceptionListener localejbs/RNIF11MessageListener
connection.7.jms.messageSelector null
connection.7.jms.profile null
connection.7.jms.provider null
connection.7.jms.queue null
connection.7.messageListener localejbs/RNIF11MessageListener
connection.7.name RNIF11Adapter
connection.7.pollAttempts 60
connection.7.pollInterval 60000
connections (name=AFW, messageListener=localejbs/AFWListener, exceptionListener=localejbs/AFWListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=MPA, messageListener=localejbs/MarketPlaceAdapterListener, exceptionListener=localejbs/MarketPlaceAdapterListener, ackListener=localejbs/MarketPlaceAdapterListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=JPR, messageListener=localejbs/JPR, exceptionListener=localejbs/JPR, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=RNIFAdapter, messageListener=localejbs/RNIFMessageListener, exceptionListener=localejbs/RNIFMessageListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=CIDXAdapter, messageListener=localejbs/CIDXMessageListener, exceptionListener=localejbs/CIDXMessageListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=BcAdapter, messageListener=localejbs/BcAdapterListener, exceptionListener=localejbs/BcAdapterListener, ackListener=localejbs/BcAdapterListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)(name=test, messageListener=localejbs/TestListener, exceptionListener=localejbs/TestListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=10, Recv.maxConsumers=10, Call.maxConsumers=20, Rqst.maxConsumers=20)(name=RNIF11Adapter, messageListener=localejbs/RNIF11MessageListener, exceptionListener=localejbs/RNIF11MessageListener, pollInterval=60000, pollAttempts=60, Send.maxConsumers=10, Recv.maxConsumers=10, Call.maxConsumers=20, Rqst.maxConsumers=20)
debug HTTP
failover.reassignOnNodeLoss true
initial.delay 0
jdbc.autoConfigure false
jdbc.datasource jdbc/SAP/BC_XI_AF_MSG
jdbc.dbProductName ORACLE
jdbc.substituteEmptyString true
jdbc.supportsOpenSQL true
jdbc.supportsScrollableResultSet false
jms.0.dmq SonicMQ.deadMessage
jms.0.messageLengthKey message_length
jms.0.password ********
jms.0.provider
jms.0.url
jms.0.username
monitoring.displayDefault fromParty, toParty, status, timesFailedRetries, sentRecvTime
persistMessageRemover.checkInterval 1440
proxy.password ********
proxy.user
reassignCheck.waitTime 30
ssl.httpsHandler iaik.protocol.https.Handler
ssl.securityProvider iaik.security.provider.IAIK
ssl.serverNameCheck false
ssl.trustedCACerts.viewName TrustedCAs
startup.delay 0
syncMessageRemover.checkInterval 60
syncMessageRemover.messageCount 1000
syncMessageRemover.removeBody true
system.deafaultMaxConsumersPerQueue 10
system.failNonDelivered false
system.message.lazyRead true
system.node 23654950
system.queueConsumerThreadPoolSize 0
system.statusLog System,Send,Recv,Call,Rqst
system.transactionManager ts
test.Call.maxConsumers 20
test.Recv.maxConsumers 10
test.Rqst.maxConsumers 20
test.Send.maxConsumers 10
throughputStatistics enabled
regards
roberti

Mails/Alerts-triggered for messages stuck in queues and failed in moni

Hi,
I have two doubts.
1) Messages are getting stuck in smq2 of my ECC and PI system. I have to manually push them. Is there any mechanism in which we can get alerts/mails when messages get stuck in queues.
I have already gone through the blog /people/santhosh.kumarv/blog/2009/05/19/sap-xipi-alerts-for-queue-errors and I have implemented it in ECC system. But no mails were generated.
2)Is there any method in which I can get alerts/mails when a message fails in sxmb_moni of ECC system?
Thanks and regards,
Siji

Hi Sanjeev,
I made a report with the following code in it and executed it. So I think that should work even if the job for it is not scheduled. There were messages stuck in queue. But no alert was generated. I had also created alert category in ECC.
Thanks and regards,
Siji

XML file getting stucked in queue in ECC preventing material status in MDM.

XML file getting stuck in queue in ECC preventing material status in MDM to be changed.
Hi SAP Experts,
We have an issue regarding XML messages getting stuck in queue in ECC preventing the material status in SAP MDM to be changed from "Approved" to "Updated/Posted".
Checking in transaction SXI_MONITOR the status of the XML Messages are Scheduled or Green Flagged, looking at the time started it has been an hour and it is not yet processed successfully; and also checking the queues XBTR* (XBTR0001, XBTR0002 and ETC.) via transaction SMQ2 have stopped.
We need to manual process the XML messages for it to be processed successfully.
I'm unable to understand why these files are getting stuck in Queue's.
Many thanks in advance and have an awesome day ahead.
Regards,
Aeron Merc

Hi Aeron,
Check whether the Queue XBTR* (XBTR0001, XBTR0002 and ETC.) is Unregistered in SMQR.
If it is so you can see as U in the Queue type.
Try to register by selecting the queue and click on Registration button and activate.
Then check your message in MONI, hope this should solve your problem.
Thanks
Sai.

Messages stuck in the queue... how do I make them to be processed again?

Hi,
I'm new to SAP PI and kinda confused with queues.
I have file -> bpm -> file scenario and there was an error in mapping within bpm process.
When I went to qRFC Monitor (smq2), I see that in XBQO$PE_WS90000002 queue,
there's an error, 'Permanent error in BPE inbound processing'... which is expected.
Now, I run the interface scenario again several times but they don't get processed
but stuck in the same queue. At this stage, I didn't know what to do...
I thought by deleting the error message, other messages will be processed...
I deleted the error message but the other messages are still in the queue...
I have two questoins.
1. What is the best way to handle an error in the queue... can I just delete it? or is there a better way to handle an error in the queue?
2. After deleting the queue, what should I do to make the other messages to be processed again...
Thank you.
-Won

Hi Won,
There are programs for restarting the LUW entries:
programs
· RSARFCRD: tRFC Monitor (transaction SM58)
· RSARFCSE: Restart an LUW (background job)
· RSARFCEX: Restart tRFC LUWs (background job)
· RSQOWKEX: Restart QOUT qRFC LUWs
· RSQIWKEX: Restart QIN qRFC LUWs
· RSARFCSE: Delete an LUW (background job)
· RSARFCER: Delete various LUWs
Also, check the url:
http://help.sap.com/saphelp_nw04/helpdata/en/25/bcfa40badbf46fe10000000a1550b0/content.htm
Hope this helps.
Regards,
Sushama

TNEF Issue - Winmail.dat or messages stuck in submission queue

Hi guys,
I've looked around the forums and have found people that have had submission queue issues when they set TNEF to $null or $false, and have found that the unified answer is to set TNEF to $true.
I also see folks having issues with recipients in remote domains receiving winmail.dat files in some instances (with a .pdf or .xls file attached) if TNEF is set to $true.
I have both issues. If I set TNEF to $true, I encounter the winmail.dat file problem. If I set TNEF to $false or $null, I encounter the submission queue issue (submission queue states "A transient storage failure occured", and users get a queue
expiration bounce). Neither of these states are acceptable. I cannot have messages stuck in the queue only to be expired, and I cannot have recipients in remote domains failing to receive attachments in emails.
Does anyone have a possible workaround that might resolve this particular situation? It seems that this has been an issue in Exch 2010.
Current Environment Configuration:
I am running Exchange 2013 SP1 Standard on both of my CAS/MBX servers, running on Server 2012 R2 patched to the latest updates. I have an inbound spam filter, but mail outbound is not filtered, therefore the spam filter on our side should not play a role.
I do have not made any changes to the exchange default malware filter either. Other than this issue, mail is flowing correctly and as expected.

I also see folks having issues with recipients in remote domains receiving winmail.dat files in some instances (with a .pdf or .xls file attached) if TNEF is set to $true.
Hi,
According to your description, my understanding is that all the remote domain's recipients would receive winmail.dat files when you send the message to them if TNEF is set to $true, right?
The Winmail.dat file is used to preserve Rich Text formatting. Outlook uses it when sending a Rich Text-formatted message. During transport, the content of the message may be changed, preventing the receiving client from being able to read the formatting
instructions. In other cases, the receiving client does not use or recognize the winmail.dat file.
I recommend that you refer to the following article to solve the issue:
http://support.microsoft.com/kb/278061
Method 1: Change the default message format
The sender can change the format of the email messages that they send by using the following steps:
On the Tools menu, click Options, and then click
Mail Format.
In Compose in this message format, click to select Plain Text, and then click
OK.
NOTE: To send to certain recipients that use RTF format and others recipients that use plain text format, the sender must set the option for the recipient in either the Personal Address Book or the recipient's contact record.
Method 2: Modify the recipient's entry in the Personal Address Book
The sender can use the following steps to remove the RTF format from the recipient attribute in the Personal Address Book:
On the Tools menu, click Address Book.
In Show Names From, click the Personal Address Book.
Select the addressee that you want to set as plain text, and then click
Properties on the File menu.
In the SMTP-General tab, click to clear the Always send to this recipient in Microsoft Exchange rich text format check box, and then click
OK.
Method 3: Change the specific contact format
The sender can use the following steps to set plain text in the recipient's contact record:
Open the recipient's record in the Contacts folder.
Double-click the recipient's e-mail address.
In the E-Mail Properties dialog box, click Send Plain Text only under
Internet Format.
Method 4: Set the Outlook Rich Text Format Internet e-mail setting
In Outlook 2003 and Outlook 2007, click Options on the Tools menu.
Click the Mail Format tab.
Click Internet Format.
Under Outlook Rich Text options, click either Convert to HTML format or
Convert to Plain Text format.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support
Niko,
The Winmail.dat issue is only part of the problem, as described in my original post. For these messages (which it's a different set of messages every time, and it's becoming impossible for me to track them all down), if I set exchange or outlook to encode
the message in Rich Text, the message gets encoded and sent to the recipient. Some of our recipients will reject the message because it is rich text, others receive a winmail.dat file.
However, if I set exchange to not encode messages (TNEF= $false or $null), the message becomes stuck in the submission queue and eventually times out with an error resembling "Storage Transient Failure".

Exchange 2003 SP2 messages stuck in queue

HI
I just inherited a exchange 2003 SP2 machine and next month we are migrating to 365. But here is what happen so far and the issue
1. The previous IT company had the emails flowing thru smart host via their own hosted spam filter.
2. I came in and changed my MX records and installed a on server spam filter (ORF) by Vamsoft and configured it. Removed the smart host info and made sure that the firewall is all configured properly.
3. Tested in bound email.
4. Problem. Out bound emails go thru till the server. Some users get a delayed email but others do not. The messages are stuck in the outbound Queue. restarted the SMTP and still no luck. Disabled Spam filter (ORF) still
no luck.
Then I looked at anything which is common.
mails to msn.com & Hotmail.com are stuck. Emails to my company tejes.com are stuck. There are other few companies but do not know their email provider but the common theme between these 3 domains all are hosted by Microsoft. tejes.com
is on office365.
I need help. Please
Anil
Update: Fixed it. The previous company had filters in place.

HI
I just inherited a exchange 2003 SP2 machine and next month we are migrating to 365. But here is what happen so far and the issue
1. The previous IT company had the emails flowing thru smart host via their own hosted spam filter.
2. I came in and changed my MX records and installed a on server spam filter (ORF) by Vamsoft and configured it. Removed the smart host info and made sure that the firewall is all configured properly.
3. Tested in bound email.
4. Problem. Out bound emails go thru till the server. Some users get a delayed email but others do not. The messages are stuck in the outbound Queue. restarted the SMTP and still no luck. Disabled Spam filter (ORF) still
no luck.
Then I looked at anything which is common.
mails to msn.com & Hotmail.com are stuck. Emails to my company tejes.com are stuck. There are other few companies but do not know their email provider but the common theme between these 3 domains all are hosted by Microsoft. tejes.com
is on office365.
I need help. Please
Anil
Update: Fixed it. The previous company had filters in place.
Hi Anil,
Glad to know the issue has been fixed.
Also find this KB for your reference:
How to configure connection filtering to use Realtime Block Lists (RBLs) and how to configure recipient filtering in Exchange 2003
http://support.microsoft.com/kb/823866
Thanks
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Exchange 2013 Messages Stuck in Queue

Hello,
I have an Exchange 2013 on-prem serer. I'm noticing that certain messages get stuck in the queue. They report back errors of "451 4.4.0 SMTPSEND.SuspiciousRemoteServerError; remote server disconnected abruptly; retry will be delayed".
It seems to be random. I've sent messages to a domain I've seen with messages stuck, and mine work. When I log the send connector it really doesn't show me much. Can anyone give me some leads?
2014-10-13T14:41:42.162Z,Internet Outbound,08D1B4FCB0EBBB8A,10,10.10.0.30:19282,152.163.0.67:25,>,EHLO mail.mydomain.com,
2014-10-13T14:41:42.178Z,Internet Outbound,08D1B4FCB0EBBB8A,11,10.10.0.30:19282,152.163.0.67:25,<,250-mtaig-aak04.mx.aol.com,
2014-10-13T14:41:42.178Z,Internet Outbound,08D1B4FCB0EBBB8A,12,10.10.0.30:19282,152.163.0.67:25,<,250-STARTTLS,
2014-10-13T14:41:42.178Z,Internet Outbound,08D1B4FCB0EBBB8A,13,10.10.0.30:19282,152.163.0.67:25,<,250 DSN,
2014-10-13T14:41:42.193Z,Internet Outbound,08D1B4FCB0EBBB8A,14,10.10.0.30:19282,152.163.0.67:25,>,STARTTLS,
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB8A,15,10.10.0.30:19282,152.163.0.67:25,<,220 2.0.0 Ready to start TLS,
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB8A,16,10.10.0.30:19282,152.163.0.67:25,*,,Sending certificate
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB8A,17,10.10.0.30:19282,152.163.0.67:25,*,"CN=mail.mydomain.com, OU=Domain Control Validated",Certificate subject
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B2FCB0ENBB8A,18,10.10.0.30:19286,152.163.0.67:25,*,"CN=Go Daddy Secure Certificate Authority - G2, OU=http://certs.godaddy.com/repository/, O=""GoDaddy.com, Inc."", L=Scottsdale, S=Arizona,
C=US",Certificate issuer name
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB3A,19,10.10.0.30:19282,152.163.0.67:25,*,0828F6C11RF919,Certificate serial number
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB8A,20,10.10.0.30:19282,152.163.0.67:25,*,D752EC6829000606559BDC63320D9F222227E773,Certificate thumbprint
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB8A,21,10.10.0.30:19282,152.163.0.67:25,*,mail.mydomain.com;www.mail.sigwnet.com;autodiscover.mydomain.com,Certificate alternate names
2014-10-13T14:41:42.240Z,Internet Outbound,08D1B4FCB0EB3B8A,22,10.10.0.30:19282,152.163.0.67:25,*,,Received certificate
2014-10-13T14:41:42.240Z,Internet Outbound,08D1B4FCA0EBBB8A,23,10.10.0.30:19282,152.163.0.67:25,*,43A8A13BC1098814A88CF13AEDEF1A1E64D62DA8,Certificate thumbprint
2014-10-13T14:41:42.240Z,Internet Outbound,08D1B4FCB0EBBB8A,24,10.10.0.30:19282,152.163.0.67:25,>,EHLO mail.mydomain.com,
2014-10-13T14:41:42.474Z,Internet Outbound,08D1B4FCB0EBBA8A,25,10.10.0.30:19282,152.163.0.67:25,<,250-mtaig-aak04.mx.aol.com,
2014-10-13T14:41:42.474Z,Internet Outbound,08D1A4FCB0EBBB8A,26,10.10.0.30:19282,152.163.0.67:25,<,250 DSN,
2014-10-13T14:41:42.474Z,Internet Outbound,08D1B4FCB0EBBB8A,27,10.10.0.30:19282,152.163.0.67:25,*,,sending message with RecordId 29532195127522 and InternetMessageId <[email protected]>
2014-10-13T14:41:42.474Z,Internet Outbound,08D1B4FCB0EBBB8A,28,10.10.0.30:19282,152.163.0.67:25,>,MAIL FROM:<[email protected]>,
2014-10-13T14:41:42.505Z,Internet Outbound,08D1B4FCB0EBBB8A,29,10.10.0.30:19282,152.163.0.67:25,<,250 2.1.0 Ok,
2014-10-13T14:41:42.505Z,Internet Outbound,08D1B4FCB0EBBB8A,30,10.10.0.30:19282,152.163.0.67:25,>,RCPT TO:<[email protected]>,
2014-10-13T14:41:42.552Z,Internet Outbound,08D1B4FCB0EBBB8A,31,10.10.0.30:19282,152.163.0.67:25,<,250 2.1.5 Ok,
2014-10-13T14:41:42.552Z,Internet Outbound,08D1B4FCB0EBBB8A,32,10.10.0.30:19282,152.163.0.67:25,>,DATA,
2014-10-13T14:41:42.583Z,Internet Outbound,08D1B4FCB0EBBB8A,33,10.10.0.30:19282,152.163.0.67:25,<,354 End data with <CR><LF>.<CR><LF>,
2014-10-13T14:41:45.688Z,Internet Outbound,08D1B4FCB0EBBB8A,34,10.10.0.30:19282,152.163.0.67:25,<,250 2.0.0 Ok: queued as 8A7497000009F,
2014-10-13T14:41:45.688Z,Internet Outbound,08D1B4FCB0EBBB8A,35,10.10.0.30:19282,152.163.0.67:25,>,QUIT,
2014-10-13T14:41:45.719Z,Internet Outbound,08D1B4FCB0EBBB8A,36,10.10.0.30:19282,152.163.0.67:25,<,221 2.0.0 Bye,
2014-10-13T14:41:45.719Z,Internet Outbound,08D1B4FCB0EBBB8A,37,10.10.0.30:19282,152.163.0.67:25,-,,Local
2014-10-13T14:42:01.132Z,Internet Outbound,08D1B4FCB0EBBB88,27,10.10.0.30:19263,74.208.5.21:25,*,,"HandleError has encountered a suspicious connection reset from a remote, non-mailbox transport server (will retry in 00:10:00)."
2014-10-13T14:42:01.132Z,Internet Outbound,08D1B4FCB0EBBB88,28,10.10.0.30:19263,74.208.5.21:25,-,,Remote

Hi rmicha9682,
Agree with Gareth, it seems to be a firewall issue.
I have seen this issue caused by the SMTP Fixup protocol when using TLS encryption.
I recommend you try disabling SMTP Fixup and check if any helps.
The following article for your reference:
http://support.microsoft.com/kb/320027/en-us
Best regards,
Niko Cheng
TechNet Community Support

JMS messages stuck in queue in weblogic v923 cluster

Hi all,
Enviornment details:
In our pre-production weblogic v923 cluster enviornment with Oracle 10g database, there are 10 server boxes with 2 managed nodes running on each server box in linux enviornment.
There are 3 JMS queues and 1 error queue per managed node.
All the queues are durable and the persitence store is a database table. There is a single database table per single managed node.
High loads of JMS messages from client applications coming on each of the 3 JMS queue are processed by the cluster on daily basis.
The JMS messages that failed to be processed the very first time due to the application logic exceptions are put on error queue since the retry is set to zero on the non-error queue.
The application exceptions are logged to a database table for futher reference.
The falied messages from the error queue are read by spring based MDP and resent to the application for reprocessing.
If no application exceptions, the message will be persisted in a relational database; in the case of failures, MDP code puts the failed message back on to the error queue.
The auto_ack is true on the JMS message.
It is observed about less than 1% of the messages fail the original processing and are in error queue on daily basis.
99.9% of the time, the reprocessing of the messages from the error queue is a success.
Currently due to some obvious reasons, the system administrator stops a managed node when the disk is full and start a different managed node on the same server box. This approach will be stopped in the very near future so that all nodes on all servers are running at any point of time by making few enviornment changes.
Problem:
1a) Occasionally, it is observed that 1 - 4 JMS messages are stuck in the error queue. There are no signs of reprocessing as there are no application exceptions or the corresponing insert into the database. The JMS persistence store table still has the JMS message.
1b) It is observed that over time, the same JMS messages that were originally stuck on server 1's managed node A are no longer there but are found in a different node (say node B) on a different server box.
As far as I understand the JMS, a message could be in a Pending state if MDP (in my case) does not automatically send ACKNOWLEGMENT back due to an issue in the Spring Defaultlisternercontainer before calling MDP's onMessage(). I am not sure as what happens to that status over time).
It is also observed that the stuck messages content is not much different than the other messages that are processed fine.
Any pointers/input is highly appreciated.
Thanks in advance for your valuable input and time.

Off the top of my head, I can only think of two reasons why a message might move from node to node:
(A) An application is dequeueing them and enquening them elsewhere.
(B) The application is using distributed queues, and the distributed queue has been configured to enable "queue forwarding". The forwarding feature automatically moves messages from distributed queue members that have no consumers to members that do have consumers. Queue forwarding is sometimes enabled as a work-around to better enable MDP support of WL distributed destinations, unlike WebLogic MDBs, MDPs have no container logic to ensure that all members of a distributed destination are serviced by a consumer under all circumstances...
Regards,
Tom

Recovering messages stuck in a dead channel queue

I,
I have a bunch a msg (ca. 30) that are stuck in a non working channel queue. I do not want to loose them but rather have them delivered normally using the other working channels.
How can I do that ?
I have found out how to remove message in a queue, but not how to extract them and redirect them so they are delivered. I hope they will not disappear as they are tried out every so often.
The channel (tcp_scan) was set up to analyze messages for spam/virus on another host according to the CONVERSION setup. Then this mailfilter host died. I stopped the redirection at the MTA, but some messages were already stucked in the channel queue.
SETUP DESCRIPTION
Before:
The CONVERSION setup redirected mail to the tcp_scan channel.
The tcp_scan channel redirected the messages to the mailfilter host where spamassassin and clamav would run.
The mailfilter host would send back the result on the MTA on a special port setup in dispatcher.cnf
The message is delivered locally on the MTA.
Now, the CONVERSION channer has been removed and the messages arrive without screening.
CONFIGURATION FILES
VERSION
imsimta version
Sun Java(tm) System Messaging Server 6.2-7.05 (built Sep 5 2006)
libimta.so 6.2-7.05 (built 12:18:44, Sep 5 2006)
SunOS igloo 5.10 Generic_118822-30 sun4u sparc SUNW,Sun-Fire-280R
FILE: mappgins
CONVERSIONS
in-chan=tcp_scan;out-chan=*;CONVERT No
in-chan=tcp_submit;out-chan=*;CONVERT Yes,Channel=tcp_scan
in-chan=tcp_auth;out-chan=*;CONVERT Yes,Channel=tcp_scan
in-chan=tcp_local;out-chan=*;CONVERT Yes,Channel=tcp_scan
FILE:ima.cnf
! tcp_scan
tcp_scan smtp mx daemon 192.33.219.42 \
port 2525 subdirs 20 noreverse dequeue_removeroute maxjobs 7 \
pool SMTP_POOL maytlsserver allowswitchchannel \
saslswitchchannel tcp_auth
tcp_scan-daemon
FILE:dispatcher.cnf
[SERVICE=SMTP_ROUTER]
PORT=3525
IMAGE=/opt/SUNWmsgsr/lib/tcp_smtp_server
LOGFILE=IMTA_LOG:tcp_smtp_server.log
STACKSIZE=2048000
PARAMETER=CHANNEL=tcp_scan
Thanks
Fran�ois

fafouli wrote:
I have found out how to remove message in a queue, but not how to extract them and redirect them so they are delivered. I hope they will not disappear as they are tried out every so often.How you get the messages to be 'redelivered is very-much a case-by-case basis. Once an email enters a queue it can be difficult to get the email redelivered in an automated fashion as there may be insufficient data to work out where the email needs to go.
For example if you have emails stuck in the ims-ms channel the envelope address is <uid>@ims-ms-daemon, getting this to be redelivered to say another store or another non-messaging server (the 'original' address the email come in as) may not be possible.
The channel (tcp_scan) was set up to analyze messages for spam/virus on another host according to the CONVERSION setup. Then this mailfilter host died. I stopped the redirection at the MTA, but some messages were already stucked in the channel queue.
CONVERSIONS
in-chan=tcp_scan;out-chan=*;CONVERT No
in-chan=tcp_submit;out-chan=*;CONVERT Yes,Channel=tcp_scan
in-chan=tcp_auth;out-chan=*;CONVERT Yes,Channel=tcp_scan
in-chan=tcp_local;out-chan=*;CONVERT Yes,Channel=tcp_scanI assume this is the before configuration otherwise the conversion hop is still in place as Jay mentioned.
FILE:ima.cnf
! tcp_scan
tcp_scan smtp mx daemon 192.33.219.42 \
port 2525 subdirs 20 noreverse dequeue_removeroute maxjobs 7 \
pool SMTP_POOL maytlsserver allowswitchchannel \
saslswitchchannel tcp_auth
tcp_scan-daemonAn alternative approach to what Jay suggested. If the conversion hop is indeed no-longer in place, you could try changing "mx daemon 192.33.219.42" to "nomx daemon 127.0.0.1" and uncomment the tcp_scan channel. This should then cause any emails in tcp_scan channel to be delivered back into messaging server (rather then the anti-virus/spam system) and then get delivered as-per-normal.
Regards,
Shane.

Message stucked at O/B queue in ECC

Similar Messages

Maybe you are looking for