DB_ACCESS_ERROR in the pipeline Message Branch

Hi, all.
In the IDoc -> XI -> File Scenario, sometimes(twice in this week) DB_ACCESS_ERROR occurs and the corresponding message shows System Error - Manual Restart Possible.
The error message in SXMB_MONI shows like the following and the trace shows similar error message.
- <!--  Message Branch According to Receiver List -->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
  <SAP:Category>XIServer</SAP:Category>
  <SAP:Code area="INTERNAL">DB_ACCESS_ERROR</SAP:Code>
  <SAP:P1>SXMSQEUE_RCV</SAP:P1>
  <SAP:P2>INSERT</SAP:P2>
  <SAP:P3 />
  <SAP:P4 />
  <SAP:AdditionalText />
  <SAP:ApplicationFaultMessage namespace="" />
  <SAP:Stack>Error accessing table SXMSQEUE_RCV method INSERT</SAP:Stack>
  <SAP:Retry>M</SAP:Retry>
  </SAP:Error> 
When we rerun the message by using SXMB_MONI - Restart button, the message is executed without any problem. And our Database(SQL server) shows no error at all and XI system doesn't show any error.
Is there anyone who bumped into this trouble? Please give me some advice.
Best Regards.

This problem was solved by applying the following note.
Note 871891 - DB_ACCESS_ERROR
Best Regards.

Similar Messages

  • Is there any tool monitoring messages in the pipeline?

    I wonder whether there is a tool which can tell the time each queue spends in each step of the pipeline?
    e.g. how much time a queue spent on client determination, on xml conversion, ...
    Thanks!

    I wonder whether there is a tool which can tell the time each queue spends in each step of the pipeline?
    Pipeline step means the Receiver Determination, Interface Determination etc.....so you can find this time in SXMB_MONI itself.
    SXMB_MONI --> Open Message Processing entry --> Performance Header --> Under Performance Header --> SAP:Timestamp --> For every step you will have the respective timestamp......I think the value after decimal indicates miliseconds (not sure on this part)
    Regards,
    Abhishek.

  • Why do I get the error message for video chat only with a select few?  :(

    I've been trying for weeks trying to get video chat going to a few people with my invitation for video chat timing out and giving me the error message. At first I thought it may be the other people's systems, but they told me I was the only one in their list that this happens. With a few people it works just fine; is it my setup? I have an Airport Base Station connected to the DSL modem and running WIFi in the house and a Power Mac G5 with ethernet going to the Base Station.
    Please give me an heads up what might be the issue. Thanks in advance!!!
    Here's the error message I've clicked on to send to Apple with zero feedback:
    Date/Time: 2010-02-10 16:32:50.582 -0800
    OS Version: 10.5.8 (Build 9L31a)
    Report Version: 4
    iChat Connection Log:
    2010-02-10 16:32:11 -0800: AVChat started with ID 3929692955.
    2010-02-10 16:32:11 -0800: pushlife1: State change from AVChatNoState to AVChatStateWaiting.
    2010-02-10 16:32:12 -0800: 0x7550e90: State change from AVChatNoState to AVChatStateInvited.
    2010-02-10 16:32:22 -0800: 0x7550e90: State change from AVChatStateInvited to AVChatStateConnecting.
    2010-02-10 16:32:22 -0800: pushlife1: State change from AVChatStateWaiting to AVChatStateConnecting.
    2010-02-10 16:32:44 -0800: 0x7550e90: State change from AVChatStateConnecting to AVChatStateEnded.
    2010-02-10 16:32:44 -0800: 0x7550e90: Error -8 (Did not receive a response from 0x7550e90.)
    2010-02-10 16:32:44 -0800: pushlife1: State change from AVChatStateConnecting to AVChatStateEnded.
    2010-02-10 16:32:44 -0800: pushlife1: Error -8 (Did not receive a response from 0x7550e90.)
    Video Conference Error Report:
    18.654670 @SIP/SIP.c:2719 type=4 (900A0015/0)
    [SIPConnectIPPort failed]
    20.656764 @SIP/SIP.c:2719 type=4 (900A0015/0)
    [SIPConnectIPPort failed]
    22.659005 @SIP/SIP.c:2719 type=4 (900A0015/0)
    [SIPConnectIPPort failed]
    Video Conference Support Report:
    0.445346 @Video Conference/VCInitiateConference.m:1584 type=2 (00000000/0)
    [Connection Data for call id: 1 returns 1
    10.629729 @Video Conference/VCInitiateConference.m:1599 type=2 (00000000/0)
    [Prepare Connection With Remote Data - remote VCConnectionData: 1, local VCConnectionData: 1
    10.652610 @Video Conference/VCInitiateConference.m:1703 type=2 (00000000/0)
    [Initiate Conference To User: u0 with Remote VCConnectionData: 1 with Local Connection Data: 1 conferenceSettings: 1]
    16.653967 @SIP/Transport.c:2362 type=1 (00000000/0)
    [INVITE sip:user@rip:16402 SIP/2.0
    Via: SIP/2.0/UDP sip:59842;branch=z9hG4bK42631a8124217001
    Max-Forwards: 70
    To: "u0" <sip:user@rip:16402>
    From: "0" <sip:user@lip:16402>;tag=173998958
    Call-ID: eefb7f0e-16a4-11df-9457-bdecd7624012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@sip:59842>;isfocus
    User-Agent: Viceroy 1.3
    Content-Type: application/sdp
    Content-Length: 737
    v=0
    o=lukegreenfield 0 0 IN IP4 sip
    s=0
    c=IN IP4 sip
    b=AS:2147483647
    t=0 0
    a=hwi:288:2:1800
    a=iChatEncryption:NO
    a=bandwidthDetection:YES
    m=audio 59842 RTP/AVP 110 121 12 3 0
    a=rtcp:59842
    a=rtpmap:121 speex/16000
    a=rtpmap:122 speex/8000
    a=rtpmap:113 X-AAC_LD/44100
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpmap:3 GSM/8000
    a=rtpmap:0 PCMU/8000
    a=rtpID:3197311419
    m=video 59842 RTP/AVP 123 126 34
    a=rtcp:59842
    a=rtpmap:123 H264/90000
    a=rtpmap:126 X-H264/90000
    a=rtpmap:34 H263/90000
    a=fmtp:34 imagesize 1 rules 30:352:288
    a=framerate:30
    a=RTCP:AUDIO 59842 VIDEO 59842
    a=fmtp:126 imagesize 0 rules 30:320:240:320:240:30
    a=fmtp:123 imagesize 0 rules 30:320:240:320:240:30
    a=rtpID:4249151525
    17.154608 @SIP/Transport.c:2362 type=1 (00000000/0)
    [INVITE sip:user@rip:16402 SIP/2.0
    Via: SIP/2.0/UDP sip:59842;branch=z9hG4bK42631a8124217001
    Max-Forwards: 70
    To: "u0" <sip:user@rip:16402>
    From: "0" <sip:user@lip:16402>;tag=173998958
    Call-ID: eefb7f0e-16a4-11df-9457-bdecd7624012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@sip:59842>;isfocus
    User-Agent: Viceroy 1.3
    Content-Type: application/sdp
    Content-Length: 737
    v=0
    o=lukegreenfield 0 0 IN IP4 sip
    s=0
    c=IN IP4 sip
    b=AS:2147483647
    t=0 0
    a=hwi:288:2:1800
    a=iChatEncryption:NO
    a=bandwidthDetection:YES
    m=audio 59842 RTP/AVP 110 121 12 3 0
    a=rtcp:59842
    a=rtpmap:121 speex/16000
    a=rtpmap:122 speex/8000
    a=rtpmap:113 X-AAC_LD/44100
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpmap:3 GSM/8000
    a=rtpmap:0 PCMU/8000
    a=rtpID:3197311419
    m=video 59842 RTP/AVP 123 126 34
    a=rtcp:59842
    a=rtpmap:123 H264/90000
    a=rtpmap:126 X-H264/90000
    a=rtpmap:34 H263/90000
    a=fmtp:34 imagesize 1 rules 30:352:288
    a=framerate:30
    a=RTCP:AUDIO 59842 VIDEO 59842
    a=fmtp:126 imagesize 0 rules 30:320:240:320:240:30
    a=fmtp:123 imagesize 0 rules 30:320:240:320:240:30
    a=rtpID:4249151525
    18.155291 @SIP/Transport.c:2362 type=1 (00000000/0)
    [INVITE sip:user@rip:16402 SIP/2.0
    Via: SIP/2.0/UDP sip:59842;branch=z9hG4bK42631a8124217001
    Max-Forwards: 70
    To: "u0" <sip:user@rip:16402>
    From: "0" <sip:user@lip:16402>;tag=173998958
    Call-ID: eefb7f0e-16a4-11df-9457-bdecd7624012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@sip:59842>;isfocus
    User-Agent: Viceroy 1.3
    Content-Type: application/sdp
    Content-Length: 737
    v=0
    o=lukegreenfield 0 0 IN IP4 sip
    s=0
    c=IN IP4 sip
    b=AS:2147483647
    t=0 0
    a=hwi:288:2:1800
    a=iChatEncryption:NO
    a=bandwidthDetection:YES
    m=audio 59842 RTP/AVP 110 121 12 3 0
    a=rtcp:59842
    a=rtpmap:121 speex/16000
    a=rtpmap:122 speex/8000
    a=rtpmap:113 X-AAC_LD/44100
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpmap:3 GSM/8000
    a=rtpmap:0 PCMU/8000
    a=rtpID:3197311419
    m=video 59842 RTP/AVP 123 126 34
    a=rtcp:59842
    a=rtpmap:123 H264/90000
    a=rtpmap:126 X-H264/90000
    a=rtpmap:34 H263/90000
    a=fmtp:34 imagesize 1 rules 30:352:288
    a=framerate:30
    a=RTCP:AUDIO 59842 VIDEO 59842
    a=fmtp:126 imagesize 0 rules 30:320:240:320:240:30
    a=fmtp:123 imagesize 0 rules 30:320:240:320:240:30
    a=rtpID:4249151525
    18.655978 @SIP/Transport.c:2362 type=1 (00000000/0)
    [INVITE sip:user@rip:16402 SIP/2.0
    Via: SIP/2.0/UDP sip:59842;branch=z9hG4bK511f58e54bf60cc6
    Max-Forwards: 70
    To: "u0" <sip:user@rip:16402>
    From: "0" <sip:user@lip:16402>;tag=150492620
    Call-ID: f02d0e60-16a4-11df-9457-a720c1b94012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@sip:59842>;isfocus
    User-Agent: Viceroy 1.3
    Content-Type: application/sdp
    Content-Length: 737
    v=0
    o=lukegreenfield 0 0 IN IP4 sip
    s=0
    c=IN IP4 sip
    b=AS:2147483647
    t=0 0
    a=hwi:288:2:1800
    a=iChatEncryption:NO
    a=bandwidthDetection:YES
    m=audio 59842 RTP/AVP 110 121 12 3 0
    a=rtcp:59842
    a=rtpmap:121 speex/16000
    a=rtpmap:122 speex/8000
    a=rtpmap:113 X-AAC_LD/44100
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpmap:3 GSM/8000
    a=rtpmap:0 PCMU/8000
    a=rtpID:3197311419
    m=video 59842 RTP/AVP 123 126 34
    a=rtcp:59842
    a=rtpmap:123 H264/90000
    a=rtpmap:126 X-H264/90000
    a=rtpmap:34 H263/90000
    a=fmtp:34 imagesize 1 rules 30:352:288
    a=framerate:30
    a=RTCP:AUDIO 59842 VIDEO 59842
    a=fmtp:126 imagesize 0 rules 30:320:240:320:240:30
    a=fmtp:123 imagesize 0 rules 30:320:240:320:240:30
    a=rtpID:4249151525
    19.156633 @SIP/Transport.c:2362 type=1 (00000000/0)
    [INVITE sip:user@rip:16402 SIP/2.0
    Via: SIP/2.0/UDP sip:59842;branch=z9hG4bK511f58e54bf60cc6
    Max-Forwards: 70
    To: "u0" <sip:user@rip:16402>
    From: "0" <sip:user@lip:16402>;tag=150492620
    Call-ID: f02d0e60-16a4-11df-9457-a720c1b94012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@sip:59842>;isfocus
    User-Agent: Viceroy 1.3
    Content-Type: application/sdp
    Content-Length: 737
    v=0
    o=lukegreenfield 0 0 IN IP4 sip
    s=0
    c=IN IP4 sip
    b=AS:2147483647
    t=0 0
    a=hwi:288:2:1800
    a=iChatEncryption:NO
    a=bandwidthDetection:YES
    m=audio 59842 RTP/AVP 110 121 12 3 0
    a=rtcp:59842
    a=rtpmap:121 speex/16000
    a=rtpmap:122 speex/8000
    a=rtpmap:113 X-AAC_LD/44100
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpmap:3 GSM/8000
    a=rtpmap:0 PCMU/8000
    a=rtpID:3197311419
    m=video 59842 RTP/AVP 123 126 34
    a=rtcp:59842
    a=rtpmap:123 H264/90000
    a=rtpmap:126 X-H264/90000
    a=rtpmap:34 H263/90000
    a=fmtp:34 imagesize 1 rules 30:352:288
    a=framerate:30
    a=RTCP:AUDIO 59842 VIDEO 59842
    a=fmtp:126 imagesize 0 rules 30:320:240:320:240:30
    a=fmtp:123 imagesize 0 rules 30:320:240:320:240:30
    a=rtpID:4249151525
    20.157652 @SIP/Transport.c:2362 type=1 (00000000/0)
    [INVITE sip:user@rip:16402 SIP/2.0
    Via: SIP/2.0/UDP sip:59842;branch=z9hG4bK511f58e54bf60cc6
    Max-Forwards: 70
    To: "u0" <sip:user@rip:16402>
    From: "0" <sip:user@lip:16402>;tag=150492620
    Call-ID: f02d0e60-16a4-11df-9457-a720c1b94012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@sip:59842>;isfocus
    User-Agent: Viceroy 1.3
    Content-Type: application/sdp
    Content-Length: 737
    v=0
    o=lukegreenfield 0 0 IN IP4 sip
    s=0
    c=IN IP4 sip
    b=AS:2147483647
    t=0 0
    a=hwi:288:2:1800
    a=iChatEncryption:NO
    a=bandwidthDetection:YES
    m=audio 59842 RTP/AVP 110 121 12 3 0
    a=rtcp:59842
    a=rtpmap:121 speex/16000
    a=rtpmap:122 speex/8000
    a=rtpmap:113 X-AAC_LD/44100
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpmap:3 GSM/8000
    a=rtpmap:0 PCMU/8000
    a=rtpID:3197311419
    m=video 59842 RTP/AVP 123 126 34
    a=rtcp:59842
    a=rtpmap:123 H264/90000
    a=rtpmap:126 X-H264/90000
    a=rtpmap:34 H263/90000
    a=fmtp:34 imagesize 1 rules 30:352:288
    a=framerate:30
    a=RTCP:AUDIO 59842 VIDEO 59842
    a=fmtp:126 imagesize 0 rules 30:320:240:320:240:30
    a=fmtp:123 imagesize 0 rules 30:320:240:320:240:30
    a=rtpID:4249151525
    20.657977 @SIP/Transport.c:2362 type=1 (00000000/0)
    [INVITE sip:user@rip:50912 SIP/2.0
    Via: SIP/2.0/UDP sip:59842;branch=z9hG4bK3c817e4509921e53
    Max-Forwards: 70
    To: "u0" <sip:user@rip:50912>
    From: "0" <sip:user@lip:16402>;tag=2108242043
    Call-ID: f15e8c96-16a4-11df-9457-cdd2619e4012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@sip:59842>;isfocus
    User-Agent: Viceroy 1.3
    Content-Type: application/sdp
    Content-Length: 737
    v=0
    o=lukegreenfield 0 0 IN IP4 sip
    s=0
    c=IN IP4 sip
    b=AS:2147483647
    t=0 0
    a=hwi:288:2:1800
    a=iChatEncryption:NO
    a=bandwidthDetection:YES
    m=audio 59842 RTP/AVP 110 121 12 3 0
    a=rtcp:59842
    a=rtpmap:121 speex/16000
    a=rtpmap:122 speex/8000
    a=rtpmap:113 X-AAC_LD/44100
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpmap:3 GSM/8000
    a=rtpmap:0 PCMU/8000
    a=rtpID:3197311419
    m=video 59842 RTP/AVP 123 126 34
    a=rtcp:59842
    a=rtpmap:123 H264/90000
    a=rtpmap:126 X-H264/90000
    a=rtpmap:34 H263/90000
    a=fmtp:34 imagesize 1 rules 30:352:288
    a=framerate:30
    a=RTCP:AUDIO 59842 VIDEO 59842
    a=fmtp:126 imagesize 0 rules 30:320:240:320:240:30
    a=fmtp:123 imagesize 0 rules 30:320:240:320:240:30
    a=rtpID:4249151525
    21.158703 @SIP/Transport.c:2362 type=1 (00000000/0)
    [INVITE sip:user@rip:50912 SIP/2.0
    Via: SIP/2.0/UDP sip:59842;branch=z9hG4bK3c817e4509921e53
    Max-Forwards: 70
    To: "u0" <sip:user@rip:50912>
    From: "0" <sip:user@lip:16402>;tag=2108242043
    Call-ID: f15e8c96-16a4-11df-9457-cdd2619e4012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@sip:59842>;isfocus
    User-Agent: Viceroy 1.3
    Content-Type: application/sdp
    Content-Length: 737
    v=0
    o=lukegreenfield 0 0 IN IP4 sip
    s=0
    c=IN IP4 sip
    b=AS:2147483647
    t=0 0
    a=hwi:288:2:1800
    a=iChatEncryption:NO
    a=bandwidthDetection:YES
    m=audio 59842 RTP/AVP 110 121 12 3 0
    a=rtcp:59842
    a=rtpmap:121 speex/16000
    a=rtpmap:122 speex/8000
    a=rtpmap:113 X-AAC_LD/44100
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpmap:3 GSM/8000
    a=rtpmap:0 PCMU/8000
    a=rtpID:3197311419
    m=video 59842 RTP/AVP 123 126 34
    a=rtcp:59842
    a=rtpmap:123 H264/90000
    a=rtpmap:126 X-H264/90000
    a=rtpmap:34 H263/90000
    a=fmtp:34 imagesize 1 rules 30:352:288
    a=framerate:30
    a=RTCP:AUDIO 59842 VIDEO 59842
    a=fmtp:126 imagesize 0 rules 30:320:240:320:240:30
    a=fmtp:123 imagesize 0 rules 30:320:240:320:240:30
    a=rtpID:4249151525
    22.159413 @SIP/Transport.c:2362 type=1 (00000000/0)
    [INVITE sip:user@rip:50912 SIP/2.0
    Via: SIP/2.0/UDP sip:59842;branch=z9hG4bK3c817e4509921e53
    Max-Forwards: 70
    To: "u0" <sip:user@rip:50912>
    From: "0" <sip:user@lip:16402>;tag=2108242043
    Call-ID: f15e8c96-16a4-11df-9457-cdd2619e4012@lip
    CSeq: 1 INVITE
    Contact: <sip:user@sip:59842>;isfocus
    User-Agent: Viceroy 1.3
    Content-Type: application/sdp
    Content-Length: 737
    v=0
    o=lukegreenfield 0 0 IN IP4 sip
    s=0
    c=IN IP4 sip
    b=AS:2147483647
    t=0 0
    a=hwi:288:2:1800
    a=iChatEncryption:NO
    a=bandwidthDetection:YES
    m=audio 59842 RTP/AVP 110 121 12 3 0
    a=rtcp:59842
    a=rtpmap:121 speex/16000
    a=rtpmap:122 speex/8000
    a=rtpmap:113 X-AAC_LD/44100
    a=rtpmap:110 X-AAC_LD/22050
    a=rtpmap:3 GSM/8000
    a=rtpmap:0 PCMU/8000
    a=rtpID:3197311419
    m=video 59842 RTP/AVP 123 126 34
    a=rtcp:59842
    a=rtpmap:123 H264/90000
    a=rtpmap:126 X-H264/90000
    a=rtpmap:34 H263/90000
    a=fmtp:34 imagesize 1 rules 30:352:288
    a=framerate:30
    a=RTCP:AUDIO 59842 VIDEO 59842
    a=fmtp:126 imagesize 0 rules 30:320:240:320:240:30
    a=fmtp:123 imagesize 0 rules 30:320:240:320:240:30
    a=rtpID:4249151525
    Video Conference User Report:
    0.000000 @:0 type=5 (00000000/16402)
    [Local SIP port]
    22.696811 @Video Conference/VideoConferenceMultiController.m:1474 type=5 (00000000/0)
    [IP And Port Data With Caller IP And Port Data: Obtained 120 bytes of local IP and port data (3 entries). Remote data was 0 bytes (0 entries).
    Binary Images Description for "iChat":
    0x1000 - 0x243fff com.apple.iChat 4.0.8 (619) /Applications/iChat.app/Contents/MacOS/iChat
    0x2b3000 - 0x329fff com.apple.Bluetooth 2.1.10 (2.1.10f2) /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth
    0x374000 - 0x49bfff com.apple.viceroy.framework 363.57 (363.59) /System/Library/PrivateFrameworks/VideoConference.framework/Versions/A/VideoCon ference
    0x509000 - 0x54dfff com.apple.vmutils 4.1 (104) /System/Library/PrivateFrameworks/vmutils.framework/Versions/A/vmutils
    0x56e000 - 0x58cfff com.apple.frameworks.preferencepanes 12.3 /System/Library/Frameworks/PreferencePanes.framework/Versions/A/PreferencePanes
    0x5a7000 - 0x5d7fff com.apple.remotedesktop.screensharing 1.0.3 /System/Library/PrivateFrameworks/ScreenSharing.framework/Versions/A/ScreenShar ing
    0x5e9000 - 0x5fcfff com.apple.ScreenSaver 2.2 /System/Library/Frameworks/ScreenSaver.framework/Versions/A/ScreenSaver
    0x60b000 - 0x62cfff libexpat.1.dylib /usr/lib/libexpat.1.dylib
    0x633000 - 0x69ffff com.apple.iLifeMediaBrowser 2.1.5 (368) /System/Library/PrivateFrameworks/iLifeMediaBrowser.framework/Versions/A/iLifeM ediaBrowser
    0x6e9000 - 0x71cfff com.apple.iChatCommonGUI 4.0.8 (619) /System/Library/PrivateFrameworks/iChatCommonGUI.framework/iChatCommonGUI
    0x744000 - 0x746fff com.apple.BezelServicesFW 1.4.9215 /System/Library/PrivateFrameworks/BezelServices.framework/Versions/A/BezelServi ces
    0x76d000 - 0x76ffff com.apple.iChat.Styles.Text 4.0.8 (619) /Applications/iChat.app/Contents/PlugIns/Text.transcriptstyle/Contents/MacOS/Te xt
    0x7bd000 - 0x7c2fff com.apple.iChat.Styles.Balloons 4.0.8 (619) /Applications/iChat.app/Contents/PlugIns/Balloons.transcriptstyle/Contents/MacO S/Balloons
    0x7d0000 - 0x7d3fff com.apple.iChat.Styles.Boxes 4.0.8 (619) /Applications/iChat.app/Contents/PlugIns/Boxes.transcriptstyle/Contents/MacOS/B oxes
    0x7d9000 - 0x7defff com.apple.iChat.Styles.Compact 4.0.8 (619) /Applications/iChat.app/Contents/PlugIns/Compact.transcriptstyle/Contents/MacOS /Compact
    0xf28000 - 0xf2efff com.apple.CoreGraphics 1.409.5 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCGXCoreImage.A.dylib
    0xf95000 - 0xf9ffff com.apple.IOFWDVComponents 1.9.5 /System/Library/Components/IOFWDVComponents.component/Contents/MacOS/IOFWDVComp onents
    0xfb0000 - 0xfb4fff com.apple.audio.AudioIPCPlugIn 1.0.6 /System/Library/Extensions/AudioIPCDriver.kext/Contents/Resources/AudioIPCPlugI n.bundle/Contents/MacOS/AudioIPCPlugIn
    0xfb9000 - 0xfbafff com.apple.aoa.halplugin 2.5.8 (2.5.8f1) /System/Library/Extensions/IOAudioFamily.kext/Contents/PlugIns/AOAHALPlugin.bun dle/Contents/MacOS/AOAHALPlugin
    0x5060000 - 0x5247fff com.apple.RawCamera.bundle 2.1.1 (508) /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
    0x5a58000 - 0x5a87fff com.apple.QuickTimeIIDCDigitizer 7.6.4 (1327.73) /System/Library/QuickTime/QuickTimeIIDCDigitizer.component/Contents/MacOS/Quick TimeIIDCDigitizer
    0x5aae000 - 0x5aecfff com.apple.QuickTimeFireWireDV.component 7.6.4 (1327.73) /System/Library/QuickTime/QuickTimeFireWireDV.component/Contents/MacOS/QuickTim eFireWireDV
    0x5af8000 - 0x5b4afff com.apple.QuickTimeUSBVDCDigitizer 2.3.2 /System/Library/QuickTime/QuickTimeUSBVDCDigitizer.component/Contents/MacOS/Qui ckTimeUSBVDCDigitizer
    0x5b58000 - 0x5b98fff com.apple.iSightAudio 7.6.4 (1327.73) /Library/Audio/Plug-Ins/HAL/iSightAudio.plugin/Contents/MacOS/iSightAudio
    0x5c92000 - 0x5caefff com.apple.opengl 1.5.10 /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloa t.bundle/GLRendererFloat
    0x5f00000 - 0x60ecfff com.apple.audio.codecs.Components 1.9 /System/Library/Components/AudioCodecs.component/Contents/MacOS/AudioCodecs
    0x613f000 - 0x62b7fff com.apple.opengl 1.5.10 /System/Library/Frameworks/OpenGL.framework/Resources/GLEngine.bundle/GLEngine
    0x62e9000 - 0x6472fff com.apple.GeForceFXGLDriverPPC 1.5.48 (5.4.8) /System/Library/Extensions/GeForceFXGLDriverPPC.bundle/Contents/MacOS/GeForceFX GLDriverPPC
    0x7b65000 - 0x7b6afff com.apple.iokit.IOQTComponents 1.6 /System/Library/Components/IOQTComponents.component/Contents/MacOS/IOQTComponen ts
    0x8fe00000 - 0x8fe30fff dyld /usr/lib/dyld
    0x90003000 - 0x9000bfff libbsm.dylib /usr/lib/libbsm.dylib
    0x9000c000 - 0x9001afff libz.1.dylib /usr/lib/libz.1.dylib
    0x9001b000 - 0x90344fff com.apple.Accelerate.vecLib 3.4.2 (vecLib 3.4.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
    0x90345000 - 0x90459fff com.apple.vImage 3.0 /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.fr amework/Versions/A/vImage
    0x90583000 - 0x905d1fff com.apple.framework.familycontrols 1.0.4 /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyCon trols
    0x905d2000 - 0x90614fff com.apple.quartzfilters 1.5.0 /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuartzFilters .framework/Versions/A/QuartzFilters
    0x90615000 - 0x9061dfff com.apple.CoreGraphics 1.409.5 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCGATS.A.dylib
    0x9064f000 - 0x9127afff com.apple.QuickTimeComponents.component 7.6.4 (1327.73) /System/Library/QuickTime/QuickTimeComponents.component/Contents/MacOS/QuickTim eComponents
    0x9127b000 - 0x91305fff com.apple.Accelerate.vecLib 3.4.2 (vecLib 3.4.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
    0x91306000 - 0x91313fff com.apple.CoreGraphics 1.409.5 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
    0x91314000 - 0x913f7fff libobjc.A.dylib /usr/lib/libobjc.A.dylib
    0x913f8000 - 0x9151dfff com.apple.CoreFoundation 6.5.7 (476.19) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x9151e000 - 0x915a0fff com.apple.print.framework.PrintCore 5.5.4 (245.6) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore
    0x915a1000 - 0x915a1fff com.apple.audio.units.AudioUnit 1.5 /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
    0x915a2000 - 0x91604fff com.apple.htmlrendering 68 (1.1.3) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering .framework/Versions/A/HTMLRendering
    0x91605000 - 0x91605fff com.apple.MonitorPanelFramework 1.2.0 /System/Library/PrivateFrameworks/MonitorPanel.framework/Versions/A/MonitorPane l
    0x91606000 - 0x91622fff com.apple.IMFramework 4.0.8 (584) /System/Library/Frameworks/InstantMessage.framework/Versions/A/InstantMessage
    0x91623000 - 0x9162efff com.apple.helpdata 1.0.1 (14.2) /System/Library/PrivateFrameworks/HelpData.framework/Versions/A/HelpData
    0x9162f000 - 0x91818fff com.apple.security 5.0.6 (37592) /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x91819000 - 0x9186ffff com.apple.opengl 1.5.10 /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
    0x91940000 - 0x919dafff com.apple.ApplicationServices.ATS 3.8 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
    0x919df000 - 0x91a23fff com.apple.CoreMediaIOServicesPrivate 20.0 /System/Library/PrivateFrameworks/CoreMediaIOServicesPrivate.framework/Versions /A/CoreMediaIOServicesPrivate
    0x91a24000 - 0x91a34fff com.apple.agl 3.0.9 (AGL-3.0.9) /System/Library/Frameworks/AGL.framework/Versions/A/AGL
    0x91a35000 - 0x91a6afff com.apple.AE 402.3 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
    0x91a6b000 - 0x91a70fff com.apple.KerberosHelper 1.1 (1.0) /System/Library/PrivateFrameworks/KerberosHelper.framework/Versions/A/KerberosH elper
    0x91a71000 - 0x91aecfff com.apple.SearchKit 1.2.2 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
    0x91bb9000 - 0x91bf6fff com.apple.CoreGraphics 1.409.5 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
    0x91bf7000 - 0x91bfafff com.apple.help 1.1 (36) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framewor k/Versions/A/Help
    0x91bfb000 - 0x91c0efff com.apple.CFOpenDirectory 10.5 /System/Library/PrivateFrameworks/OpenDirectory.framework/Versions/A/Frameworks /CFOpenDirectory.framework/Versions/A/CFOpenDirectory
    0x91c0f000 - 0x91c14fff com.apple.OpenDirectory 10.5 /System/Library/PrivateFrameworks/OpenDirectory.framework/Versions/A/OpenDirect ory
    0x91c15000 - 0x91c1bfff com.apple.DisplayServicesFW 2.0.2 /System/Library/PrivateFrameworks/DisplayServices.framework/Versions/A/DisplayS ervices
    0x91c1c000 - 0x91d06fff libxml2.2.dylib /usr/lib/libxml2.2.dylib
    0x91d07000 - 0x91d2efff libcups.2.dylib /usr/lib/libcups.2.dylib
    0x91d2f000 - 0x91d36fff com.apple.print.framework.Print 218.0.3 (220.2) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framewo rk/Versions/A/Print
    0x91d37000 - 0x91d37fff com.apple.quartzframework 1.5 /System/Library/Frameworks/Quartz.framework/Versions/A/Quartz
    0x91d38000 - 0x91d3bfff com.apple.CrashReporterSupport 10.5.7 (161) /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/Cra shReporterSupport
    0x91ddf000 - 0x91e08fff com.apple.shortcut 1.0.1 (1.0) /System/Library/PrivateFrameworks/Shortcut.framework/Versions/A/Shortcut
    0x91e14000 - 0x91e71fff com.apple.HIServices 1.7.1 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
    0x91e72000 - 0x91fbefff com.apple.ImageIO.framework 2.0.7 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/ImageIO
    0x91fbf000 - 0x9208ffff com.apple.ColorSync 4.5.3 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync
    0x92096000 - 0x920abfff com.apple.datadetectors 1.0.1 (66.2) /System/Library/PrivateFrameworks/DataDetectors.framework/Versions/A/DataDetect ors
    0x920ac000 - 0x920aefff com.apple.ImageIO.framework 2.0.7 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRadiance.dylib
    0x920af000 - 0x920c4fff com.apple.IMUtils 4.0.8 (584) /System/Library/Frameworks/InstantMessage.framework/Frameworks/IMUtils.framewor k/Versions/A/IMUtils
    0x920c5000 - 0x920d4fff com.apple.DSObjCWrappers.Framework 1.3 /System/Library/PrivateFrameworks/DSObjCWrappers.framework/Versions/A/DSObjCWra ppers
    0x920d5000 - 0x92185fff edu.mit.Kerberos 6.0.13 /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
    0x92186000 - 0x92196fff libsasl2.2.dylib /usr/lib/libsasl2.2.dylib
    0x92197000 - 0x921b1fff com.apple.CoreVideo 1.6.0 (20.0) /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
    0x921b2000 - 0x9223afff com.apple.audio.CoreAudio 3.1.2 /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
    0x9223b000 - 0x9223bfff com.apple.Carbon 136 /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x9230d000 - 0x92313fff com.apple.backup.framework 1.0 /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup
    0x92320000 - 0x923e8fff com.apple.CoreData 100.2 (186.2) /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
    0x923e9000 - 0x9242dfff com.apple.DirectoryService.PasswordServerFramework 3.0.4 /System/Library/PrivateFrameworks/PasswordServer.framework/Versions/A/PasswordS erver
    0x9257d000 - 0x92650fff com.apple.CoreServices.OSServices 228 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
    0x92651000 - 0x926bbfff com.apple.PDFKit 2.1.2 /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/PDFKit.framew ork/Versions/A/PDFKit
    0x926bc000 - 0x92c38fff com.apple.CoreGraphics 1.409.5 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
    0x92c39000 - 0x92d20fff com.apple.WebKit 5531.21 (5531.21.8) /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit
    0x92d21000 - 0x92d62fff com.apple.ImageIO.framework 2.0.7 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libTIFF.dylib
    0x92d63000 - 0x9331dfff com.apple.Accelerate.vecLib 3.4.2 (vecLib 3.4.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
    0x9331e000 - 0x9334ffff com.apple.coreui 1.2 (62) /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
    0x93350000 - 0x93368fff com.apple.DictionaryServices 1.0.0 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
    0x93369000 - 0x93385fff com.apple.ImageIO.framework 2.0.7 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libPng.dylib
    0x93386000 - 0x933affff com.apple.CoreMediaPrivate 15.0 /System/Library/PrivateFrameworks/CoreMediaPrivate.framework/Versions/A/CoreMed iaPrivate
    0x933b0000 - 0x93460fff com.apple.QD 3.11.57 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
    0x93461000 - 0x93489fff libxslt.1.dylib /usr/lib/libxslt.1.dylib
    0x9348a000 - 0x934d4fff com.apple.QuickLookUIFramework 1.3.1 (170.9) /System/Library/PrivateFrameworks/QuickLookUI.framework/Versions/A/QuickLookUI
    0x934d5000 - 0x9350afff com.apple.LDAPFramework 1.4.5 (110) /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP
    0x9350b000 - 0x9350bfff com.apple.Accelerate 1.4.2 (Accelerate 1.4.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
    0x9350c000 - 0x93573fff libstdc++.6.dylib /usr/lib/libstdc++.6.dylib
    0x93574000 - 0x937bafff com.apple.Foundation 6.5.9 (677.26) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x9382d000 - 0x9382efff libffi.dylib /usr/lib/libffi.dylib
    0x9382f000 - 0x938c4fff com.apple.framework.IOKit 1.5.2 (???) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x938c5000 - 0x9397cfff com.apple.QTKit 7.6.4 (1327.73) /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit
    0x9397d000 - 0x9397efff com.apple.ApplicationServices 34 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
    0x9397f000 - 0x93a04fff libsqlite3.0.dylib /usr/lib/libsqlite3.0.dylib
    0x93b19000 - 0x93b60fff com.apple.NavigationServices 3.5.2 (163) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationSer vices.framework/Versions/A/NavigationServices
    0x93b61000 - 0x93bb0fff com.apple.datadetectorscore 1.0.2 (52.14) /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDe tectorsCore
    0x93bb1000 - 0x93eb3fff com.apple.CoreServices.CarbonCore 786.11 (786.14) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
    0x93eb4000 - 0x93ec7fff com.apple.LangAnalysis 1.6.5 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
    0x93ec8000 - 0x93ec8fff com.apple.CoreServices 32 /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x93ec9000 - 0x93f0ffff com.apple.securityinterface 3.0.4 (37213) /System/Library/Frameworks/SecurityInterface.framework/Versions/A/SecurityInter face
    0x93f10000 - 0x940b1fff com.apple.QuartzComposer 2.1 (106.13) /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuartzCompose r.framework/Versions/A/QuartzComposer
    0x940b2000 - 0x940bdfff com.apple.speech.recognition.framework 3.7.24 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
    0x940be000 - 0x940c7fff com.apple.DiskArbitration 2.2.1 /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    0x940c8000 - 0x94268fff libSystem.B.dylib /usr/lib/libSystem.B.dylib
    0x94269000 - 0x94287fff com.apple.QuickLookFramework 1.3.1 (170.9) /System/Library/Frameworks/QuickLook.framework/Versions/A/QuickLook
    0x94288000 - 0x942a7fff libresolv.9.dylib /usr/lib/libresolv.9.dylib
    0x942a8000 - 0x942a8fff com.apple.installserver.framework 1.0 (8) /System/Library/PrivateFrameworks/InstallServer.framework/Versions/A/InstallSer ver
    0x942a9000 - 0x942c4fff com.apple.DirectoryService.Framework 3.5.7 /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce
    0x942c5000 - 0x9437ffff libcrypto.0.9.7.dylib /usr/lib/libcrypto.0.9.7.dylib
    0x94380000 - 0x943b9fff com.apple.SystemConfiguration 1.9.2 /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
    0x943ba000 - 0x9457cfff com.apple.CoreAUC 3.08.0 /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC
    0x9457d000 - 0x946a2fff com.apple.imageKit 1.0.2 (1.0) /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/ImageKit.fram ework/Versions/A/ImageKit
    0x946a3000 - 0x946b1fff com.apple.opengl 1.5.10 /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
    0x946b2000 - 0x9481efff com.apple.AddressBook.framework 4.1.2 (702) /System/Library/Frameworks/AddressBook.framework/Versions/A/AddressBook
    0x9481f000 - 0x94849fff libssl.0.9.7.dylib /usr/lib/libssl.0.9.7.dylib
    0x9484a000 - 0x948fdfff com.apple.CFNetwork 438.14 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
    0x948fe000 - 0x94986fff com.apple.ink.framework 101.3 (86) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
    0x949d5000 - 0x94a6cfff com.apple.LaunchServices 292 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
    0x94a6d000 - 0x94b06fff com.apple.Accelerate.vecLib 3.4.2 (vecLib 3.4.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
    0x94b07000 - 0x94b27fff com.apple.ImageIO.framework 2.0.7 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJPEG.dylib
    0x94b28000 - 0x94e5afff com.apple.QuickTime 7.6.4 (1327.73) /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime
    0x950d8000 - 0x95139fff com.apple.CoreText 2.0.4 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreText.framework/Versions/A/CoreText
    0x9513a000 - 0x95151fff com.apple.ImageCapture 5.0.2 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture. framework/Versions/A/ImageCapture
    0x95152000 - 0x9516efff com.apple.openscripting 1.2.8 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting .framework/Versions/A/OpenScripting
    0x9516f000 - 0x95172fff com.apple.securityhi 3.0 (30817) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.fr amework/Versions/A/SecurityHI
    0x95173000 - 0x95177fff com.apple.ImageIO.framework 2.0.7 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libGIF.dylib
    0x95178000 - 0x951a3fff libauto.dylib /usr/lib/libauto.dylib
    0x951a4000 - 0x951b7fff com.apple.speech.synthesis.framework 3.7.1 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
    0x95223000 - 0x95272fff com.apple.opengl 1.5.10 /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dyl ib
    0x95273000 - 0x95292fff com.apple.Accelerate.vecLib 3.4.2 (vecLib 3.4.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/vecLib
    0x95293000 - 0x95a09fff com.apple.AppKit 6.5.9 (949.54) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x95a0a000 - 0x95a99fff com.apple.DesktopServices 1.4.8 /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
    0x95a9a000 - 0x95be2fff libicucore.A.dylib /usr/lib/libicucore.A.dylib
    0x95be3000 - 0x96011fff com.apple.opengl 1.5.10 /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgramma bility.dylib
    0x96012000 - 0x9634bfff com.apple.HIToolbox 1.5.6 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
    0x9634c000 - 0x96358fff com.apple.audio.SoundManager 3.9.2 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.f ramework/Versions/A/CarbonSound
    0x96359000 - 0x96359fff com.apple.Cocoa 6.5 (???) /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
    0x9635a000 - 0x964b1fff com.apple.JavaScriptCore 5531.21 (5531.21.9) /System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore
    0x964b2000 - 0x964b9fff com.apple.CommonPanels 1.2.4 (85) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels. framework/Versions/A/CommonPanels
    0x964ba000 - 0x9681ffff com.apple.QuartzCore 1.5.8 /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
    0x96820000 - 0x9686ffff com.apple.Metadata 10.5.8 (398.26) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
    0x96870000 - 0x9688ffff com.apple.vecLib 3.4.2 (vecLib 3.4.2) /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
    0x96890000 - 0x969d7fff com.apple.audio.toolbox.AudioToolbox 1.5.3 /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
    0x969d8000 - 0x969ddfff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib
    0x969e4000 - 0x969effff libgcc_s.1.dylib /usr/lib/libgcc_s.1.dylib
    0x969f0000 - 0x96a1dfff com.apple.opengl 1.5.10 /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
    0x96a1e000 - 0x9740dfff com.apple.WebCore 5531.21 (5531.21.8) /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.frame work/Versions/A/WebCore
    0x9740e000 - 0x9744bfff com.apple.securityfoundation 3.0.2 (36131) /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoun dation

    Hi,
    Welcome to the    Discussions
    So we have DSL Modem <-> Base Station <-> Computer connected by Ethernet.
    Is the Modem Routing ?
    Is the Base Station set to "Share An IP" ?
    (i.e are there two DHCP servers on your LAN ?)
    Is Internet Sharing On in th G5s System Preferences > Sharing pane ?
    In the Base Station is Port Mapping Protocol Enabled if it is doing routing ?
    It is in the NAT tab of the Internet Pane.
    Is the G5 also doing WiFi to the Base Station ?
    Also check the Modem is not Blocking PINGS as this log shows no PING (But I am not sure it even got that far)
    7:45 PM Thursday; February 18, 2010
    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

  • File is picked up but never show the XML message in SXMB_MONI

    All,
    I am working on the file to SAP integration scenario issue. High level interface design is,
    File Adapter picks the file from XI application server and send the data to SAP Application system(in this case ECC) to post data as per the business requirement. The scenario is working perfect since long time and we don't have any issues as yesterday.
    This morning, I noticed File adapter picks the file and moved the file to archive folder (based on settings in communication channel) but XML message never shown in SXMB_MONI. I had a look into the RWB to check status of the communication channel. every thing looks fine from communication channel monitoring.
    Did any one come across this scenario? What else to be checked to move forward on this issue?
    Thank you..
    Anil

    Hi Kumar,
    The error message indicates the URL the adapter engine is using to send the data to the integration engine is wrong. The last part of it has somehow become truncated: "type=ent" should read "type=entry".
    In the SLD lookup the XI technical system, under the integration tab check the setting for the "Pipeline URL" field, you should see something like: http://HOST:PORT/sap/xi/engine?type=entry  if not, you can correct it.
    Then go to the XI ABAP client using SAPGUI and in transaction: SXMB_ADM, option "Integration Engine Configuration", check that Corresponding Integ. Server has the same URL, if it has something of the sort of: "dest://...." check in transaction SM59 for that RFC destination name, it should have the correct URL.  Also in the specific configuration (using the same transaction), check the RUNTIME->IS_URL parameter value.
    Hope that helps.
    -Sam.

  • Correct and re-send the error messages in PI

    Hi everyone,
    Today when iam monitoring my PI i found error like some objects missing in the que, I toublshooted it by using inbount xml payload and found the error and cunsulted the user he asked me to correct and re-send the error messages. as iam really new to PI monitoring i really dont know how to correct and re-send the error messages in PI, can any one please help me with it.
    Thanks in advance

    When you send the messages from RWB-->Component Monitoring ->Integration Engine>test message, runtime parameters like Sender System, Receiver system, Adapter specific message attributes won't carry any values. If you are using any of these paramters in the mapping step,, the mapping will fail.
    I think in your case, RFC look up would have been configured based on Sender Business system/Service. but when you send message from RWB, the value for this field is empty. So that is why it is failing  as the message cannot find the business system and communication channel.
    If you use the sender file name, server name or any other parameters in the message mapping, then message will fail in the message mapping step. That is the major set back in RWB-->Test message.
    Reasons:
    1)We post messages directly into pipeline step message mapping.
    2)The previous pipeline steps are ignored when post messages from RWB such as Receiver determination, routing etc
    3)Receiver determination step is responsible to send Sender/Receiver values into the mapping step.
    Hope i have clarified your questions

  • Accessing the original message body in Error handler

    Hello everybody,
    The loanGatewy3 proxy service in the OSB tutorial uses a stage in the request pipeline for validation. If a validation error occurs the error handler reports the original body message using a reporting action.
    Now if an error happens inside the Routing node; and if an error handler is defined to report the original message ($body), the reporting action will report the error message not the original message. It seems that the $body variable contains the erroneous response instead of the original message. So is there a way to access the original request $body inside a node error handler?
    Best regards,
    Tarek

    you can always put the original message into a dummy variable $origMessage, then in the event of an error report on $origMessage not $body
    cheers
    James

  • [svn] 1594: Update the warning message when outbound throttle policy of REPLACE is used one more time .

    Revision: 1594
    Author: [email protected]
    Date: 2008-05-07 11:10:27 -0700 (Wed, 07 May 2008)
    Log Message:
    Update the warning message when outbound throttle policy of REPLACE is used one more time. Now the warning says this. . .
    Throttle outbound policy 'REPLACE' found on message destination 'MESSAGE_DESTINATION'. The 'REPLACE' throttle outbound policy has been deprecated. Please remove it from your configuration file.
    Modified Paths:
    blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/MessageDestination.java

    hamish72 wrote:
    You can still download as much as you can only a lot slower during peak times off peak will not be restricted.
    Thanks for this explanation. I had taken it that it was at all times.
    As I said in the first place it will be great if they throttle me to 1Mb at peak times as it will be better half the time than I am getting anyway!!!!!!!!!
    hamish72 wrote:
    Have you chased up why your line is so bad, long way from exchange and so on
    Posting your router stats may get advice from someone
    enter for homehub for other routers will differ
    192.168.1.254 in browser click A to Z top right
    then ADSL enter pas and click MORE DETAIL
    POST RESULTS
    Also post results of test at ( best done from master test socket)
    http://speedtester.bt.com/
    Connection Information
    Line state
    Connected
    Connection time
    6 days, 11:57:55
    Downstream
    5,760 Kbps
    Upstream
    448 Kbps
    ADSL Settings
    VPI/VCI
    0/38
    Type
    PPPoA
    Modulation
    G.992.1 Annex A
    Latency type
    Interleaved
    Noise margin (Down/Up)
    5.7 dB / 21.0 dB
    Line attenuation (Down/Up)
    44.6 dB / 24.0 dB
    Output power (Down/Up)
    8.9 dBm / 1.6 dBm
    Loss of Framing (Local/Remote)
    0 / 0
    Loss of Signal (Local/Remote)
    0 / 0
    Loss of Power (Local/Remote)
    0 / 0
    FEC Errors (Down/Up)
    25279 / 134
    CRC Errors (Down/Up)
    700 / 196
    HEC Errors (Down/Up)
    5427 / 142
    Error Seconds (Local/Remote)
    477 / 102

  • [svn:bz-4.x] 16147: Fix a few more regression tests on the 4. x branch that were failing when using Spring integration.

    Revision: 16147
    Revision: 16147
    Author:   [email protected]
    Date:     2010-05-17 06:18:38 -0700 (Mon, 17 May 2010)
    Log Message:
    Fix a few more regression tests on the 4.x branch that were failing when using Spring integration.
    Modified Paths:
        blazeds/branches/4.x/qa/apps/qa-regress/WEB-INF/src/runtimeconfig/remoteobjects/ROMessage Destination.java
        blazeds/branches/4.x/qa/apps/qa-regress/WEB-INF/src/runtimeconfig/remoteobjects/RuntimeCo nfigurator.java
        blazeds/branches/4.x/qa/resources/webtier/flex_sdk_4/flex-config.xml

    Well heres my story. I tried kde4 from extra the last 3 weeks and I like it. I have used xfce for the past 3 years, previous to that gnome. Tried kde but never really liked it. Now I am only using workspace, base, mutimedia and graphics.
    Here is what I like.
    1- Dolphin, awesome I have used thunar a while and it is great but I love splitview, and fish for ssh (which has been around a while I know), and the ability to mount other partitions on my hdd with a click no fstab entry or nothin'.
    2-Pretty, I've used xfce with built in compositor an love the snappiness. But I like desktop grid with kde4 and flipswitch. Compiz-fusion is cool but I prefer not to use I'll take what the DE gives. Plasmoid are cool too.
    3- Gwenview is nice too. Use to use gqview, but thumnails are nice.
    Looking forward to or lacking
    1- Keyboard shortcuts, Yes xbindkeys is there but if I have a DE I want it to do it. They just don't work now.
    2- kde4 has windows specific settings, but I can't set the opacity for particular windows , doesn't work.
    3- Ram of course is much higher in kde4, but maybe I'm getting old I just don't care as much.

  • IDOC to File (BYpass)-- Error or Warning  :  " Message Branched. "

    HI all,
    Iam trying idoc to file scenario(bypass)
    my idoc is triggered succesfully and it is reaching to the receiver system.
    but the problem is in SXMB_MONI ,it is not showing my Receiver service details and showing with different symbol like " <b>>></b>  " with message as " MESSAGE BRANCHED".
    what might be the problem....???
    Also Idoc reaching to the receiving system very lately.
    Pls suggest me ASAP..
    Thanks in Advance.
    Regards,
    Vijji

    In the receiver determination, do you have multiple receivers, i.e , is the same idoc being sent to multiple receivers ?
    If yes, then the message branch is used to split the source message so that it can be send to differetn targets. You will find multiple entires below the Slit Message Entry one for each receiver.
    Regards
    Bhavesh

  • [svn:fx-beta1] 7179: Improving the error message when Flex 4 primitives are added as children to Halo containers .

    Revision: 7179
    Author:   [email protected]
    Date:     2009-05-21 08:54:48 -0700 (Thu, 21 May 2009)
    Log Message:
    Improving the error message when Flex 4 primitives are added as children to Halo containers.
    QE: Yes, please add test cases and update any negative test error strings.
    Doc: No
    Checkintests: Pass
    Cyclone Tests: Mxmlcunit, Mxunit - full, Mxunit - compc, Mxunit - rsl, and Compiler API all pass.
    Reviewers: Paul, Glenn
    Bugs:
    SDK-21300 - Compiler error for using Graphic tags (like SimpleText) in a Halo container is wrong and misleading
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-21300
    Modified Paths:
        flex/sdk/branches/beta1/modules/compiler/src/java/flex2/compiler/mxml/builder/ComponentBu ilder.java
        flex/sdk/branches/beta1/modules/compiler/src/java/flex2/compiler/mxml/builder/DocumentBui lder.java
        flex/sdk/branches/beta1/modules/compiler/src/java/flex2/compiler/mxml/lang/StandardDefs.j ava
        flex/sdk/branches/beta1/modules/compiler/src/java/flex2/compiler_en.properties

  • About understanding the pi' message processing

    Dear All:
       I wanna to know  the detailed step of  message  process  in PI,for example  :   message throught the adapter  message system  IS  , Anyone can helpe me,or give me some doucument.
    thanks!
    kevin  liang

    hi,
    Message flow from Adapter Engine to Integration Server
    1.     For the message to be picked up by the communication channel, the channel should be associated with a sender agreement. Mere creation of a communication channel doesnu2019t ensure the message to be polled and picked up by the adapter. The message reaches the adapter in its native message format. As the communication in SAP XI happens in XI message format, a module inside the adapter converts the message in native format into XI message format.
    2.     During this process, a message ID is generated for the message. To build the XI header (sender agreement details like the sender system, sender message interface and the interface namespace) the details are fetched by performing a CPA lookup(collaboration-partner-agreement are the configuration object details that have been created using the configuration time. The details are updated into the runtime cache when you activate the Configuration objects in Integration builder u2013Configuration time. This cache is referred to as CPA cache).
    3.     This message is then sent to module processor for further processing. During the process of sending the message to module processor, the message u201CApplication attempting to send an XI message asynchronously using connection AFWu201D is logged.
    4.     The module processor performs steps like structure conversion, communication channel specific conversions (that have been specified in the u201Cmodule tabu201D of the adapter channel). These conversion modules are executed in the same sequence as mention in the communication channel.
    5.     After the successful execution of the conversion modules, the appropriate module (call SAP adapter module) of the module processor is called which will send this message for persistent storage. This message is put into the Send Queue of the messaging system for further processing. Messages like u201CMessage trying to put into the send Queueu201D and u201CMessage successfully put into the queueu201D are logged during this process. A confirmation message (success/ failure) is sent back to the sender application at this stage. This confirmation message is used by the channel to perform various steps like deleting the file that has a processing mode as delete.
    6.     The message that has been put in the Send Queue has to be picked up and sent to the Integration Engine. The Adapter Engine and XI Integration server use XI Adapter for internal communication purposes. So the XI Adapter picks up message from the send queue and parses the XI message. In this process, the status of the message is set to DLNG and. Messages like u201CThe message was successfully retrieved from the send queue and message status set to DLNGu201Dare logged.
    7.     The XI adapter performs a SLD look up (System landscape Directory) to find the Integration server with which the Adapter framework has register itself.
    8.     On successful SLD look up, the message is sent via HTTP to the XI IS pipeline, using the pipeline URL (http://hostname:abap-httpport/sap/xi/engine?type=entry). . If this is successful, a message u201CThe message was successfully transmitted to endpoint http://hostname:8000/sap/xi/engine?type=entry using connection AFWu201D is logged and the message statues is set to DLVD means message has been successfully delivered to the endpoint( XI IS in this case)
    <h5>see also pipeline steps that are executed in Integration Server</h5>
    also see this
    [http://help.sap.com/saphelp_nw04/helpdata/en/1b/89d24032f68231e10000000a1550b0/frameset.htm]

  • [svn] 762: -update the 3.0 branch to use build. properties to create the flex-sdk-description.xml

    Revision: 762
    Author: [email protected]
    Date: 2008-03-10 07:44:49 -0700 (Mon, 10 Mar 2008)
    Log Message:
    -update the 3.0 branch to use build.properties to create the flex-sdk-description.xml
    Modified Paths:
    flex/sdk/branches/3.0.x/build.properties
    flex/sdk/branches/3.0.x/build.xml
    Added Paths:
    flex/sdk/branches/3.0.x/collateral/en_US/flex-sdk-description.xml

    By the way, simply adding the quotes around the lexical names in the sql statement doesn't work. That causes the lexical references to be ignored as simple string values:
    SELECT
       '&FLEX_GL_BALANCING_APROMPT' alias_gl_balancing_aprompt
      ,'&FLEX_GL_ACCOUNT_LPROMPT'   alias_gl_account_lprompt
      ,'&ACCT_BAL_LPROMPT'          alias_acct_bal_lprompt
    FROM dualI turned on statement-level debugging via xdodebug.cfg and saw how it compiled the lexicals. By replicating the call to apps.fnd_flex_xml_publisher_apis.kff_segments_metadata that I found there, I was able to hack together a workaround for this issue.
    Please point me to a better way of doing this if possible, as I had to GRANT EXECUTE on this apps package to my custom code schema. Is there a better lexical/flexfields reference than the XML Publisher documentation?
    Here is the call I made in my before-report trigger:
    --set ACCT_BAL_LPROMPT flexfield segment metadata lexical
    begin
    apps.fnd_flex_xml_publisher_apis.kff_segments_metadata(
      'FLEX_ACCT_BAL_LPROMPT',
      'SQLGL',
      'GL#',
      101,
      'GL_BALANCING',
      'Y',
      'LEFT_PROMPT',
      c_FLEX_ACCT_BAL_LPROMPT
    end;

  • [svn:fx-3.x] 11842: Submit Window/ WindowedApplication patch from Beau Scott to the 3.x branch.

    Revision: 11842
    Revision: 11842
    Author:   [email protected]
    Date:     2009-11-16 08:45:39 -0800 (Mon, 16 Nov 2009)
    Log Message:
    Submit Window/WindowedApplication patch from Beau Scott to the 3.x branch.
    Instead of using rawChildren.addChildAt() to add a non-content child, use rawChildren.addChild() and then set the child's index using rawChildren.setChildIndex().
    QE notes: None.
    Doc notes: None.
    Bugs: SDK-16464
    Reviewer:
    Tests run: checkintests
    Is noteworthy for integration: no
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-16464
    Modified Paths:
        flex/sdk/branches/3.x/frameworks/projects/airframework/src/mx/core/Window.as
        flex/sdk/branches/3.x/frameworks/projects/airframework/src/mx/core/WindowedApplication.as

    Have you tried adding the following css selector to your css file.
    .nav-bar a {
        text-align: center;
    or insert it in the <style> tag you have on the page:
      <style type="text/css">
      body {
        margin-left: 200px;
      .n {
        text-align: center;
    .nav-bar a {
        text-align: center;
      </style>

  • Message Branching Incorrect payload

    Hi
    Im using message branching by passing the 2 different PO numbers to two different idocs
    For this im using two mapping programs and obviously 2 interfacing mappings. Now when im running the scenario both the mappings are taking the first PO number only.. the second PO number is being discarded..
    In the MM test tab both the mappings are successful with different PO number. But at runtime during message branching the second PO is being discarded.. I've checked "Maintain Order at runtime" in Interface determination too
    But no use .. did i miss anythig
    -keerthi

    Wat I suggest is:-
    Create two message type and inbound message interface.
    In message mapping go to message tab - provide both the message type in target message.
    Now go to Design tab and put the below logic at root node of both the mapping.
    if PO value( take all PO value in one context) Equals constant value -> pass the output to If then function and map it to root node.
    do the same for other message type.
    And do the enhance configuration in Interface mapping.
    chirag

  • SXMB_MONI only getting the Inbound Message ( CENTRAL ) not other steps

    Hi All,
    I am doing a File to proxy scenerios. I am posting the file using file content cnversion. When ever i am checking the scenerios throught tool-->Test
    Its working perfectly fine.
    But when i am sending the file and checking the SXMB_MONI.
    Its only showing the Inbound Message ( CENTRAL ) step. After that its not showing any receiver messages steps. What is the problem? Is there any services not activated? Can you help me on this?
    Thanks
    Manas

    HI Ravi,
    i have check the trace lavel this is 1. I have given the trace lavel below.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="T">Party normalization: sender</Trace>
      <Trace level="1" type="T">Sender scheme external = XIParty</Trace>
      <Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
      <Trace level="1" type="T">Sender party external =</Trace>
      <Trace level="1" type="T">Sender party normalized =</Trace>
      <Trace level="1" type="T">Party normalization: receiver</Trace>
      <Trace level="1" type="T">Receiver scheme external =</Trace>
      <Trace level="1" type="T">Receiver agency external =</Trace>
      <Trace level="1" type="T">Receiver party external =</Trace>
      <Trace level="1" type="T">Receiver party normalized =</Trace>
      <Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
      <Trace level="1" type="T">COMMIT is done by XMB !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="1" type="T">system-ID = PID</Trace>
      <Trace level="1" type="T">client = 100</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2008-07-08T11:24:07Z PST</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = 04B466276FDB48713ABDB7E5A31732C5</Trace>
      <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
      <Trace level="1" type="T">Queue name : XBTI0006</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTI0006</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">--start sender interface action determination</Trace>
      <Trace level="1" type="T">select interface MIOA_MT_GLEmpExp*</Trace>
      <Trace level="1" type="T">select interface namespace http://omnicell.com/FIN</Trace>
      <Trace level="1" type="T">no interface found</Trace>
      <Trace level="1" type="T">--start receiver interface action determination</Trace>
      <Trace level="1" type="T">Loop 0000000001</Trace>
      <Trace level="1" type="T">select interface *</Trace>
      <Trace level="1" type="T">select interface namespace</Trace>
      <Trace level="1" type="T">no interface found</Trace>
      <Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
      <Trace level="1" type="T">Hence set action to DEL</Trace>
      </SAP:Trace>

Maybe you are looking for