Disconnect Enforced: by second log in to the same account

[philip999]

I'm trying to log in to my demo account but get the following message

"Disconnect Enforced: by second log in to the same account".

Is this normal?

Can I get my demo account back please?

[NinjaTrader_Bertrand]

Welcome to our forums - have you been using the account only on one PC? Could you please email us your log and trace files via Help > Mail to Support from inside the application so we could review which user name you used here in the setup?

Thanks,

[philip999]

Hi,

Yes just using Ninja on one pc.

My user name is demo11880

[NinjaTrader_Bertrand]

Thanks, from which broker is the demo login you use?

[philip999]

Ninja Trader Continuum

[NinjaTrader_Bertrand]

Thanks we will check into it.

[philip999]

Any idea what's happening with my demo account?

[NinjaTrader_Bertrand]

Unfortunately would not have an update yet, I will follow up here when I have more.

[SteveGlover51]

Error message.

Good morning, I had NT up over Saturday night and had the same error message on Sunday morning on my Live account (first time seeing this error in 3 years of use). Rebooted and all seems fine (NT has been up since 5:30 yesterday). Doesn't answer why this happened but wanted to let you know I saw it too. Since it happened to at least 2 users it was probably a system issue and not a computer issue.

[NinjaTrader_Bertrand]

Thanks Steve, could you please contact us via Help > Mail to Support as well to review the trace and logs for this scenario?

[NinjaTrader_Bertrand]

We cannot directly see any backend system issues related after review - so far I've not seen logs to review however for this scenario you likely saw a temporary connection loss with a quick reconnect attempt then by NT, before the original session was considered fully closed.

[ScorpioTravis]

Over the weekend I had similar issues with my CQG connection while not experiencing any with IQFeed, including the error message "Disconnect Enforced: by second log in to the same account" (11/23/2014 5:01:39 AM).

I agree with SteveGlover51 - it was probably a system issue and not a computer issue.