Armory 0.96 Error during start up

[Hein2017]

Bitcoin Client Software and Version Number: Bitcoin Core 0.14.2, Armory 0.96

Operating System: Windows 8 64-bit

System Hardware Specs: Intel Premium CPU G645 @ 2.9GHz

Description of Problem:
I moved the node to D:\bitcoin and when adding -datadir="d:\bitcoin" to the short cut on my desktop I get the following error:
The logfile 'c:\[..]\Armory\ArmoryQt.exe.log' could not be opened:
[Errno 13] Permission denied: '[same file]'
When starting Armory without the -datadir addition it starts building the node again on the c drive (no space). Seems a simple issue to resolve, have tried a lot, now need some help.
Thanks!

(Edit on my earlier post: it does not actually start to build the node again on the c-drive, that was with a previous version of Armory which had core running in the background. It just does not find any blocks.)

[achow101]

Make sure that your user has permissions to read and write data to D:\bitcoin. Ideally you should have the "full control" permission.

[Hein2017]

Yes, permissions OK. The odd thing is that Armory has in the past run absolutely fine (with the node on the d drive), but then during upgrade and trying to get it to work again after a time of no activity I ran into a bunch of problems (including crashing at the end of having synchronised, etc), and now I seem to be stuck with this.

[Hein2017]

Just taking a step back - when I start ArmoryDB, this is what pops up:

logging in C:\Users\Maria\AppData\Roaming/Armory/dbLog.txt
-INFO  - 1498989947: (..\main.cpp:23) Running on 2 threads
-INFO  - 1498989947: (..\main.cpp:24) Ram usage level: 4
-INFO  - 1498989947: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\Maria\AppData
\Roaming/Bitcoin/blocks
-INFO  - 1498989947: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\Maria\AppData\Ro
aming/Armory/databases
-INFO  - 1498989947: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1498989948: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO  - 1498989950: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO  - 1498989950: (..\DatabaseBuilder.cpp:169) Reading headers from db
-WARN  - 1498989950: (..\lmdb_wrapper.cpp:1175) No headers in DB yet!
-INFO  - 1498989950: (..\DatabaseBuilder.cpp:208) Found 1 headers in db
-INFO  - 1498989950: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-DEBUG - 1498989950: (..\Blockchain.cpp:242) Organizing chain
-INFO  - 1498989950: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.014s
-INFO  - 1498989950: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-WARN  - 1498989953: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threa
ds
-WARN  - 1498989958: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threa
ds
-WARN  - 1498989958: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threa
ds
-WARN  - 1498989958: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threa
ds
-WARN  - 1498989958: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threa
ds

So the 4th line refers to the default c drive location, whereas it should go to the d drive. As mentioned before, this was working OK earlier but now I don't know what I changed (apart from re-installing bitcoin core and Armory a couple of times).

Somewhere I read about the bitcoin.conf file. Something to add there? I already tried adding -datadir="d:\bitcoin" but no luck.

[Hein2017]

I resolved the issue, by adding:
"C:\Program Files (x86)\Armory\ArmoryDB.exe" --satoshi-datadir="D:\Bitcoin\blocks" to the ArmoryDB shortcut, running ArmoryDB first followed by ArmoryQt without any extension.
I am not sure if I saw this recommendation anywhere but happy it's solved.

What I don't get though is why, having used Armory for 5 years now, every time I turn my back on this for more than a couple of months, it's a good 24 to 48 hours work to figure out what has changed and how to get it up and running again. I do think it is good that Armory is decoupled from bitcoin qt (or at least I think that is the case?) making it a bit less 'heavy' to run and use, but I do wonder how bitcoin will ever make the jump to the wider population as long as the user needs to understand a thing or two about databases, etc. And with the blockchain getting so big you cannot experiment much...!