Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Thu, 25 Apr 2024 20:23:10 +0000
Sub-Instance disconnects repeatedly
View Count: 982
| [2019-10-15 15:32:00] |
| jomanos - Posts: 27 |
|
Very similar problem to this thread: LMAX I have multiple instances (Main, #2, #3, #4). Only instance #2 has a problem with disconnection. It occurs almost immediately. Start Main Instance Error Message: DTCServer (1) | Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine. | 2019-10-15 11:17:10.774 * DTCServer (1) | Socket gracefully closed by remote side. | 2019-10-15 11:17:10.774 DTCServer (1) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2019-10-15 11:17:10.784 DTCServer (1) | Closed. | 2019-10-15 11:17:10.784 Unsubscribed from market depth data for ESZ9-CME | 2019-10-15 11:17:11.087 End Main Instance Message Log. I am trying to figure out why this one instance is disconnecting. This has not happened before with previous versions. Steps to trouble-shoot: 1. Open new instance #2 with no chartbooks. Good. 2. Open chartbook(s) with a couple of default and custom studies (MBox, harmonicPatterns). Good. 3. Open chartbook(s) with different charts (including Number Bars) with default and custom studies (MBox, Emoji Order Flow suite). Disconnection. At this point the instance disconnects and closes abruptly. No further message log is saved for this disconnection. So, I don't know what the specific errors are. Note that previously I was able to open all the chartbooks upon startup of the second instance. See attachments: Attachment No. 1: Main instance message log. Attachment No. 2: Second instance message log. |
 Main_Instance_messagelog_20191015.txt - Attached On 2019-10-15 15:23:01 UTC - Size: 10.44 KB - 234 views InstanceNo2_messagelog_20191015.txt - Attached On 2019-10-15 15:23:13 UTC - Size: 16.26 KB - 321 views |
| [2019-10-15 15:46:44] |
| |
|
There could not be any problem with Sierra Chart in this regard. It must be an external issue. Run Sierra Chart in Safe Mode: Sierra Chart - Software Login Instructions: Using Safe Mode Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2019-10-15 15:46:51
|
| [2019-10-15 17:34:20] |
| jomanos - Posts: 27 |
|
Ok. Went into Safe Mode. That was a pain. Removed all custom studies. Then re-installed one by one for each chart. The only thing I can think of: I went on vacation for two weeks. Since all of the charts in the problematic chartbook(s) were limited to 5 days of data, maybe some of the custom studies were seeking data that was no longer available causing errors. That is my only guess. Seems all good now. Thanks! |
| [2019-10-15 17:43:04] |
| |
|
You did not have to remove the studies. When you use Safe Mode, they just do not get loaded. And removing and/or re-adding them them is an unnecessary procedure. That is not anything we would recommend.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2019-10-15 17:53:55] |
| jomanos - Posts: 27 |
|
Interesting. But, when I re-started the instance with Safe Mode unchecked, some of the lingering custom studies were causing the instance to abruptly close again. Deleting and then re-installing the custom studies seems to have fixed the problem. |
To post a message in this thread, you need to log in with your Sierra Chart account: