Does the debugger work on Windows Server 2019 VPS

Desktop SDK - Strategies
1

Hi,

The moment I try to connect my 2022 visual studio debugger to NinjaTrader, it crashes without any errors.

Does the debugger work on Windows Server 2019 OS, my installation is on an interserver VPS.

Please let me know, I dont want to spend hours trying to fix something that cannot be fixed.

Thanks in advance.

2

Perhaps another community member can speak on potential issues with the debugger when running on Windows Server 2019 and/or an interserver VPS, but I did want to mention that there is another reason why this may be happening as well:

Note that one reason that the Visual Studio debugger may crash when attaching it to NinjaTrader.exe is if you have an indicator or strategy that has been"protected" in such a way that intentionally causes the Visual Studio debugger to crash. Vendors do this as one more level of protection to protect their code from the prying eyes of their competitors and software pirates.

If this is the reason for your issue, then to fix this, you would need to remove the offending strategy or indicator that is causing the Visual Studio debugger to crash.

1 Like
3

Thanks, Actually it is Ninjatrader that is crashing immediately without any error, and all the debugger says is cannot connect to NinjaTrader.exe because it does not exist which is true because it just disappeared.
Its mostly because of x86 and x64 conflict in some dll which is causing ninjatrader to crash, i have many indicators under custom/bin.

But it will be interesting to know if someone has successfully used the debugger on Server 2019, because that will confirm the issue is with some indicator in my ninjatrader.

1 Like
4

In safe mode the debugger is able to connect to ninjatrader, so the issue is with some indicator or addon that has been added to my ninjascript.

5

If you using a 3rd party, or even your own, dll?
that was exported in any version prior 8.1.2.1..

VS will lock up if you try to attach NT process!
New Agile, NewtonSoft, C#, much changed!

Removing old exported offending dll is only fix!
Outside of Re-Exporting/Importing a new version.

.
Be Safe in this Crazy World!
:smiling_face_with_sunglasses: