View Full Version : Connecting to IB throws error
hemlock
10-19-2009, 01:22 PM
When connecting to IB, NT7 throws an error.
Might be related to a strategy that I have not yet moved over to NT7.
Also throws error when trying to delete SIM102 account, looks like this is related to a foreign key constraint.
Trace file is attached.
Thanks.
NinjaTrader_Ray
10-19-2009, 01:25 PM
When connecting to IB, NT7 throws an error.
Might be related to a strategy that I have not yet moved over to NT7.
Also throws error when trying to delete SIM102 account, looks like this is related to a foreign key constraint.
Trace file is attached.
Thanks.
Thanks for reporting...Will look into and come back if more information is required.
johannes
10-19-2009, 01:26 PM
I have also a connection problem, just to let you know.
Within NT 6.5 I had to change within the connection settings the host parameter from 127.0.0.1 to the text 'localhost', otherwise it wasn't and isn't possible for me to connect to Interactive Brokers. This problem still exists within NT 7. I don't know if this is because I'm on Vista, but otherwise it could be better to set it default to 'localhost' so less people will have this problem.
Just a consideration and tip.
hemlock
10-19-2009, 01:27 PM
Additional information:
The preceding problems occured immediately after NT7 installation and migration.
I have since reset the database and both problems have disappeared.
hemlock
10-19-2009, 01:29 PM
I have also a connection problem, just to let you know.
Within NT 6.5 I had to change within the connection settings the host parameter from 127.0.0.1 to the text 'localhost', otherwise it wasn't and isn't possible for me to connect to Interactive Brokers. This problem still exists within NT 7. I don't know if this is because I'm on Vista, but otherwise it could be better to set it default to 'localhost' so less people will have this problem.
Just a consideration and tip.
Thanks johannes.
Since reseting the database I can now connect to IB and I can connect with 127.0.0.1. I have never had a problem with 127.0.0.1.