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.

Similar Messages

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

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

  • When i click on an excel or word file in 2007 the program begins to open but then an error message says There was a problem sending the command to the program

    when i click on an excel or word file in 2007 the program begins to open but then an error message says There was a problem sending the command to the program.
    i am using office2007  with windows7 premium home edition.  i have checked file associations., all DDE settings. i have even tried this in safe mode. the same thing happens. please note once i see the error. i can then go back to the file click on
    it a second time and it WILL open. AND i can open any file if i open excel and and find the file from there. i uninstalled and re-installed office 2007 from scratch. And i checked the compatibility mode (all un-checked) still the problem persisits. this is
    a real PITA.   anyone have any solution for this? Thanks 
    ken yanow

    Hi,
    Have you try to un-select the Ignore other applications that use Dynamic Data Exchange (DDE) setting?
    Click the Microsoft Office Button, and then click Excel Options.
    Click Advanced, and then click to clear the Ignore other applications that use Dynamic Data Exchange (DDE)
    check box in the General area.
    Click OK.
    If the problem cannot resolve, the Run as administrator may selected.
    Go to Office default install location: C:\Program Files\Microsoft Office\Office12.
    Right-click EXCEL.EXE > Properties >
    Compatibility tab.
    Under Privilege Level, uncheck Run this program as an administrator
    check box.
    Best regards.
    William Zhou
    TechNet Community Support

  • Using VI Example Basic Serial Write Read to send AT commands to Cell phone modem error 1073807360

    I am using the NI Example VI: Basic Serial Write and Read to send AT commands to a Cell phone acting as a Modem.  I can send AT commands to this phone using Hyperterm when I select the modem driver by name in the hypert port selection field but not as com 7 which it occupies according to device manager modem properties. The basic serial vi does not show the modem driver as a selection, only ports by comX are shown. I get error 1073807360.

    Have you tried to put the name you enter in Hyperterminal in the VISA resource control? If Com 7 doesn't show, you can simply type "COM 7" in the VISA resource control. Or use "ASRL::INSTR 7".
    Also, make sure the connection in hyperterminal is closed, before you open the port in LabVIEW.
    Hope it helps,
    Wiebe.

  • After updating to Firefox 3.6.9, when I click on a link in Outlook email, I get a message which says "General failure. The URL was: .... An error occurred in sending the command to the applicatio." and the link will not open. How can I fix this?

    I updated Firefox yesterday to 3.6.9. When I receive a URL link in an email within Outlook, I cannot open the link in Firefox. As I said in the question, when I click on the link, a Microsoft Office Outlook error message appears which states that a General failure has occurred in sending the command to the application (which is Firefox). I am using Office 2007 This did not occur prior to the upgrade of Firefox.

    See this lnk for a fix, it worked for me!
    http://www.pcworld.com/article/200103/fix_outlook_general_failure_error_for_email_links.html

  • Since switching to Firefox this week, when I click on a hyperlink in an e-mail in Outlook, I get this message, "General failure. An error occurred in sending the command to the application." It doesn't open a new window or do anything.

    Since switching to Firefox this week, when I click on a hyperlink in an e-mail in Outlook, I get this message, "General failure. An error occurred in sending the command to the application." It doesn't open a new window or do anything. Any work around to fix this?

    See this lnk for a fix, it worked for me!
    http://www.pcworld.com/article/200103/fix_outlook_general_failure_error_for_email_links.html

  • Excel won't open and error message There was a problem sending the command to the programe

    Hi there
    I'd be grateful for your help.
    I've just bought a new laptop and installed Office 2013.  I used Excel 2013, did what I needed to do and saved it.  This was 5 days ago.
    Today, I've tried opening the file from my desktop and get the error message 'There was a problem sending the command to the program'.
    And when I try to open Excel to do the DDE fix, which seems to be the best suggestion, I can't open Excel at all.  I've tried to get into it from the Apps screen.
    Any help would be gratefully appreciated.
    Thanks

    Don't seem like this can be fixed so I went back to version 6.0.2 which works good.
    I have Chrome now as my default browser and will not use fire fox until they fix it!
    Chrome works great!

  • "An error occurred sending the command to the application" When trying to open excel document from outlook 2007

    Error message "An error occurred sending the command to the application" When trying to open excel document from outlook 2007.
    OS: Windows Server 2008 R2
    If I save the document then it opens fine, messing with default file associations does not resolve this problem, I've googled for ir it and some suggest unticking compatibility mode or "run as admin" for excel application, neither is selected in my case.
    Outlook is configured to run as remote application from remoteApp server, this error is only occurring for one user, for others excel documents open just fine.

    Hi
    Thank you for using
    Microsoft Office for IT Professionals Forums.
    From your description, we can Create a trusted location follow these steps
    Click the Microsoft Office Button , and then click Excel Options.
    Click Trust Center, click Trust Center Settings, and then click
    Trusted Locations.
    If you want to create a trusted location that is not local to your computer, select the Allow trusted locations on my network (not recommended) check
    box.
    Click Add new location.
     IMPORTANT   We recommended that you don't make your entire
    Documents or My Documents folder a trusted location. Doing so creates a larger target for a hacker to potentially exploit and increases your security risk. Create a subfolder within Documents or My Documents, and make only that folder a trusted location.
    In the Path box, type the name of the folder that you want to use as a trusted location, or click Browse to
    locate the folder.
    If you want to include subfolders as trusted locations, select the
    Subfolders of this location are also trusted check box.
    In the Description box, type what you want to describe the purpose of the trusted location.
    Click OK.
    More detailed information you can refer to this link:
    http://office.microsoft.com/en-us/word-help/create-remove-or-change-a-trusted-location-for-your-files-HA010031999.aspx?CTT=1#BM12
    Please take your time to try the suggestions and let me know the results at your earliest convenience. If anything is unclear or if there is anything
    I can do for you, please feel free to let me know.
    Hope that helps.
    Sincerely
    William Zhou CHN
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

  • How to send AT Command in fax modem from fax api?

    hi,
    i want to send a dial pad number in my fax modem.
    i am using Interop.FAXCOMEXLib dll in my C# Project.i can send and receive fax.
    i want to send a number of dial (after 20 sec dialing) for example send 5 number or send at command : "AT5" for dialing pad.
    can i send AT Command in Interop.FAXCOMEXLib ?
    please help me.
    Thanks.

    Hi Ali,
    I am not expert on AT Command.
    I have seen
    Send and Read SMS through a GSM Modem using AT Commands and
    AT commands Send/receive SMS. But i have never seen send AT Command in Interop.FAXCOMEXLib. I am afraid this is not support.
    Actually, this case related to desktop. If you still not resolve this issue, please redirect to
    Windows Desktop Development  >
    General Windows Desktop Development Issues
    forum for better support.
    Thanks for your understanding.
    Good Luck.
    Kristin
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • TCP connection error when sending MODBUS commands to WAGO 750-881 controller after 113655 bytes of data have been sent

    Hi all,
    I am new to the world of labview and am attempting to build a VI which sends commands to a 750-881 WAGO controller at periodic intervals of 10ms. 
    To set each of the DO's of the WAGO at once I therefore attempt to send the Modbus fc15 command every 10ms using the standard Labview TCP write module. 
    When I run the VI it works for about a minute before I recieve an Error 56 message telling me the TCP connection has timed out. Thinking this strange, I decided to record the number of bytes sent via the TCP connection whilst running the program. In doing so I noticed that the connection broke after exactly 113655 Bytes of data had been sent each time. 
    Thinking that I may have been sending too many messages I increased the While-loop delay from 10ms to 20, 100 and 200 ms but the error remained. I also tried playing with the TCP connection timeout and the TCP write timeout but neither of these had any effect on the problem. 
    I cannot see why this error is occuring, as the program works perfectly up untill the 113655 Bytes mark. 
    I have attached a screenshot of the basic VI (simply showing a MODBUS command being sent every second) and of a more advanced VI (where I am able to control each DO of the WAGO manually by setting a frequency at which the DO should switch between ON and OFF). 
    If anybody has any ideas on where the problems lie, or what I could do to further debug the program this would be greatly appreciated. 
    Solved!
    Go to Solution.
    Attachments:
    Basic_VI.png ‏84 KB
    Expanded_VI.png ‏89 KB

    AvdLinden wrote:
    Hi ThiCop,
    Yes the error occurs after exactly 113655 bytes every time. The timeout control I would like to use is 10ms, however even increasing this to 1s or 10s does not remove the error, which leads me to believe that this is not the issue (furthermore, not adding any delay to the while loop, thus letting it run at maximum speed, has shown that the TCP connection is able to send all 113655 bytes in under 3 seconds again pointing towards the timeout control not being the issue here). 
    I attempted Marco's suggestion but an having difficulty translating the string returned into a readable string, (rightnow the response given is "      -#   +   ").
    As to your second suggestion, I implemented something similar where I created a sub VI to build a TCP connection, send a message and then close the connection. I now build each message and then send the string to this subVI which successfully sends the command to my application. Whilst not being the most elegant method of solving the issue, it has resolved the timeout problem meaning I am able to send as many commands as I want. So in that sense the problem has been solved. 
    If you still have tips on how to correctly read the TCP read output, I would however like to see if I could not get my first program to work as it is slightly more robust in terms of timing. 
    Modbus TCP RTU is a binary protocol, as you show in your Basic VI, where you format the data stream using byte values. So you have to interprete the returned answer accordingly with the Modbus RTU spec in hand. Now what is most likely happening is that the connection gets hung after a while since you do NOT read the data the device sends as response to your commands. The TCP/IP stack buffers those bytes and at some point the internal buffers overflow and the connection is blocked by the stack. So adding the TCP Read at strategic places (usually after each write) is the proper solution for this. Is there any reason that you didn't use the NI provided Modbus TCP library?
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Using Firefox 4 & Windows 7. Everytime I start Firefox from a shortcut to a website it comes up with the following error 'there was a problem sending the command to the program'. The requested website does load after this. with no problems.

    Using Firefox 4 & Windows 7. Everytime I start Firefox from a shortcut to a website it comes up with the following error 'there was a problem sending the command to the program'. The requested website does load after this. with no problems.
    If a shortcut is used while Firefox is already open the error does not occur.

    As reported in earlier replies, the annoyance disappeared after I upgraded to Roboform 7.5.6, from 7.5.4.
    Regards, Steve

  • After updating to 3.6.10 links in Outlook 2007 no longer open - "An error occurred in sending the command to the application"

    After updating to Firefox 3.6.10 this morning, Outlook 2007 can no longer open up links embedded in emails. Normally when you clicked a link it would open up Firefox and send you to the website, but when you click on any link it now says:
    General failure. The URL was: [url here]
    An error occurred in sending the command to the application.
    I don't know what happened. I didn't change any other settings on the computer.
    I am running Windows 7 64 Professional, MS Outlook 2007 with latest updates, and Firefox 3.6.10

    Please read this article to see if it helps:
    https://support.mozilla.com/tiki-view_forum_thread.php?locale=en-US&comments_parentId=542907&comments_offset=20&comments_per_page=20&forumId=1
    Also, you might try this first:
    https://support.mozilla.com/en-US/kb/troubleshooting+extensions+and+themes

  • Word2007 in windows 7 -There was a problem sending the command to the program!

    I just bought my new HP laptop with windows 7 Home premier edition, and then I installed windows office 2007 suite. It's ok if I only open the word without any existing word file. But if I open word with a word file, it says " there was a problem sending
    the command to the program". I try this action under safe mode, it's no problem, I can open an existing word file. If I open the winword.exe and use menu "file-open" to open a word file, it's alright. But If I double click a word file, it shows that error.
    I tried to change the registry information according to the solution on internet, but it doesn't work.  I checked the compatibility mode, it says run in "windows XP sp3", and it is grey, I can't uncheck it.
    Anyone got any idea to fix this problem?
    Thanks a lot.

    Hi
    Thank you for using
    Microsoft Office for IT Professionals Forums.
    From your description, This sounds like a problem with the file associations in Windows.. If there is any misunderstanding, please feel free to let
    me know.
    The first thing to check is to make sure that the file extensions are correctly associated with Word.
    1.      
    Click Start > type or copy following command to the Search box
    "C:\Program Files\Microsoft Office\Office12\winword.exe" /unregserver
    2.      
    You should then, immediately, use the following command:
    "C:\Program Files\Microsoft Office\Office12\winword.exe" /regserver
    Re-associate the Word file  manually:
    Please go to
    Start \Control Panel\Programs\Default Programs\Set Associations.
    Locate the files .doc, .docm,.docx, .dot, .dotm, check if there are associated with
    Microsoft Word. If not, highlight the file and click the
    Change Program button. Choose Microsoft Word from the list. If you are unable to see Microsoft Word from the list, click the
    Browse button. Browse to the folder: C:\Program Files\Microsoft Office\Office12, and choose
    WINWORD.EXE.
    Click
    OK to save the settings.
    Please take your time to try the suggestions and let me know the results at your earliest convenience. If anything is unclear or if there is anything
    I can do for you, please feel free to let me know.
    Hope that helps.
    Sincerely
    William Zhou CHN
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

  • Since upgrading to Firefox 4.0 I keep getting the error message "THERE WAS APROBLEM SENDING THE COMMAND TO THE PROGRAM", please can you advise how I get it to stop?

    I have just upgraded to Firefox 4.0 and ever since then I get this message when I try to go to either Yahoo or Gmail
    "THERE WAS A PROBLEM SENDING THE COMMAND TO THE PROGRAM",
    I had this problem a month or so ago so downgraded to Firefox 3.6 and the problem went away but have now been advised to upgrade which indeed I have and hey presto the error message again, please how can I fix it??

    OK, you seem to be running Zone Alarm as your firewall. It includes a utility which checks to see whether a site is safe or not and also adds a plugin to Firefox which is listed as '''npFFApi'''. Can you disable that and see if it makes any difference?
    To get to the plugins manager, click the orange Firefox button, then click "Add-ons". In the page that opens, click the "Plugins" link on the left which will open the menu. Then find '''npFFApi '''and click the "''Disable''" button.

Maybe you are looking for

  • Oracle UCM 10gr3 and webcenter 11g, WCM Portlets

    Hi, I have installed Oracle UCM 10gR3, Site Studio 10gR4 and Webcenter 11g. Now my problem is how to get the WYSIWIG (WCM Portlet) created in UCM to be retrieved in webcenter spaces. My understanding after reading some articles is the only way i can

  • HT1476 What is fire wire charging device

    What is a fire wire charging device

  • How do I soft wrap text documents by default?

    I use a lot of plain-text (or markdown-formatted) documents on my computer and on my server for storing basic information. When I open those documents in Firefox, though, the lines aren't soft-wrapped. Is there a way to set Firefox to soft wrap simpl

  • To find all the child records are processed before parent records

    Hi, When i am trying to process consignment pulls and my client is using third party tool to insert the data into interface tables. My logic is written in such a way that it should pick parent record associated with child but there is some delay in c

  • All links change color when click 1

    HI, I've tried searching for this as many ways as I can think of - so forgive me if this has been covered before. I've made a template file and have a series of links to various pages (I'm in the VERY beginning stages here). On my pages that have thi