anyone ever have NT just refuse to update price on the chart and show n/a in the bid/ask/last etc on the orders tab of control center.

connected?yes errors in log? no

gp

What instrument are you looking at? Expiry if a futures contract? Who are you connected to for data? If multiple-connections, what order?

gparkis 

anyone ever have NT just refuse to update price on the chart and show n/a in the bid/ask/last etc on the orders tab of control center. connected?yes errors in log? no gp

There is always an explanation/resolution and we are happy to provide it. I suggest sending in this inquiry to our support team and they can promptly handle your inquiry.

NinjaTrader stock, futures and forex charting software and online trading platform. Support.

Yes, once in while I've had the same issue pop up, but no one reason. Contract expiration has happened. I wasn't aware of some holidays when markets were closed. Sometimes the CQG and/or the the Zenfire servers have had a problem sending data (especially on weekends). They connected but didn't send any data. Instrument settings for the contract (RTH/ETH/24/7, etc) have caused the problem. In addition to playing with the Instrument Manager, sometimes a restart of NT has worked, but other times I've had to uninstall/re-install NT. Sometimes waiting 24-48 hours and restarting Ninjatrader has been the solution. Sometimes errors in the log, sometimes not.

I've been using NT for three years and am on it almost daily. In that time, I've had this issue occur maybe a dozen times, mostly when I was first learning to use NT. Fortunately, it hasn't happened to me after placing a real trade as it seems to have for some on this forum. Hope this gives you some additional insight.

problem solved.

turns out that the updated iq feed does not work with the updated nt7. i had to bring back the old iq feed.

this was discovered with NT support.

g

gparkis 

problem solved. turns out that the updated iq feed does not work with the updated nt7. i had to bring back the old iq feed. this was discovered with NT support. g

Excellent, glad we were able resolve your issue.