Login Page - Create Account

Support Board


Date/Time: Sat, 15 Mar 2025 02:51:50 +0000



Continuous connection error message

View Count: 545

[2022-07-06 10:14:16]
Sitting Bull - Posts: 11
Good morning
I have a persistent error message in the message log since this morning.
I have installed the last version 2411 but the error is still coming up all the time.
Not sure I can trade live with it.
Can you check the "Message log" copy below and let me know what I can do to solve the problem?
Thanks
Kind regards
Arnaud Meurice


Software version: 2411 64-bit | 2022-07-06 12:06:15.613
Primary Thread ID: 10828 | 2022-07-06 12:06:15.613
Usage end date: 2022-10-15 | 2022-07-06 12:06:15.613
Enabled for: Advanced Features 2. | 2022-07-06 12:06:15.613
Enabled for: Sierra Chart Historical Data Service. | 2022-07-06 12:06:15.613
Enabled for: Denali Real-Time Exchange Data Feed. | 2022-07-06 12:06:15.613
Enabled for: Delayed Denali Exchange Data Feed. | 2022-07-06 12:06:15.613
Enabled for exchange2: CME | 2022-07-06 12:06:15.613
Enabled for exchange2: fairx_exchange.data | 2022-07-06 12:06:15.613
Allow Support for Sierra Chart Data Feeds is enabled. | 2022-07-06 12:06:15.613
Current selected Data/Trading service: Rithmic Direct - DTC | 2022-07-06 12:06:15.613
Custom symbol settings values: enabled | 2022-07-06 12:06:15.613
Chart Update Interval: 100 | 2022-07-06 12:06:15.613
Intraday Data Storage Time Unit: 0 | 2022-07-06 12:06:15.613
Time Zone: +02:00:00 (CET+01CEST+01,M3.5.0/02:00,M10.5.0/03:00) | 2022-07-06 12:06:15.613
2022-07-06 10:06:15 Local computer time in UTC | 2022-07-06 12:06:15.613
2022-07-06 12:06:15 Local computer time in SC Time Zone | 2022-07-06 12:06:15.613
2022-07-06 09:44:05 Server time in UTC | 2022-07-06 12:06:15.613
Local computer UTC time and Server UTC time difference: 0 seconds. | 2022-07-06 12:06:15.613
Program path: C:\SierraChart\ | 2022-07-06 12:06:15.613
Data Files path: C:\SierraChart\Data\ | 2022-07-06 12:06:15.613
OS Version Number: 10.0 | 2022-07-06 12:06:15.613
Locale Setting: C | 2022-07-06 12:06:15.613
DLLs: ETFISv3.dll, ETFISv3_64.dll, StochCycle_64.dll, UserContributedStudies_64.dll | 2022-07-06 12:06:15.614
Allowed protected custom studies: | 2022-07-06 12:06:15.614
Crash reporter started: true | 2022-07-06 12:06:15.614

HTTPS connection ID:45 to www.rithmic.com:443 for request ID:45 (1) | Creating socket. Using TLS 1.2. | 2022-07-06 12:06:22.698
HTTPS connection ID:45 to www.rithmic.com:443 for request ID:45 (1) | New receive buffer size: 32768 | 2022-07-06 12:06:22.698
HTTPS connection ID:45 to www.rithmic.com:443 for request ID:45 (1) | Connecting to IP: 38.79.0.89. | 2022-07-06 12:06:22.698
HTTPS connection ID:45 to www.rithmic.com:443 for request ID:45 (1) | Connect event error. Windows error code 10060: Une tentative de connexion a échoué car le parti connecté n’a pas répondu convenablement au-delà d’une certaine durée ou une connexion établie a échoué car l’hôte de connexion n’a pas répondu. | 2022-07-06 12:06:43.740 *
HTTPS connection ID:45 to www.rithmic.com:443 for request ID:45 (1) | CloseSocket call. | 2022-07-06 12:06:43.855
HTTPS connection ID:45 to www.rithmic.com:443 for request ID:45 (1) | Closed. | 2022-07-06 12:06:43.855
HTTPS connection ID:46 to www.rithmic.com:443 for request ID:46 (1) | Creating socket. Using TLS 1.2. | 2022-07-06 12:06:52.620
HTTPS connection ID:46 to www.rithmic.com:443 for request ID:46 (1) | New receive buffer size: 32768 | 2022-07-06 12:06:52.620
HTTPS connection ID:46 to www.rithmic.com:443 for request ID:46 (1) | Connecting to IP: 38.79.0.89. | 2022-07-06 12:06:52.620
HTTPS connection ID:46 to www.rithmic.com:443 for request ID:46 (1) | Connect event error. Windows error code 10060: Une tentative de connexion a échoué car le parti connecté n’a pas répondu convenablement au-delà d’une certaine durée ou une connexion établie a échoué car l’hôte de connexion n’a pas répondu. | 2022-07-06 12:07:13.678 *
HTTPS connection ID:46 to www.rithmic.com:443 for request ID:46 (1) | CloseSocket call. | 2022-07-06 12:07:13.685
HTTPS connection ID:46 to www.rithmic.com:443 for request ID:46 (1) | Closed. | 2022-07-06 12:07:13.685
HTTPS connection ID:47 to www.rithmic.com:443 for request ID:47 (1) | Creating socket. Using TLS 1.2. | 2022-07-06 12:07:22.686
HTTPS connection ID:47 to www.rithmic.com:443 for request ID:47 (1) | New receive buffer size: 32768 | 2022-07-06 12:07:22.686
HTTPS connection ID:47 to www.rithmic.com:443 for request ID:47 (1) | Connecting to IP: 38.79.0.89. | 2022-07-06 12:07:22.686
HTTPS connection ID:47 to www.rithmic.com:443 for request ID:47 (1) | Connect event error. Windows error code 10060: Une tentative de connexion a échoué car le parti connecté n’a pas répondu convenablement au-delà d’une certaine durée ou une connexion établie a échoué car l’hôte de connexion n’a pas répondu. | 2022-07-06 12:07:43.735 *
HTTPS connection ID:47 to www.rithmic.com:443 for request ID:47 (1) | CloseSocket call. | 2022-07-06 12:07:43.849
HTTPS connection ID:47 to www.rithmic.com:443 for request ID:47 (1) | Closed. | 2022-07-06 12:07:43.849
HTTPS connection ID:48 to www.rithmic.com:443 for request ID:48 (1) | Creating socket. Using TLS 1.2. | 2022-07-06 12:07:52.783
HTTPS connection ID:48 to www.rithmic.com:443 for request ID:48 (1) | New receive buffer size: 32768 | 2022-07-06 12:07:52.783
HTTPS connection ID:48 to www.rithmic.com:443 for request ID:48 (1) | Connecting to IP: 38.79.0.89. | 2022-07-06 12:07:52.783
HTTPS connection ID:48 to www.rithmic.com:443 for request ID:48 (1) | Connect event error. Windows error code 10060: Une tentative de connexion a échoué car le parti connecté n’a pas répondu convenablement au-delà d’une certaine durée ou une connexion établie a échoué car l’hôte de connexion n’a pas répondu. | 2022-07-06 12:08:13.830 *
HTTPS connection ID:48 to www.rithmic.com:443 for request ID:48 (1) | CloseSocket call. | 2022-07-06 12:08:13.846
HTTPS connection ID:48 to www.rithmic.com:443 for request ID:48 (1) | Closed. | 2022-07-06 12:08:13.846
HTTPS connection ID:49 to www.rithmic.com:443 for request ID:49 (1) | Creating socket. Using TLS 1.2. | 2022-07-06 12:08:22.714
HTTPS connection ID:49 to www.rithmic.com:443 for request ID:49 (1) | New receive buffer size: 32768 | 2022-07-06 12:08:22.714
HTTPS connection ID:49 to www.rithmic.com:443 for request ID:49 (1) | Connecting to IP: 38.79.0.89. | 2022-07-06 12:08:22.714
HTTPS connection ID:49 to www.rithmic.com:443 for request ID:49 (1) | Connect event error. Windows error code 10060: Une tentative de connexion a échoué car le parti connecté n’a pas répondu convenablement au-delà d’une certaine durée ou une connexion établie a échoué car l’hôte de connexion n’a pas répondu. | 2022-07-06 12:08:43.760 *
HTTPS connection ID:49 to www.rithmic.com:443 for request ID:49 (1) | CloseSocket call. | 2022-07-06 12:08:43.831
HTTPS connection ID:49 to www.rithmic.com:443 for request ID:49 (1) | Closed. | 2022-07-06 12:08:43.831
HTTPS connection ID:50 to www.rithmic.com:443 for request ID:50 (1) | Creating socket. Using TLS 1.2. | 2022-07-06 12:08:52.670
HTTPS connection ID:50 to www.rithmic.com:443 for request ID:50 (1) | New receive buffer size: 32768 | 2022-07-06 12:08:52.670
HTTPS connection ID:50 to www.rithmic.com:443 for request ID:50 (1) | Connecting to IP: 38.79.0.89. | 2022-07-06 12:08:52.670
HTTPS connection ID:50 to www.rithmic.com:443 for request ID:50 (1) | Connect event error. Windows error code 10060: Une tentative de connexion a échoué car le parti connecté n’a pas répondu convenablement au-delà d’une certaine durée ou une connexion établie a échoué car l’hôte de connexion n’a pas répondu. | 2022-07-06 12:09:13.734 *
HTTPS connection ID:50 to www.rithmic.com:443 for request ID:50 (1) | CloseSocket call. | 2022-07-06 12:09:13.739
HTTPS connection ID:50 to www.rithmic.com:443 for request ID:50 (1) | Closed. | 2022-07-06 12:09:13.740
HTTPS connection ID:51 to www.rithmic.com:443 for request ID:51 (2) | Creating socket. Using TLS 1.2. | 2022-07-06 12:09:22.647
HTTPS connection ID:51 to www.rithmic.com:443 for request ID:51 (2) | New receive buffer size: 32768 | 2022-07-06 12:09:22.647
HTTPS connection ID:51 to www.rithmic.com:443 for request ID:51 (2) | Connecting to IP: 38.79.0.89. | 2022-07-06 12:09:22.647
HTTPS connection ID:51 to www.rithmic.com:443 for request ID:51 (2) | Connect event error. Windows error code 10060: Une tentative de connexion a échoué car le parti connecté n’a pas répondu convenablement au-delà d’une certaine durée ou une connexion établie a échoué car l’hôte de connexion n’a pas répondu. | 2022-07-06 12:09:43.720 *
HTTPS connection ID:51 to www.rithmic.com:443 for request ID:51 (2) | CloseSocket call. | 2022-07-06 12:09:43.792
HTTPS connection ID:51 to www.rithmic.com:443 for request ID:51 (2) | Closed. | 2022-07-06 12:09:43.792
HTTPS connection ID:52 to www.rithmic.com:443 for request ID:52 (1) | Creating socket. Using TLS 1.2. | 2022-07-06 12:09:52.676
HTTPS connection ID:52 to www.rithmic.com:443 for request ID:52 (1) | New receive buffer size: 32768 | 2022-07-06 12:09:52.677
HTTPS connection ID:52 to www.rithmic.com:443 for request ID:52 (1) | Connecting to IP: 38.79.0.89. | 2022-07-06 12:09:52.677
HTTPS connection ID:52 to www.rithmic.com:443 for request ID:52 (1) | Connect event error. Windows error code 10060: Une tentative de connexion a échoué car le parti connecté n’a pas répondu convenablement au-delà d’une certaine durée ou une connexion établie a échoué car l’hôte de connexion n’a pas répondu. | 2022-07-06 12:10:13.718 *
HTTPS connection ID:52 to www.rithmic.com:443 for request ID:52 (1) | CloseSocket call. | 2022-07-06 12:10:13.722
HTTPS connection ID:52 to www.rithmic.com:443 for request ID:52 (1) | Closed. | 2022-07-06 12:10:13.722
imageCapture d’écran 2022-07-06 115644.jpg / V - Attached On 2022-07-06 10:02:39 UTC - Size: 206.4 KB - 133 views
[2022-07-06 10:23:59]
Sierra Chart Engineering - Posts: 104368
This is due to a server problem on the Rithmic side or an Internet connectivity problem. So you need to look into either of these.

Sierra Chart is just not able to request the list of servers from Rithmic:

HTTPS connection ID:45 to www.rithmic.com:443 for request ID:45 (1) | Connecting to IP: 38.79.0.89. | 2022-07-06 12:06:22.698

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: 2022-07-06 10:24:14
[2022-07-06 10:59:16]
Borubar - Posts: 17
I'm getting the same error.
[2022-07-06 11:21:09]
Sierra Chart Engineering - Posts: 104368
Therefore it could be a Rithmic issue. It should be resolved by them today.
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
[2022-07-06 11:49:39]
Impressive_Emu - Posts: 1
Same Error here also, will wait to see if Rithmic updates. Is it safe to trade? The charts and DOM seem to be functional.
Also I'm getting the same error message after I disconnect from data feed.

HTTPS connection ID:14 to www.rithmic.com:443 for request ID:14 (2) | 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. | 2022-07-06 07:43:53.995 *
HTTPS connection ID:14 to www.rithmic.com:443 for request ID:14 (2) | CloseSocket call. | 2022-07-06 07:43:53.996
HTTPS connection ID:14 to www.rithmic.com:443 for request ID:14 (2) | Closed. | 2022-07-06 07:43:53.996
HTTPS connection ID:15 to www.rithmic.com:443 for request ID:15 (2) | Creating socket. Using TLS 1.2. | 2022-07-06 07:44:02.964
HTTPS connection ID:15 to www.rithmic.com:443 for request ID:15 (2) | New receive buffer size: 32768 | 2022-07-06 07:44:02.965
HTTPS connection ID:15 to www.rithmic.com:443 for request ID:15 (2) | Connecting to IP: 38.79.0.89. | 2022-07-06 07:44:02.965
HTTPS connection ID:15 to www.rithmic.com:443 for request ID:15 (2) | 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. | 2022-07-06 07:44:24.013 *
HTTPS connection ID:15 to www.rithmic.com:443 for request ID:15 (2) | CloseSocket call. | 2022-07-06 07:44:24.013
HTTPS connection ID:15 to www.rithmic.com:443 for request ID:15 (2) | Closed. | 2022-07-06 07:44:24.014
HTTPS connection ID:16 to www.rithmic.com:443 for request ID:16 (2) | Creating socket. Using TLS 1.2. | 2022-07-06 07:44:32.965
HTTPS connection ID:16 to www.rithmic.com:443 for request ID:16 (2) | New receive buffer size: 32768 | 2022-07-06 07:44:32.965
HTTPS connection ID:16 to www.rithmic.com:443 for request ID:16 (2) | Connecting to IP: 38.79.0.89. | 2022-07-06 07:44:32.965
HTTPS connection ID:16 to www.rithmic.com:443 for request ID:16 (2) | 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. | 2022-07-06 07:44:54.006 *
HTTPS connection ID:16 to www.rithmic.com:443 for request ID:16 (2) | CloseSocket call. | 2022-07-06 07:44:54.006
HTTPS connection ID:16 to www.rithmic.com:443 for request ID:16 (2) | Closed. | 2022-07-06 07:44:54.006
HTTPS connection ID:17 to www.rithmic.com:443 for request ID:17 (2) | Creating socket. Using TLS 1.2. | 2022-07-06 07:45:02.963
HTTPS connection ID:17 to www.rithmic.com:443 for request ID:17 (2) | New receive buffer size: 32768 | 2022-07-06 07:45:02.963
HTTPS connection ID:17 to www.rithmic.com:443 for request ID:17 (2) | Connecting to IP: 38.79.0.89. | 2022-07-06 07:45:02.963
HTTPS connection ID:17 to www.rithmic.com:443 for request ID:17 (2) | 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. | 2022-07-06 07:45:23.984 *
HTTPS connection ID:17 to www.rithmic.com:443 for request ID:17 (2) | CloseSocket call. | 2022-07-06 07:45:23.984
HTTPS connection ID:17 to www.rithmic.com:443 for request ID:17 (2) | Closed. | 2022-07-06 07:45:23.984
HTTPS connection ID:18 to www.rithmic.com:443 for request ID:18 (2) | Creating socket. Using TLS 1.2. | 2022-07-06 07:45:32.963
HTTPS connection ID:18 to www.rithmic.com:443 for request ID:18 (2) | New receive buffer size: 32768 | 2022-07-06 07:45:32.963
HTTPS connection ID:18 to www.rithmic.com:443 for request ID:18 (2) | Connecting to IP: 38.79.0.89. | 2022-07-06 07:45:32.963
HTTPS connection ID:18 to www.rithmic.com:443 for request ID:18 (2) | 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. | 2022-07-06 07:45:54.007 *
HTTPS connection ID:18 to www.rithmic.com:443 for request ID:18 (2) | CloseSocket call. | 2022-07-06 07:45:54.007
HTTPS connection ID:18 to www.rithmic.com:443 for request ID:18 (2) | Closed. | 2022-07-06 07:45:54.007
HTTPS connection ID:19 to www.rithmic.com:443 for request ID:19 (2) | Creating socket. Using TLS 1.2. | 2022-07-06 07:46:02.964
HTTPS connection ID:19 to www.rithmic.com:443 for request ID:19 (2) | New receive buffer size: 32768 | 2022-07-06 07:46:02.964
HTTPS connection ID:19 to www.rithmic.com:443 for request ID:19 (2) | Connecting to IP: 38.79.0.89. | 2022-07-06 07:46:02.964
HTTPS connection ID:19 to www.rithmic.com:443 for request ID:19 (2) | 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. | 2022-07-06 07:46:24.001 *
HTTPS connection ID:19 to www.rithmic.com:443 for request ID:19 (2) | CloseSocket call. | 2022-07-06 07:46:24.001
HTTPS connection ID:19 to www.rithmic.com:443 for request ID:19 (2) | Closed. | 2022-07-06 07:46:24.001
HTTPS connection ID:20 to www.rithmic.com:443 for request ID:20 (2) | Creating socket. Using TLS 1.2. | 2022-07-06 07:46:32.962
HTTPS connection ID:20 to www.rithmic.com:443 for request ID:20 (2) | New receive buffer size: 32768 | 2022-07-06 07:46:32.963
HTTPS connection ID:20 to www.rithmic.com:443 for request ID:20 (2) | Connecting to IP: 38.79.0.89. | 2022-07-06 07:46:32.963
Date Time Of Last Edit: 2022-07-06 12:09:03
[2022-07-06 12:30:19]
Sierra Chart Engineering - Posts: 104368
Yes it is fully safe to do trading. This is not related. To prevent the Message Log from opening you can temporarily enable this:
General Settings Window: Never Automatically Open Message Log or Trade Service Log (Global Settings >> General Settings >> Log >> Log)
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
[2022-07-06 12:30:38]
User303551 - Posts: 3
Same here. This is the second time it has happened. Usually resolves itself, but very annoying

To post a message in this thread, you need to log in with your Sierra Chart account:

Login

Login Page - Create Account