Armory not sending...

[BitHits]

http://gyazo.com/773891dfb2243d4accf527e49fccc4b6

Why isnt Armory sending?

I've tried just clicking send as well as create offline, signing and then broadcasting!?

[Tril]

Are you sure Armory is connected to bitcoind/bitcoin-qt?  And bitcoind/bitcoin-qt has peers?  Watch the end of your debug.log right after you press send, and it should show your node accepting the tx.  Then check blockchain.info for that tx to see if it propagates and gets confirmed.

[rambog]

I am having the same issue and mine shows right after entering my passphrase upon attempting to send BTC.  The dialogue box title is "Broadcast failed" and the body reads "The broadcase process failed unexpectedly.  Report this error to the development team if this issue occurs repeatedly"  It occurs to me repeatedly over one day.  It is a freshly restored wallet so I have not yet successfully sent anything.  I attempted to verify whether the blockchain was up-to-date but "bitcoin-cli.exe getblockcount" returns "error: couldn't connect to server" yet Armory is reporting "Armory is online!" and "Connected ( such number of blocks). 

Please advise.

[goatpig]

Turn off auto bitcoind and start bitcoinqt manually. Then start Armory and take it from there.

[rambog]

I already have "Let Armory Run Bitcoin-Core/bitcoind in the background" de-selected.  I made sure this time I stated bidcoin core first before Armory.  I was able to send (yet the command "c:\program files\bitcoin\daemon\bitcoin-cli getblockcount" still protests it "couldn't connect to server").  In the past, my command bitcoin-cli was working- I could match it up (see my post https://bitcointalk.org/index.php?topic=1817142.0).  Thank you for your help in enabling me to send the BTC.  Any insight was to why, however, my bitcoin-cli commands no longer appear working?

[goatpig]

Any insight was to why, however, my bitcoin-cli commands no longer appear working?

Check your bitcoin.conf:

1) It should have server=1

2) Remove rpclogin and rpcpassword if you have that, and try again. I expect bitcoin-cli relies on the cookie file after that has been introduced. rpclog/pass block that.

Since you are running your node manually, consider using bitcoin-qt with disablewallet=1, that gives you a tab to run rpc commands from the GUI.