You're downloading Armory from the wrong place... So you're using an old, outdated version.
Correct website is: https://btcarmory.com
Most recent "stable" version is here: https://btcarmory.com/0.96.3-release/
However, that version doesn't play well with Bitcoin Core v0.15.0.1... so you'll need the latest beta release from here: https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.3.99
Aka v0.96.4 RC1
Topic: Unceremonious ArmoryDB death when scanning tx history (Read 346 times)
Yep. Odd. So I basically just renamed my L:\Armory folder, created an empty one, and had Armory rebuild the database from the blockchain. Then imported my wallet files from the old folder. Seems to be working.
I hadn't done any actual transactions with my wallet in a while until yesterday. I noticed that while I could send bitcoins out, the database didn't seem to be updating. I'd have a bunch of confirmations visible on blockchain.info, and none reflected in Armory. So after much fiddling around, I upgraded Bitcoin Core to 0.15.0.1, and Armory to the latest version which appears to be 0.96-beta-a3d01aa722.
ArmoryDB, however, commits suicide at 81% through scanning the transaction history:
I don't know why it's falling on its face like this but I presume that there's a corrupt block. Unfortunately, since it isn't telling me which one to delete and redownload or even giving me a timeframe, it isn't so easy.
I'm going to try a complete rebuild of the database and see how that works.
ArmoryDB, however, commits suicide at 81% through scanning the transaction history:
Code:
-INFO - 1509778726: (..\BlockchainScanner.cpp:650) scanned from height #445832 to #445875
-INFO - 1509778727: (..\BlockchainScanner.cpp:650) scanned from height #445876 to #445893
-INFO - 1509778727: (..\BlockchainScanner.cpp:650) scanned from height #445894 to #445896
-INFO - 1509778727: (..\BlockchainScanner.cpp:650) scanned from height #445897 to #445909
-INFO - 1509778727: (..\BlockchainScanner.cpp:650) scanned from height #445910 to #445913
-INFO - 1509778727: (..\BlockchainScanner.cpp:650) scanned from height #445914 to #445926
-INFO - 1509778727: (..\BlockchainScanner.cpp:650) scanned from height #445927 to #446013
-INFO - 1509778727: (..\BlockchainScanner.cpp:650) scanned from height #446014 to #446039
-INFO - 1509778728: (..\BlockchainScanner.cpp:650) scanned from height #446040 to #446074
-INFO - 1509778728: (..\BlockchainScanner.cpp:650) scanned from height #446075 to #446199
-INFO - 1509778728: (..\BlockchainScanner.cpp:650) scanned from height #446200 to #446282
-INFO - 1509778729: (..\BlockchainScanner.cpp:650) scanned from height #446283 to #446608
-ERROR - 1509778730: (..\BlockchainScanner.cpp:271) raw data does not match expected block hash
PS C:\Program Files (x86)\Armory>
-INFO - 1509778727: (..\BlockchainScanner.cpp:650) scanned from height #445876 to #445893
-INFO - 1509778727: (..\BlockchainScanner.cpp:650) scanned from height #445894 to #445896
-INFO - 1509778727: (..\BlockchainScanner.cpp:650) scanned from height #445897 to #445909
-INFO - 1509778727: (..\BlockchainScanner.cpp:650) scanned from height #445910 to #445913
-INFO - 1509778727: (..\BlockchainScanner.cpp:650) scanned from height #445914 to #445926
-INFO - 1509778727: (..\BlockchainScanner.cpp:650) scanned from height #445927 to #446013
-INFO - 1509778727: (..\BlockchainScanner.cpp:650) scanned from height #446014 to #446039
-INFO - 1509778728: (..\BlockchainScanner.cpp:650) scanned from height #446040 to #446074
-INFO - 1509778728: (..\BlockchainScanner.cpp:650) scanned from height #446075 to #446199
-INFO - 1509778728: (..\BlockchainScanner.cpp:650) scanned from height #446200 to #446282
-INFO - 1509778729: (..\BlockchainScanner.cpp:650) scanned from height #446283 to #446608
-ERROR - 1509778730: (..\BlockchainScanner.cpp:271) raw data does not match expected block hash
PS C:\Program Files (x86)\Armory>
I don't know why it's falling on its face like this but I presume that there's a corrupt block. Unfortunately, since it isn't telling me which one to delete and redownload or even giving me a timeframe, it isn't so easy.
I'm going to try a complete rebuild of the database and see how that works.
Jump to: