Support Board
Date/Time: Thu, 28 Nov 2024 12:46:42 +0000
Sierra chart not connecting
View Count: 374
| [2023-05-02 16:44:26] |
| ssangha84 - Posts: 122 |
|
Hello, my Sierra chart is not connect for the last couple of hours. Here is the message log: Rithmic Direct - DTC | Using server connection: Apex-Chicago Area-Non-Aggregated | 2023-05-02 12:36:30.222 Rithmic Direct - DTC | Connecting to the server rsc.rithmic.com. Port 50528 | 2023-05-02 12:36:30.234 DTC Client socket (1) | Creating socket. Using TLS 1.2. | 2023-05-02 12:36:30.238 DTC Client socket (1) | New receive buffer size: 5242880 | 2023-05-02 12:36:30.239 DTC Client socket (1) | Connecting to IP: 216.57.156.163. | 2023-05-02 12:36:30.239 HTTPS connection ID:27 to www.rithmic.com:443 for request ID:27 (4) | Creating socket. Using TLS 1.2. | 2023-05-02 12:36:50.319 HTTPS connection ID:27 to www.rithmic.com:443 for request ID:27 (4) | New receive buffer size: 32768 | 2023-05-02 12:36:50.319 HTTPS connection ID:27 to www.rithmic.com:443 for request ID:27 (4) | Connecting to IP: 38.79.0.89. | 2023-05-02 12:36:50.319 HTTPS connection ID:27 to www.rithmic.com:443 for request ID:27 (4) | New receive buffer size: 65536 | 2023-05-02 12:36:50.778 HTTPS connection ID:27 to www.rithmic.com:443 for request ID:27 (4) | Socket gracefully closed by remote side. | 2023-05-02 12:36:50.897 HTTPS connection ID:27 to www.rithmic.com:443 for request ID:27 (4) | CloseSocket call. | 2023-05-02 12:36:50.898 HTTPS connection ID:27 to www.rithmic.com:443 for request ID:27 (4) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2023-05-02 12:36:50.899 HTTPS connection ID:27 to www.rithmic.com:443 for request ID:27 (4) | Closed. | 2023-05-02 12:36:50.899 DTC Client socket (1) | Connect event error. Windows error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | 2023-05-02 12:36:51.289 * DTC Client socket (1) | CloseSocket call. | 2023-05-02 12:36:51.291 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2023-05-02 12:36:51.291 Select 'File >> Disconnect' to prevent further connection attempts. | 2023-05-02 12:36:51.291 DTC Client socket (1) | Closed. | 2023-05-02 12:36:51.291 DTC Client socket (0) | CloseSocket call. | 2023-05-02 12:36:51.380 Rithmic Direct - DTC | Disconnected. | 2023-05-02 12:36:51.380 Will reconnect to the server in 4.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2023-05-02 12:36:51.380 Rithmic Direct - DTC | Using server connection: Apex-Chicago Area-Non-Aggregated | 2023-05-02 12:36:55.426 Rithmic Direct - DTC | Connecting to the server rsc.rithmic.com. Port 50528 | 2023-05-02 12:36:55.433 DTC Client socket (1) | Creating socket. Using TLS 1.2. | 2023-05-02 12:36:55.433 DTC Client socket (1) | New receive buffer size: 5242880 | 2023-05-02 12:36:55.433 DTC Client socket (1) | Connecting to IP: 216.57.156.163. | 2023-05-02 12:36:55.433 |
| [2023-05-02 17:40:02] |
| John - SC Support - Posts: 36350 |
|
We can not say why there would be a problem connecting to Rithmic. Have you tried a different server?
For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2023-05-02 17:55:11] |
| ssangha84 - Posts: 122 |
|
Yes. I tried CQG as well. Still not connecting: CQG WebAPI | Connecting to server api.cqg.com | 2023-05-02 13:49:16.274 CQG WebSocket | Connecting to WebSocket server api.cqg.com:443 | 2023-05-02 13:49:16.274 CQG WebSocket socket (3) | Creating socket. Using TLS 1.2. | 2023-05-02 13:49:16.275 CQG WebSocket socket (3) | New receive buffer size: 5242880 | 2023-05-02 13:49:16.275 CQG WebSocket socket (3) | Connecting to IP: 208.48.16.17. | 2023-05-02 13:49:16.275 F.US.CLEM23 [CS] 1 Min #10 | Reloading chart. | 2023-05-02 13:49:16.290 F.US.CLEM23 [CS] 1 Min #9 | Reloading chart. | 2023-05-02 13:49:16.317 Loaded depth data records for F.US.CLEM23 2023-04-26 from 2023-04-26 10:06:46.060000 to 2023-04-26 11:07:36.556000. | 2023-05-02 13:49:16.376 F.US.CLEM23 [CS] 1 Min #6 | StartDateTimeForLoadingOrderFills: 2023-03-31 09:49:00 | 2023-05-02 13:49:16.428 Chart #6 has tagged chart #3 for full recalculation. Chartbook: Oil Default.cht | 2023-05-02 13:49:16.448 F.US.CLEM23 [CS] 1 Min #6 | Reloading chart. | 2023-05-02 13:49:16.685 F.US.CLEM23 [CS] 1 Min #4 | Reloading chart. | 2023-05-02 13:49:17.337 F.US.CLEM23 [CS] 5 Min #1 | StartDateTimeForLoadingOrderFills: 2023-03-31 09:45:00 | 2023-05-02 13:49:17.501 F.US.CLEM23 [CS] 1 Min #5 | Reloading chart. | 2023-05-02 13:49:18.050 F.US.CLEM23 [CS] 15 Min #7 | Reloading chart. | 2023-05-02 13:49:18.156 Loading market depth data. | 2023-05-02 13:49:18.452 F.US.CLEM23 [CS] 1 Min #10 | StartDateTimeForLoadingOrderFills: 2023-03-31 09:49:00 | 2023-05-02 13:49:18.546 Loaded depth data records for F.US.CLEM23 2023-04-26 from 2023-04-26 10:06:46.060000 to 2023-04-26 11:07:36.556000. | 2023-05-02 13:49:18.600 F.US.CLEM23 [CS] 1 Min #9 | StartDateTimeForLoadingOrderFills: 2023-03-31 09:49:00 | 2023-05-02 13:49:18.600 F.US.CLEM23 [CS] 1 Min #6 | StartDateTimeForLoadingOrderFills: 2023-03-31 09:49:00 | 2023-05-02 13:49:18.710 Chart #6 has tagged chart #3 for full recalculation. Chartbook: Oil Default.cht | 2023-05-02 13:49:18.728 F.US.CLEM23 [CS] 5 Min #1 | Reloading chart. | 2023-05-02 13:49:19.108 F.US.CLEM23 [CS] 1 Min #5 | StartDateTimeForLoadingOrderFills: 2023-03-31 09:49:00 | 2023-05-02 13:49:19.274 F.US.CLEM23 [CS] 15 Min #7 | StartDateTimeForLoadingOrderFills: 2022-01-20 04:30:00 | 2023-05-02 13:49:19.456 F.US.CLEM23 [CS] 5 Min #1 | StartDateTimeForLoadingOrderFills: 2023-03-31 09:45:00 | 2023-05-02 13:49:20.151 F.US.CLEM23 [CS] 1 Min #3 | Performing a full recalculation because it has been tagged. Chartbook: Oil Default.cht | 2023-05-02 13:49:20.272 CQG WebSocket socket (3) | Connect event error. Windows error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | 2023-05-02 13:49:37.307 * CQG WebSocket socket (3) | CloseSocket call. | 2023-05-02 13:49:37.314 CQG WebSocket | WebSocket closed. | 2023-05-02 13:49:37.314 CQG WebAPI | WebSocket closed. | 2023-05-02 13:49:37.314 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2023-05-02 13:49:37.314 Select 'File >> Disconnect' to prevent further connection attempts. | 2023-05-02 13:49:37.314 CQG WebSocket socket (3) | Closed. | 2023-05-02 13:49:37.314 CQG WebSocket socket (0) | CloseSocket call. | 2023-05-02 13:49:37.408 CQG WebAPI | Disconnected. | 2023-05-02 13:49:37.408 Will reconnect to the server in 2.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2023-05-02 13:49:37.409 CQG WebAPI | Connecting to server api.cqg.com | 2023-05-02 13:49:39.496 CQG WebSocket | Connecting to WebSocket server api.cqg.com:443 | 2023-05-02 13:49:39.496 CQG WebSocket socket (1) | Creating socket. Using TLS 1.2. | 2023-05-02 13:49:39.506 CQG WebSocket socket (1) | New receive buffer size: 5242880 | 2023-05-02 13:49:39.506 CQG WebSocket socket (1) | Connecting to IP: 208.48.16.17. | 2023-05-02 13:49:39.506 CQG WebSocket socket (1) | Connect event error. Windows error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | 2023-05-02 13:50:00.550 * CQG WebSocket socket (1) | CloseSocket call. | 2023-05-02 13:50:00.554 CQG WebSocket | WebSocket closed. | 2023-05-02 13:50:00.554 CQG WebAPI | WebSocket closed. | 2023-05-02 13:50:00.554 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2023-05-02 13:50:00.554 Select 'File >> Disconnect' to prevent further connection attempts. | 2023-05-02 13:50:00.554 CQG WebSocket socket (1) | Closed. | 2023-05-02 13:50:00.554 CQG WebSocket socket (0) | CloseSocket call. | 2023-05-02 13:50:00.684 CQG WebAPI | Disconnected. | 2023-05-02 13:50:00.684 Will reconnect to the server in 2.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2023-05-02 13:50:00.684 CQG WebAPI | Connecting to server api.cqg.com | 2023-05-02 13:50:02.719 CQG WebSocket | Connecting to WebSocket server api.cqg.com:443 | 2023-05-02 13:50:02.719 CQG WebSocket socket (1) | Creating socket. Using TLS 1.2. | 2023-05-02 13:50:02.720 CQG WebSocket socket (1) | New receive buffer size: 5242880 | 2023-05-02 13:50:02.720 CQG WebSocket socket (1) | Connecting to IP: 208.48.16.17. | 2023-05-02 13:50:02.720 CQG WebSocket socket (1) | Connect event error. Windows error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | 2023-05-02 13:50:23.757 * CQG WebSocket socket (1) | CloseSocket call. | 2023-05-02 13:50:23.760 CQG WebSocket | WebSocket closed. | 2023-05-02 13:50:23.760 CQG WebAPI | WebSocket closed. | 2023-05-02 13:50:23.760 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2023-05-02 13:50:23.760 Select 'File >> Disconnect' to prevent further connection attempts. | 2023-05-02 13:50:23.760 CQG WebSocket socket (1) | Closed. | 2023-05-02 13:50:23.760 CQG WebSocket socket (0) | CloseSocket call. | 2023-05-02 13:50:23.952 CQG WebAPI | Disconnected. | 2023-05-02 13:50:23.952 Will reconnect to the server in 2.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2023-05-02 13:50:23.952 CQG WebAPI | Connecting to server api.cqg.com | 2023-05-02 13:50:26.018 CQG WebSocket | Connecting to WebSocket server api.cqg.com:443 | 2023-05-02 13:50:26.018 CQG WebSocket socket (1) | Creating socket. Using TLS 1.2. | 2023-05-02 13:50:26.019 CQG WebSocket socket (1) | New receive buffer size: 5242880 | 2023-05-02 13:50:26.019 CQG WebSocket socket (1) | Connecting to IP: 208.48.16.17. | 2023-05-02 13:50:26.019 CQG WebSocket socket (1) | Connect event error. Windows error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | 2023-05-02 13:50:47.170 * CQG WebSocket socket (1) | CloseSocket call. | 2023-05-02 13:50:47.177 CQG WebSocket | WebSocket closed. | 2023-05-02 13:50:47.177 CQG WebAPI | WebSocket closed. | 2023-05-02 13:50:47.177 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2023-05-02 13:50:47.177 Select 'File >> Disconnect' to prevent further connection attempts. | 2023-05-02 13:50:47.177 CQG WebSocket socket (1) | Closed. | 2023-05-02 13:50:47.177 CQG WebSocket socket (0) | CloseSocket call. | 2023-05-02 13:50:47.470 CQG WebAPI | Disconnected. | 2023-05-02 13:50:47.470 Will reconnect to the server in 2.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2023-05-02 13:50:47.470 CQG WebAPI | Connecting to server api.cqg.com | 2023-05-02 13:50:49.632 CQG WebSocket | Connecting to WebSocket server api.cqg.com:443 | 2023-05-02 13:50:49.632 CQG WebSocket socket (1) | Creating socket. Using TLS 1.2. | 2023-05-02 13:50:49.633 CQG WebSocket socket (1) | New receive buffer size: 5242880 | 2023-05-02 13:50:49.633 CQG WebSocket socket (1) | Connecting to IP: 208.48.16.17. | 2023-05-02 13:50:49.633 CQG WebSocket socket (1) | Connect event error. Windows error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | 2023-05-02 13:51:10.810 * CQG WebSocket socket (1) | CloseSocket call. | 2023-05-02 13:51:10.812 CQG WebSocket | WebSocket closed. | 2023-05-02 13:51:10.812 CQG WebAPI | WebSocket closed. | 2023-05-02 13:51:10.812 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2023-05-02 13:51:10.812 Select 'File >> Disconnect' to prevent further connection attempts. | 2023-05-02 13:51:10.812 CQG WebSocket socket (1) | Closed. | 2023-05-02 13:51:10.812 CQG WebSocket socket (0) | CloseSocket call. | 2023-05-02 13:51:10.985 CQG WebAPI | Disconnected. | 2023-05-02 13:51:10.985 Will reconnect to the server in 2.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2023-05-02 13:51:10.985 |
| [2023-05-03 13:36:48] |
| John - SC Support - Posts: 36350 |
|
In both cases you are getting the following error: CQG WebSocket socket (1) | Connect event error. Windows error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | 2023-05-02 13:50:47.170 *
This indicates a general network issue. Refer to the following: Data/Trading Service Connection and Symbol Issues: 1.2. Network Communication or Server Problem For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: