Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- discounts are available after registering.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Hi, I'm using my own indicator for trading and recently I got an error (see screenshot) after my order being placed and fullfilled.After the error my indicator automatically turning off. The error message is Error:elsystem.UserException: Trade Manager GetTMSessionInterface.CreateInstance function failed
Found nothing in the documentation or on google. Maybe somebody knows what the problem might be. Thank you!
Can you help answer these questions from other members on NexusFi?
according to the official TS forum other users are experiencing a similar error message from time to time. You might be able to find some temporary solutions in the forum, and according to the thread below the issue should be fixed (check John's statement from end of January this year) in an upcoming update. https://community.tradestation.com/Discussions/Topic.aspx?Topic_ID=177438
If you do not want to wait for the fix I would suggest rewriting your code to access the information you need using OOEL instead of Trade Manager Get commands.
I am still on update 1205 and so far they haven't fixed this problem in the current releases so I am staying on 1205 for as long as I can. I stumbled on a work around if you are still on 1205. I have 2 desktops. After opening trade station I close the desktop that causes the error and reopen it.. It works without the error.
im glad it worked for you too... let me know if you update to a later version that works without this problem. i'm staying on 1205 until im sure they have solved it. if i ever update to a later version and it doesn't work, i cant return to 1205. i will let you know when i update to a good version.
