Stuck messages in Queue

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

Similar Messages

  • How to skip stuck message in queue folder.

    Hello,<o:p></o:p>
    I am using SMTP virtual server with office365. I frequently find out some of stuck or delayed messages after some messages have successfully delivered. I don't know why
    these messages are delayed or stuck. But I would just like to skip the stuck message, after these are tried to deliver for 10minutes.
    I have already changed some configurations in delivery tab that is located in properties of SMTP virtual server. I expected that the stuck message is expired, yet all of messages
    are expired in queue folder.
    Please, let me know how to configure that the stuck messages only skip.<o:p></o:p>
    Thank you,
    Park.

    Hi Park,
    Since this forum is for Server Manager issue on Windows Server, to solve the issue about office365, please go to this forum for more effective support:
    http://community.office365.com/en-us/f/default.aspx
    Thanks for your understanding.

  • Stuck Messages in Queue in SMQ2

    Hi,
    I have messages that are stuck in a specific queue seen in SMQ2. when I checked the status of the queue, it is RUNNING and the first message in the queue has a statusText 'Transaction Executing'.
    We have deregister - register, activate, unlock, lock the queues already but nothing happened.
    there are NO ERROR seen inside the queue.
    Already referred to these links:
    RECORDED FOR OUTBOUND PROCESS in SXMB_MONI
    Recorded for outbound processing
    Restarting "Recorded for outbound processing"
    Problem Recorded for Outbound Processing...
    XI :  How to Re-Process failed XI Messages Automatically
    thank you.

    Hi,
    did you check other Tcodes...like SLDCHECK,SXI_CACHE and ST22 whether everthing is working fine.
    else as suggested by Rudra, please to ABAP Stack restart.
    Regards,
    Mastan vali

  • Some Journaled Calendar Requests get stuck in Submission queue - 550 5.6.0 - storage error in content conversion

    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 SASIDHARAN

    H 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". 

  • Message stuck in inbound queue of r/3 for inbound proxy

    Hi Experts,
    The scenerio is Inbound Proxy.
    I m using standard prgram  rfbibl00  to post a document (FB01) in Inbound proxy. When the message is triggered from XI, it get stuck in inbound queue of R/3 ( SMQ2) giving the status text "Session     1: Special character for 'empty field' .
    Please help to resolve this issue.
    Thanks in advance.

    dear experts,
    did u get chance to look into this issue.
    Thanks in advance.

  • Unable to delete messages from queue.

    I have a journaling rule setup to send mail to a archive appliance. I have two messages in my queue that are From Address:<>  to my recipient (my archiver's email address). The journal rule works fine since it is working for all my users mail, but I have two messages stuck in my queue complaining that they could not be categorized and an event 9213 for MSExchangeTransport every 30 minutes. 
    "A non-expirable message with the internal message ID 7996 could not be categorized. This message may be a journal report or other system message. The message will remain in the queue until administrative action is taken to resolve the error. Other messages may also have encountered this error. To further diagnose the error, use the Queue Viewer or the Mail Flow Troubleshooter."
    I have tried via the GUI and Shell to remove these two messages. The GUI gives me an error:
    Microsoft Exchange Error
    Action 'Remove (with NDR)' could not be performed on object 'RE: Test to determine if email can be delivered & Received'.
    RE: Test to determine if email can be delivered & Received
    Failed
    Error:
    The requested operation can't be performed for the object with identity MyMailServerName\Submission\7999.
    OK
    The Shell will actually not report back an error but I still have those messages in the queue. The command to see info about the message was:
    Get-Message -IncludeRecipientInfo | Where { $_.Recipients -Like "*[email protected]*" } | Format-List
    Then I tried deleting the message using the "InternetMessageID" info I gathered from this.
    Remove-Message -Filter {InternetMessageID -eq "[email protected]"} -WithNDR $false
    This prompts me for a Yes, No, etc... responce (I thought I had it this time) and gave me no error, but the message still resides in queue.
    I am at a loss. Any help?

    Correct, two messages stuck in queue and cannot remove.
    Environment is a Windows 2003 R2 w/ SP2 64bit server, Exchange 2007 SP1 with all roles, AD/DNS is also Windows 2003 R2 w/ SP2 64bit.
    This just seemed to start happening a few days ago and just with these two particular messages. I have a archive appliance from ArcMail and a journal rule setup in Exchange to journal all mail to the ArcMail appliance. This has been working and continues to work except for these two messages. 
    [PS] C:\>Get-Message -IncludeRecipientInfo | Where { $_.Recipients -Like "*[email protected]*" } | Format-List
    Identity          : CO-MAIL1\Submission\7996
    Subject           : RE: Test to determine if email can be delivered & Received
    InternetMessageId : <[email protected]>
    FromAddress       : <>
    Status            : Retry
    Size              : 29638B
    MessageSourceName : Journaling
    SourceIP          : 255.255.255.255
    SCL               : 0
    DateReceived      : 9/18/2008 1:39:34 PM
    ExpirationTime    :
    LastError         : Categorization failed. The message will be deferred and ret
                        ried because it was marked for retry if rejected.
    RetryCount        : 0
    Queue             : CO-MAIL1\Submission
    Recipients        : {[email protected]}
    IsValid           : True
    ObjectState       : Unchanged
    Identity          : CO-MAIL1\Submission\7999
    Subject           : RE: Test to determine if email can be delivered & Received
    InternetMessageId : <[email protected]>
    FromAddress       : <>
    Status            : Retry
    Size              : 29623B
    MessageSourceName : Journaling
    SourceIP          : 255.255.255.255
    SCL               : 0
    DateReceived      : 9/18/2008 1:39:34 PM
    ExpirationTime    :
    LastError         : Categorization failed. The message will be deferred and ret
                        ried because it was marked for retry if rejected.
    RetryCount        : 0
    Queue             : CO-MAIL1\Submission
    Recipients        : {[email protected]}
    IsValid           : True
    ObjectState       : Unchanged
    Domain Controller Diagnosis
    Performing initial setup:
       Done gathering initial info.
    Doing initial required tests
       Testing server: co-site\CO-DNS1
          Starting test: Connectivity
             ......................... CO-DNS1 passed test Connectivity
    Doing primary tests
       Testing server: co-site\CO-DNS1
          Starting test: Replications
             ......................... CO-DNS1 passed test Replications
          Starting test: NCSecDesc
             ......................... CO-DNS1 passed test NCSecDesc
          Starting test: NetLogons
             ......................... CO-DNS1 passed test NetLogons
          Starting test: Advertising
             ......................... CO-DNS1 passed test Advertising
          Starting test: KnowsOfRoleHolders
             ......................... CO-DNS1 passed test KnowsOfRoleHolders
          Starting test: RidManager
             ......................... CO-DNS1 passed test RidManager
          Starting test: MachineAccount
             ......................... CO-DNS1 passed test MachineAccount
          Starting test: Services
             ......................... CO-DNS1 passed test Services
          Starting test: ObjectsReplicated
             ......................... CO-DNS1 passed test ObjectsReplicated
          Starting test: frssysvol
             ......................... CO-DNS1 passed test frssysvol
          Starting test: frsevent
             ......................... CO-DNS1 passed test frsevent
          Starting test: kccevent
             ......................... CO-DNS1 passed test kccevent
          Starting test: systemlog
             ......................... CO-DNS1 passed test systemlog
          Starting test: VerifyReferences
             ......................... CO-DNS1 passed test VerifyReferences
       Running partition tests on : ForestDnsZones
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
       Running partition tests on : DomainDnsZones
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
       Running partition tests on : Schema
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
       Running partition tests on : Configuration
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
       Running partition tests on : lcsd
          Starting test: CrossRefValidation
             ......................... lcsd passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... lcsd passed test CheckSDRefDom
       Running enterprise tests on : lcsd.local
          Starting test: Intersite
             ......................... lcsd.local passed test Intersite
          Starting test: FsmoCheck
             ......................... lcsd.local passed test FsmoCheck
    [PS] C:\>Remove-Message -filter {FromAddress -eq "<>"} -withNDR $false -debug -verbose
    VERBOSE: Remove-Message : Beginning processing.
    Confirm
    Are you sure you want to perform this action?
    Removing the messages that match filter "FromAddress -eq "<>"".
    Yes  Yes to All  No  [L] No to All  Suspend  [?] Help
    (default is "Y"):Y
    VERBOSE: Remove-Message : Ending processing.
    [PS] C:\>Remove-Message -Filter {InternetMessageID -eq "[email protected]"} -WithNDR $false -debug -verbose
    VERBOSE: Remove-Message : Beginning processing.
    Confirm
    Are you sure you want to perform this action?
    Removing the messages that match filter "InternetMessageID -eq
    "[email protected]"".
    Yes  Yes to All  No  [L] No to All  Suspend  [?] Help
    (default is "Y"):Y
    VERBOSE: Remove-Message : Ending processing.
    [PS] C:\>Remove-Message -filter {FromAddress -eq ""} -withNDR $false -debug -ver
    bose
    VERBOSE: Remove-Message : Beginning processing.
    Confirm
    Are you sure you want to perform this action?
    Removing the messages that match filter "FromAddress -eq """.
    Yes  Yes to All  No  [L] No to All  Suspend  [?] Help
    (default is "Y"):Y
    VERBOSE: Remove-Message : Ending processing.
    [PS] C:\>
    Tried several filter options and all had the same result. No events in the event viewer and did not remove the stuck messages.

  • MDB and "stuck" messages

    Hi,
    We're developing a MDB listening to a AQ/JMS database persistant queue, on a Oracle JMS provider.That MDB as to be bullet proof (no lost messages), and that's why we're using database persistance.So far everything is working fine, but we have one issue that cause some headackes.
    For what I know, the onMessage() method doesn't acknowledge to the provider until the method completes, without trowing an exception. In that case, the provider rollback so he can try to redeliver the message again. Since we have some important processing done within the onMessage() method, we were worried about what would happen if the MDB crash (java code crash, server crash, sledgehammer hit). I tryed to read that message via a java class I wrote, but I couldn't. (i guess the message is still waiting for the acknowledge)
    So to make it short, I placed a "thread.Sleep" in the middle of the onMessage() method, I deployed it on my application server, put a message in the queue, and I pressed the reset button of my machine. The result was that the message was still in the queue (that's nice since we didn't lost it), but never redelivered, and after some time (like 12h), the message was gone of the database and not delivered. (the message expiration was set to 0)
    So the big question would be: what happen to a JMS message if the MDB crash for any reason and what's the behavior of the JMS provider, and if there's anything we can do to redeliver that "stuck" message?
    I guess the provider keep the status of each message somewhere in the database (something that says to him that the message is in develery, waiting for acknowledge).
    Thanks

    Most likely this is some server configuration issue and not an actual programming problem (because as you say yourself, on another system it works). I can advise only two things.
    - dig through the weblogic documentation
    - take your question to the weblogic forum
    https://forums.oracle.com/forums/category.jspa?categoryID=193

  • Blocking messages in Queue

    Hi All,
    We have two different interfaces for different projects . If we get any error for first interface it will block
    all the messages in the Queue of other interfaces. I unlocked a week back  using SMQ2 but again the same problem today.
    Any idea to outcome of thise issue .
    Thanks....

    Hi,
    This is bound to happen, if messages are stuck in one queue then all other messages in sequence of the same queue will get blocked and unless you clear the queues, they won't be processed.
    You can use EOIO(Exactly once in order) service for the interface for which messages are failing.
    Here you have to mention the queue name for this particular interface, so that all the messages of it will take the same queue.
    And all other messages of other interface will take different queue and will  get processed.
    -Supriya.

  • Re-processing failed messages in queue automatically

    Hi,
    While executing messages via PI to external system, sometimes the messages stucked in inbound queue with status "SYSFAIL" with status text "Command to tRFC/qRFC: Execute LUW again" (communication problem). The only way to execute LUW again is via DEBUG mode (F8). After using F8 the message runs and the queue released until the next time.
    How can I execute those messages with F6 (Execute LUW) or by any scheduling program (preferability to scheduling program)?
    Regards,
    Gil

    Hi Gigi,
    As stated in one of the blog (/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically):
    For automatic qRfc failure recovery, Schedule the report RSQIWKEX to run periodically. This report enables automatically resets the queues.
    Also, refer the following threads for more information on this topic:
    Re-Process failed XI Messages Automatically
    /people/krishna.moorthyp/blog/2006/04/08/reconciliation-of-messages-in-bpm

  • 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
    Abhijit

    Hi 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,
    Wilson

    Are 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

Maybe you are looking for