Crashing with an awful tracefile

[Harry]

Nt 7.0.0.18 was well behaved so far (exception loading IB data on Saturdays)

With NT 7.0.0.19. I am getting awful crashes, with ever expanding RAM usage. Do not know what is happening here. Also it seems that the vendor license seems to reference NT 7.0.0.18. There are paint overflow errors. System indicators and other indicators that have worked fine with all prior version do no longer work. Really teriible.
See sreenshot and tracefile.

I did not even connect today, just using NT without data loading.

Crash happened after I used the editor to edit an indicator. It seems that the editor could not for some reason reference the new version, but tried to reference version 7.0.0.18. The overflow error already occured prior to this, so is not related. RAM usage by NInjatrader was exceeding 1.5 Gbyte, usually my workspace only takes 10% to 20% of that.

[Harry]

Have done some trials. The main problem occurs, if I open any indicator with the editor and then save it (no need to do any changes). This is the message shown in the trace file (after opening and saving an indicator with the editor)

2010-07-26 00:57:35:625 Code.Editor.OnLoad: Failed to reference 'NinjaTrader.Custom, Version=7.0.0.18, Culture=neutral, PublicKeyToken=null': System.IO.FileNotFoundException: Das angegebene Modul wurde nicht gefunden. (Ausnahme von HRESULT: 0x8007007E)
   bei System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
   bei System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
   bei System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   bei System.Reflection.Assembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, StackCrawlMark& stackMark)
   bei System.Reflection.Assembly.LoadFrom(String assemblyFile)
   bei NinjaTrader.Code.Editor.OnLoad(Object sender, EventArgs e) 

[Harry]

Now made a completely new reinstall: No vendor assemblies installed. Now I am getting a new error message after I have opened one of my indicators and compiled it via F5:

Now it is failing to reference NT 7.0.0.19 instead of NT 7.0.0.18. How can this be explained. Only getting this message, when opening the editor and compiling one of my indicators.

2010-07-26 02:28:28:843 Code.Editor.OnLoad: Failed to reference 'NinjaTrader.Custom, Version=7.0.0.19, Culture=neutral, PublicKeyToken=null': System.IO.FileNotFoundException: Das angegebene Modul wurde nicht gefunden. (Ausnahme von HRESULT: 0x8007007E)
   bei System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
   bei System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
   bei System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   bei System.Reflection.Assembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, StackCrawlMark& stackMark)
   bei System.Reflection.Assembly.LoadFrom(String assemblyFile)
   bei NinjaTrader.Code.Editor.OnLoad(Object sender, EventArgs e) 

[Harry]

Crash is not reproducible

After fresh reinstall NT 7.0.0.19 is stable again. Same workspaces and indicators.

However, the error message in the tracefile (reference error) occurs on both fresh reinstalls, whenever I have opened a file with the NinjaTrader editor and compiled it.

Not sure that this has anything to do with yesterday's crash. It is just the few lines shown below.

[NinjaTrader_JoshP]

Harry,

The Code.Editor.OnLoad message will show up and is inconsequential. You can ignore them. They have been present for many beta versions.

The issues you reported look dependent on the indicators you were using. Were you running them on a very extensive chart?

[Harry]

My standard workspace, not related to indicators. If you have a close look, the first indicator creating problems was TEMA, a system indicator. The whole problem was related to upgrading from NT 7.0.0.18 to NT 7.0.0.19. Now made a fresh reinstall and copied indicators, workspaces, templates, database, etc. into the new folder NT7. Works without problems today.

If I need to reinstall NinjaTrader from scratch, is there any way to keep

(1) instrument settings (default list, session templates for instrument settings, rollover dates, offsets)
(2) session templates
(3) account connections

In particular (1) takes a lot of time as I have to put in rollover dates manually for a number of instruments (CL and BC already have 48 rollover dates and offsets).

So would be nice if this could be simplified, as I have to do this after each crash.

Harry,

The Code.Editor.OnLoad message will show up and is inconsequential. You can ignore them. They have been present for many beta versions.

The issues you reported look dependent on the indicators you were using. Were you running them on a very extensive chart?

[Alfred]

If I need to reinstall NinjaTrader from scratch, is there any way to keep

(1) instrument settings (default list, session templates for instrument settings, rollover dates, offsets)
(2) session templates
(3) account connections

In particular (1) takes a lot of time as I have to put in rollover dates manually for a number of instruments (CL and BC already have 48 rollover dates and offsets).

So would be nice if this could be simplified, as I have to do this after each crash.

Harry...

To do an easy clean install of a new beta...I previously make a backup of just the control center...this will save ones instrument settings, session templates,
& account connection plus custom hotkeys and control center settings etc....also sometimes will also do another similar backup that includes the DOM and Basic entry widows for their monitor locations in a similar backup. This method has seemed to work well for me so far....so everything does not have to be done over again at a clean install...

Also have found that one can do an XP system restore to take you back to when a previous beta version was running if desired....this recently worked OK for me...

Thanks...

[Harry]

Alfred,

thanks for your answer. A system restore has some unwanted side effects, as I am running other programs on my PC. This would be like hunting ducks with canon balls.
The control center setup will not help, if NT is corrupted as it does not replace the offending files Config.xml, NinjaTrader.Custom.* and NinjaTrader.Vendor.* .

I am afraid no way to improve this, I have done more NinjaTrader installs than cumulated installs of all other programs.

Harry...

To do an easy clean install of a new beta...I previously make a backup of just the control center...this will save ones instrument settings, session templates,
& account connection plus custom hotkeys and control center settings etc....also sometimes will also do another similar backup that includes the DOM and Basic entry widows for their monitor locations in a similar backup. This method has seemed to work well for me so far....so everything does not have to be done over again at a clean install...

Also have found that one can do an XP system restore to take you back to when a previous beta version was running if desired....this recently worked OK for me...

Thanks...

[Alfred]

Harry...the way this works for me is I will do a complete uninsall of NT...next I do a clean install of the new Beta version...then I run a restore of the Control Center only backup (the backup is from a clean uncorrupted version of the Control Center with all of my custom settings and templates etc.)...would that work for you ??

Thanks...Alfred

[Harry]

I am afraid that the restore of the control center will not help, if the installation is corrupted. This will effectively restore the corrupted files.

Harry...the way this works for me is I will do a complete uninsall of NT...next I do a clean install of the new Beta version...then I run a restore of the Control Center only backup (with all custom settings and templates etc.)...would that work for you ??

Thanks...Alfred

[NinjaTrader_JoshP]

Harry,

You can selectively restore what you want from the Restore utility. As far as backing up instrument settings and session templates, those are stored in the database. For the account connections, those are stored in the Config.xml. If you really wanted to you could open up the .xml and copy paste the relevant lines for the connection only to your new Config.xml if you didn't want to restore the whole .xml file.

[Harry]

NinjaTrader.sdf is probably not reusable after a crash, but I could try, of course. Does it make sense to copy this file from the old folder to the new one?

[QUOTE=NinjaTrader_Josh;181505]Harry,
As far as backing up instrument settings and session templates, those are stored in the database. [QUOTE]

[aviat72]

Harry,

You can selectively restore what you want from the Restore utility.

Could you elaborate more on the above? Does this mean that a full backup will not be restored and you can pick and chose what you want to restore?

[NinjaTrader_Jason]

Hello Harry,

Yes, you can copy/paste the .sdf file to the new (My) Documents-->NinjaTrader 7-->db folder. The .sdf file named NinjaTrader in the db folder will be used as database.

Hello aviat72,

You can select which backup file you like to restore. You can create backup files for separate items and subsequently restore them in order to restore only certain files/settings.

If you create a backup file for all items and you restore this backup file, all items will be restored.