problem getting armory working after it was off for a month or so

[crashtest22]

Hey all,
I have looked over every thread and tutorial I could find and still cant get armory back up.
I am on a windows 10 machine with latest updates.
bitcoin core 15.1
latest armory 9.6.33

Every time I start armory it just hangs on prepping databases and does not go any further.

I have both bitcoin and armory installed on their own drive in the same directory
E:\bitcoin and E:\bitcoin\armory

What do I need to post up for us to figure this out.
I have tried factory reset to the one just before redo blockchain.
Thanks in advance

[Holliday]

Latest Armory: https://bitcointalk.org/index.php?topic=2660500.0

Possible pathing issue. https://btcarmory.com/docs/pathing

[crashtest22]

installing that version and though it could be path issue too but cant figure out how to change or check them.
I have looked at the log and it seems it is right.

[crashtest22]

installed that latest version and so far it seems to be loading scanning trans history now and its not stuck.

[crashtest22]

ok added info.
got it up and running but send coins would not open anything up.
closed and then it would not open again.

manually opened armoryDB.exe and then armory and it shows all my coins and such but still no send coin working.

after a min or 2 the armoryDB crashes

If I just open Armory hangs on preparing databases and no green bar just all grey

[crashtest22]

Still not working...
Anyone have any ideas?

[Peg]

1. bitcoin-core must be completely synced, may need a few days to update
2. then run armory to get the data from core.......

[crashtest22]

Thanks for the reply.
I have bitcoin core fully synced

I think armory is not linking properly to its database or core.
if I check my node it has been up and running for 2 days so core is up and running as it should

[crashtest22]

after being away for 4 days came back to same problem.
Really could use some help on this

[Holliday]

I would try deleting the Armory/databases folder and restart from scratch.

[forensixguy]

I'm having the same problem with "Send Bitcoin" button not working On Ubuntu 16.04, except that my problem happened out of the blue on a fully functioning copy of Armory (96.2)...Made one successful transfer, then tried to make another to a different wallet and the button doesn't respond. Core v0.15.1 is fully synced and I even uninstalled and upgraded to Armory 0.96.3.991. No change in behavior.

[droark]

You'll want to upgrade to at least 0.96.3 (preferably 0.96.4 RC2) if you're on Core 0.15.1. Core 0.15.0.1 revealed an issue that wasn't fixed until 0.96.3.

[forensixguy]

The .deb for 0.96.4 RC2 is labeled 0.96.3.991...unless there is an even more recent version?

[PhoenixFire]

The .deb for 0.96.4 RC2 is labeled 0.96.3.991...unless there is an even more recent version?

That is the correct one.

[crashtest22]

Finally got it to work.
I uninstalled armory and reinstalled in default locations.
Also renamed the bitcoin folder in appdata\roaming to bitcoin.old
then ran bitcoin core and let it update
then opened armory back up and it finally worked.

not really sure which of those fixed the issue but its up and running.

Thanks for all the tips

[forensixguy]

Finally got it to work.
I uninstalled armory and reinstalled in default locations.
Also renamed the bitcoin folder in appdata\roaming to bitcoin.old
then ran bitcoin core and let it update
then opened armory back up and it finally worked.

not really sure which of those fixed the issue but its up and running.

Thanks for all the tips

Firstly, apologies to crashtest22 et al...I didn't intend to threadjack this convo.

That being said, I also got my setup to work as well. I tried many things, and wouldn't know what fixed the issue had I not been able to compare what I did against your list. By combining our lists, it seems that the way to fix this (for me) was to upgrade to latest version of Armory, delete the database folder in bitcoin core, run bitcoin core and let it re-update (mine took the better part of a day), and then run Armory.

Everything's back to normal. Thanks to all who responded!