I was sitting here watching the IB shenanigans at around 12 midnight EST , it is clear that IB does a number of connections and disconnections at this time rebooting their systems or whatever, NT7.0 crashed 5 times in a row , oh what fun forcing a close and restarting and reloeading charts and losing my range bar flows messing up indicators . This never happened with NT6.5 . If the volumeStop indicator by Cory () for NT6.5 works the same as in NT7.0 then I guess I'm going to bite the bullet , say good riddance to NT7.0 and take the retrograde step. So frustrating, thanks for listening.

NT 6.5 is not the solution, you can't even trade live with it on CME anymore.

Mike

MrBean 

I was sitting here watching the IB shenanigans at around 12 midnight EST , it is clear that IB does a number of connections and disconnections at this time rebooting their systems or whatever, NT7.0 crashed 5 times in a row , oh what fun forcing a close and restarting and reloeading charts and losing my range bar flows messing up indicators . This never happened with NT6.5 . If the volumeStop indicator by Cory () for NT6.5 works the same as in NT7.0 then I guess I'm going to bite the bullet , say good riddance to NT7.0 and take the retrograde step. So frustrating, thanks for listening.

Are you using IB data feed to display range bars or any other bars built from tick charts? This is like trying to climb the Mount Everest wearing a pyjama and sandals. It is not possible to have decent tick charts, without a professional data feed and historical tick data. This is not what you get from Interactive Brokers.

I do use the NinjaTrader 7.0 and Interactive Brokers, and as you discovered, there are frequent disconnections after the close. However, NinjaTrader 7.0 has not crashed even a single time on those disconnections.

So whatever causes the crashs is specific to your setup! You may have some corrupted indicatiors, which cause the crash. I can easily code a few for your if you like, so I know that it is possible.


Have you tried out my suggestions as per post above?.


A single corrupted indicator is capable of causing your problem. You need to get rid of all custom indicator and check whether it happens when just using system indicators. NinjaTrader 7.0 does not usually crash on disconnects from Interactive Brokers.

Also, as @ Big Mike explained, NinjTrader 6.5 is no solution, you can scrap it.

MrBean 

I was sitting here watching the IB shenanigans at around 12 midnight EST , it is clear that IB does a number of connections and disconnections at this time rebooting their systems or whatever, NT7.0 crashed 5 times in a row , oh what fun forcing a close and restarting and reloeading charts and losing my range bar flows messing up indicators . This never happened with NT6.5 . If the volumeStop indicator by Cory () for NT6.5 works the same as in NT7.0 then I guess I'm going to bite the bullet , say good riddance to NT7.0 and take the retrograde step. So frustrating, thanks for listening.

In NT7 that is not in NT6.5, NinjaTrader closes the bars on all standard chart types @ midnight to sync all their charts.

This could be the cause of some of your issues.

Personally I do not see the advantage when it comes to range bars. As a coder myself of 4 price based chart types, I have excluded this midnight event from my own personal chart types.

Thanks everyone for your help . To be honest I have not yet removed all of my custom indicators because I have paid for some and need them all to trade, but I guess I have no choice. I will remove them all and add them one by one to find the culprit , and go from there. It seems that 6.5 isn't the way forward

Has Cory's volume stop indicator caused anyone else a problem? That was the last indicator I added before the trouble started. Before that I added TCTrending but that is made by professional$ so seems unlikely to be a cause of trouble.

Any suggestions for professional data providers? I mostly trade SPY QQQ and NQ, and KOSPI options (IB is OK for that).

The story continues... I removed all custom indicators and it ran well for a few hours and it seemed to be running a bit smother and faster (when you change settings and move things around etc).

But just now IB disconnected & reconnected the HKfarm , then they also did the same for the euro farm, the HKfarm disconnection tripped up my poor NT7.0 and crashed it.

So it would seem then that bad code is not the issue here. Now I'm screwed, danggit.

What should I try next? How about completely removing NT and re-installing it? Any ideas? Thanks heaps.

Just a random idea, is it possible that having a disconnection sound alert could be throwing a spanner in the works? I shall remove all alerts and see how it goes.

MrBean 

The story continues... I removed all custom indicators and it ran well for a few hours and it seemed to be running a bit smother and faster (when you change settings and move things around etc). But just now IB disconnected & reconnected the HKfarm , then they also did the same for the euro farm, the HKfarm disconnection tripped up my poor NT7.0 and crashed it. So it would seem then that bad code is not the issue here. Now I'm screwed, danggit. What should I try next? How about completely removing NT and re-installing it? Any ideas? Thanks heaps. Just a random idea, is it possible that having a disconnection sound alert could be throwing a spanner in the works? I shall remove all alerts and see how it goes.

I have not read the entire thread but if you have not done so already, I suggest contact our support team for futher investigation.

Progress report:
I uninstalled everything including NT7.0 and all it's custom indicators. I had to use a special uninstall tool because NT was detected and it would not let me. I also did full virus scan and PC maintenance. I had already installed NET4.0 but it is not compatible with NT so I thoroughly (using the uninstall special tool) uninstalled all the NET stuff and then loaded it up with NET3.5 instead. After that I downloaded a new copy of NT7.0 from the NT site (not a custom build). And FINALLY I have a working NT7.0 after all this time (I have been trying NT7.0 since beta). I have been watching as IB does it's regular disconnections and re-connections and so far NT7.0 has not been fazed by it. So far so good , fingers crossed.

I sent this progress report to NT but they didn't bother to reply. I wonder if they fixed the bug without admitting it existed , and without changing the build number, just conjecture of course. Anyway, I am happy the issue is finally solved.

It is sometimes difficult to find out what exactly causes the behaviour. I run NinjaTrader on Interactive Brokers data feed, and I have never experienced the issue that the disruptions of the data feed after the market close had caused a crash. If this happens, it is probably linked to some specific settings or an antivirus-tool, and it is not so easy to find out the reasons.

NinjaTrader developers certainly do not fix bugs without admitting that they existed. But sometimes it is near impossible to replicate a behavior of a specific machine. If your NT7 works now, something - whatever it was .NET, NinjaTrader - has been installed in a slightly different manner compared to the prior state of your machine. That difference may have fixed the problem.

I had already tried the same procedure a few times before hoping to resolve the issue, but it never worked so I always fell back to 6.5 . This time it did work and so I assumed that it was an issue with NT not with anything on my end. They also offered me a custom build, but ironically I didn't need it as I finally got the regular build to work properly at precisely the same time as when they offered the custom build. See what I mean? I'm sure it was just one of those funny coincidences/synchronicities. Thanks everyone who help me out on this thread!