EDIT3: Looking at the logs, this is what is says:
"Log file opened at 23:30:55.000: C:\Users\Bla\AppData\Roaming/Armory/dbLog.txt
-INFO - 23:30:55.000: (..\main.cpp:32) Running on 8 threads
-INFO - 23:30:55.000: (..\main.cpp:33) Ram usage level: 50
-INFO - 23:30:55.000: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:263) Listening on port 9001
-ERROR - 23:30:55.016: (..\BDM_Server.cpp:1270) There is already a process listening on 127.0.0.1:9001
-ERROR - 23:30:55.016: (..\BDM_Server.cpp:1272) ArmoryDB cannot start under these conditions. Shutting down!
-ERROR - 23:30:55.016: (..\BDM_Server.cpp:1273) Make sure to shutdown the conflicting processbefore trying again (most likely another ArmoryDB instance)."
Have you set Armory to specifically use port 9001? Mine uses a random-ish high port each launch and I'm fairly sure that is the default.
Either way, something is listening on port 9001, and ArmoryDB is trying to use that port too. As it says, it could be another ArmoryDB process that you would need to kill, or another program entirely.
If it is ArmoryDB, it is possible that it is choking on a bad DB, depending on which version you upgraded from, which is usually resolved with a rebuild and rescan.
EDIT2: I'm also using bitcoin core 0.13.1, should I update?
Probably, yeah. I think Core will need to update the DB format so be prepared for that to take a little while.
Hello ConnyH,
Bitcoin Core will never ever follow the BCH chain (no matter which version). Replace Bitcoin Core temporarily with Bitcoin ABC and let that work as backend to Armory. Then you will be getting there.
EDIT1: And then move your BCH funds to a new wallet you create in a wallet that intends to support the future hard forks of BCH (e.g. Bitcoin ABC). Goatpig has made it clear, that he will not support Altcoins in Armory other than moving your hard-fork funds out of Armory wallets.
Depends on how they intend to split the BCH and the situation with UTXOs, but ABC isn't always required. All covered in the BCH thread, though.