Armory is stuck during the 'Scanning of Transaction History'.
My Armory version is 0.96.5-beta-8730390989, and I am running the full 648Gb blockchain with Bitcoin 27.0 both in 64 bit on Win 11.
I have tried both options of running Bitcoin Core with "Let Armory run Bitcoin/bitcoind in the background" ticked and unticked.
The Scanning Transaction History sticks at 59% (1 second)
The Armory Log states as follows:
-INFO - 11:55:04.094: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #692116 to #692705
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:445) Missing file map for output scan, this is unexpected
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:447) Has the following block files:
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449) --- #2864
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449) --- #2865
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449) --- #2866
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449) --- #2867
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449) --- #2868
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449) --- #2869
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449) --- #2870
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449) --- #2871
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449) --- #2872
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:451) Was looking for id #2873
Questions:
1. Is this likely to be a problem with the Bitcoin Blockchain that may need re-downloading, or
2. Is this more likely to be caused by the Armory program not being updated to be fully compatible with Bitcoin Core v27.0 (2024 year), for example not working with certain forks etc?
In case of 2. above is it recommended to downgrade Bitcoin Core to a prior version to match the year Armory was last updated in 2018 ?
Any advice would be appreciated
My Armory version is 0.96.5-beta-8730390989, and I am running the full 648Gb blockchain with Bitcoin 27.0 both in 64 bit on Win 11.
I have tried both options of running Bitcoin Core with "Let Armory run Bitcoin/bitcoind in the background" ticked and unticked.
The Scanning Transaction History sticks at 59% (1 second)
The Armory Log states as follows:
-INFO - 11:55:04.094: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #692116 to #692705
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:445) Missing file map for output scan, this is unexpected
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:447) Has the following block files:
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449) --- #2864
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449) --- #2865
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449) --- #2866
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449) --- #2867
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449) --- #2868
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449) --- #2869
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449) --- #2870
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449) --- #2871
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449) --- #2872
-ERROR - 11:55:04.110: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:451) Was looking for id #2873
Questions:
1. Is this likely to be a problem with the Bitcoin Blockchain that may need re-downloading, or
2. Is this more likely to be caused by the Armory program not being updated to be fully compatible with Bitcoin Core v27.0 (2024 year), for example not working with certain forks etc?
In case of 2. above is it recommended to downgrade Bitcoin Core to a prior version to match the year Armory was last updated in 2018 ?
Any advice would be appreciated