I have a clean Windows 11 test machine, only ever used for installing NT8 8.1.x builds. It’s very clean as it has been rebuilt several times and only ever used for NT8.1 testing. It has a working verion of one of the recent prior builds of NT 8.1. I’ve never had any issues with it. Install the current release from the other day, and on startup it fails with the error Unable to Connect to DB: Unable to load DLL ‘SQLite.Interop.dll’. The specified module cannot be found.
Now, given this is a pure, clean test machine, only ever used for NT8 8.1, and the prior version (or 3) had installed and was working perfectly prior for some time, I have to assume this is the problem with the latest release?
How to fix, please?
1 Like
OK, so I now realise NT no longer participates in these ‘forums’, so, Q raised with support directly. Please ignore! If they provide a solution, I will update here in case anyone else has the problem too!
3 Likes
Hi @pjsmith yes please update if you get solution. Thanks in advance. Just updated NT to 8.1.5.2 64-bit and now getting same error.
EDIT: Am using windows 11-- not sure if fixed for long but I did a “repair” via
control panel >Programs and Features and it now NT starts up.
Also did not try this but found a post from years ago might be worth a try:
https://forum.ninjatrader.com/forum/ninjatrader-8/platform-technical-support-aa/1121327-unable-to-connect-to-db
That’s interesting. NT support told me it can’t be down to the update as no one else had reported it. I was told to remove my DB, and restart NT. I did that, but the new build just recreates the empty DB and I still get the same error. Then I was told to completely uninstall NT8, rename my Ninjatrader folder in documents, essentially, a completely clean install. This did work, but of course, you lose all your data and settings. For me on this machine it was more of an annoyance, but a very poor upgrade i think!
So, the NT support solution was delete everything and start again 
Haha. If I had a $ for every time I’ve had that response & subsequently found not to be so. Thinking behind the statement is flawed, lazy. ‘Can be but not worth our time’ would be more honest
