Support Board
Date/Time: Fri, 29 Nov 2024 08:35:49 +0000
Unable to create new (additional) instance of Sierra Chart on same machine
View Count: 408
[2023-01-17 18:54:25] |
sola5180 - Posts: 13 |
I am getting error messages after File --> New instance. The new instance closes shortly after starting up. I will send the message log, but here is a short snippet that shows Windows error codes: [ 10053 | 10054 ]. Please note I am running Windows on Arm. DTC client #1. Sierra Chart. 127.0.0.1 | Sent successful Logon response message to client. Username: Result text: Connected to SC DTC Protocol server. Service=sc_futures_direct.dtc.trading|SymbolSettings=sc_futures_direct.dtc.trading | 2023-01-17 18:43:05.949 HD Server | Thread:11748 (3) | Socket gracefully closed by remote side. | 2023-01-17 18:43:07.975 HD Server | Thread:11748 (3) | Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine. | 2023-01-17 18:43:07.976 * DTC client #1. 127.0.0.1 (2) | Socket gracefully closed by remote side. | 2023-01-17 18:43:07.976 DTC client #1. 127.0.0.1 (2) | Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine. | 2023-01-17 18:43:07.976 * HD Server | Thread:11748 (3) | Socket send error. Windows error code 10054: An existing connection was forcibly closed by the remote host. | 2023-01-17 18:43:07.989 HD Server | HD Request | Socket: 3 | Symbol: USOil | ServiceCode: DTCSubInstance | RecordInterval: 0 | Records Served: 1040384 | ClientReqID: 1 | Username: | Thread:11748 | 2023-01-17 18:43:08.007 HD Server | Thread:11748 (3) | CloseSocket call. | 2023-01-17 18:43:08.007 DTC client #1. 127.0.0.1 (2) | Socket send error. Windows error code 10054: An existing connection was forcibly closed by the remote host. | 2023-01-17 18:43:08.008 HD Server | Thread:11748 (0) | CloseSocket call. | 2023-01-17 18:43:08.008 |
[2023-01-18 22:24:35] |
Sierra_Chart Engineering - Posts: 17224 |
We see that the new instance is abnormally shutting down. Try to enable saving of the Message Log in the sub instance: Message Log: Automatically Saving Message Log to File See if there are already logs in the C:\SierraChart\SierraChartInstance_2\Logs subfolder. 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: 2023-01-18 22:25:16
|
[2023-02-20 23:30:42] |
sola5180 - Posts: 13 |
This thread can be closed, not because the issue was resolved but because I'm now using a new PC with Intel processor / Win10.
|
To post a message in this thread, you need to log in with your Sierra Chart account: