Crash on DOM instrument change

[Tremblinghandtrader]

Hi

Every time I change the instrument within the DOM NT crashes. It also crashes if I have one DOM open then I try to open another. It happens every time.

When I close and reopen 1/2 of my charts have gone nuts with incorrect data as per the pic.

Another issue is the log has hundreds and hundreds of error lines saying,

IB.IntradayRequest.Process: invalid datetime format '20100604 16:10:00': instrument='HHI.HK 06-10' from='2010-06-09' to='2010-06-09' period=Daily splitAdjusted=False dividendAdjusted=False bars=0: String was not recognized as a valid DateTime.

As per second pic. Also happens with the HSI futs

[NinjaTrader_Dierk]

A member of our staff will follow up the crash you experienced.

On the log entries you got: unfortunately IB's data is corrupted for the instruments in questions. You had chart (or an indicator) which works on a data series based on daily bars. However, TWS returns the data in incorrect format with having an intraday timestamp. I suggest contacting IB in order to get this corrected for your account.

[NinjaTrader_Brett]

Hello,

Thank you for your forum post.

Can you please send a note to support at ninjatrader dot com and but ATTN: Brett in the subject line then reference this forum post and send the following 2 files so that I may diagnose your crash.


You can find these files at the following locations, please attach these to a return email.

Start Menu--> My Documents--> NinjaTrader 7--> Trace--> trace.20100610 for today. (trace.yyyymmdd for any other date)

Start Menu--> My Documents--> NinjaTrader 7--> Log--> log.20100610 for today. (log.yyyymmdd for any other date)

Thank You and I look forward to assisting you further.

[NinjaTrader_Brett]

Hello,

Also, NinjaTrader 7 Beta 17 was released today. The first step I would have you do also is to reproduce on Beta 17. So if you would like to go ahead and upgrade to beta 17 before sending me the trace that and see if you can reproduce the crash would also be a good way to go here.

http://www.ninjatrader.com/webnew/download_trading_software.htm

I look forward to assisting you further.

[Tremblinghandtrader]

The upgrade to Beta 17 has fixed it but somewhere in the change over I seem to have lost some open positions in the sim account for a system that I was testing. Is there anyway to re-enter these trades??

[NinjaTrader_Bertrand]

Thanks for reporting back - you could just reopen those position in your Sim account to sync this up to a historical strategy position you're having.

[Tremblinghandtrader]

Thanks for reporting back - you could just reopen those position in your Sim account to sync this up to a historical strategy position you're having.

Except they will not be the same price nor hold period which is the reason why I'm testing the system

Are you telling me there is no way to replace those positions and is this an expected outcome of the upgrade that will repeat in the future?

[NinjaTrader_Bertrand]

Unfortunately you can't adjust the price later of the position added to your sim account. Do you have a database file you use for a restore? The outcome is not expected and positions stored in the database should me maintained (except you reset the simulator in between). However, so far I've not come across a reproducible scenario for this - please send me in your DB file as well as trace / logs so we could investigate what may have caused this on your end.

Thanks for your support.

[Tremblinghandtrader]

OK problems back with something else terminal going on. NinjaTrader.exe is taking up 700,000 k of memory before the splash screen even appears on the the screen. Takes for ever to load and even with a blank workspace and no data connections it takes 900,000 k or more of memory. Completely locking up my computer. Opening any DOM cause an instant crash and strangely from the log file it say I have exceeded number of DOMs yet I only have 1 open?? Have uninstalled and tried again but same problem.

Trace & log files are huge for the two hours I wasted trying to get it to work. Have had to go back to nt 6.

Have sent the trace & log files to you via email.

thanks

[NinjaTrader_Jason]

Hello Jason,

Please see my response to the email you sent us.

Can you please tell me if you have your IB connection set to connect automatically on startup? If so, please go to (My) Documents-->NinjaTrader 7 and delete the Config.xml. Subsequently start NinjaTrader and check if the issue persists.

How many workspaces are opened on startup? Please try the following. Go to (My) Documents-->NinjaTrader 7-->workspaces and transfer the content to a temporary different location. Start NinjaTrader and check if it will make a difference.

If so, close NinjaTrader and transfer back the workspaces. Start NinjaTrader and check again.

I suggest to only load an empty Default workspace on startup. You can accomplish this by having only the Default workpsace opened when exiting NinjaTrader. The next time you start NinjaTrader, only the Default workspace will be loaded.

Before you exit NinjaTrader, please close all workspaces except the Default workspace. Go to File-->Workspaces and check what workspaces are listed below 'Save Workspace As'. The workspace with the checkmark is the workspace opened on your monitor. Any additional workspaces listed, are opened in the background. Select a workspace without a checkmark and subsequently go to File-->Workspaces-->Close Workspace. Repeat this process until only one workspace is opened.

[Tremblinghandtrader]

Hi

No luck there. There was only ever 1 workspace loading but in any case I created a new blank workspace and closed all other and removed the files from Documents-->NinjaTrader 7-->workspaces

restarted and the same thing. I don't think its a workspace issue or an auto connect, which has never been enabled, as before I even see the splash screen NT is taking up 750 meg of memory!! see pic

[NinjaTrader_Bertrand]

Tremblinghandtrader, curious - how big would the current day's trace and log files be in your case?

[Tremblinghandtrader]

Huge!!

See pic.

[NinjaTrader_Bertrand]

Thanks, please deleting those (just move them out of those folder to a temp folder) and then restart fresh and recheck.

[Tremblinghandtrader]

Yep that fixed it. The DOM is working fine so far. Will see how it goes.

I wonder what was the cause?

Thanks for your help.