-snip- Same case like
This and has resolved when he changes form databases to
dbLog.txt dbLog.txt contains logs, there nothing to change there.
Upon examining the thread: martyman just posted what was in the command line after running armorydb manually.
I've also noticed that the linked thread was quite chaotic because there were other two posters who claimed to have the "
same issue" but didn't seem like it. And they replied after one another.
The "
glitch" may have been a "
zombie armorydb" process that wasn't terminated after the last Armory session.
In that case, a PC restart, end task or the manual armorydb launch attempt(s) might have fixed the issue.