Thanks your advice.

Could you explain what are the implications of this.

Does this advice come with any kind of recommendation to run Armory v0.96.5 with the older Bitcoin Core v27 or v27.2, in place of Bitcoin Core v28 or v29 ?

For those having issues running Armory v0.96.5 after upgrading Bitcoin Core from v27 to v28 or v29 here are some tips:

When running Armory v0.96.5, Armory will work, with Bitcoin Core v27 or 27.2 present, but not running.

If you upgrade Bitcoin core to v28 v28.1 or v29, but load Armory on its own, you can get an error in Armory saying: 

  "Armory failed to spawn the DB!
  Continuing operations in offline mode instead.
  Refer to the dbLog.txt for more information."

I found the simple solution was to run Bitcoin Core, and keep it running, before starting Armory.

This way you can upgrade Bitcoin Core v28, v28.1 or v29.

Note that I did NOT have to resort to "Add a blocksxor=0 line to bitcoin.conf file or use it as a command line arg: --blocksxor=0".

I decided to revert back to v27.2, so I can run Armory on its own, which I feel is a safer option, however I am putting this information out there for those confident in running Armory v0.96.5 with the latest v29 of Bitcoin Core.

I run Windows 11 (64bit) on a PC.

Hope this helps.

I am pleased to say that I have mananged to fix the issue.

As indicated due to the same error repeating as a last resort I uninstalled and reinstalled both programs and see if that helps to get things working correctly.

It took approx 2 days to download the complete blockchain, and fortunately there were no errors and both Bitcoin Core and Armory are working well.

goatpig - Thanks for confirming that running Armory version is 0.96.5-beta-8730390989 together with the full 648 Gb blockchain of Bitcoin Core 27.0 (64 bit) is capable of working on Win 11.

nc50lc - Thanks the tip regarding ghost processes which I will use next time if I encounter a similar problem.

From this excercise I have learned the following:

 1. If all else fails re-download the entire blockchain as it takes less than 2 days (and not just re-index it).

 2. In my specific case the Armory program did not behave as per the user manual. Entering the directiries for Bitcoin Core, the blockchain and Armory databases (for my setup locations on a spare fast SSD), into FILE / SETTINGS made no change to the program. Neither did placing the same information into the armoryqt.conf file. The only way I could get Armory online was to use suffixes in the desktop shortcut i.e. using
[ Z:\Armory\ArmoryQt.exe --satoshi-datadir="Z:\Bitcoin Core Data\blocks"  --dbdir="Z:\Armory Data" ].

Hope this helps anyone finding themselves in the same situation as myself.

 

Thanks for your advice on this. From your advice at least I know that running Armory version is 0.96.5-beta-8730390989 together with the full 648 Gb blockchain of Bitcoin Core 27.0 (64 bit) is capable of working on Win 11.

As recommended I deleted the Armory database folder, but had the same error.

I also tried re-indexed the bitcoin core blockchain, and deleted the Armory database folder, but unfortunately the same error occured again at Scanning Transaction History at 59%.

A last resort will be to uninstall and reinstall both programs and see if that helps to get things working correctly.

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