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

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

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

Still not working...
Anyone have any ideas?

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

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

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.

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

Not totally sure what fixed the problem but after reindex its up and running as full node again.

Decided to start a reindex via command prompt will report back after it's done. only 3 years to go lol

Hello all,
I have been searching for a day and cant seem to figure out why bitcoin core is stuck.
win 10 latest updates
was working fine 6 days ago
debug log attached
have checked ports and 8333 is set to open on firewall and asus router but port checker says blocked.


2017-12-27 18:15:29 Bitcoin version v0.15.1

2017-12-27 18:15:49 ProcessMessages(headers, 75009 bytes) FAILED peer=0
2017-12-27 18:15:51 receive version message: /Satoshi:0.15.1/: version 70015, blocks=501299, us=73.93.78.5:51556, peer=1
2017-12-27 18:15:51 ERROR: AcceptBlockHeader: block 0000000000000000006a69cc9058e643bbecff0d328b59553f2802d75d7ebe9b is marked invalid
2017-12-27 18:15:51 ERROR: invalid header received
2017-12-27 18:15:51 ProcessMessages(headers, 75009 bytes) FAILED peer=1
2017-12-27 18:15:52 receive version message: Armory:0.96.3.99: version 70012, blocks=-1, us=127.0.0.1:8333, peer=2
2017-12-27 18:15:55 Loading addresses from DNS seeds (could take a while)
2017-12-27 18:15:55 234 addresses found from DNS seeds
2017-12-27 18:15:55 dnsseed thread exit
2017-12-27 18:16:13 receive version message: /Satoshi:0.14.2/UASF-Segwit:1.0(BIP148)/: version 70015, blocks=501299, us=73.93.78.5:58345, peer=3
2017-12-27 18:16:14 ERROR: AcceptBlockHeader: block 0000000000000000006a69cc9058e643bbecff0d328b59553f2802d75d7ebe9b is marked invalid
2017-12-27 18:16:14 ERROR: invalid header received
2017-12-27 18:16:14 ProcessMessages(headers, 75009 bytes) FAILED peer=3
2017-12-27 18:16:20 receive version message: /Satoshi:0.15.1/: version 70015, blocks=501299, us=139.59.210.12:8333, peer=5
2017-12-27 18:16:21 ERROR: AcceptBlockHeader: block 0000000000000000006a69cc9058e643bbecff0d328b59553f2802d75d7ebe9b is marked invalid
2017-12-27 18:16:21 ERROR: invalid header received
2017-12-27 18:16:21 ProcessMessages(headers, 75009 bytes) FAILED peer=5
2017-12-27 18:16:21 receive version message: /Satoshi:0.13.1/: version 70014, blocks=501299, us=73.93.78.5:58369, peer=6
2017-12-27 18:16:22 receive version message: /Satoshi:0.15.0/: version 70015, blocks=501299, us=[2601:647:ca01:4708:aded:5d88:9938:3075]:58366, peer=4
2017-12-27 18:16:22 receive version message: /Satoshi:0.15.1/: version 70015, blocks=501299, us=73.93.78.5:58370, peer=7
2017-12-27 18:16:28 receive version message: /Satoshi:0.14.2/: version 70015, blocks=501299, us=73.93.78.5:58386, peer=8
2017-12-27 18:16:28 ERROR: AcceptBlockHeader: block 0000000000000000006a69cc9058e643bbecff0d328b59553f2802d75d7ebe9b is marked invalid
2017-12-27 18:16:28 ERROR: invalid header received
2017-12-27 18:16:28 ProcessMessages(headers, 75009 bytes) FAILED peer=4
2017-12-27 18:16:28 receive version message: /Satoshi:0.15.1/: version 70015, blocks=501299, us=73.93.78.5:58391, peer=9
2017-12-27 18:16:29 ERROR: AcceptBlockHeader: block 0000000000000000006a69cc9058e643bbecff0d328b59553f2802d75d7ebe9b is marked invalid
2017-12-27 18:16:29 ERROR: invalid header received
2017-12-27 18:16:29 ProcessMessages(headers, 75009 bytes) FAILED peer=7
2017-12-27 18:16:30 ERROR: AcceptBlockHeader: block 0000000000000000006a69cc9058e643bbecff0d328b59553f2802d75d7ebe9b is marked invalid
2017-12-27 18:16:30 ERROR: invalid header received
2017-12-27 18:16:30 ProcessMessages(headers, 75009 bytes) FAILED peer=8
2017-12-27 18:16:35 receive version message: /Satoshi:0.15.1/: version 70015, blocks=501299, us=73.93.78.5:58408, peer=10
2017-12-27 18:16:35 receive version message: /Satoshi:0.15.0/: version 70015, blocks=501299, us=73.93.78.5:58409, peer=11
2017-12-27 18:16:36 ERROR: AcceptBlockHeader: block 0000000000000000006a69cc9058e643bbecff0d328b59553f2802d75d7ebe9b is marked invalid
2017-12-27 18:16:36 ERROR: invalid header received
2017-12-27 18:16:36 ProcessMessages(headers, 75009 bytes) FAILED peer=10
2017-12-27 18:16:36 ERROR: AcceptBlockHeader: block 0000000000000000006a69cc9058e643bbecff0d328b59553f2802d75d7ebe9b is marked invalid
2017-12-27 18:16:36 ERROR: invalid header received
2017-12-27 18:16:36 ProcessMessages(headers, 75009 bytes) FAILED peer=11
2017-12-27 18:16:58 receive version message: /Satoshi:0.15.1/: version 70015, blocks=501299, us=73.93.78.5:58466, peer=12
2017-12-27 18:16:58 ERROR: AcceptBlockHeader: block 0000000000000000006a69cc9058e643bbecff0d328b59553f2802d75d7ebe9b is marked invalid
2017-12-27 18:16:58 ERROR: invalid header received
2017-12-27 18:16:58 ProcessMessages(headers, 75009 bytes) FAILED peer=12
2017-12-27 18:17:37 receive version message: /Satoshi:0.15.1/: version 70015, blocks=501299, us=[2a03:b0c0:3:d0::2400:f001]:8333, peer=13
2017-12-27 18:17:38 ERROR: AcceptBlockHeader: block 0000000000000000006a69cc9058e643bbecff0d328b59553f2802d75d7ebe9b is marked invalid
2017-12-27 18:17:38 ERROR: invalid header received
2017-12-27 18:17:38 ProcessMessages(headers, 75009 bytes) FAILED peer=13
2017-12-27 18:18:01 receive version message: /Satoshi:0.15.1/: version 70015, blocks=501299, us=73.93.78.5:58629, peer=14
2017-12-27 18:18:06 receive version message: /Satoshi:0.15.0.1/: version 70015, blocks=501299, us=[2601:647:ca01:4708:aded:5d88:9938:3075]:58641, peer=15
2017-12-27 18:18:07 receive version message: /Satoshi:0.15.1/: version 70015, blocks=501299, us=73.93.78.5:58644, peer=16
2017-12-27 18:18:13 receive version message: /Satoshi:0.15.0.1/: version 70015, blocks=501299, us=73.93.78.5:58661, peer=17
2017-12-27 18:18:25 receive version message: /Satoshi:0.15.1/: version 70015, blocks=501299, us=73.93.78.5:58696, peer=18
2017-12-27 18:18:47 receive version message: /Satoshi:0.15.1/: version 70015, blocks=501299, us=73.93.78.5:58746, peer=19
2017-12-27 18:18:59 receive version message: /Satoshi:0.15.0.1/: version 70015, blocks=501299, us=73.93.78.5:58771, peer=20
2017-12-27 18:19:05 receive version message: /Satoshi:0.15.1/: version 70015, blocks=501299, us=73.93.78.5:58789, peer=21
2017-12-27 18:19:06 receive version message: /Satoshi:0.15.0.1(UASF-SegWit-BIP148)/: version 70015, blocks=501299, us=73.93.78.5:58791, peer=22
2017-12-27 18:19:46 receive version message: /Satoshi:0.14.2/: version 70015, blocks=501299, us=73.93.78.5:58873, peer=23
2017-12-27 18:20:20 ProcessMessages(version, 113 bytes) FAILED peer=24
2017-12-27 18:22:53 receive version message: /Satoshi:0.15.1/: version 70015, blocks=501299, us=73.93.78.5:59308, peer=25

Reposting because I still have not figured this out

Hello,
So I have a single Antminer S1 works fine on wifi or hardwire but.....

When I have it just connected on wifi I can not log into it from a web browser.
I have verified I am trying to logon to the proper ip and it says "LuCI - Lua Configuration Interface" for about 20 seconds then goes to the oops! google chrome blablabla

I have reset the unit 2-3 times and checked everything.
I have WAN and WWAN both set to DHCP and can see both the assigned IP's in my router settings

Thanks in advance
Crash

Hello,
So I have a single Antminer S1 works fine on wifi or hardwire but.....

When I have it just connected on wifi I can not log into it from a web browser.
I have verified I am trying to logon to the proper ip and it says "LuCI - Lua Configuration Interface" for about 20 seconds then goes to the oops! google chrome blablabla

I have reset the unit 2-3 times and checked everything.
I have WAN and WWAN both set to DHCP and can see both the assigned IP's in my router settings

Thanks in advance
Crash