Complied indicator locking up NT

[RonKiker]

I made some changes to a working indicator, then compiled the indicator. The indi compiled without any problems. But, when I updated the indi on my chart it locked up NT and NT shutdown. When I try to restart NT it locks up and shuts down because it is trying to open the same workspace which includes the offending indicator.

When this happened previously I uninstalled and reinstalled NT. The reinstall only includes NT stock indicators so the offending indi was not installed. But that takes a lot of time, plus I have to reinstall all of my 3rd party and personally created indicators.

Does anyone have any suggestions on how I can get to the ofending indi without having to do a complete uninstall/reinstall?

Thanks,
Ron

[NinjaTrader_PatrickH]

Hello RonKiker,

Thank you for your post.

Please send me your log and trace files for today so that I may look into what occurred.

You can do this by going to the Control Center-> Help-> Mail to Support.

Please place 'ATTN: Patrick - 904744' in the subject line and reference this threadd in the body of the email: http://www.ninjatrader.com/support/f...ad.php?t=60469

I look forward to assisting you further.

[RonKiker]

Patrick,

How can I get to the control center if NT keeps locking up and shutting down because it is trying to open the offending workspace and indicator?

Anyway, I have already been given a solution over on Big Mike's forum.

The solution I used was to go to \Documents\NinjaTrader 7\workspaces and delete the offending workspace. NT then opened (and stayed open) without any problems. I was then able to open the offending indicator, undo the change I had made in the indi, and then rebuild the workspace.

Thanks for your offer to assist.
Ron

[RonKiker]

Patrick,

Have you ever heard of this happening before where an indi that compiles without any problems locks NT up when added to a chart?

This is the 3rd time I've had it happen. Did a complete uninstall and reinstall the first two times. This "delete the workspace" solution is a LOT easier and faster.

Ron

[NinjaTrader_ChelseaB]

Hi RonKiker,

It sounds like a run-time error. (Such as attempting to access something that doesn't exist)

Do you have any errors in the Log tab of the Control Center?