MB Trading Connection Error

[upshon]

Hi

I Keep getting the following error in the Log when trying to connect to My Live MBTrading account. Once the error occurs I get no further.

[IMG]file:///Users/Mike/Library/Caches/TemporaryItems/moz-screenshot.png[/IMG][IMG]file:///Users/Mike/Library/Caches/TemporaryItems/moz-screenshot-1.png[/IMG][IMG]file:///Users/Mike/Library/Caches/TemporaryItems/moz-screenshot-2.png[/IMG][IMG]file:///Users/Mike/Library/Caches/TemporaryItems/moz-screenshot-3.png[/IMG]Mbt.Callback.OnAccountLoadedNow: exception caught: A duplicate value cannot be inserted into a unique index. [ Table name = nt_instrument,Constraint name = nt_instrument_ui ]

I have tried the following.

1. Repair DB
2. Reset DB

I have the correct version of the MB Client installed as I can connect to other MB Trading Accounts.

I am running on a new install of Windows 7 & latest version of NinjaTrader 7.

Please Help.

Thanks

Mike

[NinjaTrader_Kyle]

Hi Mike,

Thanks for your note.

Unfortunately, none of the images came through. In the future, these need to be uploaded to the forum unless hosted elsewhere.

In any case, if you'll just provide the text of the error that should suffice.

[upshon]

Thats strange, I didnt add any images.

The error message is

Mbt.Callback.OnAccountLoadedNow: exception caught: A duplicate value cannot be inserted into a unique index. [ Table name = nt_instrument,Constraint name = nt_instrument_ui ]

Cheers

Mike

[NinjaTrader_Kyle]

Hi Mike,

Please send a note to Support [AT] NinjaTrader [DOT] com with 'ATTN: Kyle' in the subject line.

In the message, include the following:

1.) A link to this thread.

2.) Your most current trace file.
You will find the trace file in the Documents > NinjaTrader 7 > Trace folder.

• The trace file will be named ‘trace.YYYYMMDD.txt’

[DTRADE88]

I'm experiencing a similar problem. How was this resolved?

[NinjaTrader_Kyle]

Hi DTRADE88,

Unfortuantely, I'm not able to find the email which was associated with this thread and don't recall the resolution. In any case, if you'll follow up with me as per post #4 with a link to this thread and today's trace file we should be able to get things back up and running quickly.