"the broadcast process failed unexpectedly"

[paranoidx]

Getting the following error when trying to send bitcoins "the broadcast process failed unexpectedly"
Armory v 0.95-beta-374672b751 shows it's online and connected.

bitcoin 0.12.1 is fully synced

log file: http://pastebin.com/SqSGCjvG

[1714123110]

1714123110

[1714123110]

1714123110

[1714123110]

1714123110

[paranoidx]

Updated to 0.13.1 and relaunched Armory.
It's working now. 

[Cobbler7]

Hi, I am repeatedly getting the same error message, but am
running Ubuntu 16.04 LTS and Armory 0.95.1.

("Broadcast failed unexpectedly. Report this error to the developer
team if this issue occurs repeatedly").

I also repeatedly get the same error message when I run Armory 0.95.1 on a
Ubuntu 14 laptop.

I can connect to the bitcoin network okay through Armory on both machines,
and it updates both the balances in my online and offline wallets.

But when I try to transfer the small amount of bitcoin from my encrypted
online armory wallet to my cold storage armory wallet, I get the error
message repeatedly. It doesn't seem like armory/bitcoin tries to connect
for awhile and gives up. It just hits me bam! with an error message as soon as
I hit the send button.

Anyone have any idea about what is going one or how to possibly fix this?!

Thanks for your consideration.

[goatpig]

Grab the raw transaction from Armory and broadcast it directly with core for a better error message.

[Cobbler7]

Thank you for the quick response. Unfortunately, I am a newbie and
have no idea how to broadcast a raw armory transaction over bitcoin
core.

That is, I should be able to find the raw Armory transaction file, but
could you give me a sentence or two about how to make core broadcast
that file directly?

Thanks much for your help!

[goatpig]

Start Bitcoin Core with -disablewallet and go the console tab. Then type "sendrawtransaction tx" where tx is your raw transaction in hexits (not line breaks, no spaces, no symbols)

[marcind]

Hello,
I have the same error when trying to send btc from Armory v 0.95.1-beta-374672b751
Bitcoin Core wersja v0.13.2 (32-bit)

empty address is created: 1B6zDd41anwF4vMkLPCoSP7zWdtRpaCwCr but there is no transfer of btc

thank you for help

[goatpig]

Hello,
I have the same error when trying to send btc from Armory v 0.95.1-beta-374672b751
Bitcoin Core wersja v0.13.2 (32-bit)

empty address is created: 1B6zDd41anwF4vMkLPCoSP7zWdtRpaCwCr but there is no transfer of btc

thank you for help

Grab the raw transaction from Armory and broadcast it directly with core for a better error message.

Same stuff applies.

[KeptUpLate]

Me too have the same problem.

Grab the raw transaction from Armory and broadcast it directly with core for a better error message.

Yehw, but this I cannot understand at all. Allready peeked in the Armory Appdata and other nearby subdirectories.
Probably the wrong places.

I have troubles understanding "RAW Data", let alone finding them. Can't understand the concept of it.
That's how Newby someone can be.

I am sorry, but I really need some more help, already put some bitcoins in this Armory Wallet, wich seems have to stay there forever.
Oh man , I really feel miserable by such a misstake.

[goatpig]

Me too have the same problem.

Grab the raw transaction from Armory and broadcast it directly with core for a better error message.

Yehw, but this I cannot understand at all. Allready peeked in the Armory Appdata and other nearby subdirectories.
Probably the wrong places.

I have troubles understanding "RAW Data", let alone finding them. Can't understand the concept of it.
That's how Newby someone can be.

I am sorry, but I really need some more help, already put some bitcoins in this Armory Wallet, wich seems have to stay there forever.
Oh man , I really feel miserable by such a misstake.

In your case, you'll have to wait for 0.96

[dugan_sharp_b9zB]

KeptUpLate -- I explain a bit about how I got the raw transaction from Armory and broadcast via Core over in the following thread:

https://bitcointalk.org/index.php?topic=1753579.0

Note that it was on linux, but the Armory portion might still help you....

[clatos]

I seem to have the exact same problem as Cobbler7. But I run v.0.95.1-beta on Windows 10. Armory is online and I could restore an old wallet and also create a new one. But I cannot send the bitcoins from my old wallet to the new one since I get this error message "Broadcast failed unexpectedly. Report this error to the developer team if this issue occurs repeatedly". Sending bitcoins from my bitcoin exchange also seems to fail. They keep canceling my withdraws.

As goatpig suggested, I tried to start Bitcoin Core with –disablewallet. But then I get the message “The logfile ’C:\Program Files (x86)\Armory\ArmoryQt.exe.log’ could not be opend: [Errno 13] Permission denied: ‘C:\\Program Files (x86)\\Armory\\ArmoryQt.exe.log’”

However ArmoryQt.exe.log is at this location and I can open it. Btw, this log is full of errors. The top line reads: “(ERROR) BDM.pyc:265 - setSatoshiDir: directory does not exist: C:\Users\Bob\AppData\Roaming\Bitcoin\”. And again, this directory exists too, since I installed Bitcoin Core with the default settings.

Please help!

[goatpig]

What command line arguments are your running Armory with?

[achow101]

Those who have are experiencing this issue, can you please post your armorylog.txt and dbLog.txt files found in the Armory data folder? I am investigating what is causing this problem, and I will need to see both log files to confirm my current hypothesis.

[clatos]

What command line arguments are your running Armory with?

I'm running "C:\Program Files (x86)\Armory\ArmoryQt.exe" -disablewallet

[clatos]

Those who have are experiencing this issue, can you please post your armorylog.txt and dbLog.txt files found in the Armory data folder? I am investigating what is causing this problem, and I will need to see both log files to confirm my current hypothesis.

Text from "C:\Users\Cledoux\AppData\Roaming\Armory\armorylog.txt"
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1137 - C++ block utilities loaded successfully
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1247 -
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1248 -
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1249 -
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1250 - ************************************************************
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1251 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1252 - ************************************************************
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1253 - Loading Armory Engine:
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1254 -    Armory Version        : 0.95.1
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1255 -    Armory Build:         : 374672b751
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1256 -    PyBtcWallet  Version  : 1.35
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1257 - Detected Operating system: Windows
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1258 -    OS Variant            : 8-6.2.9200--Multiprocessor Free
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1259 -    User home-directory   : C:\Users\Cledoux\AppData\Roaming
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1260 -    Satoshi BTC directory : C:\Users\Cledoux\AppData\Roaming\Bitcoin\
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1261 -    Armory home dir       : C:\Users\Cledoux\AppData\Roaming\Armory\
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1262 - Detected System Specs    :
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1263 -    Total Available RAM   : 15.92 GB
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1264 -    CPU ID string         : Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1265 -    Number of CPU cores   : 8 cores
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1266 -    System is 64-bit      : True
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1267 -    Preferred Encoding    : cp1252
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1268 -    Machine Arch          : amd64
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1269 -    Available HDD (ARM)   : 384 GB
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1270 -    Available HDD (BTC)   : 384 GB
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1271 -
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1272 - Network Name: Main Network
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1273 - Satoshi Port: 8333
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1274 - Do wlt check: True
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1275 - Named options/arguments to armoryengine.py:
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     thread_count    : -1
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     rescan          : False
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     ignoreAllZC     : False
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     rescanBalance   : False
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     disableModules  : False
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     port            : None
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     interport       : 8223
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     skipStatsReport : False
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     forceWalletCheck: False
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     regtest         : False
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     rebuild         : False
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     nettimeout      : 2
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     datadir         : DEFAULT
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     clearMempool    : False
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     offline         : False
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     coverageOutputDir: None
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     armoryDBDir     : DEFAULT
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     armorydb_port   : 9001
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     satoshiPort     : DEFAULT
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     useTorSettings  : False
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     netlog          : False
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     keypool         : 100
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     coverageInclude : None
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     forceOnline     : False
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     skipAnnounceCheck: False
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     redownload      : False
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     armorydb_ip     : 127.0.0.1
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     multisigFile    : DEFAULT
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     ram_usage       : -1
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     testAnnounceCode: False
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     mtdebug         : False
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     logDisable      : False
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     settingsPath    : C:\Users\Cledoux\AppData\Roaming\Armory\ArmorySettings.txt
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     db_type         : DB_FULL
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     doDebug         : False
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     enableDetSign   : True
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     disableConfPermis: False
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     testnet         : False
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     rpcport         : DEFAULT
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     satoshiHome     : DEFAULT
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     satoshiRpcport  : DEFAULT
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     logFile         : C:\Users\Cledoux\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1277 -     verbosity       : None
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1278 - Other arguments:
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1281 - ************************************************************
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:1684 - C++ block utilities loaded successfully
2017-03-23 17:54 (INFO) -- BDM.pyc:367 - Using the asynchronous/multi-threaded BlockDataManager.
2017-03-23 17:54 (INFO) -- BDM.pyc:368 - Blockchain operations will happen in the background. 
2017-03-23 17:54 (INFO) -- BDM.pyc:369 - Devs: check TheBDM.getState() before asking for data.
2017-03-23 17:54 (INFO) -- BDM.pyc:370 - Registering addresses during rescans will queue them for
2017-03-23 17:54 (INFO) -- BDM.pyc:371 - inclusion after the current scan is completed.
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:3597 - Using settings file: C:\Users\Cledoux\AppData\Roaming\Armory\ArmorySettings.txt
2017-03-23 17:54 (INFO) -- ArmoryQt.py:2485 - loadWalletsAndSettings
2017-03-23 17:54 (INFO) -- ArmoryQt.py:2539 - Loading wallets...
2017-03-23 17:54 (WARNING) -- ArmoryQt.py:2565 - ***WARNING: Duplicate wallet detected, mPc9fAqD
2017-03-23 17:54 (WARNING) -- ArmoryQt.py:2575 - Second wallet is more useful than the first one...
2017-03-23 17:54 (WARNING) -- ArmoryQt.py:2576 -      Wallet 1 (skipped): C:\Users\Cledoux\AppData\Roaming\Armory\armory_mPc9fAqD__WatchOnly.wallet
2017-03-23 17:54 (WARNING) -- ArmoryQt.py:2577 -      Wallet 2 (loaded):  C:\Users\Cledoux\AppData\Roaming\Armory\armory_mPc9fAqD_.wallet
2017-03-23 17:54 (INFO) -- ArmoryQt.py:2598 - Number of wallets read in: 2
2017-03-23 17:54 (INFO) -- ArmoryQt.py:2603 -    Wallet (x9ntoTwV):    "New Primary Wallet              "   (Encrypted)
2017-03-23 17:54 (INFO) -- ArmoryQt.py:2603 -    Wallet (mPc9fAqD):    "Primary Wallet                  "   (Encrypted)
2017-03-23 17:54 (INFO) -- ArmoryQt.py:2153 - Setting up networking...
2017-03-23 17:54 (INFO) -- ArmoryQt.py:1412 - setupUriRegistration
2017-03-23 17:54 (INFO) -- ArmoryQt.py:1480 - Armory already registered for current user.  Done!
2017-03-23 17:54 (INFO) -- ArmoryQt.py:546 - Usermode: Advanced
2017-03-23 17:54 (INFO) -- ArmoryQt.py:1708 - Changing usermode:
2017-03-23 17:54 (INFO) -- ArmoryQt.py:1709 -    From: Advanced
2017-03-23 17:54 (INFO) -- ArmoryQt.py:1717 -      To: Advanced
2017-03-23 17:54 (INFO) -- ArmoryQt.py:2217 - startBitcoindIfNecessary
2017-03-23 17:54 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2017-03-23 17:54 (INFO) -- SDM.pyc:382 - Reading bitcoin.conf file
2017-03-23 17:54 (INFO) -- SDM.pyc:756 - Creating proxy in SDM: host=127.0.0.1, port=8332
2017-03-23 17:54 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2017-03-23 17:54 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--spawnId="AHmiAtGMDjk1LhtFGLDz7a3EF8v8LnTpWK3Sk82LaAnf"', u'--satoshi-datadir="C:\\Users\\Cledoux\\AppData\\Roaming\\Bitcoin\\blocks"', u'--datadir="C:\\Users\\Cledoux\\AppData\\Roaming\\Armory\\"', u'--dbdir="C:\\Users\\Cledoux\\AppData\\Roaming\\Armory\\databases"']
2017-03-23 17:54 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2017-03-23 17:54 (INFO) -- ArmoryQt.py:2289 - loadBlockchainIfNecessary
2017-03-23 17:54 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2017-03-23 17:54 (INFO) -- ArmoryQt.py:5645 - Dashboard switched to "Scanning" mode
2017-03-23 17:54 (INFO) -- ArmoryQt.py:5645 - Dashboard switched to "Scanning" mode
2017-03-23 17:54 (INFO) -- ArmoryQt.py:2886 - Current block number: 458466
2017-03-23 17:54 (WARNING) -- SDM.pyc:854 - Called callJSON(estimatepriority, (3,))
2017-03-23 17:54 (WARNING) -- SDM.pyc:855 - Current SDM state: BitcoindNeverStarted
2017-03-23 17:55 (INFO) -- (PPRINT from ArmoryQt.py:3491)

  01000000 014e68a2 96e75040 6c361026 134881ab d064bd48 8f9bf558 60fc9bb0
  344c7819 52010000 008a4730 44022100 fa7d2700 55e4d635 3d59ed89 98d987d0
  f0341aa4 53279125 7bee8d96 540af1bd 021f08e0 bb5a85c2 9f20454f 5b4d6973
  e5664dbe 67807561 3ded8fc0 f8db3ed1 ca014104 dc131b6a 589768a3 f51e2239
  258ccb1d b2834051 f6014863 8a816a67 107324a8 6c3e6ebd 1aab7345 b4205f97
  387466af 7a8db115 eba6f114 7d866b64 7cf0d385 ffffffff 01809b51 00000000
  001976a9 14e55c0f 3b5f3516 1de68088 e2d3b83c ca5747a4 4388ac00 000000
2017-03-23 17:55 (INFO) -- (PPRINT from ArmoryQt.py:3492)
Transaction:
   TxHash:    83678f0cc35bf2348f7396d8502039ff330eeee01793628a5b362829bc976dfd (BE)
   Version:   1
   nInputs:   1
   nOutputs:  1
   LockTime:  0
   Inputs:
      PyTxIn:
         PrevTxHash: 5219784c34b09bfc6058f59b8f48bd64d0ab8148132610366c4050e796a2684e (BE)
         TxOutIndex: 1
         Script:     (473044022100fa7d270055e4d6353d59ed8998d987d0f0341aa4532791257bee)
         Sender:     1C3p9iFz7CZCd5QzA8y5pDVQqtBLVJZDgM
         Seq:        4294967295
   Outputs:
      TxOut:
         Value:   5348224 (0.05348224)
         Script:  OP_DUP OP_HASH160 (1Muk2LT67kW7C8bfcdgHv5kNVRphTq93Bf) OP_EQUALVERIFY OP_CHECKSIG

2017-03-23 17:55 (INFO) -- ArmoryQt.py:3496 - Sending Tx, fd6d97bc2928365b8a629317e0ee0e33ff392050d896738f34f25bc30c8f6783
2017-03-23 17:55 (INFO) -- ArmoryQt.py:6368 - BDM is safe for clean shutdown
2017-03-23 17:55 (INFO) -- SDM.pyc:588 - Called stopBitcoind
2017-03-23 17:55 (INFO) -- SDM.pyc:594 - ...but bitcoind is not running, to be able to stop
2017-03-23 17:55 (INFO) -- ArmoryQt.py:6386 - Attempting to close the main window!

[clatos]

Those who have are experiencing this issue, can you please post your armorylog.txt and dbLog.txt files found in the Armory data folder? I am investigating what is causing this problem, and I will need to see both log files to confirm my current hypothesis.

Text from "C:\Users\Cledoux\AppData\Roaming\Armory\dbLog.txt"


Log file opened at 1490288077: C:\Users\Cledoux\AppData\Roaming\Armory\dbLog.txt
-INFO  - 1490288077: (..\main.cpp:23) Running on 8 threads
-INFO  - 1490288077: (..\main.cpp:24) Ram usage level: 4
-INFO  - 1490288077: (..\BlockUtils.cpp:1338) blkfile dir: C:\Users\Cledoux\AppData\Roaming\Bitcoin\blocks
-INFO  - 1490288077: (..\BlockUtils.cpp:1339) lmdb dir: C:\Users\Cledoux\AppData\Roaming\Armory\databases
-INFO  - 1490288077: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1490288079: (..\BlockUtils.cpp:1521) Executing: doInitialSyncOnLoad
-INFO  - 1490288079: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO  - 1490288079: (..\BDM_Server.cpp:797) registered bdv: d0b1b9fa09cac19a8593
-INFO  - 1490288080: (..\DatabaseBuilder.cpp:208) Found 458467 headers in db
-INFO  - 1490288082: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO  - 1490288082: (..\DatabaseBuilder.cpp:477) Found next block after skipping 394205bytes
-INFO  - 1490288083: (..\DatabaseBuilder.cpp:268) parsed block file #811
-DEBUG - 1490288083: (..\Blockchain.cpp:242) Organizing chain
-INFO  - 1490288083: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.352s
-INFO  - 1490288083: (..\DatabaseBuilder.cpp:106) scanning new blocks from #458467 to #458466
-INFO  - 1490288083: (..\BlockchainScanner.cpp:52) no history to scan
-INFO  - 1490288083: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO  - 1490288083: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.005s
-INFO  - 1490288083: (..\DatabaseBuilder.cpp:160) init db in 3.988s
-INFO  - 1490288083: (..\BlockUtils.cpp:1636) Enabling zero-conf tracking
-ERROR - 1490288103: (..\SocketObject.cpp:125) poll() error in writeToSocket: 10038
-INFO  - 1490288106: (..\BDM_Server.cpp:826) unregistered bdv: d0b1b9fa09cac19a8593
-INFO  - 1490288106: (..\BDM_Server.cpp:737) proceeding to shutdown
-ERROR - 1490288110: (..\SocketObject.cpp:262) poll() error in readFromSocketThread: 10038
-ERROR - 1490288110: (..\BitcoinP2P.cpp:851) caught SocketError exception in processDataStackThread: poll() error in readFromSocketThread: 10038
-INFO  - 1490288115: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-ERROR - 1490288115: (..\BDM_mainthread.cpp:257) caught exception in main thread: terminate

[achow101]

I'm running "C:\Program Files (x86)\Armory\ArmoryQt.exe" -disablewallet

-dsiablewallet is an argument for bitcoin-qt (Bitcoin Core) not for Armory. Anyways, you don't need to use that option.

Restart Armory. Watch the ArmoryDB window (a command prompt window that will have some output) that appears and your current block count in the bottom right hand corner of Armory. When you want to send, make sure that the block count is up to date and that there is no error in the ArmoryDB window that says anything like "Disconnected from Bitcoin node". If you do see that error, or the ArmoryDB window has disappeared, restart Armory, check those again, then send. Repeat until you are able to send.

The bug that is causing this issue has been fixed for 0.96. The 0.96 testing builds will be out soon, after goatpig finishes implementing RBF for 0.96.

[clatos]

I'm running "C:\Program Files (x86)\Armory\ArmoryQt.exe" -disablewallet

-dsiablewallet is an argument for bitcoin-qt (Bitcoin Core) not for Armory. Anyways, you don't need to use that option.

Restart Armory. Watch the ArmoryDB window (a command prompt window that will have some output) that appears and your current block count in the bottom right hand corner of Armory. When you want to send, make sure that the block count is up to date and that there is no error in the ArmoryDB window that says anything like "Disconnected from Bitcoin node". If you do see that error, or the ArmoryDB window has disappeared, restart Armory, check those again, then send. Repeat until you are able to send.

The bug that is causing this issue has been fixed for 0.96. The 0.96 testing builds will be out soon, after goatpig finishes implementing RBF for 0.96.

Thank you for your advise. I just did what you suggested. In the ArmoryDB.exe commandprompt window, there is no error and the line with the current blocks correspond with the one on the bottom right hand corner of Armory. However, when I send bitcon from one wallet to my other wallet, an error in the ArmoryDB.exe windows appears: "-ERROR -1490370418: (..\SocketObject.cpp:125) poll() error in writeToSocket: 10038". I guess I just wait for the new version and hopefully, the problem will be solved. Otherwise I'm screwed.