Cannot send btc, even to same wallet w/ different address

[dv-partners]

All,

Any advise would be appreciated. Can't figure out why I cannot send out any BTC from my armory wallet. It worked fine yesterday when I sent from 1 wallet address to another address within same wallet.

Now when I try to send to a different address (outside of my wallet), nothing happens when I click send. No prompt for unlocking wallet, nothing. When I tried again to send to myself, same problem. Nothing. No dialog box.

Any ideas?

I'm running Armory 0.90-beta with 0.8.6-beta bitcoind, the same as yesterday when it worked fine.

Edit: Windows 7 x64

Thanks in advance.

[dv-partners]

I have now "Cleared all Unconfirmed" and rebuilt and rescanned the database. Same issue.

[goatpig]

Send us your log file at support@bitcoinarmory.com

I think we already encountered this bug and have a fix scheduled for the next release.

[dv-partners]

Send us your log file at support@bitcoinarmory.com

I think we already encountered this bug and have a fix scheduled for the next release.

k, sent. Btw ultimately resolved the issue by restoring my original (day one) wallet. I noticed that then the wallet was restored, there was no record of the within-wallet transfer I executed yesterday and what I mentioned in my initial post. Should there have been? Wonder if that caused the issue.



I take the above back. It doesn't seem as though it solved anything. While the wallet registers and shows the decreased balance, the blockchain still has no record after an hour. Doesn't seem as though the request is being sent.

[goatpig]

You need to push you address chain up to its previous length. Start Armory in Expert mode, go to your wallet properties and click the number next to "Addresses Used", and extend your total address count by 100, see if that does it.

[dv-partners]

k, will do.

BTW, prior to this, I did "clear all unconfirmed" and the wallet did once again increase its balance by ~2 BTC (the amount I sent).

I then retransmitted the send and after ~6 hours, still nothing on blockchain. I will now try what you suggested wrt expert mode and updating wallet addresses. Will let you know how it goes.  

[dv-partners]

After multiple attempts to rescan/rebuild databases Armory keeps on crashing and becomes non-responsive. As soon as it finishes rebuilding and rescanning the database and states "Armory is online!" it becomes nonresponsive.

Here's the most recent log entries. What is this "BDM" that isn't ready? In meantime, I'm going to manually delete the Armory database, wait a few hours for it to repopulate and hope for the best. In the meantime, if you have any alternative courses of action, please let me know. Really need to send out this btc. Thanks

2014-01-21 13:56 (ERROR) -- armoryengine.pyc:13289 - ErrorOut var over-represented number of errors!
2014-01-21 13:56 (INFO) -- ArmoryQt.py:4465 - Dashboard switched to fully-online mode
2014-01-21 13:56 (INFO) -- ArmoryQt.py:3838 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2014-01-21 13:56 (INFO) -- ArmoryQt.py:3780 - Switching Armory functional mode to "Online"
2014-01-21 13:56 (INFO) -- ArmoryQt.py:3838 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2014-01-21 13:56 (INFO) -- ArmoryQt.py:1913 - Syncing wallet: xxxxxxxx[removed]
2014-01-21 13:56 (ERROR) -- ArmoryQt.py:4826 - Error in heartbeat function
Traceback (most recent call last):
  File "ArmoryQt.py", line 4684, in Heartbeat
  File "ArmoryQt.py", line 1921, in finishLoadBlockchain
  File "ArmoryQt.py", line 2098, in createCombinedLedger
  File "ArmoryQt.py", line 2158, in convertLedgerToTable
  File "ArmoryQt.py", line 2297, in getCommentForLE
  File "armoryengine.pyc", line 8549, in getCommentForLE
  File "armoryengine.pyc", line 8520, in getAddrCommentIfAvail
AttributeError: 'bool' object has no attribute 'isInitialized'
2014-01-21 13:56 (INFO) -- armoryengine.pyc:10634 - Received new block.  00000000000000010d2c02e02fbd8380a362d027e31c33b47f894394a98f9c32
2014-01-21 13:56 (INFO) -- ArmoryQt.py:4465 - Dashboard switched to fully-online mode
2014-01-21 13:56 (INFO) -- ArmoryQt.py:3838 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2014-01-21 13:56 (INFO) -- ArmoryQt.py:3780 - Switching Armory functional mode to "Online"
2014-01-21 13:56 (INFO) -- ArmoryQt.py:3838 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2014-01-21 13:56 (INFO) -- ArmoryQt.py:1913 - Syncing wallet: xxxxxxxx[removed]
2014-01-21 13:57 (ERROR) -- armoryengine.pyc:12346 - BDM was not ready for your request!  Waited 20 sec.
2014-01-21 13:57 (ERROR) -- armoryengine.pyc:12347 -   getattr   name: getTopBlockHeight
2014-01-21 13:57 (ERROR) -- armoryengine.pyc:12348 - BDM currently doing: Passthrough (77085921)
2014-01-21 13:57 (ERROR) -- armoryengine.pyc:12349 - Waiting for completion: ID= 87922959
2014-01-21 13:57 (ERROR) -- armoryengine.pyc:12350 - Direct traceback
2014-01-21 13:57 (ERROR) -- armoryengine.pyc:12353 - Traceback:
Traceback (most recent call last):
  File "armoryengine.pyc", line 12343, in passthruFunc
  File "Queue.pyc", line 176, in get
Empty
2014-01-21 13:57 (ERROR) -- armoryengine.pyc:12346 - BDM was not ready for your request!  Waited 20 sec.
2014-01-21 13:57 (ERROR) -- armoryengine.pyc:12347 -   getattr   name: scanRegisteredTxForWallet
2014-01-21 13:57 (ERROR) -- armoryengine.pyc:12348 - BDM currently doing: Passthrough (77085921)
2014-01-21 13:57 (ERROR) -- armoryengine.pyc:12349 - Waiting for completion: ID= 90872121
2014-01-21 13:57 (ERROR) -- armoryengine.pyc:12350 - Direct traceback
2014-01-21 13:57 (ERROR) -- armoryengine.pyc:12353 - Traceback:
Traceback (most recent call last):
  File "armoryengine.pyc", line 12343, in passthruFunc
  File "Queue.pyc", line 176, in get
Empty
2014-01-21 13:57 (ERROR) -- armoryengine.pyc:13289 - ErrorOut var over-represented number of errors!
2014-01-21 13:57 (ERROR) -- armoryengine.pyc:12346 - BDM was not ready for your request!  Waited 20 sec.
2014-01-21 13:57 (ERROR) -- armoryengine.pyc:12347 -   getattr   name: getTopBlockHeight
2014-01-21 13:57 (ERROR) -- armoryengine.pyc:12348 - BDM currently doing: Passthrough (22990345)
2014-01-21 13:57 (ERROR) -- armoryengine.pyc:12349 - Waiting for completion: ID= 7485478
2014-01-21 13:57 (ERROR) -- armoryengine.pyc:12350 - Direct traceback
2014-01-21 13:57 (ERROR) -- armoryengine.pyc:12353 - Traceback:
Traceback (most recent call last):
  File "armoryengine.pyc", line 12343, in passthruFunc
  File "Queue.pyc", line 176, in get
Empty
2014-01-21 13:58 (ERROR) -- armoryengine.pyc:12346 - BDM was not ready for your request!  Waited 20 sec.
2014-01-21 13:58 (ERROR) -- armoryengine.pyc:12347 -   getattr   name: getTopBlockHeight
2014-01-21 13:58 (ERROR) -- armoryengine.pyc:12348 - BDM currently doing: Passthrough (22990345)
2014-01-21 13:58 (ERROR) -- armoryengine.pyc:12349 - Waiting for completion: ID= 90260218
2014-01-21 13:58 (ERROR) -- armoryengine.pyc:12350 - Direct traceback
2014-01-21 13:58 (ERROR) -- armoryengine.pyc:12353 - Traceback:
Traceback (most recent call last):
  File "armoryengine.pyc", line 12343, in passthruFunc
  File "Queue.pyc", line 176, in get
Empty
2014-01-21 13:58 (ERROR) -- armoryengine.pyc:13289 - ErrorOut var over-represented number of errors!
2014-01-21 13:58 (ERROR) -- ArmoryQt.py:4826 - Error in heartbeat function
Traceback (most recent call last):
  File "ArmoryQt.py", line 4684, in Heartbeat
  File "ArmoryQt.py", line 1921, in finishLoadBlockchain
  File "ArmoryQt.py", line 2059, in createCombinedLedger
  File "ArmoryQt.py", line 2059, in <lambda>
TypeError: unsupported operand type(s) for -: 'NoneType' and 'int'

[goatpig]

At this point you have to manually delete the DB and rebuild.

[dv-partners]

At this point you have to manually delete the DB and rebuild.

yup, what I'm doing now. 45% more to go. If that doesn't work is there anything else I can do? (In the event that you're not here when it's done repopulating.)

[dv-partners]

good news finally. deleted the databases manually and let it repopulate.

The troubleshooting FAQ treats this as a last resort, but it took as much time as rebuilding and re-searching. Why not just go straight to this step if it's more reliable?

In any case, thanks for your assistance.

[goatpig]

We actually are changing to this behavior in the next release, turns out it is preferable.