NT7 beta 3 and static super dom problem

[NinjaTrader_Kyle]

Hi williammanda,

Thanks for following up.

1.) This issue, it seems, relates to an unsuccessful upgrade to the Zen-Fire API with the installation of 7.0.1000.3. By simply recreating the connection, this issue can be resolved. This being the case, you should see no further issues by upgrading to 7.0.1000.3 once again.

2.) It is possible to use Zen-Fire in 64 bit mode as well, but an option needs to be enabled in the Connection Wizard. For more information, please see the following link: http://www.ninjatrader.com/Connectio...tion-Guide.php

[williammanda]

Hi williammanda,

Thanks for following up.

1.) This issue, it seems, relates to an unsuccessful upgrade to the Zen-Fire API with the installation of 7.0.1000.3. By simply recreating the connection, this issue can be resolved. This being the case, you should see no further issues by upgrading to 7.0.1000.3 once again.

So I need to delete the current zenfire connection and then create it? Was this issue created by the backup I installed?

[NinjaTrader_Kyle]

Hi williammanda,

Correct, the connection needs to be recreated.

This is due to a server-side issue which is to be corrected this weekend, but this procedure will get you up and running in the meantime.

[williammanda]

So will I be able to load 7.0.1000.3 after this weekend and it work correctly (superdom)?

[NinjaTrader_Kyle]

Hi williammanda,

That is correct, however, you can also install .3 right now, then recreate your Zen-Fire connection and you would also have a functional installation of NT.

[williammanda]

I uninstalled 7.0.1000.2 and installed 7.0.1000.3. Deleted the Zenfire connection. Restarted NT7 and created the new Zenfire connection. The static superdom is functioning correctly.

[aligator]

I rolled back to 7.0.1000.2 and there are no problems now with the static superdom. I noticed that I can only run 32 bit version with zenfire...is this correct?

I too had the same problem using PFG feed. I did a complete uninstall and house cleaning and re-installed rev 2. No more problems.

[NinjaTrader_Kyle]

Hi williammanda,

Thanks for reporting back - I'm glad to hear that did the trick.

We'd expect no such issues in the future.

Hi aligator,

I'm not sure if that issue was reported elsewhere, but if you're interested in tracking that issue down with us, please let me know.