After the NT upgrade I first started experience an intermittent issue where when I disconnect (Continuum) or exit NT8, I would not be able to reconnect until the next day. This does not a hard fault as on occasion it does allow me to reconnect! It would just hang/pause and never give me a green light, nor show my SIM or broking ac balances.
As I live in Australia, I often trade during DE/UK market opening then switch off until the US opens. But unable to reconnect at this time ...
If I try and put a timeline to this, I first experienced this issue after an NT8 upgrade where the back-end database was replaced (I was very out of date due to inactivity prior).
I have spend much time with support trying to get this resolved - including numerous supplies of the log and trace files, reinstalling NT8 completely and uninstalling AV (TrendMicro) and backup (Acronis) altogether.
In the end I was advised by NT8 Support that this issue was definitely not NT8 issue and had to be a platform issue and to engage the services of a PC technician. Lol - I have work in IT for 25 years and am very IT literate. In desperation if completely rebuilt Windows 10 from the ground up as well as all the platform software (Trend/Acronis/Office) and the platform is again fully patched.
I installed NT8 and then restored NT8 settings from backup as I did not want to loose my setups. They have taken years to develop.
The problem did not manifest for some 2 weeks but then returned and now seems to be pretty solid again.
It *possibly* relates to when I switched trading between sim and live and possibly relates to historical trading records?
Has anyone seen or experienced anything like this before? Any suggestions? I have run out of ideas and this is causing me a lot of frustration and it is not good for my head space.
TIA, Lex
Can you help answer these questions from other members on futures io?
I feel your pain Lex. One more reason to NOT update NT8 far as I'm concerned.
I haven't heard a single benefit to doing it. Seems they launched it too soon but
maybe im wrong.
It doesn't sound good that NT is saying it's your fault or your rig coincidentally
right after updating. Wish I could share some good news but I can't.
Please post when you find a solution. Guessing plenty of us will need that info.
Hope you're up and running soon. JM
The following user says Thank You to johnnymustard for this post:
I just logged in and it looks like NT is forcing our hand via a mandatory upgrade ... both the act of upgrading and fact that everyone is being forced is quite concerning. They are starting to behave like M$FT!!!
I am with you on that - same for any software releases. On this occasion I had contacted support with a strategy development issue and was basically advised that there would be no coding support if I was not on the latest. I can emphasize with that as I was well and truly out of date.
The log files basically stop logging without any clue (identical to it works except for it continues to log!). Certainly no clues.
The issue did not present itself on a separate laptop. But this one just had a new installation of NT8 and did not go through the upgrade process (separate NT8 license).
My thinking is it NT specific on my desktop as a result of the upgrade. The restore of NT8 from backup on a fresh windows install may have carried the issue forward?
Thanks for responding!
Lex
The following user says Thank You to grzltn for this post:
