Hi,
Every 2-7 days I lose the broker broker position in position tracker leading me to not knowing if MC is in sync with the brokers trades. My only solution so far has been to exit MC completely.
I'm using MC > Interactive Brokers Gateway 952 (demo trading account) > TS for data.
I installed a recommend bug fix that I think pertains to this issue to no avail. MC_IB_91x64.zip
I'll be using Rithmic soon so hopefully not an issue there?
Losing Broker Position Randomly
Losing Broker Position Randomly
- Attachments
-
- Screen Shot 2016-04-21 at 10.41.18 AM.png
- (12.48 KiB) Downloaded 1207 times
Re: Losing Broker Position Randomly
I love Rithmic. I stared with IB and would never go back. I think you'll be happy with the switch.Hi,
I'll be using Rithmic soon so hopefully not an issue there?
- Henry MultiСharts
- Posts: 9165
- Joined: 25 Aug 2011
- Has thanked: 1264 times
- Been thanked: 2957 times
Re: Losing Broker Position Randomly
Hello shane1800,
Have you tried using IB TWS instead of Gateway? Does it have the same issue?
Have you noticed if the issue happens after IB servers restart?
Have you tried using IB TWS instead of Gateway? Does it have the same issue?
Have you noticed if the issue happens after IB servers restart?
Re: Losing Broker Position Randomly
Hi Henry. I had the same issue with tws. I'm not sure how to see if the IB server restarts and is then the cause of the issue. I do know that restarting IB doesn't help and that IB doesn't show any connection issues. I will check the log for server restarts.
- Henry MultiСharts
- Posts: 9165
- Joined: 25 Aug 2011
- Has thanked: 1264 times
- Been thanked: 2957 times
Re: Losing Broker Position Randomly
Hello shane1800,
In order to study this case please enable API log in Gateway/TWS->Configure->API->Settings and check the box for "Create API message log file".
Select “Detail” Logging Level.
After this box being checked, all future API requests and responses will be logged in the API log saved in your settings directory (usually it is C:\JTS).
The files are named the following way log.Mon.txt
When the issue happens again please send us the corresponding IB logs and MultiCharts logs to support@multicharts.com so that we can check it.
Please also specify the exact time you have noticed the position info disappeared.
In order to study this case please enable API log in Gateway/TWS->Configure->API->Settings and check the box for "Create API message log file".
Select “Detail” Logging Level.
After this box being checked, all future API requests and responses will be logged in the API log saved in your settings directory (usually it is C:\JTS).
The files are named the following way log.Mon.txt
When the issue happens again please send us the corresponding IB logs and MultiCharts logs to support@multicharts.com so that we can check it.
Please also specify the exact time you have noticed the position info disappeared.
Re: Losing Broker Position Randomly
Now that I'm using Rithmic (paper trading account) I'm having the same issue.
Was working all week but then sometime Friday evening the broker connection was lost and has not came back even with the Sunday futures markets being open.
Is there a way to see log files for Rithmic?
Everything else looks like it's working and connected still.
Was working all week but then sometime Friday evening the broker connection was lost and has not came back even with the Sunday futures markets being open.
Is there a way to see log files for Rithmic?
Everything else looks like it's working and connected still.
Re: Losing Broker Position Randomly
Here's a Rithmic publication which I believe covers log files as well - http://eminifuturesbroker.com/wp-conten ... -Guide.pdf
From page 9:
If you find that the login process takes a long time or if you are having trouble connecting, click on "ECL" located at the bottom left of the login screen. A window will pop up from which you may select or identify a file into which R | TraderTM will log information about its connection process. Kindly e-mail the contents of that file to operations@rithmic.com so that Rithmic may use it to help determine the source of the connection problem.
From page 9:
If you find that the login process takes a long time or if you are having trouble connecting, click on "ECL" located at the bottom left of the login screen. A window will pop up from which you may select or identify a file into which R | TraderTM will log information about its connection process. Kindly e-mail the contents of that file to operations@rithmic.com so that Rithmic may use it to help determine the source of the connection problem.
Re: Losing Broker Position Randomly
Thanks for that, I haven't installed R Trader so will try this if the problem happens again. My broker may have reset my Rithmic paper trading account causing the broker position of 0 being displayed.
Re: Losing Broker Position Randomly
Did you complete non-professional agreements? When you log into R-Trader you will have to complete two forms, and I believe then your account will be active. Until then it may not. That may be the reason right there. Once you figure it out, trust me, you'll love Rithmic.
- Henry MultiСharts
- Posts: 9165
- Joined: 25 Aug 2011
- Has thanked: 1264 times
- Been thanked: 2957 times
Re: Losing Broker Position Randomly
Hello shane1800,
Please close all MultiCharts64 processes and import the attached reg file (double click on it->Yes) to enable Rithmic API logs.
Now once you start MultiCharts and connect to Rithmic - Rapi.log file will be created in the MultiCharts logs folder (%userprofile%\AppData\Local\TS Support\MultiCharts64).
You can send this file to your broker for the issue analysis.
Please close all MultiCharts64 processes and import the attached reg file (double click on it->Yes) to enable Rithmic API logs.
Now once you start MultiCharts and connect to Rithmic - Rapi.log file will be created in the MultiCharts logs folder (%userprofile%\AppData\Local\TS Support\MultiCharts64).
You can send this file to your broker for the issue analysis.
- Attachments
-
- RAPI_log_MC64.zip
- RAPI log for MultiCharts64
- (238 Bytes) Downloaded 150 times