Topic: Cannot send coins - Bitcoin-Qt has disconnected (Read 1447 times)

Ok, I take part of that back. There was 2 transactions after that one which were not listed in Armory so it must indeed have been trying to double spend old funds. Just did a Rescan Databases and the missing transactions appeared and a new spend now worked correctly.
Don't know how it lost the other 2 but this issues seems resolved now.

Thanks,
-M.

Here is a blockchain decode of that exported raw transaction if that helps:

{
   "lock_time":0,
   "size":119,
   "inputs":[
      {
         "prev_out":{
            "index":0,
            "hash":"a3a9289e65507e1ed1eed508d464c29741f03f17452eefe28b416c8e8c14856d"
         },
         "script":""
      }
   ],
   "version":1,
   "vin_sz":1,
   "hash":"be345d474f4239ae26d556dd8dda4a0e8e49ec2f4157d47c966db70a1300d21c",
   "vout_sz":2,
   "out":[
      {
         "script_string":"OP_DUP OP_HASH160 e47dea41434f8681a7059281ae72a290192f1c7b OP_EQUALVERIFY OP_CHECKSIG",
         "address":"1Mq9uUCbYzX8DXvRe7wP94RRCxFkcYnqQk",
         "value":500000,
         "script":"76a914e47dea41434f8681a7059281ae72a290192f1c7b88ac"
      },
      {
         "script_string":"OP_DUP OP_HASH160 4008faea265eb318074af7343379f84a5261fde2 OP_EQUALVERIFY OP_CHECKSIG",
         "address":"16qb1EDcuP9DMM6gdGtb6pp1QKUwACsUYR",
         "value":23109500,
         "script":"76a9144008faea265eb318074af7343379f84a5261fde288ac"
      }
   ]
}

So the input is this:
https://blockchain.info/tx/a3a9289e65507e1ed1eed508d464c29741f03f17452eefe28b416c8e8c14856d

Which based on amounts & timing looks like the last successful spend I did from this wallet and I should have had 0.23BTC change from it.
Does that mean that input tx should have that much left for spending, or does that become a new input in the chain and for some reason Armory is trying to re-use an old one?

Thanks,
-M.

Thanks Kupsi. I just tried that but this button is available prior to me unlocking the wallet, and soon as I unlock the wallet the transaction tries to send. Wouldn't the transaction have to get signed before I can broadcast it like that?

For what its worth putting the pre-unlock one into that url results in this:
An outpoint is already spent in [DBBitcoinTx [txIndex=67394115,  getEstimatedBTCSent()=0, isGeneratedBlockReward()=false, getTotalBTCSent()=0, getHash()=a99ba1b23a5b2da8d01f745bbc9bc2575bb5d5bad96deb92dc5a11697b4f1feb, getVersion()=1, getSize()=257, toString()=BitcoinTx{hash=a99ba1b23a5b2da8d01f745bbc9bc2575bb5d5bad96deb92dc5a11697b4f1feb, version=1, lockTime=0, in=[], out=[]}, getClass()=class piuk.blockchain_db.DBBitcoinTx]] [(66544405, 0)]

I checked this URL for a few mins after a failed attempt from Armory but the txid does not show up in this list either:
https://blockchain.info/rejected
The one I pasted in manually does and is recorded with that error above.

-M.

If you need to send the transaction before you get help, you can try to copy the transaction (the button "Copy Final Tx (Hex)") and paste it here: https://blockchain.info/en/pushtx

Hello,

I've started hitting this recently and it seems I can no longer make payments from my Armory wallet. Every time I try to send I get a popup from tray saying connection to Bitcoin-qt has been lost. It re-connects shortly after and then armory pops up a window saying the transaction failed and to verify it in the block chain. It never shows up in the block explorer.

Windows 7 x64.
At the time I was on Bitcoin Core 0.9.1 and Armory 0.91.2. It's a standard online wallet. A few weeks before that I made a payment with no issues so not sure what changed. Receiving coins is no problem as I just transferred around 1BTC into it before this problem appeared; which now appears stuck there.

On advice from Armory support I upgraded to latest versions of both (0.9.3 core & 0.92.3 Armory) but the problem remains the same.

At the time of attempt the only thing logged in bitcoin core debug file is this:
2014-12-07 02:49:43 receive version message: Armory:0.92.3: version 40000, blocks=-1, us=[::127.0.0.1]:8333, them=[::127.0.0.1]:62906, peer=127.0.0.1:62906
2014-12-07 02:49:44 keypool reserve 6
2014-12-07 02:49:44 keypool return 6
...and lots more of those. No other clues; is this the right log file to look at?

Armory just logs that the connection was lost:
2014-12-07 13:49 (INFO) -- Networking.pyc:278 - sendTx called...
2014-12-07 13:49 (INFO) -- ArmoryQt.py:3759 - Transaction sent to Satoshi client...!
2014-12-07 13:49 (ERROR) -- Networking.pyc:357 - ***Connection to Satoshi client LOST!  Attempting to reconnect...

There has been no further follow up on my Armory support ticket past few days so that avenue seems to be stalled for now.

Could anyone suggest ways to further debug what is going wrong here and how to recover from it?

Thanks very much.
-M.