Queues stuck in DB-Queue Monitor .
Hi,
I have B1if with some scenarios in my system, but i have a problem with Queue stuck.
Under DB-Queue Monitor, i have the stuck queues, Q.INB_IQ_INTQ_ASYN_QS.0010000000 > sap.B1SysSLDSync > message(<SLDModify sysid="0010000112" company="SBO_DEPOSITO_NILDO" task="delete" /> ).
I have checked and all IPO-Steps are active.
Any solution????
[]'s
Hi Priyanka,
To clear the no send status entry, go to R3AS, select the object say for BP (Bupa_main) press enter and then execute, then open R3AM1 enter object name as Bupa_main and select Running and done and execute.
Now you can open SMQ2 and click on each entry with nosend status and then click on activate queue in the top toolbar, this shld change the status to running and then click on refresh.
The following is the list of Queue extensions that are used in CRM, all the queues start with these extensions:
<b>Outbound queues</b>
CDB* Start queues for loads CRM -> CDB
CRM_SITE* Load queues for Mobile Clients
CSA* Send queues of CRM Server Applications
EXT* Start queues for loads CRM -> Ext.
R3AI/R* Start queues for loads from ERP Backend system
R3AU* Load queues CRM -> ERP Backend system
<b>Inbound queues</b>
CRI* Initial load queues CRM -> CDB
CRM_SITE* Load queues from Mobile Clients
R3A* Load queues ERP Backend -> CRM
CSA* Send inbound queues of CRM Server Applications
Hope this answers ur query.
Regards,
Amit
Message was edited by:
Amit Singh
Similar Messages
-
Java Proxy stuck in JPRRqst Queue
Hi,
I try to do Synchronous process between RFC to Java Proxy. it was wokrikg fine but suddenly Messages stuck in queue.
RFC sends a message after mapping. I looked sxmb_moni it looks like message delivered to Java Proxy but it didn't. after a while outbound service interface gives "no response" error because of time out. but when i look at http://*****:50000/mdt/Systatus proxy messages stuck in JPRRqst Queue
Queue Name Threads Assigned/Working
JPRRqst 11/11
My proxy didn't even start. Strange thing this process did work fine and when this error happens, I receive different data from data that come from RFC. example
RFC sends
MANDT 001
MATNR 3N5979
SERVICE_ID 16261
But i receive
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Z************ xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
<I_TPARTAV>
<MANDT>000</MANDT>
<MATNR>979</MATNR>
<SERVICE_ID>0000</SERVICE_ID>
Have you any ideas?try this - in RWB in msg monitoring at AE level see the msgs for this scenario......try to find first msg in error and cancel it...then see whether ur remaining msgs are getting processed or not........
-
Hi,
In scenarios where inbound queues are used (File IDOC -XI-SAP), when a send data error occurs the queues in XI are set to "SYSFAIL" (caused by the error) and i often have to delete the SYSFAIL messages manually to continue to process the next data.
Is there any way through which i can delete these messages which are of status=SYSFAIL (schedule some job)?
I assume that in my scenary all the error of this type can be cancelleed.
Thanks
AntonioAntonio,
From the blog,
<i>Often in asynchronous scenarios where inbound queues are used, the queues are set to SYSFAIL status and all the messages in the inbound queue are stuck (not processed). Depending on the status of XI processing queues, we can reset a queues status and trigger processing of messages.
To be able to initiate processing of messages stuck in the queue, make sure to set following IS configuration parameter
MONITOR QRFC_RESTART_ALLOWED to value 1
<b>For automatic qRfc failure recovery, schedule the report RSQIWKEX to run periodically. This report enables automatically resets the queues.</b>[\i]
Regards,
Bhavesh -
I am having an issue on hub transport servers running Exchange 2010 SP3 RU6.
Where some journaled meeting request related messages (acceptances, etc.) get stuck in the Submission queue.
The error is:
400 4.4.7 The server responded with: 550 5.6.0 M2MCVT.StorageError; storage error in content conversion. The failure was replaced by a retry response because the message was marked for retry if rejected.
I raised the issue with our mail archiving vendor and they indicated this was an Exchange Server problem which should have been fixed in Exchange 2010 SP3 RU3, however we are running SP3 RU6 and the issue continues to occur.
I realize that we could just delete the stuck messages from queue but has anyone run in to this before and know how to prevent it from happening?
Thank You.Hi Mike,
If you temporary disable\bypass third party Archiving , then what happens in the Queue.
Thanks , Prakash
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied. -
Message getting stuck in XBQO queue - Time limit exceeded
Hi All,
We have a BPM scenario in our project (on PI 7.0 SP18), where bundle of PEXR2002 Payment IDocs are received as a single flat file. This file is then consumed by the BPM, to split the message into multiple payments using Java Mapping.
However, when we get an IDoc file of size greater than 5 MB (more than 500 IDocs), the message gets stuck in XBQO queue and eventually giving a SYSFAIL with the message "Time limit exceeded". Could you please let us know if you have encountered a similar issue and are aware of a possible solution.
Any pointers to this will be really appreciated.
Thanks & Regards,
ROSIE SASIDHARANH Rosie,
1) Goto SXMB_ADM-> Integration Engine Configuration->Parameter EO_MSG_SIZE_LIMIT->possible values 0 - 2,097,151 (KB)
The parameter EO_MSG_SIZE_LIMIT enables serial processing of messages of a particular size. This applies for messages with the quality of service Exactly Once (EO). If the message is larger than the parameter value, the message is processed in a separate queue.
2) Goto SXMB_ADM-> Integration Engine Configuration->Parameter HTTP_TIMEOUT->possible values n Seconds, where n is a whole number.
The parameter Specifies the timeout for HTTP connections (time between two data packages at line level). This value overrides the system profile parameter icm/server_port_n (for example, icm/server_port_0 : PROT=HTTP, PORT=50044, TIMEOUT=900). If you do not set the parameter HTTP_TIMEOUT or if you set the parameter to 0, then the setting for the system profile parameter is used.
See SAP Note 335162 for sysfail issue....
Hope these will help u....
Regds,
Pinangshuk. -
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". -
Hi,
I have a scenario SAP ECC > PI > 3rd Party.
Messages are being send from SAP ECC to PI however the messages encountered an authorization error when sending to PI. During the fix, almost 1500 messages were stuck in the different queues in SAP ECC - SMQ2. the status of the other messages were in Green flag while the others are in Red flag.
Now the fix has been made, the messages that we are now transacting is still stuck in the queue.Why are the other messages stuck in queue? Shouldnt it proceed? Does the queue in SMQ2 have a threshold or limit in continuing the other messages even the first messages were in error?
thank you.Hi,
use TCODE--SMQR for registering and deregistering.
The queues which are avialbale in SMQR are the registerd and activated queues.
each queue has type and mode.
where type 'R' means registered and activated
Regards
Mastan -
HELP! Mail stuck in the queue.
Hey All,
We just noticed that none of us here recieved any mail today and that all of our messages incoming/outgoing have been stuck in the queue all day.
We seem to be able to view old messages with our mail clients as well as any folders. But any new messages that we send or recieve just go to the server and sit there.
It's quite puzzeling because we haven't changed anything on it, the server has just been quietly humming along for a while now.
However, this seems to have started happening after we restarted the box this morning because a web app we were building on it ended up in an infinite loop.
I tried re-starting the box, restarting the mail service, resending the queue and nothing, messages hit the queue and fail to be delivered to mailboxes.
Looking at my logs I saw this:
Nov 9 16:56:28 resserver imap[4733]: DBERROR: critical database situation
Nov 9 17:00:07 resserver imap[4833]: DBERROR: critical database situation
Nov 9 17:15:56 resserver reconstruct[5700]: DBERROR: critical database situation
Nov 9 17:16:02 resserver reconstruct[5726]: DBERROR: critical database situation
In the queue some messages say this at the end:
host 127.0.0.1[127.0.0.1] said: 421 4.3.2 Service shutting down, closing channel (in reply to end of DATA command
Looking in my resources and in other places on the forums I've tried the following so far in hopes to narrow down and fix the problem:
- rebuilt with mailbfr (as per petrobytes suggestion with someone else)
- turned on and off content filtering
- confirmed that the machine has the same IP
- confirmed that it resolves forward and backward to it's hostname/IP
I can post any conf files you need, I'm desperate to get this fixed! Any help or insight anyone could provide would be well appreciated!
eMac, iBook, iMac, xServe, PowerBook Mac OS X (10.4.3)I'm noticing some interesting stuff happening in the logs can someone make sense of this?
solutionim.com /usr/bin/amavisd[7872]: (07872-01) Requesting process rundown after fatal error
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7872]: (07872-01) SMTP shutdown: Error writing a SMTP response to the socket: Bad file descriptor at (eval 36) line 760.\n
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7873]: (07873-01) TROUBLE in check_mail: mime_decode-1 FAILED: parsing file(1) results - missing last 2 results at (eval 41) line 150.
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7873]: (07873-01) PRESERVING EVIDENCE in /var/amavis/amavis-20061109T184715-07873
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7873]: (07873-01) TIMING [total 350 ms] - SMTP EHLO: 23 (7%), SMTP pre-MAIL: 2 (1%), mkdir tempdir: 1 (0%), create email.txt: 2 (0%), SMTP pre-DATA-flush: 9 (3%), SMTP DATA: 9 (3%), body_hash: 3 (1%), mkdir parts: 3 (1%), mime_decode: 72 (21%), rundown: 226 (65%)
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7873]: (07873-01) TROUBLE in process_request: Error writing a SMTP response to the socket: Broken pipe at (eval 36) line 760, <GEN4> line 568.
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7873]: (07873-01) Requesting process rundown after fatal error
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7873]: (07873-01) SMTP shutdown: Error writing a SMTP response to the socket: Bad file descriptor at (eval 36) line 760.\n
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) ESMTP::10024 /var/amavis/amavis-20061109T184715-07876: <[email protected]> -> <[email protected]> Received: SIZE=50687 from resolutionim.com ([127.0.0.1]) by localhost (resserver.resolutionim.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07876-01 for <[email protected]>; Thu, 9 Nov 2006 18:47:15 -0500 (EST)
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) Checking: [216.46.146.115] <[email protected]> -> <[email protected]>
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) p004 1 Content-Type: multipart/mixed
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) p005 1/1 Content-Type: multipart/alternative
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) p001 1/1/1 Content-Type: text/plain, size: 259 B, name:
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) p002 1/1/2 Content-Type: text/html, size: 2227 B, name:
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) p003 1/2 Content-Type: application/vnd.ms-excel, size: 33280 B, name: Emploment Application.xls
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7879]: (07876-01) run_command: child process [7879]: Can't close main::stdin: Bad file descriptor at /usr/bin/amavisd line 1589.\n
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7879]: (07876-01) SMTP shutdown: tempdir is being removed: /var/amavis/amavis-20061109T184715-07876
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) TROUBLE in check_mail: mime_decode-1 FAILED: parsing file(1) results - missing last 3 results at (eval 41) line 150.
Nov 9 18:47:15 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) PRESERVING EVIDENCE in /var/amavis/amavis-20061109T184715-07876
Nov 9 18:47:16 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) TIMING [total 366 ms] - SMTP EHLO: 24 (7%), SMTP pre-MAIL: 3 (1%), mkdir tempdir: 2 (0%), create email.txt: 2 (1%), SMTP pre-DATA-flush: 25 (7%), SMTP DATA: 31 (8%), body_hash: 3 (1%), mkdir parts: 3 (1%), mime_decode: 95 (26%), rundown: 178 (49%)
Nov 9 18:47:16 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) TROUBLE in process_request: Error writing a SMTP response to the socket: Broken pipe at (eval 36) line 760, <GEN4> line 771.
Nov 9 18:47:16 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) Requesting process rundown after fatal error
Nov 9 18:47:16 resserver.resolutionim.com /usr/bin/amavisd[7876]: (07876-01) SMTP shutdown: Error writing a SMTP response to the socket: Bad file descriptor at (eval 36) line 760.\n
Nov 9 18:48:33 resserver.resolutionim.com /usr/bin/amavisd[7759]: Net::Server: 2006/11/09-18:48:33 Server closing!
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: starting. /usr/bin/amavisd at resserver.resolutionim.com amavisd-new-2.2.0 (20041102), Unicode aware
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: user=, EUID: 0 (0); group=, EGID: 0 0 (0 0)
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Perl version 5.008006
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Net::Server: 2006/11/09-18:48:36 Amavis (type Net::Server::PreForkSimple) starting! pid(7927)
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Net::Server: Binding to UNIX socket file /var/amavis/amavisd.sock using SOCK_STREAM
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Net::Server: Binding to TCP port 10024 on host 127.0.0.1
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Net::Server: Setting gid to "82 82"
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Net::Server: Setting uid to "82"
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Amavis::Conf 2.033
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Archive::Tar 1.22
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Archive::Zip 1.14
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Compress::Zlib 1.33
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Convert::TNEF 0.17
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Convert::UUlib 1.03
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module DB_File 1.810
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module MIME::Entity 5.416
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module MIME::Parser 5.416
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module MIME::Tools 5.416
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Mail::Header 1.65
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Mail::Internet 1.65
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Mail::SpamAssassin 3.001005
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Net::Cmd 2.26
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Net::DNS 0.58
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Net::SMTP 2.29
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Net::Server 0.94
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Time::HiRes 1.65
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Module Unix::Syslog 0.99
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Amavis::DB code NOT loaded
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Amavis::Cache code NOT loaded
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Lookup::SQL code NOT loaded
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Lookup::LDAP code NOT loaded
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: AMCL-in protocol code loaded
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: SMTP-in protocol code loaded
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: ANTI-VIRUS code loaded
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: ANTI-SPAM code loaded
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Unpackers code loaded
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Found $file at /usr/bin/file
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $arc, not using it
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Found $gzip at /usr/bin/gzip
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Found $bzip2 at /usr/bin/bzip2
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $lzop, not using it
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $lha, not using it
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $unarj, not using it
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Found $uncompress at /usr/bin/uncompress
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $unfreeze, not using it
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $unrar, not using it
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $zoo, not using it
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Found $cpio at /usr/bin/cpio
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $ar, not using it
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $rpm2cpio, not using it
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $cabextract, not using it
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: No $dspam, not using it
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: Found secondary av scanner Clam Antivirus - clamscan at /usr/bin/clamscan
Nov 9 18:48:36 resserver.resolutionim.com /usr/bin/amavisd[7927]: SpamControl: initializing Mail::SpamAssassin
Nov 9 18:48:44 resserver.resolutionim.com /usr/bin/amavisd[7927]: SpamControl: done
SMTP response to the socket: Broken pipe at (eval 36) line 760, <GEN4> line 350.
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9584]: (09584-01) Requesting process rundown after fatal error
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9584]: (09584-01) SMTP shutdown: Error writing a SMTP response to the socket: Bad file descriptor at (eval 36) line 760.\n
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) ESMTP::10024 /var/amavis/amavis-20061109T194144-09586: <[email protected]> -> <[email protected]>,<[email protected]> Received: SIZE=236428 from resolutionim.com ([127.0.0.1]) by localhost (resserver.resolutionim.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09586-01; Thu, 9 Nov 2006 19:41:44 -0500 (EST)
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) Checking: [192.168.1.121] <[email protected]> -> <[email protected]>,<[email protected]>
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) ESMTP::10024 /var/amavis/amavis-20061109T194144-09587: <[email protected]> -> <[email protected]> Received: SIZE=2799147 from resolutionim.com ([127.0.0.1]) by localhost (resserver.resolutionim.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09587-01 for <[email protected]>; Thu, 9 Nov 2006 19:41:44 -0500 (EST)
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p008 1 Content-Type: multipart/alternative
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p001 1/1 Content-Type: text/plain, size: 1103 B, name:
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p009 1/2 Content-Type: multipart/mixed
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p002 1/2/1 Content-Type: text/html, size: 4971 B, name:
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p003 1/2/2 Content-Type: application/vnd.ms-excel, size: 16384 B, name: Feed Locations.xls
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p004 1/2/3 Content-Type: application/octet-stream, size: 15355 B, name: Example of Feed Locations.pdf
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p005 1/2/4 Content-Type: image/jpeg, size: 68882 B, name: zurlftoct06.JPG
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p006 1/2/5 Content-Type: image/jpeg, size: 65599 B, name: extrrtlondsoct06.JPG
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) p007 1/2/6 Content-Type: text/html, size: 184 B, name:
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9588]: (09586-01) run_command: child process [9588]: Can't close main::stdin: Bad file descriptor at /usr/bin/amavisd line 1589.\n
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9588]: (09586-01) SMTP shutdown: tempdir is being removed: /var/amavis/amavis-20061109T194144-09586
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) TROUBLE in check_mail: mime_decode-1 FAILED: parsing file(1) results - missing last 7 results at (eval 41) line 150.
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) PRESERVING EVIDENCE in /var/amavis/amavis-20061109T194144-09586
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) TIMING [total 435 ms] - SMTP EHLO: 22 (5%), SMTP pre-MAIL: 3 (1%), mkdir tempdir: 1 (0%), create email.txt: 2 (0%), SMTP pre-DATA-flush: 10 (2%), SMTP DATA: 45 (10%), body_hash: 6 (1%), mkdir parts: 3 (1%), mime_decode: 158 (36%), rundown: 185 (42%)
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) TROUBLE in process_request: Error writing a SMTP response to the socket: Broken pipe at (eval 36) line 760, <GEN4> line 3144.
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) Requesting process rundown after fatal error
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9586]: (09586-01) SMTP shutdown: Error writing a SMTP response to the socket: Bad file descriptor at (eval 36) line 760.\n
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) ESMTP::10024 /var/amavis/amavis-20061109T194144-09589: <[email protected]> -> <[email protected]> Received: SIZE=2244 from resolutionim.com ([127.0.0.1]) by localhost (resserver.resolutionim.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09589-01 for <[email protected]>; Thu, 9 Nov 2006 19:41:44 -0500 (EST)
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) Checking: [65.54.246.141] <[email protected]> -> <[email protected]>
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) p001 1 Content-Type: text/plain, size: 1084 B, name:
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9590]: (09589-01) run_command: child process [9590]: Can't close main::stdin: Bad file descriptor at /usr/bin/amavisd line 1589.\n
Nov 9 19:41:44 resserver.resolutionim.com /usr/bin/amavisd[9590]: (09589-01) SMTP shutdown: tempdir is being removed: /var/amavis/amavis-20061109T194144-09589
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) TROUBLE in check_mail: mime_decode-1 FAILED: parsing file(1) results - missing last 1 results at (eval 41) line 150.
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) PRESERVING EVIDENCE in /var/amavis/amavis-20061109T194144-09589
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) TIMING [total 240 ms] - SMTP EHLO: 19 (8%), SMTP pre-MAIL: 2 (1%), mkdir tempdir: 1 (1%), create email.txt: 2 (1%), SMTP pre-DATA-flush: 8 (3%), SMTP DATA: 2 (1%), body_hash: 2 (1%), mkdir parts: 3 (1%), mime_decode: 36 (15%), rundown: 165 (69%)
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) TROUBLE in process_request: Error writing a SMTP response to the socket: Broken pipe at (eval 36) line 760, <GEN4> line 67.
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) Requesting process rundown after fatal error
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9589]: (09589-01) SMTP shutdown: Error writing a SMTP response to the socket: Bad file descriptor at (eval 36) line 760.\n
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9591]: (09591-01) ESMTP::10024 /var/amavis/amavis-20061109T194145-09591: <[email protected]> -> <[email protected]> Received: SIZE=2799145 from resolutionim.com ([127.0.0.1]) by localhost (resserver.resolutionim.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09591-01 for <[email protected]>; Thu, 9 Nov 2006 19:41:45 -0500 (EST)
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) Checking: [65.54.246.171] <[email protected]> -> <[email protected]>
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9591]: (09591-01) Checking: [65.54.246.173] <[email protected]> -> <[email protected]>
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) p003 1 Content-Type: multipart/mixed
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) p001 1/1 Content-Type: text/html, size: 6064 B, name:
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) p002 1/2 Content-Type: video/x-ms-wmv, size: 2025860 B, name: JBSklip.wmv
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9592]: (09587-01) run_command: child process [9592]: Can't close main::stdin: Bad file descriptor at /usr/bin/amavisd line 1589.\n
Nov 9 19:41:45 resserver.resolutionim.com /usr/bin/amavisd[9592]: (09587-01) SMTP shutdown: tempdir is being removed: /var/amavis/amavis-20061109T194144-09587
Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) TROUBLE in check_mail: mime_decode-1 FAILED: parsing file(1) results - missing last 2 results at (eval 41) line 150.
Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) PRESERVING EVIDENCE in /var/amavis/amavis-20061109T194144-09587
Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-01) TIMING [total 1950 ms] - SMTP EHLO: 22 (1%), SMTP pre-MAIL: 4 (0%), mkdir tempdir: 1 (0%), create email.txt: 2 (0%), SMTP pre-DATA-flush: 9 (0%), SMTP DATA: 868 (44%), body_hash: 34 (2%), mkdir parts: 3 (0%), mime_decode: 610 (31%), rundown: 397 (20%)
Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-02) ESMTP::10024 /var/amavis/amavis-20061109T194146-09587: <[email protected]> -> <[email protected]> Received: SIZE=14124 from resolutionim.com ([127.0.0.1]) by localhost (resserver.resolutionim.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09587-02 for <[email protected]>; Thu, 9 Nov 2006 19:41:46 -0500 (EST)
Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-02) Checking: [64.233.166.181] <[email protected]> -> <[email protected]>
Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-02) p003 1 Content-Type: multipart/alternative
Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-02) p001 1/1 Content-Type: text/plain, size: 2089 B, name:
Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9587]: (09587-02) p002 1/2 Content-Type: text/html, size: 9454 B, name:
Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9593]: (09587-02) run_command: child process [9593]: Can't close main::stdin: Bad file descriptor at /usr/bin/amavisd line 1589.\n
Nov 9 19:41:46 resserver.resolutionim.com /usr/bin/amavisd[9593]: (09587-02) SMTP shutdown: tempdir is being removed: /var/amavis/amavis-20061109T194146-09587 -
545 mb file stuck in inbound queue
Hi
we are sending article master data from IS Retail to ftp server as flat file.
data size is around 545 mb...it got stuck in inbound queue(smq2) ..
error is : " Internally required memory is not available".
XI server config : RAM - 16 gb.
How to process such big file.
what are the hardware configuration needed ?
Regards
AbhijitHi Michal
Thanks for your response
This activity is done in PRD server.
An idoc with 545 mb data is triggred from SAP.
But it got stuck in inbound queue.
I came across a thread ..
Re: Processing large XML messages (>100Mb) in PI 7.1
According to this thread we need to maintain a parameter
icm/HTTP/max_request_size_KB has default value of 102400 & maximum it can accept is 2097152
Please suggest on this...do we need to maintain this parameter ?
Regards
Abhijit -
Exchange 2010 inbound email (external/internal) randomly stuck in delivery queue
Dear all,
We got a problem email is not deliver to mailbox normal.
For example. I send a email to recipient A,B and C in same internal email.
The result is A can receive email normally, but B and C email is stuck in delivery queue.
We need to re-start the CAS transport service to release the email from delivery queue.
Any idea for this kind of email deliver issue?
Exchange server environment:
1. Two CAS/HT server in NLB mode (Exchange std. ver.)
2 Two Mailbox server in DAG mode (Exchange Ent. ver.)
We got this issue around 12 months on production migrate from 2000 to 2007 to 2010.
Felix.hi,
What's the last error in the queue viewer? Do you have some error code?
You can use message tracking log to find more information about your issue.
If you create 3 new users and send a test mail to they, can they always receive the mail. May be your user account have some problem.
we need more information about your issue. Always is the stationary users or it is randomly?,The frequency of occurrence and so on.
hope can help you
thanks,
CastinLu
TechNet Community Support -
UCCX 8.0(2) - As identify that the call is stuck in the queue
Hi Guys,
My Customer complain that there are any Agent Ready, but, any calls are statying stuck in the queue. I read the documentation about the Cisco Site and the forum below, but, not is clear for me.
http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_8_0/configuration/guide/uccx801ag.pdf
https://supportforums.cisco.com/message/3070648#3070648
I would You like understand as identify that the calls really is stuck in the queue? Anybody explain for me
Thanks a lot,
WilsonAre ALL calls stuck in queue and never reaching an Agent?
Or is Supervisor Desktop just showing 1 or 2 calls "stuck" in queue, but most regular calls reach an agent?
Also what specific version are you running? There were some bugs in early 8.0(2) releases about calls showing in queue that weren't really there. If however your problem is real callers not reaching agents, it probably sounds like a skill or resource group problem.
Tom -
How do you find print center in iOS7 to check if a page is stuck in the queue?
My iPads had been printing fine up until today. I had a glitch with my Air Print printer. It has been resolved and two out of my three iPads can't find the printer now. I've looked around on the internet and remembered in iOS 6 the ability to find Print Center was easy. But how do I find it in iOS 7 when my iPad can't find the Air Printer in the first place? I want to check to see if a job is stuck in the queue and that is causing the error message.
This article says it better then I can.
http://support.apple.com/kb/ht4356
From the article.
Viewing the Print Summary
You can view the Print Summary by double-tapping the Home button and swiping to the right to reveal Printer Center. Then tap Print Center.
Note: Print Center is available only while printing is in progress. -
File to IDOC stuck in the queue
Hi Expert,
I have a file to IDOC scenario. I checked in SXMB_MONI, I can see the file coming in. But it just stuck in the queue and won't send out to SAP system. When I checked the SMQ2, it tells me the status is "SYSFAIL'. I have checked my RFC, port, logical systems, profile etc. Just don't know where is wrong. Can somebody tell me what else I need to check? Thank you very much!
CharlesHi Charles
Check SMQ2 and double click on the queue with sysfail status.
It will show you a new screen with a more detailed error description.
Regards,
Giuseppe -
Queue Stucked - Exactly Once Async Abap Proxy
Hi Guys
I have several JMS->Xi->Abap Proxy scenarios in my production environment, the Abap Proxies servers are in a SAP IS-OIL 4.72 with a SAP WEBAS 6.20 and the XI is the XI 3.0.
Some of the Abap Proxies calls are asynchronous, and when one of the abap proxies has an sysfail error (for example), it stuck the entire queue, and this is causing some problems, for the other calls (interfaces) that are not being processed until the "bad" abap proxy is "solved".
I know that we can schedule a job that reprocess the call but imagine that the problem is still not solved, I still have the other calls waiting, ie, I am putting in jeopardy some interfaces because of one error.
It seems that this queue management happens because SAP IS-OIL is treating all asynchronous AbapProxy calls as EOIO calls.
<b>1. Is my previous assumption correct???</b>
<b>2. How can I invoke from SAP XI3.0 an asynchronous Abap Proxy just with EO quality of service???</b>
<b>3. How can I setup the CCMS to alert when a queue is stucked (please be aware that I have a ERP SAP has a SAP WEBAS 6.20)???</b>
Take Care
PCHi Moorthy
> You are calling Proxy from XI right ?
Yes
> What is the source system ?
The source system is a 3rd party app that sends an XML message via JMS to XI, XI then calls the abap proxy that is in our SAP ISOIL.
> You can restrict the quality of service in the
> Outbound Interface..i.e message coming into XI.
>
Are you saying that has to be the 3rd party that has to say to Xi that the async call that XI will have to do to SAP ISOIL has to be EO??? How can this be done?? Is in the Message Interfaces configuration - Integration Repository???
Remember that I'm having queue problems in SAP ISOIL, where the abap proxies are processed !!!
> Here is the link for CCMS -
> http://help.sap.com/saphelp_nw04/helpdata/en/e5/5d1741
> b393f26fe10000000a1550b0/frameset.htm
> https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/
> 2894
> https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/
> 2895
> https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/
> 2777
>
Thanks a lot for the links, it seems that is good head start.
However I'm concerned that because my SAP ISOIL has the SAP WEBAS 6.2 (old Integration Engine), the CCMS features that are explained in the links will not work in the old version. Remember that I've probably have to configure the CCMS in XI3.0 (my integration platform) and SAP IS-OIL my main system, where all abap proxys are run and called, where IDOCS are sent and received, ie, is the point of origin and final point of all my integrations...
That's why I'm so concerned about the stopped queues in SAP ISOIL, I really need full availability in this system (queues), I am talking around 10.000 messages being sent and received... and in the near future will be around 100.000 messages for sure...
> Regards,
> Moorthy
Take Care
PC -
SMQ2 - Found a queue with name "*" and all other queues stuck in STOP state
Hi all,
We have a problem on the ECC side, on outbound asynchronous proxies. Sometimes a new queue appears on SMQ2 there with name "", and with status "STOP". At this time, all other queues stuck with STOP status... the only way of resetting all those queues to RUNNING state again is to delete the queue named as ""...
Some of you has any idea how this queue "*" appears there and stop all other queues?
thanks
robertiHi Ravi,
Is not only about one queue stopped... the problem is this queue named ""... with status STOP, all other queues stops too with it. The only way to make things work again is to delete the queue named as ""... the problem is to discover what or who is creating this stupid "*" queue. I think that this is a procedural error on datacenter, but they are saying is not the case... I'm investigating, but if someone else has any idea about I would appreciate
thanks!
roberti
Maybe you are looking for
-
Removing default folders in users home directories
My users have their home directories at /Users/<username>. I also created some directories there for users' websites and other things. All users have only access by ftp (mail, webmail, web service, etc.), but it is never intended to use AFP or other
-
File Transfer to Mini from Imac G3 (no firewire!)- Set Up
Reading the instructions for setting up my new mini, it says to use a firewire connection to move files to the mini using the Set Up assistant. The G3 Imac (slot loading) does not have a firewire port (that I know of). Will the Set Up Assistant work
-
Simplest way to display a title or caption at the beginning of each scene?
I am editing a video to make an instructional dvd covering 23 separate lessons. Without some kind of text in the first few seconds of each scene, there is no way for the viewer to quickly and efficiently distinguish one scene from another as they jum
-
WebRFC - clearing cache after making changes in SAP
I'm finding that as I make changes to my Functional Modules in SAP, and then try to test them from Personas, I can not pick up the new version until I log right out of NWBC and the log back in again .... there has to be a faster way .... right? Any t
-
Which details to use while renewing subscription?
Hi, I have a Subscription that needs to be renewed. Last time I bank deposit ZAR 117.04 in the month of April for 3 months. How should I make the payment now? The instructions clearly says that the payment reference number can only be used once. Curr