Report bursting sends empty reports

I am trying to use Business Objects Enterprise with Crystal Reports to send suppliers reminders by email. BOE should burst the reminder report into the parts relevant to each supplier, but the reports are always empty. Can anyone give me some help?
I have a very simple test case Publication installed which works correctly. The report containing all data is burst into parts and each part emailed to the expected recipient.
However for the the full reminder Publication, the emails are sent but the attached PDF reports are always empty.
Some additional information:
- The source and the recipient Crystal reports can be run in BOE and show the expected data.
- If the Publication is run without any Personalization setting, then all the recipients are emailed the full reminder report showing all data.
- If Personalization is set, the reports are sent but are always empty.
The field being used for Personalization is a Crystal Formula Field unlike the test case where it is a database field.
Any suggestions?
Regards,
Douglas

Business Objects Enterprise XI 3.1.
Data source: MS SQL Server (actually SAP Business One).
Authentication: SQL Server.
The problem seems to be with the Personalization as the Publication works OK if there are no Personalization settings. I have been wondering if the problem is something to do with the Formula Field being used to filter not being indexed. I have tried adding it as a Report Bursting Index in Crystal, but it seems to make no difference. (Of course, it is possible that I have not done it correctly.)
Regards,
Douglas

Similar Messages

  • Email bursting send report as HTML in email body

    Hello,
    I have Oracle BI Publisher 10.1.3.4.1 (build# 1101) version installed as part of Oracle Business Inteligence.
    I have question about email bursting. I created simple report and I am bursting it via email. But I would like to send report in HTML as part of email body and not as attachment. I read that it is possible in other versions of BIP (as part of EBS) with using of bursting configuration file. But I can not use this file with my version of BIP, I can configure bursting only vie SQL query.
    Is there any solution?
    Thank you

    My bursting SQL query:
    SELECT DISTINCT
    ip.APPL_ID KEY,
    '11F_Search_Prospect_Email' TEMPLATE,
    'RTF' template_format,
    'en-US' locale,
    'HTML' output_format,
    'EMAIL' DEL_CHANNEL,
    ip.email PARAMETER1,
    '[email protected]' PARAMETER3,
    'Welcome' PARAMETER4,
    'true' PARAMETER6
    FROM ugrad.inquiry_prospect ip,
    ugrad.correspondence f,
    ugrad.address e,
    ugrad.f_lookup fl
    WHERE ip.appl_id = f.appl_id
    AND ip.APPL_ID = e.APPL_ID
    AND fl.TYPE_CODE='C'
    AND ip.record_stage = 'Prospect'
    AND e.COUNTRY_CODE=fl.code
    AND e.table_name = 'INQUIRY_PROSPECT'
    AND e.address_type =
    NVL ((SELECT gg.address_type
    FROM ugradadm.address gg
    WHERE gg.address_type =
    DECODE (f.mailpref,
    'Home', 'HOME',
    'Best', 'LOCAL',
    'HOME'
    AND gg.table_name = 'INQUIRY_PROSPECT'
    AND gg.APPL_ID = ip.appl_id
    AND((gg.address_type='LOCAL' AND NVL(gg.address_expir_date,sysdate)>sysdate)
    OR gg.address_type='HOME')),
    'HOME'
    AND f.batchid = :Batch_ID
    This report when bursted sends an email with the layout template as html body.
    The EMAIL configuration is set with a server Port number and its host address.

  • T.37 onramp fax sometimes sends empty attachment

    We have T.37 onramp fax set up with incoming calls arriving on a T1 line into a Cisco 2811, and SMTP emails with fax attachments going out to our custom mailserver.  We have many of these systems in the field.  Most of the time onramp faxes work fine, but we sometimes see the 2811 sending an empty attachment to the mailserver.  We have captured the incoming audio and decoded the fax using the Asterisk PBX utilities, with no errors at all.
    What could cause a 2811 to send an empty fax attachment even though the incoming fax is good?
    Here is the SMTP conversation (with names and numbers changed) -- red from the 2811, blue from the mailserver:
    220-svr02.company.com Simple Mail Transfer Service Ready
    220 ESMTP spoken here.
    EHLO faxgateway.company.com
    250-svr02.company.com
    250-CHUNKING
    250-DSN
    250-AUTH CRAM-MD5 LOGIN PLAIN
    250-AUTH=CRAM-MD5 LOGIN PLAIN
    250-X-DCL-SOURCE
    250-X-DCL-CALLID
    250-X-DCL-DSN
    250-X-DCL-REPLACE
    250-X-DCL-TRANSCRIPT
    250-X-DCL-SENT-ITEMS
    250-X-DCL-GHOST
    250-X-MSW-NOTIFY-SUPPRESS
    250-X-MSW-OP
    250 SIZE 0
    MAIL FROM:<[email protected]>
    250 OK
    RCPT TO:<[email protected]>
    250 OK
    DATA
    354 Start mail input, end with <CRLF>.<CRLF>
    Received:  by faxgateway.company.com for <[email protected]> (with Cisco NetWorks); Thu, 21 Nov 2013 16:22:01 -0500
    To: "1231231234" <[email protected]>
    Message-ID: <[email protected]>
    Date: Thu, 21 Nov 2013 16:22:01 -0500
    Subject: Fax
    X-Mailer: Technical Support: http://www.cisco
    MIME-Version: 1.0
    Content-Type: multipart/fax-message;
    boundary="yradnuoB=_7FCF2013162201695.faxgateway.company.com"
    From: "2342342345" <[email protected]>
    X-Account-Id: 0
    --yradnuoB=_7FCF2013162201695.faxgateway.company.com
    Content-ID: <[email protected]>
    Content-Type: image/tiff; name="Cisco_fax.tif"; application=faxbw
    Content-Disposition: attachment
    Content-Transfer-Encoding: base64
    --yradnuoB=_7FCF2013162201695.faxgateway.company.com--
    550 Fax message contains 0 pages
    Note that our custom mailserver rejects these empty fax attachments because we want the sending fax machine to see a failure in this case.  (If the mailserver were to accept the empty attachment, then the sender would see success but the receiver would receive no fax.)
    The 2811 is running IOS 12.4(25d) and non-default DSP software 26.4.501 (updated to fix a problem with the DIS tones).  But we've been seeing this problem since 12.4(6)T7 with no DSP firmware patch.
    We've enabled all the relevant fax debug logs we can find, and here's the debug output for a 'zero-page fax' call from the point where the T1 connection is established, down to the point where the empty attachment is sent and the mailserver rejects it (names and numbers changed as before):
    Nov 21 21:21:53.511: ISDN Se1/0:23 Q931: TX -> CALL_PROC pd = 8  callref = 0xAA14
            Channel ID i = 0xA98382
                    Exclusive, Channel 2
    Nov 21 21:21:53.511: ISDN Se1/0:23 Q931: TX -> CONNECT pd = 8  callref = 0xAA14
    Nov 21 21:21:53.539: ISDN Se1/0:23 Q931: RX <- CONNECT_ACK pd = 8  callref = 0x2A14
    Nov 21 21:21:53.543: %ISDN-6-CONNECT: Interface Serial1/0:1 is now connected to N/A N/A
    Nov 21 21:21:56.511: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
       CSI_PACKET(1231231234)
       DIS_PACKET(speed=5, resolution=1, encoding=1)
    Nov 21 21:21:56.511: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
       fax2_response_receive, PROCESSING
    Nov 21 21:21:59.399: //50796/C6DA8CB3B86D/FMSP/t30_rx_flag:
       received flag of modulation: 0
    Nov 21 21:21:59.399: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
       fax2_response_receive, PROCESSING
    Nov 21 21:21:59.739: //50796/C6DA8CB3B86D/FMSP/t30_rx_flag:
       received flag of modulation: 0
    Nov 21 21:22:00.719: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
       fax2_response_receive, PROCESSING
    Nov 21 21:22:01.311: //50796/C6DA8CB3B86D/FMSP/fax2_response_receive:
       msg dump (size=23):
       FF C0 C2 1C EC 8C 2C 8C 2C 4C 6C AC 4C 04 04 04 04 04 04 04
       04 04 04
    Nov 21 21:22:01.311: //50796/C6DA8CB3B86D/FMSP/fax2_response_receive:
       received=TSI,  remote id string:=          2342342345
    Nov 21 21:22:01.311: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
       fax2_response_receive, PROCESSING
    Nov 21 21:22:01.407: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
       fax2_response_receive, PROCESSING
    Nov 21 21:22:01.647: //50796/C6DA8CB3B86D/FMSP/fax2_response_receive:
       msg dump (size=10):
       FF C8 C1 00 45 1F 01 01 01 00
    Nov 21 21:22:01.647: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
       fax2_response_receive, PROCESSING
    Nov 21 21:22:01.691: //50796/C6DA8CB3B86D/FMSP/fax2_response_receive:
       in response receive WAIT FOR CD
    Nov 21 21:22:01.691: //50796/C6DA8CB3B86D/CCAPI/cc_api_event_indication:
       Event=36, Call Id=50796
    Nov 21 21:22:01.691: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
       received DCS_PACKET, BR=9, resolution=0,encoding=1, remote_id_string=          2342342345
    Nov 21 21:22:01.691: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
       wait for ready for data from application
    Nov 21 21:22:01.691: //50796/C6DA8CB3B86D/FOIP_ON/lapp_on_application:
       Event(Tag=36, Name=CC_EV_FROM_FMSP_ON_CALL_DETAIL, Disposition=0)
       Call Record(Call State=LAPP_ON_CS_FMSP_CALL_DETAIL(2))
    Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_validate_context:exit@984
    Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_msp_event:
       Event(Tag=36, Name=CC_EV_FROM_FMSP_ON_CALL_DETAIL)
    Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_setup_mspi:
       Prepare MSPI Call Setup Request
    Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_setup_mspi:
       Envelope [email protected]
    Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_setup_mspi:
       Envelope [email protected]
    Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_setup_mspi:
       RFC822 To Comment=1231231234
    Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_setup_mspi:
       Faxmail Subject=Fax
    Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_setup_mspi:
       Disposition Notification=
    Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_setup_mspi:
       Originator TSI=RFC822 From Comment=2342342345
    Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_setup_mspi:
       Auth/Account ID: `0'
    Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_setup_mspi:
       Call Setup Request To MSPI
    Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/CCAPI/ccCallSetupRequest:
       Destination=, Calling IE Present=FALSE, Mode=0,
       Outgoing Dial-peer=3, Params=0x45E136F0, Progress Indication=NULL(0)
    Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/CCAPI/ccCallSetupRequest:
       Destination Pattern=.T, Called Number=1231231234, Digit Strip=FALSE
    Nov 21 21:22:01.691: //50795/C6DA8CB3B86D/CCAPI/ccCallSetupRequest:
       Calling Number=(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
       Called Number=1231231234(TON=Unknown, NPI=Unknown),
       Redirect Number=, Display Info=
       Account Number=, Final Destination Flag=TRUE,
       Guid=C6DA8CB3-5229-11E3-B86D-58BC273896C0, Outgoing Dial-peer=3
    Nov 21 21:22:01.695: //50795/C6DA8CB3B86D/CCAPI/cc_api_display_ie_subfields:
       ccCallSetupRequest:
       cisco-username=
       ----- ccCallInfo IE subfields -----
       cisco-ani=
       cisco-anitype=0
       cisco-aniplan=0
       cisco-anipi=0
       cisco-anisi=0
       dest=1231231234
       cisco-desttype=0
       cisco-destplan=0
       cisco-rdie=FFFFFFFF
       cisco-rdn=
       cisco-rdntype=-1
       cisco-rdnplan=-1
       cisco-rdnpi=-1
       cisco-rdnsi=-1
       cisco-redirectreason=-1
    Nov 21 21:22:01.695: //50795/C6DA8CB3B86D/CCAPI/ccIFCallSetupRequestPrivate:
       Interface=0x453B5564, Interface Type=19, Destination=, Mode=0x0,
       Call Params(Calling Number=(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Al                                                                                      lowed),
       Called Number=1231231234(TON=Unknown, NPI=Unknown), Calling Translated=FALSE,
       Subscriber Type Str=RegularLine, FinalDestinationFlag=TRUE, Outgoing Dial-peer=3, Call Count                                                                                       On=FALSE,
       Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Application Call Id=                                                                                      )
    Nov 21 21:22:01.695: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_new_context_guid:exit@2190
    Nov 21 21:22:01.695: //50797/C6DA8CB3B86D/MSPI_ON/mspi_call_setup_request:
       Outgoing Peer Tag=3
       Envelope [email protected]
       Envelope [email protected]
       Mime Outer Type=2
    Nov 21 21:22:01.695: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_open:
       [email protected], [email protected]
    Nov 21 21:22:01.695: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_open:exit@1881
    Nov 21 21:22:01.695: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_add_headers:
       from_comment=2342342345
    Nov 21 21:22:01.695: //50795/C6DA8CB3B86D/VTSP:(1/0:23):1:1:1/vtsp_spi_event_handler:
       Event Category=1, Event=138
    Nov 21 21:22:01.695: //50797/C6DA8CB3B86D/CCAPI/ccIFCallSetupRequestPrivate:
       SPI Call Setup Request Is Success; Interface Type=19, FlowMode=1
    Nov 21 21:22:01.695: //50797/C6DA8CB3B86D/CCAPI/ccCallSetContext:
       Context=0x44047884
    Nov 21 21:22:01.695: //50797/C6DA8CB3B86D/FOIP_ON/lapp_on_setup_mspi:exit@791
    Nov 21 21:22:01.695: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_conference_fmsp_dmsp:
        Starting Conference with FMSP and DMSP
    Nov 21 21:22:01.695: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_conference_fmsp_dmsp:
       Tiff File Created; Time=2013:11:21 16:22:01
    Nov 21 21:22:01.699: //50798/C6DA8CB3B86D/DMSP/docmsp_call_setup_request:
       ramp data dir=ONRAMP, conf dir=DEST
    Nov 21 21:22:01.699: //50796/xxxxxxxxxxxx/CCAPI/ccConferenceCreate:
       (confID=0x440478F0, callID1=0xC66C, callID2=0xC66E, tag=0x0)
    Nov 21 21:22:01.699: //50796/C6DA8CB3B86D/CCAPI/ccConferenceCreate:
       Conference Id=0x440478F0, Call Id1=50796, Call Id2=50798, Tag=0x0
    Nov 21 21:22:01.699: //50796/xxxxxxxxxxxx/CCAPI/cc_api_bridge_done:
       Conference Id=0x8B2C, Source Interface=0x45F255A0, Source Call Id=50796,
       Destination Call Id=50798, Disposition=0x0, Tag=0x0
    Nov 21 21:22:01.699: //50796/C6DA8CB3B86D/CCAPI/cc_api_caps_ind:
       Destination Interface=0x45F2554C, Destination Call Id=50798, Source Call Id=50796,
       Caps(Codec=0x4, Fax Rate=0x2, Vad=0x2,
       Modem=0x0, Codec Bytes=20, Signal Type=2)
    Nov 21 21:22:01.699: //50796/C6DA8CB3B86D/CCAPI/cc_api_caps_ind:
       Caps(Playout Mode=1, Playout Initial=60(ms), Playout Min=40(ms),
       Playout Max=250(ms), Fax Nom=300(ms))
    Nov 21 21:22:01.699: //50798/C6DA8CB3B86D/DMSP/docmsp_caps_ind:
       CallId=50798, srcCallId=50796
    Nov 21 21:22:01.699: //50798/C6DA8CB3B86D/DMSP/docmsp_bridge:
       conf id=0x8B2C, srcCallId=50798, dstCallId=50796,
       ramp data dir=ONRAMP, conf dir=DEST, encode out=0
    Nov 21 21:22:01.699: //50798/xxxxxxxxxxxx/CCAPI/cc_api_bridge_done:
       Conference Id=0x8B2C, Source Interface=0x45F2554C, Source Call Id=50798,
       Destination Call Id=50796, Disposition=0x0, Tag=0x0
    Nov 21 21:22:01.699: //50796/C6DA8CB3B86D/CCAPI/cc_generic_bridge_done:
       Conference Id=0x8B2C, Source Interface=0x45F2554C, Source Call Id=50798,
       Destination Call Id=50796, Disposition=0x0, Tag=0x0
    Nov 21 21:22:01.699: //50798/C6DA8CB3B86D/DMSP/docmsp_bridge:
       Bridge done
    Nov 21 21:22:01.699: //50796/C6DA8CB3B86D/CCAPI/ccConferenceCreate:
       Call Entry(Conference Id=0x8B2C, Destination Call Id=50795)
    Nov 21 21:22:01.699: //50798/C6DA8CB3B86D/CCAPI/ccConferenceCreate:
       Call Entry(Conference Id=0x8B2C, Destination Call Id=50796)
    Nov 21 21:22:01.699: //50798/C6DA8CB3B86D/CCAPI/ccCallSetContext:
       Context=0x44047884
    Nov 21 21:22:01.699: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_change_state:
       Old State=LAPP_ON_CS_FMSP_CALL_DETAIL(2),
       New State=LAPP_ON_CS_FMSP_DMSP_CONFERENCING(3)
    Nov 21 21:22:01.699: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_msp_event:exit@2079
    Nov 21 21:22:01.699: //50796/C6DA8CB3B86D/FOIP_ON/lapp_on_application:
       Event(Tag=29, Name=CC_EV_CONF_CREATE_DONE, Disposition=0)
       Call Record(Call State=LAPP_ON_CS_FMSP_DMSP_CONFERENCING(3))
    Nov 21 21:22:01.699: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_validate_context:exit@984
    Nov 21 21:22:01.699: //50796/C6DA8CB3B86D/FOIP_ON/lapp_on_conference_created:
       FMSP and DMSP Are Conferenced
    Nov 21 21:22:01.699: //50796/C6DA8CB3B86D/FOIP_ON/lapp_on_conference_created:
       Sending RECEIVE ENABLE to FMSP
    Nov 21 21:22:01.699: //50796/C6DA8CB3B86D/CCAPI/ccDeliverEvent:
       Event Category=0, Call Id=50796
    Nov 21 21:22:01.699: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_change_state:
       Old State=LAPP_ON_CS_FMSP_DMSP_CONFERENCING(3),
       New State=LAPP_ON_CS_FMSP_PAGE_ACCEPT_REQUESTED(4)
    Nov 21 21:22:01.699: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
       send CFR_PACKET
    Nov 21 21:22:01.703: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
       fax2_configure_rx_data, STILL_LOOKING, T2 timer not expired
    Nov 21 21:22:01.703: //50796/C6DA8CB3B86D/CCAPI/cc_process_notify_bridge_done:
       Conference Id=0x8B2C, Call Id1=50796, Call Id2=50798
    Nov 21 21:22:01.847: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_work_routine:
       socket 0 readable for first time
    Nov 21 21:22:01.863: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_work_routine:
       socket 0 readable for first time
    Nov 21 21:22:01.863: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
       (C)R: 220-svr02.company.com Simple Mail Transfer Service Ready
    Nov 21 21:22:01.863: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_work_routine:
       socket 0 readable for first time
    Nov 21 21:22:01.863: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
       (C)R: 220 ESMTP spoken here.
    Nov 21 21:22:01.863: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
       (C)S: EHLO faxgateway.company.com
    Nov 21 21:22:01.863: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:01.875: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
       (C)R: 250-svr02.company.com
    Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
       (C)R: 250-CHUNKING
    Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
       (C)R: 250-DSN
    Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
       (C)R: 250-AUTH CRAM-MD5 LOGIN PLAIN
    Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
       (C)R: 250-AUTH=CRAM-MD5 LOGIN PLAIN
    Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
       (C)R: 250-X-DCL-SOURCE
    Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
       (C)R: 250-X-DCL-CALLID
    Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
       (C)R: 250-X-DCL-DSN
    Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
       (C)R: 250-X-DCL-REPLACE
    Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
       (C)R: 250-X-DCL-TRANSCRIPT
    Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
       (C)R: 250-X-DCL-SENT-ITEMS
    Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
       (C)R: 250-X-DCL-GHOST
    Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
       (C)R: 250-X-MSW-NOTIFY-SUPPRESS
    Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
       (C)R: 250-X-MSW-OP
    Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
       (C)R: 250 SIZE 0
    Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
       (C)S: MAIL FROM:<[email protected]>
    Nov 21 21:22:01.879: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:01.895: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
       (C)R: 250 OK
    Nov 21 21:22:01.895: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
       (C)S: RCPT TO:<[email protected]>
    Nov 21 21:22:01.895: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:01.911: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
       (C)R: 250 OK
    Nov 21 21:22:01.911: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
       (C)R: 354 Start mail input, end with <CRLF>.<CRLF>
    Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
       (C)S: Received:  by faxgateway.company.com for <[email protected]> (with Cisco NetWorks); Thu, 21 Nov 2013 16:22:01 -0500
    Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
       (C)S: To: "1231231234" <[email protected]>
    Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
       (C)S: Message-ID: <[email protected]>
    Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
       (C)S: Date: Thu, 21 Nov 2013 16:22:01 -0500
    Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
       (C)S: Subject: Fax
    Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
       (C)S: X-Mailer: Technical Support: http://www.cisco
    Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
       (C)S: MIME-Version: 1.0
    Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
       (C)S: Content-Type: multipart/fax-message;
    Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
       (C)S:  boundary="yradnuoB=_7FCF2013162201695.faxgateway.company.com"
    Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
       (C)S: From: "2342342345" <[email protected]>
    Nov 21 21:22:01.927: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:01.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
       (C)S: X-Account-Id: 0
    Nov 21 21:22:01.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:02.695: //50797/C6DA8CB3B86D/MSPI_ON/mspi_check_connect:
       MMccb(Count=0)
    Nov 21 21:22:02.695: //50797/C6DA8CB3B86D/MSPI_ON/mspi_check_connect:
       SMTP Connected To The Server !
    Nov 21 21:22:02.695: //50797/C6DA8CB3B86D/CCAPI/cc_api_call_connected:
       Interface=0x453B5564, Data Bitmask=0x0, Progress Indication=NULL(0),
       Connection Handle=0
    Nov 21 21:22:02.695: //50797/C6DA8CB3B86D/CCAPI/cc_api_call_connected:
       Call Entry(Connected=TRUE, Responsed=TRUE, Retry Count=0)
    Nov 21 21:22:02.695: //50797/C6DA8CB3B86D/FOIP_ON/lapp_on_application:
       Event(Tag=8, Name=CC_EV_CALL_CONNECTED, Disposition=0)
       Call Record(Call State=LAPP_ON_CS_FMSP_PAGE_ACCEPT_REQUESTED(4))
    Nov 21 21:22:02.695: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_validate_context:exit@984
    Nov 21 21:22:02.695: //50797/C6DA8CB3B86D/FOIP_ON/lapp_on_call_connected:
       MSPI call connected:
       Start Conferencing DMSP and MSPI
    Nov 21 21:22:02.695: //50798/xxxxxxxxxxxx/CCAPI/ccConferenceCreate:
       (confID=0x440478F4, callID1=0xC66E, callID2=0xC66D, tag=0x0)
    Nov 21 21:22:02.695: //50798/C6DA8CB3B86D/CCAPI/ccConferenceCreate:
       Conference Id=0x440478F4, Call Id1=50798, Call Id2=50797, Tag=0x0
    Nov 21 21:22:02.695: //50798/C6DA8CB3B86D/DMSP/docmsp_bridge:
       conf id=0x8B2D, srcCallId=50798, dstCallId=50797,
       ramp data dir=ONRAMP, conf dir=SRC, encode out=0
    Nov 21 21:22:02.695: //50798/xxxxxxxxxxxx/CCAPI/cc_api_bridge_done:
       Conference Id=0x8B2D, Source Interface=0x45F2554C, Source Call Id=50798,
       Destination Call Id=50797, Disposition=0x0, Tag=0x0
    Nov 21 21:22:02.695: //50798/C6DA8CB3B86D/DMSP/docmsp_bridge:
       Bridge done
    Nov 21 21:22:02.695: //50797/C6DA8CB3B86D/MSPI/mspi_bridge:
       MMccb(State=CONNECTED, Type=Onramp), Destination Call Id=50798
    Nov 21 21:22:02.695: //50797/xxxxxxxxxxxx/CCAPI/cc_api_bridge_done:
       Conference Id=0x8B2D, Source Interface=0x453B5564, Source Call Id=50797,
       Destination Call Id=50798, Disposition=0x0, Tag=0x0
    Nov 21 21:22:02.695: //50798/C6DA8CB3B86D/CCAPI/cc_generic_bridge_done:
       Conference Id=0x8B2D, Source Interface=0x453B5564, Source Call Id=50797,
       Destination Call Id=50798, Disposition=0x0, Tag=0x0
    Nov 21 21:22:02.695: //50798/C6DA8CB3B86D/CCAPI/ccConferenceCreate:
       Call Entry(Conference Id=0x8B2D, Destination Call Id=50796)
    Nov 21 21:22:02.695: //50797/C6DA8CB3B86D/CCAPI/ccConferenceCreate:
       Call Entry(Conference Id=0x8B2D, Destination Call Id=50795)
    Nov 21 21:22:02.695: //50797/C6DA8CB3B86D/CCAPI/ccCallSetContext:
       Context=0x44047884
    Nov 21 21:22:02.695: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_call_connected:exit@2508
    Nov 21 21:22:02.695: //50798/C6DA8CB3B86D/FOIP_ON/lapp_on_application:
       Event(Tag=29, Name=CC_EV_CONF_CREATE_DONE, Disposition=0)
       Call Record(Call State=LAPP_ON_CS_FMSP_PAGE_ACCEPT_REQUESTED(4))
    Nov 21 21:22:02.695: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_validate_context:exit@984
    Nov 21 21:22:02.699: //50798/C6DA8CB3B86D/CCAPI/cc_process_notify_bridge_done:
       Conference Id=0x8B2D, Call Id1=50798, Call Id2=50797
    Nov 21 21:22:06.487: //50796/C6DA8CB3B86D/FMSP/t30_rx_flag:
       received flag of modulation: 0
    Nov 21 21:22:06.487: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
       fax2_configure_rx_data, DETECTED_COMMAND
    Nov 21 21:22:06.487: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
       fax2_command_receive, NO_COMMAND, T2 timer not expired
    Nov 21 21:22:12.275: //50796/C6DA8CB3B86D/FMSP/t30_rx_flag:
       received flag of modulation: 0
    Nov 21 21:22:13.207: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
       fax2_command_receive, PROCESSING
    Nov 21 21:22:13.267: //50796/C6DA8CB3B86D/FMSP/fax2_command_receive:
       msg dump (size=3):
       FF C8 F4
    Nov 21 21:22:13.267: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
       fax2_command_receive, PROCESSING
    Nov 21 21:22:13.287: //50796/C6DA8CB3B86D/FMSP/fax2_phaseB_receive:
       fax2_command_receive, RECEIVED_COMMAND
    Nov 21 21:22:13.287: //50796/C6DA8CB3B86D/FMSP/fax2_phaseD_receive:
       received EOP
    Nov 21 21:22:13.287: //50798/C6DA8CB3B86D/DMSP/docmsp_xmit:
       srcCallId=50796, dstCallId=50798, direction=0
    Nov 21 21:22:13.287: //50796/C6DA8CB3B86D/FMSP/fax2_phaseD_receive:
       waiting for page acceptance by the application
    Nov 21 21:22:13.287: //50797/C6DA8CB3B86D/MSPI_ON/mspi_xmit:
       MMccb(State=CONFERENCED, Type=Onramp, Buffer Count=0),
       Source Call Id=50798
    Nov 21 21:22:13.287: //50797/C6DA8CB3B86D/MSPI_ON/mspi_onramp_xmit:
       EOD Received
    Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
       (C)S: --yradnuoB=_7FCF2013162201695.faxgateway.company.com
    Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
       (C)S: Content-ID: <[email protected]>
    Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
       (C)S: Content-Type: image/tiff; name="Cisco_fax.tif"; application=faxbw
    Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
       (C)S: Content-Disposition: attachment
    Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
       (C)S: Content-Transfer-Encoding: base64
    Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_send_data_cisco:exit@849
    Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
       (C)S: --yradnuoB=_7FCF2013162201695.faxgateway.company.com--
    Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_work_routine:
       Sending terminating dot ...(socket=0)
    Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_writeln:
       (C)S: .
    Nov 21 21:22:13.931: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_write:
       return code=0
    Nov 21 21:22:13.959: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_getln:
       (C)R: 550 Fax message contains 0 pages
    Nov 21 21:22:13.959: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_work_routine:
       error in SMTP server's response to terminating "."
    Nov 21 21:22:13.959: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_work_routine:
       ERROR, socket=0
    Nov 21 21:22:13.959: //-1/C6DA8CB3B86D/SMTPC/esmtp_client_engine_work_routine:
       Finishing, socket=-1, bytes send=1091
    Nov 21 21:22:13.959: //50797/C6DA8CB3B86D/MSPI_ON/mspi_onramp_buff_finished_callback:
       MMccb(Call State=CONFERENCED, Buffer Count=1)
    Nov 21 21:22:13.959: //50797/C6DA8CB3B86D/MSPI_ON/mspi_onramp_buff_finished_callback:
       EOD Received; Status=1
    Nov 21 21:22:13.959: //50797/C6DA8CB3B86D/MSPI_ON/mspi_onramp_buff_finished_callback:
       Message [email protected]
    Nov 21 21:22:13.959: //50797/C6DA8CB3B86D/MSPI_ON/mspi_onramp_buff_finished_callback:
       Status=1
    Nov 21 21:22:13.959: //50797/C6DA8CB3B86D/MSPI/mspi_set_disconnect_text:
       MMccb(Disconnect Cause=network out of order (38): SMTP client engine not completed)
    Nov 21 21:22:13.959: //50797/C6DA8CB3B86D/CCAPI/cc_api_call_disconnected:
       Cause Value=38, Interface=0x453B5564, Call Id=50797
    Nov 21 21:22:13.959: //50797/C6DA8CB3B86D/CCAPI/cc_api_call_disconnected:
       Call Entry(Responsed=TRUE, Cause Value=38, Retry Count=0)
    Nov 21 21:22:13.959: //50797/C6DA8CB3B86D/FOIP_ON/lapp_on_application:
       Event(Tag=11, Name=CC_EV_CALL_DISCONNECTED, Disposition=0)
       Call Record(Call State=LAPP_ON_CS_FMSP_PAGE_ACCEPT_REQUESTED(4))
    Nov 21 21:22:13.963: //50795/C6DA8CB3B86D/FOIP_ON/lapp_on_validate_context:exit@984

    Still not solved.  Cisco support suggested adding the config command 'mta send success-fax-only' which is supposed to prevent sending empty emails or partial faxes, however there's a bug that means that has no effect IOS 12.4.  We're looking at upgrading to 15.1(4)M8 which has the fix, but that will take some time.
    Your problem sounds slightly different.  See if you can get a network capture of the SMTP conversation with the target mailserver, to see if something's going wrong there.

  • Sending empty files using SFTP Adapter

    I am trying to send empty files using SFTP adapter. The interface has to send the file whether its empty file or containing data using SFTP adapter. I am using BizTalk Server 2013 R2. Is it a bug or the hotfix is already there for this issue.

    The issue here is not your SFTP not able to send 0KB files, but the file receive adapter that is receiving the file. The file adapter deletes 0 KB files and doest not transmit it further.
    If u have a ftp receive for example you should be able to send 0KB files.
    If u have a custom file receive adapter , is it handling 0KB files ?
    Regards &lt;br/&gt; When you see answers and helpful posts,&lt;br/&gt; please click Vote As Helpful, Propose As Answer, and/or Mark As Answer

  • No client certificate available, sending empty certificate message

    Dear Experts,
        I am trying to establish SSL client certificate connection to external partner. What puzzles me is that the certificate is not picked up by SAP PI. The intermediate and root CA for the partner are OU=www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD.(c)97 VeriSign,OU=VeriSign International Server CA - Class 3,OU=VeriSign, Inc.,O=VeriSign Trust Network and OU=Class 3 Public Primary Certification Authority,O=VeriSign, Inc.,C=US, respectively. You will be able to spot them in the Accepted Certificate Authority list, yet PI insists on sending empty certificate.
        Below is trace gathered from J2EE default trace. Please help shed some light
    Date : 11/16/2011
    Time : 8:49:11:423
    Message : additional info ssl_debug(9): Starting handshake (iSaSiLk 4.3)...
    ssl_debug(9): Sending v3 client_hello message to preprod.connect.elemica.com:443, requesting version 3.2...
    ssl_debug(9): Received v3 server_hello handshake message.
    ssl_debug(9): Server selected SSL version 3.1.
    ssl_debug(9): Server created new session 22:E7:C0:9E:C1:D2:78:83...
    ssl_debug(9): CipherSuite selected by server: TLS_RSA_WITH_AES_256_CBC_SHA
    ssl_debug(9): CompressionMethod selected by server: NULL
    ssl_debug(9): Received certificate handshake message with server certificate.
    ssl_debug(9): Server sent a 1024 bit RSA certificate, chain has 2 elements.
    ssl_debug(9): ChainVerifier: No trusted certificate found, OK anyway.
    ssl_debug(9): Received certificate_request handshake message.
    ssl_debug(9): Accepted certificate types: RSA, DSA
    ssl_debug(9): Accepted certificate authorities:
    ssl_debug(9):   CN=QuoVadis Global SSL ICA,OU=www.quovadisglobal.com,O=QuoVadis Limited,C=BM
    ssl_debug(9):   CN=AAA Certificate Services,O=Comodo CA Limited,L=Salford,ST=Greater Manchester,C=GB
    ssl_debug(9):   CN=CSF - Classe III - Sign et Crypt,OU=Certification Professionnelle,O=Autorite Consulaire
    ssl_debug(9):   CN=GTE CyberTrust Global Root,OU=GTE CyberTrust Solutions, Inc.,O=GTE Corporation,C=US
    ssl_debug(9):   CN=Entrust.net Certification Authority (2048),OU=(c) 1999 Entrust.net Limited,OU=www.entrust.net/CPS_2048 incorp. by ref. (limits liab.),O=Entrust.net
    ssl_debug(9):   CN=DPWN SSL CA I2 PS,OU=I2 PS,O=Deutsche Post World Net
    ssl_debug(9):   CN=CSF,O=Autorite Consulaire
    ssl_debug(9):   C=BE,O=GlobalSign nv-sa,OU=RootSign Partners CA,CN=GlobalSign RootSign Partners CA
    ssl_debug(9):   CN=Dell Inc. Enterprise Utility CA1,O=Dell Inc.
    ssl_debug(9):   EMAIL=premium-server(a)thawte.com,CN=Thawte Premium Server CA,OU=Certification Services Division,O=Thawte Consulting cc,L=Cape Town,ST=Western Cape,C=ZA
    ssl_debug(9):   CN=TC TrustCenter Class 2 L1 CA XI,OU=TC TrustCenter Class 2 L1 CA,O=TC TrustCenter GmbH,C=DE
    ssl_debug(9):   CN=VeriSign Class 3 Extended Validation SSL SGC CA,OU=Terms of use at https://www.verisign.com/rpa (c)06,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
    ssl_debug(9):   OU=VeriSign Trust Network,OU=(c) 1998 VeriSign, Inc. - For authorized use only,OU=Class 3 Public Primary Certification Authority - G2,O=VeriSign, Inc.,C=US
    ssl_debug(9):   CN=TC TrustCenter SSL CA I,OU=TC TrustCenter SSL CA,O=TC TrustCenter GmbH,C=DE
    ssl_debug(9):   CN=Entrust Root Certification Authority,OU=(c) 2006 Entrust, Inc.,OU=www.entrust.net/CPS is incorporated by reference,O=Entrust, Inc.,C=US
    ssl_debug(9):   CN=VeriSign Class 3 International Server CA - G3,OU=Terms of use at https://www.verisign.com/rpa (c)10,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
    ssl_debug(9):   CN=Meijer ipprod,OU=IT,OU=Merch,O=Meijer Stores Limited,L=Walker,ST=MI,C=US
    ssl_debug(9):   CN=COMODO Certification Authority,O=COMODO CA Limited,L=Salford,ST=Greater Manchester,C=GB
    ssl_debug(9):   OU=www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD.(c)97 VeriSign,OU=VeriSign International Server CA - Class 3,OU=VeriSign, Inc.,O=VeriSign Trust Network
    ssl_debug(9):   CN=UTN - DATACorp SGC,OU=http://www.usertrust.com,O=The USERTRUST Network,L=Salt Lake City,ST=UT,C=US
    ssl_debug(9):   CN=Deutsche Telekom CA 5,OU=Trust Center Deutsche Telekom,O=T-Systems Enterprise Services GmbH,C=DE
    ssl_debug(9):   CN=TC TrustCenter Class 2 CA II,OU=TC TrustCenter Class 2 CA,O=TC TrustCenter GmbH,C=DE
    ssl_debug(9):   CN=VeriSign Class 3 Secure Server CA - G2,OU=Terms of use at https://www.verisign.com/rpa (c)09,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
    ssl_debug(9):   OU=www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD.(c)97 VeriSign,OU=VeriSign International Server CA - Class 3,OU=VeriSign, Inc.,O=VeriSign Trust Network
    ssl_debug(9):   CN=Thawte SGC CA,O=Thawte Consulting (Pty) Ltd.,C=ZA
    ssl_debug(9):   CN=Bertschi CA,O=Bertschi AG (Schweiz),L=Duerrenaesch,ST=Switzerland,C=CH
    ssl_debug(9):   CN=Cybertrust SureServer CA,O=GlobalSign Inc
    ssl_debug(9):   CN=VeriSign Class 3 Secure Server CA,OU=Terms of use at https://www.verisign.com/rpa (c)05,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
    ssl_debug(9):   EMAIL=server-certs(a)thawte.com,CN=Thawte Server CA,OU=Certification Services Division,O=Thawte Consulting cc,L=Cape Town,ST=Western Cape,C=ZA
    ssl_debug(9):   CN=Mark Van Hamme,O=Brain2 BVBA,L=Brussels,ST=Brabant,C=BE
    ssl_debug(9):   CN=DigiCert High Assurance EV Root CA,OU=www.digicert.com,O=DigiCert Inc,C=US
    ssl_debug(9):   EMAIL=bis.at(a)siemens.com,CN=bis.siemens.at,OU=SBS ORS EDO,O=Siemens Business Services,L=Vienna,ST=Vienna,C=AT
    ssl_debug(9):   CN=VeriSign Class 1 Public Primary Certification Authority - G3,OU=(c) 1999 VeriSign, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
    ssl_debug(9):   CN=mail2.adr-logistics.hu,O=ADR Logistics Kft.,L=Gyu00E1l,ST=Pest,C=HU
    ssl_debug(9):   EMAIL=brent.kemp(a)sscoop.com,CN=bacchusdevp.sscoop.com,OU=IS,O=Southern States Cooperative Inc,L=Richmond,ST=VA,C=US
    ssl_debug(9):   CN=Cybertrust SureServer Standard Validation CA,O=Cybertrust Inc
    ssl_debug(9):   OU=Go Daddy Class 2 Certification Authority,O=The Go Daddy Group, Inc.,C=US
    ssl_debug(9):   CN=Certipost E-Trust Secondary Normalised CA for Legal Persons,O=Certipost s.a./n.v.,C=BE
    ssl_debug(9):   EMAIL=cert(a)bit-serv.de,CN=BIT-SERV GmbH Root CA,O=BIT-SERV GmbH,C=DE
    ssl_debug(9):   CN=SAP_elemica_tester
    ssl_debug(9):   CN=GeoTrust Global CA,O=GeoTrust Inc.,C=US
    ssl_debug(9):   OU=Class 1 Public Primary Certification Authority,O=VeriSign, Inc.,C=US
    ssl_debug(9):   CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE
    ssl_debug(9):   CN=Montova Root CA,OU=Root CA,O=Montova,C=BE
    ssl_debug(9):   CN=Baltimore CyberTrust Root,OU=CyberTrust,O=Baltimore,C=IE
    ssl_debug(9):   CN=Dell Inc. Enterprise CA,O=Dell Inc.
    ssl_debug(9):   CN=COMODO High-Assurance Secure Server CA,O=COMODO CA Limited,L=Salford,ST=Greater Manchester,C=GB
    ssl_debug(9):   EMAIL=support(a)tamgroup.com,OU=Engineering,O=Tamgroup,ST=California,L=San Anselmo,C=US,CN=Tamgroup
    ssl_debug(9):   CN=GlobalSign Organization Validation CA,O=GlobalSign,OU=Organization Validation CA
    ssl_debug(9):   CN=Certinomis AC 1 u00E9toile,OU=0002 433998903,O=Certinomis,C=FR
    ssl_debug(9):   CN=GlobalSign ServerSign CA,OU=ServerSign CA,O=GlobalSign nv-sa,C=BE
    ssl_debug(9):   CN=QuoVadis Root CA 2,O=QuoVadis Limited,C=BM
    ssl_debug(9):   CN=AddTrust Class 1 CA Root,OU=AddTrust TTP Network,O=AddTrust AB,C=SE
    ssl_debug(9):   CN=Equifax Secure Global eBusiness CA-1,O=Equifax Secure Inc.,C=US
    ssl_debug(9):   CN=GlobalSign Organization Validation CA,O=GlobalSign,OU=Organization Validation CA
    ssl_debug(9):   CN=thawte Primary Root CA,OU=(c) 2006 thawte, Inc. - For authorized use only,OU=Certification Services Division,O=thawte, Inc.,C=US
    ssl_debug(9):   CN=Certipost E-Trust Primary Normalised CA,O=Certipost s.a./n.v.,C=BE
    ssl_debug(9):   CN=Thawte DV SSL CA,OU=Domain Validated SSL,O=Thawte, Inc.,C=US
    ssl_debug(9):   OU=Equifax Secure Certificate Authority,O=Equifax,C=US
    ssl_debug(9):   CN=preprod.connect.elemica.com,OU=CONNECTED SOLUTIONS,O=Elemica,L=Wayne,ST=Pennsylvania,C=US
    ssl_debug(9):   CN=Certinomis - Autoritu00E9 Racine,OU=0002 433998903,O=Certinomis,C=FR
    ssl_debug(9):   CN=DPWN Root CA R2 PS,OU=IT Services,O=Deutsche Post World Net,DC=com
    ssl_debug(9):   CN=Thawte Test CA Root,OU=TEST TEST TEST,O=Thawte Certification,ST=FOR TESTING PURPOSES ONLY,C=ZA
    ssl_debug(9):   OU=Class 3 Public Primary Certification Authority,O=VeriSign, Inc.,C=US
    ssl_debug(9):   EMAIL=santiago.tolosa(a)eu.rhodia.com,CN=Rhodia Development CA,OU=ISF - WARTE,O=Rhodia,L=La Villette,ST=France,C=FR
    ssl_debug(9):   CN=Entrust.net Secure Server Certification Authority,OU=(c) 1999 Entrust.net Limited,OU=www.entrust.net/CPS incorp. by ref. (limits liab.),O=Entrust.net,C=US
    ssl_debug(9):   CN=DigiCert High Assurance CA-3,OU=www.digicert.com,O=DigiCert Inc,C=US
    ssl_debug(9):   CN=Groep H. Essers TEST (99805D6DA33FCC1700010002),O=Montova,C=BE
    ssl_debug(9):   serialNumber=07969287,CN=Go Daddy Secure Certification Authority,OU=http://certificates.godaddy.com/repository,O=GoDaddy.com, Inc.,L=Scottsdale,ST=Arizona,C=US
    ssl_debug(9):   CN=VeriSign Class 3 Secure Server 1024-bit CA - G2,OU=Terms of use at https://www.verisign.com/rpa (c)09,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
    ssl_debug(9):   serialNumber=10688435,CN=Starfield Secure Certification Authority,OU=http://certificates.starfieldtech.com/repository,O=Starfield Technologies, Inc.,L=Scottsdale,ST=Arizona,C=US
    ssl_debug(9):   CN=Conextrade,OU=Swisscom IT,O=Swisscom AG,L=Zurich,ST=Zurich,C=CH,EMAIL=ccc.eTrade(a)swisscom.com
    ssl_debug(9):   CN=b2bproto.basf-corp.com,OU=Corporate IS,O=BASF Corporation,L=Mount Olive,ST=New Jersey,C=US
    ssl_debug(9):   CN=GlobalSign Domain Validation CA - G2,O=GlobalSign nv-sa,C=BE
    ssl_debug(9):   CN=Swisscom Root CA 1,OU=Digital Certificate Services,O=Swisscom,C=ch
    ssl_debug(9):   CN=GeoTrust DV SSL CA,OU=Domain Validated SSL,O=GeoTrust Inc.,C=US
    ssl_debug(9):   EMAIL=!sysadmin(a)elemica.com,CN=www.elemica.com,OU=Connected Solutions,O=Elemica, Inc,L=Wayne,ST=Pennsylvania,C=US
    ssl_debug(9):   CN=GeoTrust SSL CA,O=GeoTrust, Inc.,C=US
    ssl_debug(9):   CN=RapidSSL CA,O=GeoTrust, Inc.,C=US
    ssl_debug(9):   CN=Entrust Certification Authority - L1E,OU=(c) 2009 Entrust, Inc.,OU=www.entrust.net/rpa is incorporated by reference,O=Entrust, Inc.,C=US
    ssl_debug(9):   CN=EAS,O=COMPUDATA EDI Dienstleister,C=CH,EMAIL=helpdesk.dl(a)compudata.ch
    ssl_debug(9):   CN=GlobalSign Domain Validation CA,O=GlobalSign nv-sa,OU=Domain Validation CA,C=BE
    ssl_debug(9):   CN=GlobalSign Primary Secure Server CA,OU=Primary Secure Server CA,O=GlobalSign nv-sa,C=BE
    ssl_debug(9):   CN=AddTrust External CA Root,OU=AddTrust External TTP Network,O=AddTrust AB,C=SE
    ssl_debug(9):   CN=Entrust Root Certification Authority,OU=(c) 2006 Entrust, Inc.,OU=www.entrust.net/CPS is incorporated by reference,O=Entrust, Inc.,C=US
    ssl_debug(9):   CN=Thawte SSL CA,O=Thawte, Inc.,C=US
    ssl_debug(9):   CN=Entrust Certification Authority - L1C,OU=(c) 2009 Entrust, Inc.,OU=www.entrust.net/rpa is incorporated by reference,O=Entrust, Inc.,C=US
    ssl_debug(9):   CN=UTN-USERFirst-Hardware,OU=http://www.usertrust.com,O=The USERTRUST Network,L=Salt Lake City,ST=UT,C=US
    ssl_debug(9):   EMAIL=vladimir.polak(a)esa.ch,CN=Vladimir Polak,O=Einkaufsorganisation des Schweizerischen Auto- und Motorfahrzeuggewerbes,C=CH
    ssl_debug(9):   CN=IT Directions and Strategies,OU=ITDS EDI,ST=WI,C=US,L=Hartland,EMAIL=aklumpp(a)itdsllc.com,O=ITDS EDI
    ssl_debug(9):   CN=Entrust Certification Authority - L1B,OU=(c) 2008 Entrust, Inc.,OU=www.entrust.net/CPS is incorporated by reference,OU=CPS CONTAINS IMPORTANT LIMITATIONS OF WARRANTIES AND LIABILITY,OU=AND ADDITIONAL TERMS GOVERNING USE AND RELIANCE,O=Entrust, Inc.,C=US
    ssl_debug(9):   CN=GlobalSign Organization Validation CA - G2,O=GlobalSign nv-sa,C=BE
    ssl_debug(9):   CN=VeriSign Class 1 Individual Subscriber CA - G3,OU=Persona Not Validated,OU=Terms of use at https://www.verisign.com/rpa (c)09,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
    ssl_debug(9):   CN=VeriSign Class 1 Individual Subscriber CA - G2,OU=Persona Not Validated,OU=Terms of use at https://www.verisign.com/rpa (c)05,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
    ssl_debug(9):   CN=TeleSec ServerPass CA 1,OU=Trust Center Services,O=T-Systems International GmbH,C=DE
    ssl_debug(9):   CN=TC TrustCenter Class 3 L1 CA V,OU=TC TrustCenter Class 3 L1 CA,O=TC TrustCenter GmbH,C=DE
    ssl_debug(9):   C=NL,ST=Zuid-Holland,L=Spijkenisse,O=De Rijke Transport,OU=ICT,CN=smtphost.derijke.com
    ssl_debug(9):   CN=VeriSign Class 3 Secure Server CA - G3,OU=Terms of use at https://www.verisign.com/rpa (c)10,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
    ssl_debug(9):   CN=Comodo Class 3 Security Services CA,OU=(c)2002 Comodo Limited,OU=Terms and Conditions of use: http://www.comodo.net/repository,OU=Comodo Trust Network,O=Comodo Limited,C=GB
    ssl_debug(9):   CN=UTN-USERFirst-Hardware,OU=http://www.usertrust.com,O=The USERTRUST Network,L=Salt Lake City,ST=UT,C=US
    ssl_debug(9):   OU=Starfield Class 2 Certification Authority,O=Starfield Technologies, Inc.,C=US
    ssl_debug(9):   EMAIL=ftp(a)csx.com,C=US,O=CSX Corporation Inc,CN=CSX_CORPORATION_AS2_02062009
    ssl_debug(9):   CN=EssentialSSL CA,O=COMODO CA Limited,L=Salford,ST=Greater Manchester,C=GB
    ssl_debug(9):   CN=Network Solutions Certificate Authority,O=Network Solutions L.L.C.,C=US
    ssl_debug(9):   CN=VeriSign Class 3 Public Primary Certification Authority - G5,OU=(c) 2006 VeriSign, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
    ssl_debug(9): Received server_hello_done handshake message.
    ssl_debug(9): No client certificate available, sending empty certificate message...
    ssl_debug(9): Sending client_key_exchange handshake...
    ssl_debug(9): Sending change_cipher_spec message...
    ssl_debug(9): Sending finished message...
    ssl_debug(9): Received alert message: Alert Fatal: bad certificate
    ssl_debug(9): SSLException while handshaking: Peer sent alert: Alert Fatal: bad certificate
    ssl_debug(9): Shutting down SSL layer...
    Severity : Error
    Category : /Applications/ExchangeInfrastructure/AdapterFramework/SAPLibraries/SAPXDK
    Location : com.sap.aii.messaging.net.HTTPClientConnection.call(Object)
    Application : sap.com/com.sap.xi.rwb
    Thread : SAPEngine_Application_Thread[impl:3]_0
    Datasource : 7662250:E:\usr\sap\T37\DVEBMGS00\j2ee\cluster\server0\log\defaultTrace.trc
    Message ID : 00505688007A006A0000005100001B8C0004B1CF78E9602A
    Source Name : com.sap.aii.messaging.net.HTTPClientConnection
    Argument Objs :
    Arguments :
    Dsr Component :
    Dsr Transaction : cc6d1cee0fec11e1c90200000074eaaa
    Dsr User :
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 0
    Relatives : /Applications/ExchangeInfrastructure/AdapterFramework/SAPLibraries/SAPXDK
    Resource Bundlename :
    Session : 365
    Source : com.sap.aii.messaging.net.HTTPClientConnection
    ThreadObject : SAPEngine_Application_Thread[impl:3]_0
    Transaction :
    User : CPWONG
    Dsr Root Context ID :
    Dsr Connection :
    Dsr Counter : -1

    Hi ,
    Is the above problem solved , can you share the solution.
    Thanks

  • JAX-WS Dispatch client deployed in weblogic 10.3.0 sends empty namespace

    We have a weird issue.
    Currently in the production environment we have the below application deployed
    1.     WebService1.war
    2.     WebApp1.war
    3.     WebApp2.war
    Webapp1.war and WebApp2.war invokes WebService1.war and there is no issue in production.
    We have another new webservice2.war component that is going to production soon is deployed in dev and QA environment. After deploying WebService2.war in dev and QA, WebApp1.war started sending empty namespace in the request to Webservice1.war but WebApp2.war which also uses the same web webservice method is sending the proper request. This is how request from WebApp1.war looks like (For security reason I have not given the entire request):
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Header/><env:Body><GetDetails xmlns="Test"><Info xmlns=""></Info></GetDetails></env:Body></env:Envelope>
    In the above request xmlns is empty and that is an issue because at the service layer the Info object is null and it is throwing NullPointerException.
    Additional Details:
    1.All the above mentioned applications are deployed in Weblogic 10.3.0. WebService1.war was implemented using JAX-WS and created in Bottom Up fashion. WebService2.war is also implemented using JAX-WS and created using wsdl (Top Down webservice).
    WebApp1.war uses JAX-WS dispatch client. And there is no issue when the client is tested as a standalone client from our local machine even when WebService2.war is deployed. WebApp2.war uses stubs created using com.sun.tools.ws.ant.WsImport to invoke the webservice. And there is no issue no matter WebService2.war is deployed or not.
    We dont know how the new webservice2 component can cause webapp1 to send empty namespace in the request to webservice1
    Please let me know if you need any other details. And I would really appreciate your inputs.
    Edited by: user8115570 on Feb 2, 2012 8:01 PM

    Child element should be added like this at the client side.
    SOAPElement message = payload.addChildElement("Info","",targetNameSpace);

  • CR Server no send empty report

    Hi, I'm a new CR 'user.
    On Central Management Console, I have a report scheduled, but I would like not send report when this is empty.
    Is it possible?
    tanks

    a

  • Not sending empty reports

    If we shedule a report, how can we be sure that a report is not send to people when it has no data?

    If the report is crystal reports you can use its alerting features. It only sends the alert, but this has a link to the report included.
    You can also look at publications.
    Regards
    Alan

  • BI Publisher Bursting sending Email even after I delete schedule job

    I am facing some weird issue in BI Publisher. We have a BI Publisher report and we are using Bursting query to burst the report to destination Email. It works fine when i run manually. It also worked fine when i schedule it first time for particular time. few days ago client wanted to change the scheduling time. Since there is no way to modify the scheduling time, i deleted the old schedule jobs from BI Publisher as well as i truncated the following tables from DB where it stores scheduling job information.
    XMLP_SCHED_JOB
    XMLP_SCHED_OUTPUT
    XMLP_SCHED_SUBSCRIPTION
    I also created the new scheduling job based on new time. The issue is Clients are getting the emails in old time as well as new scheduling timel. I can see the new scheduling information in following table so no information of old scheduling time. How BI Publisher is still running the report on old time. I research a lot but still i am not able to find the place from where it is still sending the old emails. Can anyone please have any idea to resolve this?

    Did you delete the job schedule using the GUI first? Otherwise by manually deleting the records from XMLP_ tables
    may somehow have corrupted the scehduling option.
    There are other components for the scheduler which are not only saved in XMLP_ tables and these
    are the QUARTZ tables.
    As of release 11g there is not mechanism to manage BIP scheduler tables.
    regards
    Jorge

  • Iphone sending empty emails

    My problem is that from time to time not all the time, messages I send using my Iphone are received at the other end as totally empty.
    In my sent message everything is fine, but when the people reply I can definitely see the message is not there.
    The problem was reported by more than one person, so I am tempted to think the problem is on my side.
    Though they are both using Videotron one major ISP in my neighborhood.
    Any suggestions ?

    Additionnal Info.
    It appears that in deed the problem is restricted to that one ISP.
    The problem is probably not on my iPhone, but still is a problem.
    Any suggestions are still welcome.

  • Cisco CNA: Sending empty commands

    Hi all,
    I'd encountered the following situation – while working with Cisco's CNA (Cisco Network Assistant) on a 2960 switch, any change done by this tool is sent out as an empty set of commands, to a TACACS server to approve.
    Let me explain. I have 2960 switch, a PC with CNA on it and brand new ACS 5.2. This switch is set up for TACACS+ authorization. While working with TELNET/SSH, all commands are authorized properly. When doing "debug aaa authorization", you can see the commands are being sent to a TACACS server (as expected) for approval. And what is more important – within the debug output every command appears at "AV CMD= …" and "Arguments = …" Those commands seen by the ACS and approved correctly.
    But, when working with CNA, those fields (i.e. av cmd and arguments) are empty in the first place. Hence all what ACS does see are "empty commands" and no clue for the correct ones (say, changing interface's description). The HTTP server has it set of authorization commands.
    I had no time to dig into it. Maybe someone encountered a similar problem before? Post here the correct settings (as he/she thinks) to authorize CNA? Anyhow, every suggestion will be appreciated.
    Thank you.

    Hello Alex,
    I think I have narrowed the issue. Unfortunately, I have bad news
    I recreated this on my lab using a 3750 switch running IOS version 12.2(55)SE3, ACS 5.3 and Cisco Network Assistant 4.1 and 5.7.
    I configured the following:
    aaa authentication login httpauth group tacacs+ local
    aaa authorization exec httpauthor group tacacs+ local
    aaa authorization commands 0 httpcommands group tacacs+ local
    aaa authorization commands 1 httpcommands group tacacs+ local
    aaa authorization commands 15 httpcommands group tacacs+ local
    ip http server
    ip http authentication aaa login-authentication httpauth
    ip http authentication aaa exec-authorization httpauthor
    ip http authentication aaa command-authorization 0 httpcommands
    ip http authentication aaa command-authorization 1 httpcommands
    ip http authentication aaa command-authorization 15 httpcommands
    ip http secure-server
    The above configuration binds the AAA feature for Authentication, User Authorization and Command Authorization for HTTP(S) access to the IOS. However, the ACS reports [CmdAV=] as you stated on your first post when a "Restricted" users performs changes on the IOS device configuration through CNA.
    I performed debugs and captures when performing changes with a CLI Restricted user (CLI works fine) when using CNA. No Command is send to the TACACS+ server to validate as no command is send from the Application (CNA) for the IOS to authorize.
    Performing a deeper research I found the root cause of the issue
    http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsz24369
    AAA authorization is very inconsistent when using CNA
    Symptom:When using CNA to configure the switches not all configuratin options
    being done are passed through the AAA command authorization on the switch.
    Some configuration options are and some cofniguration options are not
    passed through the AAA command authorization
    Conditions:
    Workaround:Do not use CNA when command authorization is required
    It seems to be a CNA application bug and not an IOS or ACS related issue. The caveat is no fixed yet, however, it is listed to be fixed with CNA 6.0 (I do not have an ETA for CNA 6.0 release).
    I hope this helps.
    Regards.

  • Is there a way to prevent users from sending empty or incomplete PDF forms?

    Hi all,
    Using Acrobat Professional 8, I made a fillable form to individuals to fill in and submit to me as a pdf attachment to an e-mail or print out it and fill by hand.
    Question 1. I want to make sure they don't send incomplete or empty forms back to me. Is there a way to do that?
    2. The form is 8.5x15 inches. I want it to look like one continuous page on screen but print as 2 letter size pages. However, when i go to print it, acrobat scales it down to fit in one page which makes the text too small to read.
    Please advise! Thanks.
    Karen

    On Question 2:
    when you get to the Print menu in Acrobat/Reader look for scale to fit paper and uncheck if there is a reference to Full size check that.

  • IDOC to BPM-SOAP adapter is sending Empty envelop

    Hello,
    I have a scenario where im using BPM Async/sync bridge to realize the IDOC to SOAP adapter scenario.
    The web services will take the request and send the response in string (CDATA). Everything is working fine upto the synchronous interface mapping. After the data gets converted, It calls the SOAP adapter.It is here that im facing the issue. The soap adapter is sending an empty envelop without any data. But in monitoring i can see the data that it is supposed to send.
    Please, can anybody help me????
    Thanks,
    Lakshmi

    If I understand correctlty, you are doing a asynt to sync to asyn scenario. In this case you dont need an async-sync bridge.
    Your BPM should have only a receive step, sync send and then an asyn send step. You might have one transformation wherever applicable. If you have opened any bridges in BPM, please remove them and try.
    VJ

  • [SOLVED] msmtp: Gmail sends empty mails, Yahoo ignores "from"

    I have recently embarked on the atrocious adventure of migrating from Thunderbird to mutt.
    So far however, msmtp has consistently refused to properly send mail. Using
    echo "Yet another test" | msmtp -a <account> <test>@gmail.com
    with this config
    defaults
    auth on
    tls on
    tls_starttls on
    tls_trust_file /usr/share/ca-certificates/mozilla/Equifax_Secure_CA.crt
    # first gmail address
    account gmail
    host smtp.gmail.com
    port 587
    from <mail1>@gmail.com
    user <mail1>@gmail.com
    password <pass1>
    # second gmail address
    account gmail2 : gmail
    from <mail2>@gmail.com
    user <mail2>@gmail.com
    password <pass2>
    # yahoo
    account yahoo
    tls_starttls off
    host smtp.mail.yahoo.de
    from <mail3>@yahoo.de
    user <mail3>
    password <pass3>
    # default
    account default : gmail
    yields:
    1. An empty mail if one of the Gmail accounts is used, including the proper "from" address.
    2. A mail with the test sentence if Yahoo is used, but having "youknow@smtp<three digits>.mail.ukl.yahoo.com" as "from".
    Any help, please? This is getting really tiresome.
    edit: Solution below
    Last edited by misc (2010-07-05 16:01:38)

    If brisbin33's page comes back up, I highly recommend it. It has a ton of great information, and I configured mine based on that. My msmtprc file contains:
    # gmail
    account gmail
    host smtp.gmail.com
    port 587
    protocol smtp
    auth on
    from [email protected]
    user [email protected]
    password EMAILPASS
    tls on
    tls_nocertcheck
    account default : gmail
    So my suggestion is to try these tls* lines, and add the protocol lines. Other than that, I don't know much about it. brisbin33 uses these forums, so he may be able to help you directly
    Last edited by jac (2010-07-06 13:32:26)

  • Invoke Web Services - Send empty SOAP package

    We have a SOAP interface that we have consumed through a service layer for 5+ years.
    There are many functions available from this endpoint.
    Example, one is called Ping and requires no additional parameters. We can send this via Orchestrator with no issues and we get a response.
    However all other functions have param requirements such as a set name or authentication data.
    Orchestrator has no issue pulling the Format Hint. Ive attached wireshark and fiddler and all calls get sent by Orchestrator with empty packages, all parms get stripped.
    We can use SOAP runner and have no issues sending these commands.
    Thoughts?
    Designer: 7.2.84.0
    Orchestrator Management Servers:
     NAME: 7.2.84.0
    Libraries:
     Compression-6-4109999.op4caw: 7.2.84.0
     Compression-6-4109999.op4saw: 7.2.84.0
     Database-14-40801.op4caw: 7.2.84.0
     Database-14-40801.Op4saw: 7.2.84.0
     DataMapper-689-5000001.op4caw: 7.2.84.0
     DataMapper-689-5000001.op4saw: 7.2.84.0
     DateTime-1-5000001.op4saw: 7.2.84.0
     Email-2-40803.op4saw: 7.2.84.0
     Email-2-4109999.op4caw: 7.2.84.0
     Encryption-628-5000001.op4caw: 7.2.84.0
     Encryption-628-5000001.op4saw: 7.2.84.0
     EncryptionDomainLibResources.dll: 7.2.84.0
     FileAndFolderFOCommon.dll: 7.2.84.0
     FileList-38-40801.op4cbw: 7.2.84.0
     FileManagement-4-40802.op4caw: 7.2.84.0
     FileManagement-4-40802.op4saw: 7.2.84.0
     FileManagementClientExtension.dll: 7.2.84.0
     FileManagementDomain.dll: 7.2.84.0
     FileManagementResource.dll: 7.2.84.0
     FileManagementServerExtension.dll: 7.2.84.0
     FileMonitorClientExtension.dll: 7.2.84.0
     FileMonitorDomain.dll: 7.2.84.0
     FileMonitorServerExtension.dll: 7.2.84.0
     FolderMonitorClientExtension.dll: 7.2.84.0
     FolderMonitorDomain.dll: 7.2.84.0
     FolderMonitorServerExtension.dll: 7.2.84.0
     FormatDateTimeClientExtension.dll: 7.2.84.0
     FormatDateTimeDomainLibResources.dll: 7.2.84.0
     FormatDateTimeServerExtension.dll: 7.2.84.0
     Internet-13-40801.op4caw: 7.2.84.0
     Internet-13-4109999.op4saw: 7.2.84.0
     jf.SCOrch.Integration.DataManipulation.DataManipulationImages.dll: 1.0.0.0
     jf.SCOrch.Integration.SharePoint.ActivityImages.dll: 1.0.0.0
     Kelverion.IntegrationPack.RunbookManagement.Images.dll: 1.0.0.1
     Kelverion.IntegrationPack.SqlServer.Images.dll: 2.0.0.0
     ManageTextFileClientExtension.dll: 7.2.84.0
     ManageTextFileDomain.dll: 7.2.84.0
     ManageTextFileServerExtension.dll: 7.2.84.0
     Microsoft.EnterpriseManagement.Core.dll: 7.5.3046.0
     Microsoft.SystemCenter.Orchestrator.ActiveDirectoryIP.Images.dll: 7.2.43.0
     Microsoft.SystemCenter.Orchestrator.Integration.SCCM2012.ClientExtension.dll: 7.2.56.0
     Microsoft.SystemCenter.Orchestrator.Integration.SCCM2012.Domain.dll: 7.2.56.0
     Microsoft.SystemCenter.Orchestrator.Integration.SCCM2012.ServerExtension.dll: 7.2.56.0
     Microsoft.SystemCenter.Orchestrator.Integration.SCOM2012.ClientExtension.dll: 7.2.56.0
     Microsoft.SystemCenter.Orchestrator.Integration.SCOM2012.Domain.dll: 7.2.56.0
     Microsoft.SystemCenter.Orchestrator.Integration.SCOM2012.ServerExtension.dll: 7.2.56.0
     Microsoft.SystemCenter.Orchestrator.Integration.SCSM2012.ClientExtension.dll: 7.2.56.0
     Microsoft.SystemCenter.Orchestrator.Integration.SCSM2012.Domain.dll: 7.2.56.0
     Microsoft.SystemCenter.Orchestrator.Integration.SCSM2012.ServerExtension.dll: 7.2.56.0
     Microsoft.SystemCenter.Orchestrator.Integration.Toolkit.IP.ClientExtension.2.dll: 7.2.7.0
     Microsoft.SystemCenter.Orchestrator.Integration.Toolkit.IP.ClientExtension.dll: 7.0.359.0
     Microsoft.SystemCenter.Orchestrator.Integration.Toolkit.IP.ServerExtension.2.dll: 7.2.7.0
     Microsoft.SystemCenter.Orchestrator.Integration.Toolkit.IP.ServerExtension.dll: 7.0.359.0
     Microsoft.SystemCenter.Orchestrator.Integration.Toolkit.Wizard.Images.dll: 7.2.7.0
     MpCore4LibResources.dll: 7.2.84.0
     MpCoreLibResources.dll: 7.2.84.0
     NetBrowser-40-40801.op4cbw: 7.2.84.0
     NetUseObjectsClientExtension.dll: 7.2.84.0
     NetUseObjectsServerExtension.dll: 7.2.84.0
     Network-24-407.op4caw: 7.2.84.0
     Network-24-40801.op4saw: 7.2.84.0
     ObjectResources.dll: 7.2.84.0
     OpCoreLibResources.dll: 7.2.84.0
     OpToolsLibResources.dll: 7.2.84.0
     ProcessBrowser-69-40801.op4cbw: 7.2.84.0
     PS_Tools.dll: 1.0.0.19
     QueryXmlClientExtension.dll: 7.2.84.0
     QueryXmlServerExtension.dll: 7.2.84.0
     RandomStringClientExtension.dll: 7.2.84.0
     RandomStringDomainLibResources.dll: 7.2.84.0
     RandomStringServerExtension.dll: 7.2.84.0
     RASPhoneBook-56-40801.op4sbw: 7.2.84.0
     RASPhoneBrowser-56-40801.op4cbw: 7.2.84.0
     RunScriptClientExtension.dll: 7.2.84.0
     RunScriptDomain.dll: 7.2.84.0
     RunScriptServerExtension.dll: 7.2.84.0
     Schedule-1-40801.op4caw: 7.2.84.0
     SnmpClient-119-4109999.op4caw: 7.2.84.0
     SNMPClientExtension.dll: 7.2.84.0
     SnmpDomainLibResources.dll: 7.2.84.0
     SnmpService-119-4109999.op4saw: 7.2.84.0
     SSHClient-117-4109999.op4caw: 7.2.84.0
     SSHService-117-4109999.op4saw: 7.2.84.0
     StandardObjects.dll: 7.2.84.0
     SystemCenter.IntegrationPack.ExchangeAdmin.Images.dll: 7.2.51.0
     SystemCenter.IntegrationPack.ExchangeUser.Images.dll: 7.2.49.0
     SystemCenter.IntegrationPack.Ftp.Images.dll: 7.2.47.0
     SystemCenter.IntegrationPack.SharePoint.Images.dll: 7.2.52.0
     SystemUtilities-16-40801.op4caw: 7.2.84.0
     SystemUtilities-16-40802.op4saw: 7.2.84.0
     TextFile-15-40801.op4caw: 7.2.84.0
     TextFile-15-40801.op4saw: 7.2.84.0
     WebServiceChannelLibResources.dll: 7.2.84.0
     WebServicesBase.dll: 7.2.84.0
     WebServicesClientExtension.dll: 7.2.84.0
     WebServicesProxy.dll: 7.2.84.0
     WebServicesServerExtension.dll: 7.2.84.0
     WindowsUtilities-21-40801.op4caw: 7.2.84.0
     WindowsUtilities-21-40801.op4saw: 7.2.84.0
     Wmi-8-40802.op4caw: 7.2.84.0
     Wmi-8-40809.op4saw: 7.2.84.0
     XsltTransformClientExtension.dll: 7.2.84.0
     XsltTransformServerExtension.dll: 7.2.84.0
    Moved On

    I've noticed the same behaviour.
    When I call a webservice using the "Invoke Web Services"-activity using only the elements of the xml e.g. <object>somevalue</object> the xml that gets sent is complete and consumed by the webservice.
    However when I call another method that requires attributes (e.g. <object name="something">somevalue</object>) the attributes (name="something") gets stripped from the xml causing the webservice to bounce my call as certain
    (mandatory) parameters are missing.
    I've confirmed this through Wireshark.
    I'm possitive my XML payload is correct as this works through both SOAPUI and Powershell.
    (not intending to hijack the question, mainly confirming the behaviour and providing and additional use case)

Maybe you are looking for

  • Mountain Lion or Mavericks?

    Hello. I don't know which operating system I want to get on my Mac Mini. The Best Buy retail stores have the Minis with Mountain Lion pre-installed. While both the Apple Retail Store and Online Store have Mavericks pre-installed. I liked iOS6 on the

  • I can't use the Mail app after updating to 8.0.2

    I can add my Gmail account to my phone just fine.  It adds my calendar, my contacts and my notes with no problem.  But when I open the Mail app, I get a blank screen.  It stays blank for about 15-20 seconds and then closes automatically. Also, there

  • Lost all applications after upgrading

    Hi, I've just got a 3GS and was trying to sync with itunes to activate the phone Here's what happened: 1. Did a back up with previous phone (3G) with iTunes. 2. Connect new 3GS with iTunes. 3. Sync/restore new 3GS 4. Update phone firmware to version

  • Lightening to 30 Pin Connector- Accessory not Supported

    My Lightening to 30 PIN Apple connector is having issues with my ipod nano- 7th generation. It keeps saying "accessory not supported" It will randomly work (not very often anymore) and I have tried cleaning it but to no avail. Does anyone have any ot

  • Student in need of HELP!Best application for writting java Code?

    I've been working on two different systems and need to be able to work on both..On one system the SDK is installed on a linux machine on another on a windows machine...unfortunately i cant open the linux created files on my windows machine although i