I can not see core running on your screenshot. Do you have core synced and running ?
Armory needs core to be fully synced and running since it retrieves the data (incoming transations, balances, ..) from your local core installation.
Running bitcoind in the background - Note that Armory says connected, but 0 blocks - confirmed in the logs.Armory needs core to be fully synced and running since it retrieves the data (incoming transations, balances, ..) from your local core installation.
@truebits
Going on the last entry in your logs, it was still scanning the blocks at this point:
Code:
-INFO - 23:31:19.719: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #507886 to #508389
If I'm reading it right, you kept everything running overnight then exported the log?Code:
2018-09-03 23:31:19 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-09-04 04:57:54 (INFO) -- ArmoryQt.py:3672 - Log saved to D:/armorylog_20180904_0457.txt
2018-09-04 04:57:54 (INFO) -- ArmoryQt.py:3672 - Log saved to D:/armorylog_20180904_0457.txt
Assuming Bitcoin Core is fully synced, ArmoryDB might be choking on some corrupt data... though there is or was something strange going on with the 2bW2mnkwH wallet.
I'd guess an Armory database rebuild, and failing that a reindex in Bitcoin Core. Running Bitcoin Core separately from Armory would be worth a shot too, but needs a little configuration to work.
