Support Board
Date/Time: Sun, 15 Jun 2025 06:55:18 +0000
SUBINSTANCES - Connection Problem
View Count: 149
| [2025-06-09 02:04:19] |
| Meklon - Posts: 241 |
|
Hello Support, I am experiencing a disconnect on my 2 Sierra sub-instances. Main instance is configured to start 2 additional sub-instances and all 3 do not start any chartbooks - just a plain main instance and sub-instance start. All 3 (Main SC instance, and 2 sub-instances start successfully and establish successful connection to a live Denali / Teton connection. I am able to successfully open chartbooks in sub-instance 1 and sub-instance 2 - no issues. However, when I am opening a chartbook in the main instance (it takes several minutes to load) the sub-instance-1 and sub-instance-2 disconnect and no longer able to reconnect. When the chartbook in the main instance loads successfully, it runs fine without any issues, but both sub-instances still remain off line and any attempt to reconnect them fail. This has not happened before, configuration and the chartbooks are the same. Is there a way to manually restart just the sub-instance 1 and 2 to re-establish their connection without terminating the main instance? Here is what the sub-instance log says: 2025-06-08 22:00:46.857 | DTC - Sub Instance | Connecting to the server 127.0.0.1. Port 11099 2025-06-08 22:00:46.857 | DTC Client socket (5) | Creating socket. 2025-06-08 22:00:46.857 | DTC Client socket (5) | New receive buffer size: 0 2025-06-08 22:00:46.857 | DTC Client socket (5) | Connecting to IP: 127.0.0.1. 2025-06-08 22:00:46.858 | DTC - Sub Instance | Network connection to server complete. 2025-06-08 22:00:46.858 | DTC - Sub Instance | Starting socket receive thread. 2025-06-08 22:00:46.858 | DTC - Sub Instance | Sending encoding request to server: Binary VLS. Compression: none 2025-06-08 22:00:54.796 | DTC Client socket (6) | Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine. * 2025-06-08 22:00:54.796 | DTC Client socket (6) | Socket gracefully closed by remote side. 2025-06-08 22:00:54.796 | DTC Client socket (6) | Closed. 2025-06-08 22:01:06.863 | DTC - Sub Instance | Did not receive Encoding Response from server. Disconnecting. * 2025-06-08 22:01:06.863 | Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. 2025-06-08 22:01:06.863 | Select 'File >> Disconnect' to prevent further connection attempts. 2025-06-08 22:01:06.879 | DTC - Sub Instance | Waiting for socket receive thread to end 2025-06-08 22:01:06.879 | DTC Client socket (5) | CloseSocket call. 2025-06-08 22:01:06.879 | DTC Client socket (5) | Shutdown started. Waiting for graceful close. 2025-06-08 22:01:06.879 | DTC - Sub Instance | Disconnected. 2025-06-08 22:01:06.879 | Will reconnect to the server in 2.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. 2025-06-08 22:01:08.876 | 2025-06-08 22:01:08.876 | DTC - Sub Instance | Connecting to the server 127.0.0.1. Port 11099 2025-06-08 22:01:08.876 | DTC Client socket (6) | Creating socket. 2025-06-08 22:01:08.876 | DTC Client socket (6) | New receive buffer size: 0 2025-06-08 22:01:08.876 | DTC Client socket (6) | Connecting to IP: 127.0.0.1. 2025-06-08 22:01:08.877 | DTC - Sub Instance | Network connection to server complete. 2025-06-08 22:01:08.877 | DTC - Sub Instance | Starting socket receive thread. 2025-06-08 22:01:08.878 | DTC - Sub Instance | Sending encoding request to server: Binary VLS. Compression: none 2025-06-08 22:01:16.819 | DTC Client socket (7) | Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine. * 2025-06-08 22:01:16.819 | DTC Client socket (7) | Socket gracefully closed by remote side. 2025-06-08 22:01:16.819 | DTC Client socket (7) | Closed. 2025-06-08 22:01:28.871 | DTC - Sub Instance | Did not receive Encoding Response from server. Disconnecting. * 2025-06-08 22:01:28.871 | Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. 2025-06-08 22:01:28.871 | Select 'File >> Disconnect' to prevent further connection attempts. 2025-06-08 22:01:28.886 | DTC - Sub Instance | Waiting for socket receive thread to end 2025-06-08 22:01:28.886 | DTC Client socket (6) | CloseSocket call. 2025-06-08 22:01:28.886 | DTC Client socket (6) | Shutdown started. Waiting for graceful close. 2025-06-08 22:01:28.886 | DTC - Sub Instance | Disconnected. 2025-06-08 22:01:28.886 | Will reconnect to the server in 2.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. 2025-06-08 22:01:30.896 | 2025-06-08 22:01:30.896 | DTC - Sub Instance | Connecting to the server 127.0.0.1. Port 11099 2025-06-08 22:01:30.896 | DTC Client socket (7) | Creating socket. 2025-06-08 22:01:30.896 | DTC Client socket (7) | New receive buffer size: 0 2025-06-08 22:01:30.896 | DTC Client socket (7) | Connecting to IP: 127.0.0.1. 2025-06-08 22:01:30.897 | DTC - Sub Instance | Network connection to server complete. 2025-06-08 22:01:30.897 | DTC - Sub Instance | Starting socket receive thread. 2025-06-08 22:01:30.898 | DTC - Sub Instance | Sending encoding request to server: Binary VLS. Compression: none 2025-06-08 22:01:38.832 | DTC Client socket (2) | Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine. * 2025-06-08 22:01:38.832 | DTC Client socket (2) | Socket gracefully closed by remote side. 2025-06-08 22:01:38.832 | DTC Client socket (2) | Closed. 2025-06-08 22:01:50.889 | DTC - Sub Instance | Did not receive Encoding Response from server. Disconnecting. * 2025-06-08 22:01:50.889 | Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. 2025-06-08 22:01:50.889 | Select 'File >> Disconnect' to prevent further connection attempts. 2025-06-08 22:01:50.905 | DTC - Sub Instance | Waiting for socket receive thread to end 2025-06-08 22:01:50.905 | DTC Client socket (7) | CloseSocket call. 2025-06-08 22:01:50.906 | DTC Client socket (7) | Shutdown started. Waiting for graceful close. 2025-06-08 22:01:50.906 | DTC - Sub Instance | Disconnected. 2025-06-08 22:01:50.906 | Will reconnect to the server in 2.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. 2025-06-08 22:01:52.913 | 2025-06-08 22:01:52.913 | DTC - Sub Instance | Connecting to the server 127.0.0.1. Port 11099 2025-06-08 22:01:52.914 | DTC Client socket (2) | Creating socket. 2025-06-08 22:01:52.914 | DTC Client socket (2) | New receive buffer size: 0 2025-06-08 22:01:52.914 | DTC Client socket (2) | Connecting to IP: 127.0.0.1. 2025-06-08 22:01:52.915 | DTC - Sub Instance | Network connection to server complete. 2025-06-08 22:01:52.915 | DTC - Sub Instance | Starting socket receive thread. 2025-06-08 22:01:52.915 | DTC - Sub Instance | Sending encoding request to server: Binary VLS. Compression: none 2025-06-08 22:02:00.837 | DTC Client socket (1) | Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine. * 2025-06-08 22:02:00.837 | DTC Client socket (1) | Socket gracefully closed by remote side. 2025-06-08 22:02:00.837 | DTC Client socket (1) | Closed. Date Time Of Last Edit: 2025-06-09 02:06:04
|
| [2025-06-09 16:44:25] |
| John - SC Support - Posts: 40422 |
|
You can close the sub-instances and then start them again by selecting "File >> New Instance". Just keep in mind that when you select New Instance, the actual instance that is opened is in a sequential order based on what is already open. So if there are no sub-instances already running, select New Instance will start Sub-Instance 2, then Sub-Instance 3, etc. (there is no sub-instance 1, the first sub-instance starts at #2). If you have specific sub-instance numbers that are not sequential, then the only way to open just those would be by closing the main instance and starting again. But there is no reason for there to be an issue with a sub-instance when opening a chartbook. We do see the error in the log portion you sent, and we do not know why you would be getting that error. Do you have multiple installations of Sierra Chart installed in that computer? For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2025-06-09 16:51:43] |
| Meklon - Posts: 241 |
|
Thank you for your reply. I have 2 SC installations on this server - 1 is connected to live account and configured with 2 additional sub-instances (this is the one that I am having an issue described above). Second SC installation is to testing / development only and connected to Trading Evaluator Sierra accounts. |
| [2025-06-09 18:26:09] |
| John - SC Support - Posts: 40422 |
|
When you have multiple installations on the same computer, you have to be careful about where you start the Sub-Instances and which system they are connecting to. Refer to the following: Using DTC Server for Data and Trading in Another Sierra Chart Instance: Resolving DTC Protocol Server Port Number Conflicts Note from the introduction in that section that if you are not using sub-instances in a second installation then that installation should have "Global Settings >> Sierra Chart Server Settings >> DTC Protocol Server >> Enable DTC Protocol Server" set to "No". Otherwise, look through the rest of that information to ensure you setup the systems as you want them. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2025-06-09 18:48:59] |
| Meklon - Posts: 241 |
|
Thank you John. I suspect this issue could be related to a Norton Antivirus, Firewall and Network monitoring which is interfering with DTC communication. When the main SC instance is being started it is treated as a single task of SierraChart.exe that spawns new instances. Because I have the entire Sierra Chart installation folder excluded from Norton firewall checks and attack threats it has no issue starting the main instance and sub-instances. However, when main SC instance stops communicating with sub-instances because it's busy calculating and loading charts any new outside activity from sub-instance is being identified and treated as a threat by Norton. I have vetted and excluded the SierraChart.exe and SierraChart_64.exe executables from each sub-instance subfolder by telling Norton Firewall and Monitoring to ignore it and the problem has gone away - once the main instance finished load of the chartbook the connection to sub-instances is successfully re-established. Date Time Of Last Edit: 2025-06-09 23:48:16
|
| [2025-06-09 21:23:48] |
| John - SC Support - Posts: 40422 |
|
Glad you were able to figure it out.
For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2025-06-09 23:13:50] |
| Sierra_Chart Engineering - Posts: 19916 |
|
We prepared this response before you posted this other information: There is too much of a high load in the main instance of Sierra Chart. That needs to be resolved. Refer to: High CPU Usage | Inactive User Interface | Poor Performance | Long Time to Load Chart Data | Charts Reloading Often Apparently the high load is leading to some kind of instability. 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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2025-06-09 23:15:09
|
To post a message in this thread, you need to log in with your Sierra Chart account: