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!
Charles

Hi 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

Similar Messages

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

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

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.

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

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

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

Idocs stuck in tRFC queue - why?

We had an issue where 2 Idocs looked like they where sent from our
logistics box to our HR box, but in reality, they were stuck in the tRFC
queue in our logistics box.
The idocs were created 2 days ago and were never processed. When I found
them in SM58, I executed them and they were sent and processed
successfully.
Why would those idocs get stuck in the tRFC queue? Shouldn't the queue
auto-process those idocs?
thanks,
robert.

Hi..
Normally this will happen when you Set the "Collect IDOCs" Option in the Partner profile Outbound Message type.
In that case these IDOCs will be dispatched only when the RSEOUT00 program runs in Batch or Explicitly.
If you set "Transfer Immediately" option in Partner profiles then they will be dispatched Immediately.
reward if Helpful.

FCC File-XI-IDOC: Pl confirm the validity of parameters I have specified

Hi,
I have the scenario File-XI-IDOC. I have almost completed the IR and ID config minus the FCC part.
Need to do the FCC for reading the file which will enable me to map it to IDOC structure.
I have the following TextFile structure ( Note: each field in the file is fixed length )
Header( 1 record)
Data_header (1 record)
|_ Data_Item (Multiple records)
Trailer
As expected each node has multiple fields in it like:
Header = Source, Destination, Date
Data_header = Company, Country
Data_item = Office1 address, postcode1,
Data_item = Office2 address, postcode2,
Data_item = Office3 address, postcode3,
Trailer = Checksum, Carriage_return_value
I have keyed in the following values into the various FCC parameters.
Appreciate if you could confirm if they are correct. (pl provide correct values, if needed)
Recordset_name: (should I put any value heer???)
Recordset Structure: Header,1,Data_header,1,Data_item,*,Trailer,1
Key field: (should I put any value heer???)
Header.fieldfixedlengths = 10,10,8
Header.endseparator = 1310   ( Header record ends with a carriage return value 13 followed by line feed character 10)
Header.fieldnames = Source, Destination, Date
Header.Keyfieldvalue = 1 (Should I put anything here??)
Header.keyfieldinstructure = u2018ignoreu2019
Data_Header.fieldfixedlengths = 4,4
Data_Header.endseparator = 1310   ( Data Header record ends with a carriage return value 13 followed by line feed character 10)
Data_Header.fieldnames = Company, Country
Data_Header.Keyfieldvalue = 2 (Should I put anything here??)
Data_Header.keyfieldinstructure = u2018ignoreu2019
Data_Item.fieldfixedlengths = 40,7
Data_Item.endseparator = 1310   ( Data Item record ends with a carriage return value 13 followed by line feed character 10)
Data_Item.fieldnames = Company address, postcode
Data_Item.Keyfieldvalue = 3 (Should I put anything here??)
Data_Item.keyfieldinstructure = u2018ignoreu2019
Trailer.fieldfixedlengths = 2,2,1
Trailer.endseparator = T   ( Trailer record ends with a character T)
Trailer.fieldnames = Checksum, Carriage_return_value, End_value
Trailer.Keyfieldvalue = 4 (Should I put anything here??)
Trailer.keyfieldinstructure = u2018ignoreu2019
Appreciate if you could confirm if they are correct.
Thanks and Regards
Shirin

Hi,
I am still confused with what do I do with the CR/LF character pair in my incoming file.
If possible could you let me know the value you would put in the fieldFixedlengths, endSeparator fields in all the recordsets.
As you can see all my data lines end with a value 1310, so do I not need to put it in FCC to let it know that data line is ending.
Appreciate your response.
Regards
Shirin
Header Section
Field                             Length          Notes
Source                             [10]
Destination                    [10]
Message ID                  [10]
Created Timestamp      [8]
CR/LF character pair        [4]           (Carriage return character (13) followed be line feed character (10) )
Data_Header Section
Field                             Length          Notes
Company                         [4]
Country                           [4]
CR/LF character pair         [4]           (Carriage return character (13) followed be line feed character (10) )
Data_item Section
Field                             Length          Notes
Address                          [40]
Postcode                          [7]
CR/LF character pair          [4]           (Carriage return character (13) followed be line feed character (10) )
So my file's Header and Data_header and Data_item will look like
STARSYSTEMSAP       1234567890200812121310
GB03GB 1310
101chamberlayne drive, Preston,UK,      E149PL 1310

Idoc stuck in trfc queue

Hi,
I have requirement where the idocs are sent to external (non sap) system, now when system is down or for some other reason the idocs gets queued up in trfc queue(SM58) , now when the system is up and running these idoc gets passed to the external system without any particular sequence, i.e. suppose for HR data there is 2 idoc for same employee and the IDOC1 should go before IDOC2 , then this not happens when the trfc queue(SM58) is cleared.
I wanted to know how to mantain this idoc Serialization so that the idoc go in sequence, i have gone through some idoc Serialization document but i think its useful when both system is receiveing system is also SAP.

duplicate post, locked.
Thomas

EOIO messages got held in the queue

hi,
In our scenario we are sending an IDOC from SAP whenever a material is newly created in SAP to a third party file share location.
Please note that i have to maintain EOIO(requirement)at the same time when ever we send an IDOC from SAP,the status is set to HOLD in XI(and we know that this message is because it's predecessor got stucked in the queue)
But when we check the queue in SMQ2 it looks fine(no entries there)even then if an IDOC is send from SAP the status goes to HOLD.what could be the reason for this ?
RGds,
Vasanth.

Hi Michael,
we are going as per the blog.evrything looks ok but i could not cancel the message(last step)and we are getting the following error
Unable to cancel 1 of 1 messages; update the status
(reason it says:<i>Predecessor not in final state</i>)
If we could able to cancel that message hope the problem would be solved.
RGds,
Vasanth.
Message was edited by: Vasanthakumar Balasubramani

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 processing in the queue for long time

Hello All,
We are executing a file to Idoc scenario. The mapping is very complex.
The file to be processed is of size 125kb size. Which generates around 450 Idocs.
The file is picked by the adapter engine in hardly a minute.
But I see the message taking 6 hours to process in the Queue.
(SMQ2)
Is there a way I can improve and speed up the Queue processing.

Hi,
>message taking 6 hours to process in the Queue.
It should not happen,
Check whether all the Queue are Registered.
/people/sap.india5/blog/2006/01/03/xi-asynchronous-message-processing-understanding-xi-queues-part-i
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/59e837d3-0201-0010-c096-dc1869733413
Regards
Agasthuri Doss

Idoc stuck on smq2

I have a scenario where sending idoc from SAP ECC to SAP PI without error, but to reach the SAP PI is not processed, in reviewing the TX SMQ2 the idoc gets stuck and I have to activate them manually to generate the XML, as I can investigate because automanticamnete not processed and remain in waiting to be done manually

Hi Leon,
You need to register and activate the queue by using T-Code SXMB_ADM.
Also check if ithe queue is unlocked.
By using the transaction SMQ2 you can reset the queue's status.
Set IS configuration parameter MONITOR QRFC_RESTART_ALLOWED to value 1.This will initiate processing of messages stuck in the queue
You can run RSQIWKEX to run periodically. It resets the queues automatically.
You have to go to SXMB_ADM. Then click manage Queues and you have to dergister all the queues. After doing this you need to go to SMQ2 and you have to actiavte the queues.
After all this try to re-register the queues in SXMB_ADM ..
Regards,
Rohit

Special character in File to IDoc

Hi,
am working on file to Idoc scenario.
The data is populated as expected in to the segments but when i see the idoc in the receiving system the special characters are replaced by #
For ex
how LII u201Cexceeds industry benchmarks and defeats stereotypesu201D
is cming as LII #exceeds industry benchmarks and defeats stereotypes#
Any suggestions to display the special characters.

In your File Sender channel you can set the File Encoding Scheme of your choice. We had a similar case where special characters were seen as # . Once we changed the Encoding scheme to ISO-8859-1 it worked fine.
Refer to the below link
http://help.sap.com/saphelp_nw04/helpdata/EN/e3/94007075cae04f930cc4c034e411e1/content.htm
-Mala

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

File to Idoc : Java Mapping

Hi Experts,
The scenario is file to idoc. In the file i'll be getting name,value pairs. For ex:
Structure is
MT
....Root(1..unbounded)
............Name
............Value
File contains:
Vishal....1
Raj.........2
RFC......10
Rahul.....20
Azhar....15 and so on..
I need to loop through the file. When Name="RFC", I need to make an RFC call with Value as it's input. RFC returns 4 values which will be used for mapping.
Then I need to continue looping through the file. On encountering a particular Name, I need to map corresponding Value to target field.
For this, I should have 2 mappings. One to read the file and the other for mapping. I've never used RFC and Java mapping, Can someone provide me a link or a solution for this?
Thanks,
Vishal

Hi,
You can do this using a UDF.
first let the source message contain first line and last line which you want to eliminate.
change the context of the Value to MT ..
start a for loop in UDF ignoring first & last line like
for(int i = 1; i< input.length() - 1; i++) // here i = 1 & not zero & input length is -1 so that first & last field eliminates
//carry on string operation to separate name & value on delimeter space
String name = input<i>.subString(0,.... to the indexOf space);
//similar for value also....
now you have name & value
check for name == 0052
if(name == 0052)
perform rfc lookup
else

File to IDOC stuck in the queue

Similar Messages

Maybe you are looking for