 Show Posts
|
|
Pages: [1]
|
|
Hello,
Due to some issues I was forced to restore the wallet from an old backup. After the restore I didn't received BTC to an old receiving address even I saw the confirmation of the transfer. I've tried rebuild/rescand database but still can't see the incoming BTC. Can you tell me what is wrong?
Best regards,
|
|
|
|
|
Hello again :-(
The tx broadcast timed out message is back.
Armory: 0.96
Core: 0.14.1, 0.13.2
Can I import the wallets into a more stable wallet application?
|
|
|
|
You're gonna have to delete your Armory DB folder and rebuild it from scratch.
I did it. After few "not responding" I was able to make a transfer. Thank you very much! |
|
|
|
|
1) I have restarted the PC again.
2) Start the Armory app
3) Try to initiate a transfer
4) The same issue when I press Send nothing happens but in the logs I can see the bellow lines every time I pressed Send
2017-05-09 22:47 (INFO) -- TxFrames.pyc:689 - Change address behavior: NewAddr
2017-05-09 22:47 (ERROR) -- Traceback (most recent call last):
File "ui\TxFrames.pyc", line 805, in createTxAndBroadcast
File "ui\TxFrames.pyc", line 764, in validateInputsGetUSTX
File "armoryengine\Transaction.pyc", line 2284, in createFromTxOutSelection
File "armoryengine\Transaction.pyc", line 2193, in createFromPyTx
File "CppBlockUtils.pyc", line 2988, in getTxByHash
DbErrorMsg: <CppBlockUtils.DbErrorMsg; proxy of <Swig Object of type 'DbErrorMsg *' at 0x0000000009284A50> >
|
|
|
|
|
I have restarted PC many times.
|
|
|
|
Post your armorylog.txt
I can't help you if you don't show me this one file, regardless of the issue. Check your PM! |
|
|
|
|
Well, after a few reinstall armory and core, now I have another issue. When I try to send some btc, I can select the address, the amount, the fee sometime is filled, sometime not, but when I press the Send button nothing happens.
|
|
|
|
|
Well,
I've tried to send some BTC, but I wasn't able. After I pressed send nothing happens and at some point windows said that the application stopped and I should close it.
Armory: 0.96
Core 0.14.1 and 0.13.2
|
|
|
|
I've uninstalled Core and Armory and removed the Core's folders. Installed them again and now I need to wait until the core will synchronize :-(. I'll provide updates after.
Thank you very much !
That was not necessary. If you still have the files in the recycle bin I strongly suggest you to restore them and then just install 0.13.2. It will work with the same blockchain downloaded by 0.14.1. There's really no need to waste the time and the bandwidth. It's already at 101GB and I installed Core 0.14.1 |
|
|
|
|
I've uninstalled Core and Armory and removed the Core's folders. Installed them again and now I need to wait until the core will synchronize :-(. I'll provide updates after.
Thank you very much !
|
|
|
|
|
I've asked about the version because you said " I confirm that 0.96 still has the issue! Downgrading to Core 0.13.2 fixed it for now." So event the issue is the Core 0.14 even the combination 0.96 with 0.14.
Anyway thank you very much for your answers.
Best regards,
|
|
|
|
|
Thank you very much!
What is your Armory version?
|
|
|
|
|
The Bitcoin Core version is 0.14.1rss. Both of them on 64 bit.
Which logs do you want? Can I sent them only to you?
|
|
|
|
|
Hello,
Since I've upgrade Armory to 0.96 I always got the error tx broadcast timed out. I've tried to increase the fee but the same error occur. Can you help me with some advices?
Thank you very much!
|
|
|
|
|
