Home >> Support Board

Support Board

Date/Time: Mon, 16 Sep 2024 20:07:27 +0000

How to Post a Message for Support

No connection to data - Reconnect Wait

View Count: 1980

[2024-07-16 15:46:22] #25 [Go To First Post]
User936941 - Posts: 20
Message log sent. Thank you!

[2024-07-16 15:48:03] #26 [Go To First Post]
raheemrazzak - Posts: 41
Getting error for Rithmic from las Vegs, Nevada, posting log if it helps, I disconnected/connected sierrachart, restarted sierra and restarted my system as well but same issue ------ 2024-07-16 08:42:58.146 \| Software version: 2634 64-bit 2024-07-16 08:42:58.146 \| Primary Thread ID: 5472 2024-07-16 08:42:58.146 \| Usage end date: 2024-07-23 2024-07-16 08:42:58.146 \| Enabled for: Sierra Chart Historical Data Service. 2024-07-16 08:42:58.146 \| Enabled for: Denali Real-Time Exchange Data Feed. 2024-07-16 08:42:58.146 \| Enabled for: Delayed Denali Exchange Data Feed. 2024-07-16 08:42:58.146 \| Enabled for exchange2: CME 2024-07-16 08:42:58.146 \| Allow Support for Sierra Chart Data Feeds is enabled. 2024-07-16 08:42:58.146 \| Current selected Data/Trading service: Rithmic Direct - DTC 2024-07-16 08:42:58.146 \| Custom symbol settings values: enabled 2024-07-16 08:42:58.146 \| Chart Update Interval: 1500 2024-07-16 08:42:58.146 \| Intraday Data Storage Time Unit: 0 2024-07-16 08:42:58.146 \| Time Zone: -07:00:00 (PST-08PDT+01,M3.2.0/02:00,M11.1.0/02:00) 2024-07-16 08:42:58.146 \| 2024-07-16 15:42:58 Local computer time in UTC 2024-07-16 08:42:58.146 \| 2024-07-16 08:42:58 Local computer time in SC Time Zone 2024-07-16 08:42:58.146 \| 2024-07-16 15:35:15 Server time in UTC 2024-07-16 08:42:58.146 \| Local computer UTC time and Server UTC time difference: 3 seconds. 2024-07-16 08:42:58.146 \| Program path: C:\SierraChart2\ 2024-07-16 08:42:58.146 \| Data Files path: C:\SierraChart2\Data\ 2024-07-16 08:42:58.147 \| OS Version Number: 10.0 2024-07-16 08:42:58.147 \| Locale Setting: C 2024-07-16 08:42:58.147 \| DLLs: auto_risk_reward_64.dll, CountDownPercentage_64.dll, FVG_and_News_64.dll, gc5150_Studies_2431_64.dll, KeyToHide_64.dll, magic_charts_64.dll, price_in_label_64.dll, PTM_Indicators_64.dll, PTM_Studies_64.dll, sst_FreeBundle_2273_64.dll, sst_FreeBundle_64.dll, TORobots_64.dll, TraderOracle_64.dll, UserContributedStudies_64.dll, zoom_toggle_64.dll, Zyp Free by Zyp_64.dll, Zyp Trade_Your_Plan_64.dll 2024-07-16 08:42:58.147 \| Allowed protected custom studies: SST_FreeBundle, zyp_app 2024-07-16 08:42:58.147 \| Crash reporter started: true 2024-07-16 08:42:58.147 \| 2024-07-16 08:43:01.917 \| HTTPS connection ID:23 to downloads.rithmic.com:443 for request ID:23 (1) \| Creating socket. Using TLS 1.2. 2024-07-16 08:43:01.918 \| HTTPS connection ID:23 to downloads.rithmic.com:443 for request ID:23 (1) \| New receive buffer size: 0 2024-07-16 08:43:01.918 \| HTTPS connection ID:23 to downloads.rithmic.com:443 for request ID:23 (1) \| Connecting to IP: 216.66.0.130. 2024-07-16 08:43:02.967 \| HTTPS connection ID:22 to downloads.rithmic.com:443 for request ID:22 (4) \| 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. * 2024-07-16 08:43:02.977 \| HTTPS connection ID:22 to downloads.rithmic.com:443 for request ID:22 (4) \| CloseSocket call. 2024-07-16 08:43:02.977 \| HTTPS connection ID:22 to downloads.rithmic.com:443 for request ID:22 (4) \| Closed. 2024-07-16 08:43:09.513 \| 2024-07-16 08:43:09.514 \| Rithmic Direct - DTC \| Using server connection: Apex-Chicago Area-Non-Aggregated 2024-07-16 08:43:09.514 \| Rithmic Direct - DTC \| Connecting to the server rsc.rithmic.com. Port 50528 2024-07-16 08:43:10.803 \| DTC Client socket (2) \| Creating socket. Using TLS 1.2. 2024-07-16 08:43:10.803 \| DTC Client socket (2) \| New receive buffer size: 0 2024-07-16 08:43:10.803 \| DTC Client socket (2) \| Connecting to IP: 216.57.156.163. 2024-07-16 08:43:10.886 \| Rithmic Direct - DTC \| Network connection to server complete. 2024-07-16 08:43:10.886 \| Rithmic Direct - DTC \| Starting socket receive thread. 2024-07-16 08:43:10.887 \| Rithmic Direct - DTC \| Setting DTC encoding to Binary 2024-07-16 08:43:10.887 \| Rithmic Direct - DTC \| Sending logon request message. 2024-07-16 08:43:11.162 \| Rithmic Direct - DTC \| Received logon response. 2024-07-16 08:43:11.162 \| Rithmic Direct - DTC \| Server Name: . 2024-07-16 08:43:11.162 \| Rithmic Direct - DTC \| Server protocol version: 8. Client protocol version: 8 2024-07-16 08:43:11.162 \| Rithmic Direct - DTC \| Successfully connected. 2024-07-16 08:43:11.162 \| Rithmic Direct - DTC \| Trading is supported. 2024-07-16 08:43:11.162 \| Rithmic Direct - DTC \| Order cancel and replace is supported. 2024-07-16 08:43:11.162 \| Rithmic Direct - DTC \| OCO Orders supported. 2024-07-16 08:43:11.162 \| Rithmic Direct - DTC \| Symbol and Exchange Delimiter: . 2024-07-16 08:43:11.162 \| Rithmic Direct - DTC \| MarketDepthIsSupported: 0 2024-07-16 08:43:11.162 \| Rithmic Direct - DTC \| Connected to server complete. 2024-07-16 08:43:11.164 \| No download requests in the queue to start downloads for. \| Number times message added: 3 2024-07-16 08:43:11.199 \| Mapping ESU4.CME to ESU24. Service code: cme 2024-07-16 08:43:11.199 \| Using symbol data fast lookup vector 2024-07-16 08:43:11.199 \| Denali Data Feed \| Starting real-time market data updates for: ESU4.CME (ESU24). ID: 1 Service code: cme 2024-07-16 08:43:11.199 \| Denali Data Feed \| Connecting to the server ds32.sierracharts.com. Port 443 2024-07-16 08:43:11.199 \| Denali Data Feed \| Requesting security definition data for: ESU4.CME (ESU24). ID: 1 2024-07-16 08:43:11.199 \| Added historical Intraday data request for ESU4.CME to the queue. 2024-07-16 08:43:11.199 \| Intraday data recording state for symbol ESU4.CME is set to download 'Pending'. 2024-07-16 08:43:11.199 \| Triggering next historical data download in queue. 2024-07-16 08:43:11.208 \| DTC Client socket (3) \| Creating socket. 2024-07-16 08:43:11.208 \| DTC Client socket (3) \| New receive buffer size: 0 2024-07-16 08:43:11.208 \| DTC Client socket (3) \| Connecting to IP: 67.214.125.3. 2024-07-16 08:43:11.230 \| Delaying start of download for ESU4.CME. 2024-07-16 08:43:12.080 \| Mapping NQU4.CME to NQU24. Service code: cme 2024-07-16 08:43:12.080 \| Denali Data Feed \| Starting real-time market data updates for: NQU4.CME (NQU24). ID: 2 Service code: cme 2024-07-16 08:43:12.080 \| Denali Data Feed \| Requesting security definition data for: NQU4.CME (NQU24). ID: 2 2024-07-16 08:43:12.080 \| Added historical Intraday data request for NQU4.CME to the queue. 2024-07-16 08:43:12.080 \| Intraday data recording state for symbol NQU4.CME is set to download 'Pending'. 2024-07-16 08:43:12.080 \| Triggering next historical data download in queue. 2024-07-16 08:43:16.165 \| Requesting market depth updates for: ESU4.CME if supported. NumLevels=100 2024-07-16 08:43:22.954 \| HTTPS connection ID:23 to downloads.rithmic.com:443 for request ID:23 (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. * 2024-07-16 08:43:22.954 \| HTTPS connection ID:23 to downloads.rithmic.com:443 for request ID:23 (1) \| CloseSocket call. 2024-07-16 08:43:22.954 \| HTTPS connection ID:23 to downloads.rithmic.com:443 for request ID:23 (1) \| Closed. 2024-07-16 08:43:29.505 \| HTTPS connection ID:24 to downloads.rithmic.com:443 for request ID:24 (1) \| Creating socket. Using TLS 1.2. 2024-07-16 08:43:29.506 \| HTTPS connection ID:24 to downloads.rithmic.com:443 for request ID:24 (1) \| New receive buffer size: 0 2024-07-16 08:43:29.506 \| HTTPS connection ID:24 to downloads.rithmic.com:443 for request ID:24 (1) \| Connecting to IP: 216.66.0.130. 2024-07-16 08:43:31.212 \| Denali Data Feed \| Timeout connecting to server. 2024-07-16 08:43:31.212 \| DTC Client socket (3) \| CloseSocket call. 2024-07-16 08:43:31.212 \| Denali Data Feed \| Disconnected from the server. 2024-07-16 08:43:31.212 \| Denali Data Feed \| Data feed disconnected. Will reconnect in 3 seconds. 2024-07-16 08:43:31.212 \| DTC Client socket (3) \| Closed. 2024-07-16 08:43:34.226 \| Denali Data Feed \| Connecting to the server ds13.sierracharts.com. Port 443 2024-07-16 08:43:34.226 \| DTC Client socket (3) \| Creating socket. 2024-07-16 08:43:34.226 \| DTC Client socket (3) \| New receive buffer size: 0 2024-07-16 08:43:34.226 \| DTC Client socket (3) \| Connecting to IP: 64.158.105.202. 2024-07-16 08:43:34.252 \| Denali Data Feed \| Network connection to server complete. 2024-07-16 08:43:34.252 \| Denali Data Feed \| Starting socket receive thread. 2024-07-16 08:43:34.252 \| Denali Data Feed \| Sending encoding request to server: Binary VLS. Compression: standard 2024-07-16 08:43:34.276 \| Denali Data Feed \| Setting DTC encoding to Binary VLS 2024-07-16 08:43:34.276 \| Denali Data Feed \| Sending logon request message. 2024-07-16 08:43:34.308 \| Denali Data Feed \| Received logon response. 2024-07-16 08:43:34.308 \| Denali Data Feed \| Server Name: RealTimeServer. 2024-07-16 08:43:34.308 \| Denali Data Feed \| Server protocol version: 8. Client protocol version: 8 2024-07-16 08:43:34.308 \| Denali Data Feed \| Logon error received from server: Data service (sc_exchange2.datafeed) is disabled or unsupported. A software update may be necessary. 2024-07-16 08:43:34.308 \| Denali Data Feed \| Failed connections: 2 2024-07-16 08:43:34.308 \| Denali Data Feed \| Waiting for socket receive thread to end 2024-07-16 08:43:34.308 \| DTC Client socket (3) \| CloseSocket call. 2024-07-16 08:43:34.308 \| Denali Data Feed \| Disconnected from the server. 2024-07-16 08:43:34.308 \| Denali Data Feed \| Data feed disconnected. Will reconnect in 3 seconds. 2024-07-16 08:43:34.308 \| DTC Client socket (3) \| Shutdown started. Waiting for graceful close. 2024-07-16 08:43:34.326 \| DTC Client socket (3) \| Socket gracefully closed by remote side. 2024-07-16 08:43:34.327 \| DTC Client socket (3) \| Closed. 2024-07-16 08:43:37.300 \| Denali Data Feed \| Connecting to the server ds28-2.sierracharts.com. Port 10048 2024-07-16 08:43:37.300 \| DTC Client socket (3) \| Creating socket. 2024-07-16 08:43:37.300 \| DTC Client socket (3) \| New receive buffer size: 0 2024-07-16 08:43:37.300 \| DTC Client socket (3) \| Connecting to IP: 67.214.125.6. 2024-07-16 08:43:42.650 \| HD Request # 7 \| Downloading Intraday chart data for ESU4.CME to the file ESU4.CME.scid. Service: cme 2024-07-16 08:43:42.651 \| HD Request # 7 \| Download start date-time: 2024-07-16 06:49:02.000000. File last date-time: 2024-07-16 06:49:02.142001 2024-07-16 08:43:42.651 \| HD Request # 7 \| Using server: ds28.sierracharts.com port 10149 2024-07-16 08:43:42.651 \| Socket (4) \| Creating socket. 2024-07-16 08:43:42.651 \| Socket (4) \| New receive buffer size: 0 2024-07-16 08:43:42.651 \| Socket (4) \| Connecting to IP: 67.214.125.5. 2024-07-16 08:43:49.520 \| HTTPS connection ID:25 to downloads.rithmic.com:443 for request ID:25 (5) \| Creating socket. Using TLS 1.2. 2024-07-16 08:43:49.520 \| HTTPS connection ID:25 to downloads.rithmic.com:443 for request ID:25 (5) \| New receive buffer size: 0 2024-07-16 08:43:49.520 \| HTTPS connection ID:25 to downloads.rithmic.com:443 for request ID:25 (5) \| Connecting to IP: 216.66.0.130. 2024-07-16 08:43:50.549 \| HTTPS connection ID:24 to downloads.rithmic.com:443 for request ID:24 (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. * 2024-07-16 08:43:50.549 \| HTTPS connection ID:24 to downloads.rithmic.com:443 for request ID:24 (1) \| CloseSocket call. 2024-07-16 08:43:50.549 \| HTTPS connection ID:24 to downloads.rithmic.com:443 for request ID:24 (1) \| Closed. 2024-07-16 08:43:57.297 \| Denali Data Feed \| Timeout connecting to server. 2024-07-16 08:43:57.297 \| DTC Client socket (3) \| CloseSocket call. 2024-07-16 08:43:57.297 \| Denali Data Feed \| Disconnected from the server. 2024-07-16 08:43:57.297 \| Denali Data Feed \| Data feed disconnected. Will reconnect in 3 seconds. 2024-07-16 08:43:57.297 \| DTC Client socket (3) \| Closed. 2024-07-16 08:44:00.299 \| Denali Data Feed \| Connecting to the server ds26-2.sierracharts.com. Port 10048 2024-07-16 08:44:00.312 \| DTC Client socket (1) \| Creating socket. 2024-07-16 08:44:00.312 \| DTC Client socket (1) \| New receive buffer size: 0 2024-07-16 08:44:00.312 \| DTC Client socket (1) \| Connecting to IP: 67.214.125.12. 2024-07-16 08:44:02.650 \| Socket (4) \| CloseSocket call. 2024-07-16 08:44:02.650 \| HD Request # 7 \| Error downloading historical Intraday data for ESU4.CME. Timeout error connecting to server. 2024-07-16 08:44:02.650 \| Socket (4) \| Closed. 2024-07-16 08:44:02.650 \| Added historical Intraday data request for ESU4.CME to the queue. 2024-07-16 08:44:02.650 \| Triggering next historical data download in queue. 2024-07-16 08:44:02.650 \| Historical data download thread signaled to stop. 2024-07-16 08:44:02.651 \| HD Request # 7 \| Received 0 Intraday data records from 00:00:00.000000 to 00:00:00.000000 (0.0 seconds and wrote 0 records for ESU4.CME 2024-07-16 08:44:02.651 \| HD Request # 7 \| Completion time: 20s. 2024-07-16 08:44:02.651 \| 2024-07-16 08:44:02.651 \| HD Request # 8 \| Downloading Intraday chart data for ESU4.CME to the file ESU4.CME.scid. Service: cme 2024-07-16 08:44:02.652 \| HD Request # 8 \| Download start date-time: 2024-07-16 06:49:02.000000. File last date-time: 2024-07-16 06:49:02.142001 2024-07-16 08:44:02.652 \| HD Request # 8 \| Using server: ds32.sierracharts.com port 10150 2024-07-16 08:44:02.652 \| Socket (3) \| Creating socket. 2024-07-16 08:44:02.652 \| Socket (3) \| New receive buffer size: 0 2024-07-16 08:44:02.652 \| Socket (3) \| Connecting to IP: 67.214.125.3. 2024-07-16 08:44:09.515 \| HTTPS connection ID:26 to downloads.rithmic.com:443 for request ID:26 (4) \| Creating socket. Using TLS 1.2. 2024-07-16 08:44:09.515 \| HTTPS connection ID:26 to downloads.rithmic.com:443 for request ID:26 (4) \| New receive buffer size: 0 2024-07-16 08:44:09.515 \| HTTPS connection ID:26 to downloads.rithmic.com:443 for request ID:26 (4) \| Connecting to IP: 216.66.0.130. 2024-07-16 08:44:10.563 \| HTTPS connection ID:25 to downloads.rithmic.com:443 for request ID:25 (5) \| 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. * 2024-07-16 08:44:10.563 \| HTTPS connection ID:25 to downloads.rithmic.com:443 for request ID:25 (5) \| CloseSocket call. 2024-07-16 08:44:10.563 \| HTTPS connection ID:25 to downloads.rithmic.com:443 for request ID:25 (5) \| Closed. 2024-07-16 08:44:20.290 \| Denali Data Feed \| Timeout connecting to server. 2024-07-16 08:44:20.290 \| DTC Client socket (1) \| CloseSocket call. 2024-07-16 08:44:20.290 \| Denali Data Feed \| Disconnected from the server. 2024-07-16 08:44:20.290 \| Denali Data Feed \| Data feed disconnected. Will reconnect in 3 seconds. 2024-07-16 08:44:20.290 \| DTC Client socket (1) \| Closed. 2024-07-16 08:44:22.649 \| Socket (3) \| CloseSocket call. 2024-07-16 08:44:22.649 \| Socket (3) \| Closed. 2024-07-16 08:44:22.650 \| HD Request # 8 \| Error downloading historical Intraday data for ESU4.CME. Timeout error connecting to server. 2024-07-16 08:44:22.650 \| Added historical Intraday data request for ESU4.CME to the queue. 2024-07-16 08:44:22.650 \| Triggering next historical data download in queue. 2024-07-16 08:44:22.650 \| Historical data download thread signaled to stop. 2024-07-16 08:44:22.650 \| HD Request # 8 \| Received 0 Intraday data records from 00:00:00.000000 to 00:00:00.000000 (0.0 seconds and wrote 0 records for ESU4.CME 2024-07-16 08:44:22.650 \| HD Request # 8 \| Completion time: 20s. 2024-07-16 08:44:22.650 \| 2024-07-16 08:44:22.650 \| HD Request # 9 \| Downloading Intraday chart data for ESU4.CME to the file ESU4.CME.scid. Service: cme 2024-07-16 08:44:22.651 \| HD Request # 9 \| Download start date-time: 2024-07-16 06:49:02.000000. File last date-time: 2024-07-16 06:49:02.142001 2024-07-16 08:44:22.651 \| HD Request # 9 \| Using server: ds26.sierracharts.com port 10149 2024-07-16 08:44:22.651 \| Socket (1) \| Creating socket. 2024-07-16 08:44:22.651 \| Socket (1) \| New receive buffer size: 0 2024-07-16 08:44:22.651 \| Socket (1) \| Connecting to IP: 67.214.125.11. 2024-07-16 08:44:23.312 \| Denali Data Feed \| Connecting to the server ds25.sierracharts.com. Port 10048 2024-07-16 08:44:23.313 \| DTC Client socket (3) \| Creating socket. 2024-07-16 08:44:23.313 \| DTC Client socket (3) \| New receive buffer size: 0 2024-07-16 08:44:23.313 \| DTC Client socket (3) \| Connecting to IP: 67.214.125.8. 2024-07-16 08:44:29.522 \| HTTPS connection ID:27 to downloads.rithmic.com:443 for request ID:27 (5) \| Creating socket. Using TLS 1.2. 2024-07-16 08:44:29.522 \| HTTPS connection ID:27 to downloads.rithmic.com:443 for request ID:27 (5) \| New receive buffer size: 0 2024-07-16 08:44:29.522 \| HTTPS connection ID:27 to downloads.rithmic.com:443 for request ID:27 (5) \| Connecting to IP: 216.66.0.130. 2024-07-16 08:44:30.536 \| HTTPS connection ID:26 to downloads.rithmic.com:443 for request ID:26 (4) \| 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. * 2024-07-16 08:44:30.536 \| HTTPS connection ID:26 to downloads.rithmic.com:443 for request ID:26 (4) \| CloseSocket call. 2024-07-16 08:44:30.536 \| HTTPS connection ID:26 to downloads.rithmic.com:443 for request ID:26 (4) \| Closed. 2024-07-16 08:44:42.649 \| Socket (1) \| CloseSocket call. 2024-07-16 08:44:42.650 \| Socket (1) \| Closed. 2024-07-16 08:44:42.651 \| HD Request # 9 \| Error downloading historical Intraday data for ESU4.CME. Timeout error connecting to server. 2024-07-16 08:44:42.651 \| Historical data download thread signaled to stop. 2024-07-16 08:44:42.651 \| HD Request # 9 \| Received 0 Intraday data records from 00:00:00.000000 to 00:00:00.000000 (0.0 seconds and wrote 0 records for ESU4.CME 2024-07-16 08:44:42.651 \| HD Request # 9 \| Add time&sales data \| Remembered last file record date-time: 2024-07-16 13:49:02.142001 2024-07-16 08:44:42.651 \| HD Request # 9 \| Completion time: 20s. 2024-07-16 08:44:42.651 \| HD Request # 9 \| Intraday data download complete for ESU4.CME. Unique request ID: 3 2024-07-16 08:44:42.651 \| Removing historical data download ID 3. 2024-07-16 08:44:42.651 \| Real-time Intraday chart data file updates started for ESU4.CME 2024-07-16 08:44:42.651 \| Intraday chart data file opened for ESU4.CME 2024-07-16 08:44:42.651 \| HD Request # 9 \| Enabling Intraday chart updating for symbol. 2024-07-16 08:44:42.651 \| 2024-07-16 08:44:42.651 \| Triggering next historical data download in queue. 2024-07-16 08:44:42.652 \| HD Request # 10 \| Downloading Intraday chart data for NQU4.CME to the file NQU4.CME.scid. Service: cme 2024-07-16 08:44:42.652 \| HD Request # 10 \| Download start date-time: 2024-07-16 06:50:02.000000. File last date-time: 2024-07-16 06:50:02.766000 2024-07-16 08:44:42.652 \| HD Request # 10 \| Using server: ds28.sierracharts.com port 10150 2024-07-16 08:44:42.652 \| Socket (1) \| Creating socket. 2024-07-16 08:44:42.652 \| Socket (1) \| New receive buffer size: 0 2024-07-16 08:44:42.652 \| Socket (1) \| Connecting to IP: 67.214.125.5. 2024-07-16 08:44:42.775 \| Chart #2 has tagged chart #14 for full recalculation. Chartbook: ChartbookES.Cht 2024-07-16 08:44:42.775 \| Chart #2 has tagged chart #16 for full recalculation. Chartbook: ChartbookES.Cht 2024-07-16 08:44:42.775 \| Chart #2 has tagged chart #17 for full recalculation. Chartbook: ChartbookES.Cht 2024-07-16 08:44:42.775 \| Chart #2 has tagged chart #18 for full recalculation. Chartbook: ChartbookES.Cht 2024-07-16 08:44:42.775 \| Chart #2 has tagged chart #5 for full recalculation. Chartbook: ChartbookES.Cht 2024-07-16 08:44:42.802 \| ESU4.CME [CBV][M] 610 Trades #14 \| Performing a full recalculation because it has been tagged. Chartbook: ChartbookES.Cht 2024-07-16 08:44:43.122 \| ESU4.CME [CBV][M] 5 Min #17 \| Performing a full recalculation because it has been tagged. Chartbook: ChartbookES.Cht 2024-07-16 08:44:43.202 \| ESU4.CME [CBV][M] 60 Min #16 \| Performing a full recalculation because it has been tagged. Chartbook: ChartbookES.Cht 2024-07-16 08:44:43.332 \| Denali Data Feed \| Timeout connecting to server. 2024-07-16 08:44:43.332 \| DTC Client socket (3) \| CloseSocket call. 2024-07-16 08:44:43.332 \| Denali Data Feed \| Disconnected from the server. 2024-07-16 08:44:43.332 \| Denali Data Feed \| Data feed disconnected. Will reconnect in 3 seconds. 2024-07-16 08:44:43.332 \| DTC Client socket (3) \| Closed. 2024-07-16 08:44:43.391 \| ESU4.CME [CBV][M] 15 Min #5 \| Performing a full recalculation because it has been tagged. Chartbook: ChartbookES.Cht 2024-07-16 08:44:43.397 \| Chart #10 has tagged chart #2 for full recalculation. Chartbook: ChartbookES.Cht 2024-07-16 08:44:43.398 \| Chart #7 has tagged chart #2 for full recalculation. Chartbook: ChartbookES.Cht 2024-07-16 08:44:43.413 \| ESU4.CME [CBV][M] 5 Min #2 \| Performing a full recalculation because it has been tagged. Chartbook: ChartbookES.Cht 2024-07-16 08:44:43.436 \| Chart #2 has tagged chart #14 for full recalculation. Chartbook: ChartbookES.Cht 2024-07-16 08:44:43.436 \| Chart #2 has tagged chart #16 for full recalculation. Chartbook: ChartbookES.Cht 2024-07-16 08:44:43.436 \| Chart #2 has tagged chart #17 for full recalculation. Chartbook: ChartbookES.Cht 2024-07-16 08:44:43.436 \| Chart #2 has tagged chart #5 for full recalculation. Chartbook: ChartbookES.Cht 2024-07-16 08:44:43.465 \| ESU4.CME [CBV][M] 610 Trades #14 \| Performing a full recalculation because it has been tagged. Chartbook: ChartbookES.Cht 2024-07-16 08:44:43.988 \| ESU4.CME [CBV][M] 45 Min #18 \| Performing a full recalculation because it has been tagged. Chartbook: ChartbookES.Cht 2024-07-16 08:44:44.625 \| ESU4.CME [CBV][M] 5 Min #17 \| Performing a full recalculation because it has been tagged. Chartbook: ChartbookES.Cht 2024-07-16 08:44:44.700 \| ESU4.CME [CBV][M] 60 Min #16 \| Performing a full recalculation because it has been tagged. Chartbook: ChartbookES.Cht 2024-07-16 08:44:44.893 \| ESU4.CME [CBV][M] 15 Min #5 \| Performing a full recalculation because it has been tagged. Chartbook: ChartbookES.Cht 2024-07-16 08:44:46.331 \| Denali Data Feed \| Connecting to the server ds26.sierracharts.com. Port 10048 2024-07-16 08:44:46.331 \| DTC Client socket (3) \| Creating socket. 2024-07-16 08:44:46.331 \| DTC Client socket (3) \| New receive buffer size: 0 2024-07-16 08:44:46.331 \| DTC Client socket (3) \| Connecting to IP: 67.214.125.11. 2024-07-16 08:44:49.521 \| HTTPS connection ID:28 to downloads.rithmic.com:443 for request ID:28 (4) \| Creating socket. Using TLS 1.2. 2024-07-16 08:44:49.521 \| HTTPS connection ID:28 to downloads.rithmic.com:443 for request ID:28 (4) \| New receive buffer size: 0 2024-07-16 08:44:49.521 \| HTTPS connection ID:28 to downloads.rithmic.com:443 for request ID:28 (4) \| Connecting to IP: 216.66.0.130. 2024-07-16 08:44:50.560 \| HTTPS connection ID:27 to downloads.rithmic.com:443 for request ID:27 (5) \| 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. * 2024-07-16 08:44:50.560 \| HTTPS connection ID:27 to downloads.rithmic.com:443 for request ID:27 (5) \| CloseSocket call. 2024-07-16 08:44:50.560 \| HTTPS connection ID:27 to downloads.rithmic.com:443 for request ID:27 (5) \| Closed.

[2024-07-16 15:49:21] #27 [Go To First Post]
seandunaway - Posts: 266
it's weird because i'm able to ping the server and get a response.. i think the socket error is complaining that it has connectivity but the host is hanging or rejecting the connection. 2024-07-16 08:47:54.346 \| DTC Client socket (1) \| Connect event error. Windows error code 10061: No connection could be made because the target machine actively refused it. *


screenshot 2024-07-16 at 08.48.59.png / V - Attached On 2024-07-16 15:49:16 UTC - Size: 1003.58 KB - 49 views

[2024-07-16 15:53:02] #28 [Go To First Post]
FT63 - Posts: 17
This is message log with Data Feed disconnected. For whatever reason Sierra Charts is still trying to connect to rithmic. 2024-07-16 11:50:37.183 \| Software version: 2657 64-bit 2024-07-16 11:50:37.183 \| Primary Thread ID: 17192 2024-07-16 11:50:37.183 \| Usage end date: 2024-08-25 2024-07-16 11:50:37.183 \| Enabled for: Sierra Chart Historical Data Service. 2024-07-16 11:50:37.183 \| Enabled for: Denali Real-Time Exchange Data Feed. 2024-07-16 11:50:37.183 \| Enabled for: Delayed Denali Exchange Data Feed. 2024-07-16 11:50:37.183 \| Enabled for exchange2: CME (Trading Account Required) 2024-07-16 11:50:37.183 \| Enabled for exchange2: CBOT (Trading Account Required) 2024-07-16 11:50:37.183 \| Enabled for exchange2: COMEX (Trading Account Required) 2024-07-16 11:50:37.183 \| Enabled for exchange2: NYMEX (Trading Account Required) 2024-07-16 11:50:37.183 \| Allow Support for Sierra Chart Data Feeds is enabled. 2024-07-16 11:50:37.183 \| Current selected Data/Trading service: Rithmic Direct - DTC 2024-07-16 11:50:37.183 \| Custom symbol settings values: enabled 2024-07-16 11:50:37.183 \| Chart Update Interval: 500 2024-07-16 11:50:37.183 \| Intraday Data Storage Time Unit: 0 2024-07-16 11:50:37.183 \| Time Zone: -04:00:00 (EST-05EDT+01,M3.2.0/02:00,M11.1.0/02:00) 2024-07-16 11:50:37.183 \| 2024-07-16 15:50:37 Local computer time in UTC 2024-07-16 11:50:37.183 \| 2024-07-16 11:50:37 Local computer time in SC Time Zone 2024-07-16 11:50:37.183 \| 2024-07-16 15:47:50 Server time in UTC 2024-07-16 11:50:37.183 \| Local computer UTC time and Server UTC time difference: 0 seconds. 2024-07-16 11:50:37.183 \| Program path: C:\SierraChart.RIM\ 2024-07-16 11:50:37.183 \| Data Files path: C:\SierraChart.RIM\Data\ 2024-07-16 11:50:37.184 \| OS Version Number: 10.0 2024-07-16 11:50:37.184 \| Locale Setting: C 2024-07-16 11:50:37.184 \| DLLs: ipAskBidVolumeDiffBars_64.dll, ipAutomatedTrading_64.dll, ipModifiedSCStudies_64.dll, sst_FreeBundle_64.dll, UserContributedStudies.dll, UserContributedStudies_64.dll 2024-07-16 11:50:37.184 \| Allowed protected custom studies: SST_FreeBundle 2024-07-16 11:50:37.184 \| Crash reporter started: true 2024-07-16 11:50:37.184 \| 2024-07-16 11:50:41.122 \| HTTPS connection ID:6 to downloads.rithmic.com:443 for request ID:6 (2) \| Creating socket. Using TLS 1.2. 2024-07-16 11:50:41.122 \| HTTPS connection ID:6 to downloads.rithmic.com:443 for request ID:6 (2) \| New receive buffer size: 0 2024-07-16 11:50:41.122 \| HTTPS connection ID:6 to downloads.rithmic.com:443 for request ID:6 (2) \| Connecting to IP: 208.91.197.27. 2024-07-16 11:50:43.316 \| HTTPS connection ID:6 to downloads.rithmic.com:443 for request ID:6 (2) \| Connect event error. Windows error code 10061: No connection could be made because the target machine actively refused it. * 2024-07-16 11:50:43.316 \| HTTPS connection ID:6 to downloads.rithmic.com:443 for request ID:6 (2) \| CloseSocket call. 2024-07-16 11:50:43.316 \| Rithmic Direct - DTC \| HTTP response receiving connection points not completed or OK. 2024-07-16 11:50:43.316 \| HTTPS connection ID:6 to downloads.rithmic.com:443 for request ID:6 (2) \| Closed. 2024-07-16 11:51:01.123 \| HTTPS connection ID:7 to downloads.rithmic.com:443 for request ID:7 (2) \| Creating socket. Using TLS 1.2. 2024-07-16 11:51:01.123 \| HTTPS connection ID:7 to downloads.rithmic.com:443 for request ID:7 (2) \| New receive buffer size: 0 2024-07-16 11:51:01.123 \| HTTPS connection ID:7 to downloads.rithmic.com:443 for request ID:7 (2) \| Connecting to IP: 208.91.197.27. 2024-07-16 11:51:07.040 \| HTTPS connection ID:5 to downloads.rithmic.com:443 for request ID:5 (1) \| Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine. * 2024-07-16 11:51:07.040 \| HTTPS connection ID:5 to downloads.rithmic.com:443 for request ID:5 (1) \| Socket gracefully closed by remote side. 2024-07-16 11:51:07.040 \| HTTPS connection ID:5 to downloads.rithmic.com:443 for request ID:5 (1) \| CloseSocket call. 2024-07-16 11:51:07.040 \| HTTPS connection ID:5 to downloads.rithmic.com:443 for request ID:5 (1) \| Graceful close received or receive error. Shutdown complete. Closing socket now. 2024-07-16 11:51:07.040 \| HTTPS connection ID:5 to downloads.rithmic.com:443 for request ID:5 (1) \| Closed. 2024-07-16 11:51:13.453 \| Rithmic Direct - DTC \| Wrote file: C:\SierraChart.RIM\RithmicConnections.json. Size: 2622 2024-07-16 11:51:13.453 \| Rithmic Direct - DTC \| JSON connection points parse error: Invalid value. * 2024-07-16 11:51:13.710 \| HTTPS connection ID:7 to downloads.rithmic.com:443 for request ID:7 (2) \| CloseSocket call. 2024-07-16 11:51:13.711 \| HTTPS connection ID:7 to downloads.rithmic.com:443 for request ID:7 (2) \| Shutdown started. Waiting for graceful close. 2024-07-16 11:51:13.742 \| HTTPS connection ID:7 to downloads.rithmic.com:443 for request ID:7 (2) \| Socket gracefully closed by remote side. 2024-07-16 11:51:13.742 \| HTTPS connection ID:7 to downloads.rithmic.com:443 for request ID:7 (2) \| Closed. 2024-07-16 11:51:21.128 \| HTTPS connection ID:8 to downloads.rithmic.com:443 for request ID:8 (1) \| Creating socket. Using TLS 1.2. 2024-07-16 11:51:21.129 \| HTTPS connection ID:8 to downloads.rithmic.com:443 for request ID:8 (1) \| New receive buffer size: 0 2024-07-16 11:51:21.129 \| HTTPS connection ID:8 to downloads.rithmic.com:443 for request ID:8 (1) \| Connecting to IP: 208.91.197.27.

[2024-07-16 15:54:13] #29 [Go To First Post]
allons_trading - Posts: 27
West Coast - Oregon. SC 2655 running on Linux, 3 instances. Instance 1 - Denali/Teton to Stage5 Instance 2 - Denali/Rithmic Instance 3 - Rithmic/Rithmic I've had no connections issues this morning and have seen no disconnects from any of the running instances.

[2024-07-16 15:57:05] #30 [Go To First Post]
Sierra_Chart Engineering - Posts: 16387
One thing we are observing, for the users who are affected is that you are also having problems connecting to the Rithmic Web server. We have no problems connecting to the Rithmic Web server. And this seems to be related to users on the West Coast of the US. So the user in Ontario, we do not know why you are having a problem but you are. There is some connectivity problems going on on the Internet and these are out of our control but we are going to contact the data center, and see what they know or can help with. 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

[2024-07-16 15:58:28] #31 [Go To First Post]
anthonyvegas - Posts: 12
I am also not getting any live data feed from Denali/Teton this morning as of about an hour ago.... I am not using Rithmic, I am using CQG for order routing, and Denali/Tetot for data feed. I'm located in Las Vegas. Date Time Of Last Edit: 2024-07-16 16:00:00

[2024-07-16 16:03:31] #32 [Go To First Post]
User460919 - Posts: 2
Same boat here. I'm in NV as well. Date Time Of Last Edit: 2024-07-16 16:11:34

[2024-07-16 16:06:32] #33 [Go To First Post]
FT63 - Posts: 17
I was able to connect to Rithmic after I used VPN and switch my location to Chicago. Date Time Of Last Edit: 2024-07-16 16:08:04

[2024-07-16 16:07:20] #34 [Go To First Post]
Sierra_Chart Engineering - Posts: 16387
This is clearly a connectivity issue predominantly in the Nevada California area. We have posted information here: Notice: Internet Connectivity Issues for Some Users Affecting Rithmic/Denali Data We are looking into it. 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: 2024-07-16 16:07:54

[2024-07-16 16:12:58] #35 [Go To First Post]
seandunaway - Posts: 266
tracert


tracert.png / V - Attached On 2024-07-16 16:12:52 UTC - Size: 53.69 KB - 39 views

[2024-07-16 16:17:08] #36 [Go To First Post]
Sierra_Chart Engineering - Posts: 16387
That trace route makes no sense at all. It just simply shows one single hop/connection direct to the server. Obviously the connectivity is not going to go anywhere. That is the problem. There is a routing issue. 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

[2024-07-16 16:25:37] #37 [Go To First Post]
User936941 - Posts: 20
Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved. Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows PS C:\Users\James> tracert ds28.sierracharts.com Tracing route to ds28.sierracharts.com [67.214.125.5] over a maximum of 30 hops: 1 6 ms 8 ms 10 ms 192.168.4.1 2 8 ms 6 ms 6 ms conr-cor2-ge1-9.consolidated.net [207.70.185.229] 3 14 ms * 12 ms 209.34.20.125 4 13 ms 14 ms 13 ms 209.34.53.221 5 14 ms 14 ms 13 ms 209.34.53.244 6 * * 12 ms 209.34.53.93 7 * * * Request timed out. 8 165 ms 14 ms 15 ms be2664.ccr31.dfw01.atlas.cogentco.com [154.54.41.201] 9 88 ms 178 ms 21 ms be2432.ccr21.mci01.atlas.cogentco.com [154.54.3.134] 10 225 ms 33 ms 73 ms be2831.ccr41.ord01.atlas.cogentco.com [154.54.42.166] 11 71 ms 43 ms 39 ms be2717.ccr21.cle04.atlas.cogentco.com [154.54.6.222] 12 42 ms 40 ms 41 ms be3744.rcr51.tol01.atlas.cogentco.com [154.54.0.146] 13 43 ms 46 ms 46 ms be2123.rcr21.dtw04.atlas.cogentco.com [154.54.82.138] 14 46 ms 50 ms 45 ms gi0-0-0-18.204.nr11.b015471-1.dtw04.atlas.cogentco.com [38.122.60.13] 15 50 ms 43 ms 46 ms 67.214.125.193 16 43 ms 46 ms 44 ms 67.214.125.5 Trace complete. PS C:\Users\James> From Houston, Tx

[2024-07-16 16:27:43] #38 [Go To First Post]
User253985 - Posts: 23
File attached


Trace.JPG / V - Attached On 2024-07-16 16:27:06 UTC - Size: 65.9 KB - 26 views

[2024-07-16 16:28:28] #39 [Go To First Post]
seandunaway - Posts: 266
i just assumed that was the crummy summary output of windows11's tracert.. traditional traceroute: % traceroute -m30 ds28.sierracharts.com traceroute to ds28.sierracharts.com (67.214.125.5), 30 hops max, 52 byte packets 1 192.168.0.1 (192.168.0.1) 10.235 ms 3.531 ms 3.054 ms 2 10.75.0.1 (10.75.0.1) 13.725 ms 15.152 ms 21.338 ms 3 100.127.5.94 (100.127.5.94) 19.356 ms 13.465 ms 12.927 ms 4 100.120.102.34 (100.120.102.34) 12.901 ms 13.120 ms 12.315 ms 5 sanjbprj01-ae1.rd.sj.cox.net (68.1.1.225) 28.220 ms 31.453 ms 27.355 ms 6 * * port-channel5.core3.sjc2.he.net (66.220.12.165) 36.328 ms 7 * * * 8 * * * 9 100ge0-79.core1.stl1.he.net (184.104.188.81) 67.066 ms 59.963 ms 59.710 ms 10 port-channel4.core2.ind1.he.net (184.104.196.50) 66.131 ms * * 11 port-channel6.core2.det1.he.net (184.105.81.165) 74.876 ms 76.427 ms 72.744 ms 12 123-net-inc.10gigabitethernet0-3.core2.det1.he.net (184.105.48.202) 78.541 ms 78.188 ms 81.697 ms 13 67.214.125.193 (67.214.125.193) 94.008 ms 77.120 ms 79.702 ms 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * % edit: oh i know why.. my windows machine is being virtualized with some sort of bridged networking Date Time Of Last Edit: 2024-07-16 16:29:19

[2024-07-16 16:34:41] #40 [Go To First Post]
seandunaway - Posts: 266
if i probe with ICMP instead of UDP i can reach the route % traceroute -m30 -P icmp ds28.sierracharts.com traceroute to ds28.sierracharts.com (67.214.125.5), 30 hops max, 72 byte packets 1 192.168.0.1 (192.168.0.1) 10.728 ms 3.309 ms 2.368 ms 2 10.75.0.1 (10.75.0.1) 16.526 ms 12.565 ms 12.778 ms 3 100.127.5.94 (100.127.5.94) 14.737 ms 11.897 ms 13.819 ms 4 100.120.102.34 (100.120.102.34) 12.737 ms 12.025 ms 12.268 ms 5 sanjbprj01-ae1.rd.sj.cox.net (68.1.1.225) 29.244 ms 27.395 ms 28.855 ms 6 * * * 7 * port-channel12.core2.den1.he.net (184.104.195.213) 61.497 ms * 8 * * port-channel2.core3.mci3.he.net (184.104.198.34) 55.181 ms 9 100ge0-79.core1.stl1.he.net (184.104.188.81) 60.918 ms 59.304 ms 58.407 ms 10 port-channel4.core2.ind1.he.net (184.104.196.50) 64.636 ms * * 11 port-channel6.core2.det1.he.net (184.105.81.165) 81.082 ms 72.514 ms 70.808 ms 12 123-net-inc.10gigabitethernet0-3.core2.det1.he.net (184.105.48.202) 77.946 ms 80.052 ms 77.733 ms 13 67.214.125.193 (67.214.125.193) 78.181 ms 78.521 ms 78.398 ms 14 67.214.125.5 (67.214.125.5) 78.129 ms 79.733 ms 78.424 ms %

[2024-07-16 16:37:48] #41 [Go To First Post]
raheemrazzak - Posts: 41
Tracing route to ds28.sierracharts.com [67.214.125.5] over a maximum of 30 hops: 1 9 ms 4 ms 2 ms 192.168.0.1 2 11 ms 4 ms 6 ms ip70-170-76-1.lv.lv.cox.net [70.170.76.1] 3 6 ms 7 ms 6 ms 184.185.67.1 4 10 ms 9 ms 15 ms 172.28.239.208 5 7 ms 5 ms 5 ms 100.120.103.176 6 4 ms 5 ms 5 ms 100.120.102.40 7 37 ms 19 ms 20 ms sanjbprj01-ae1.rd.sj.cox.net [68.1.1.225] 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * 54 ms 51 ms 100ge0-79.core1.stl1.he.net [184.104.188.81] 12 * * * Request timed out. 13 66 ms 62 ms 62 ms port-channel6.core2.det1.he.net [184.105.81.165] 14 72 ms 72 ms 91 ms 123-net-inc.10gigabitethernet0-3.core2.det1.he.net [184.105.48.202] 15 75 ms 67 ms 70 ms 67.214.125.193 16 72 ms 70 ms 69 ms 67.214.125.5 Trace complete.

[2024-07-16 16:39:20] #42 [Go To First Post]
Sierra_Chart Engineering - Posts: 16387
Ok thank you. We have sent one of these trace routes to the ISP. 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

[2024-07-16 16:46:07] #43 [Go To First Post]
User253985 - Posts: 23
No connection to data - Reconnect Wait \| Post: 388708 I used a VPN and set it to USA and it looks like it works now Date Time Of Last Edit: 2024-07-16 16:48:02

[2024-07-16 16:52:18] #44 [Go To First Post]
Retlo - Posts: 1
Also in Las Vegas, everything worked until 7:03 PST when charts and DOM stopped. No connection since. Using Teton, Denali, broker is Dorman. 2024-07-16 16:47:16.641 \| HD Request # 17 \| Downloading Intraday chart data for ESU24_FUT_CME to the file ESU24_FUT_CME.scid. Service: cme 2024-07-16 16:47:16.642 \| HD Request # 17 \| Download start date-time: 2024-07-16 07:03:02.000000. File last date-time: 2024-07-16 07:03:02.713000 2024-07-16 16:47:16.642 \| HD Request # 17 \| Using server: ds32.sierracharts.com port 10149 2024-07-16 16:47:16.642 \| Socket (2) \| Creating socket. 2024-07-16 16:47:16.643 \| Socket (2) \| New receive buffer size: 0 2024-07-16 16:47:16.643 \| Socket (2) \| Connecting to IP: 67.214.125.3. 2024-07-16 16:47:18.316 \| DTC Client 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. 2024-07-16 16:47:18.316 \| DTC Client socket (3) \| CloseSocket call. 2024-07-16 16:47:18.316 \| Denali Data Feed \| Failed connections: 21 2024-07-16 16:47:18.316 \| DTC Client socket (0) \| CloseSocket call. 2024-07-16 16:47:18.316 \| Denali Data Feed \| Disconnected from the server. 2024-07-16 16:47:18.316 \| DTC Client socket (3) \| Closed. 2024-07-16 16:47:18.316 \| Denali Data Feed \| Data feed disconnected. Will reconnect in 2 seconds. 2024-07-16 16:47:20.319 \| Denali Data Feed \| Connecting to the server ds32-2.sierracharts.com. Port 443 2024-07-16 16:47:20.321 \| DTC Client socket (3) \| Creating socket. 2024-07-16 16:47:20.321 \| DTC Client socket (3) \| New receive buffer size: 0 2024-07-16 16:47:20.321 \| DTC Client socket (3) \| Connecting to IP: 67.214.125.4. 2024-07-16 16:47:22.639 \| File >> Disconnect selected. 2024-07-16 16:47:22.643 \| Teton CME Order Routing \| Waiting for socket receive thread to end 2024-07-16 16:47:22.643 \| DTC Client socket (1) \| CloseSocket call. 2024-07-16 16:47:22.643 \| DTC Client socket (1) \| Max send buffers used during socket life: 3 2024-07-16 16:47:22.643 \| DTC Client socket (1) \| Max send buffer size during socket life: 329 2024-07-16 16:47:22.643 \| DTC Client socket (1) \| Shutdown started. Waiting for graceful close. 2024-07-16 16:47:22.643 \| DTC Client socket (3) \| CloseSocket call. 2024-07-16 16:47:22.643 \| Denali Data Feed \| Disconnected from the server. 2024-07-16 16:47:22.643 \| Teton CME Order Routing \| Disconnected. 2024-07-16 16:47:22.643 \| HD Request # 17 \| Active download canceled. 2024-07-16 16:47:22.643 \| DTC Client socket (3) \| Closed. 2024-07-16 16:47:22.643 \| Historical data download thread signaled to stop. 2024-07-16 16:47:22.643 \| Socket (2) \| CloseSocket call. 2024-07-16 16:47:22.643 \| HD Request # 17 \| Received 0 Intraday data records from 00:00:00.000000 to 00:00:00.000000 (0.0 seconds and wrote 0 records for ESU24_FUT_CME 2024-07-16 16:47:22.643 \| Socket (2) \| Closed. 2024-07-16 16:47:22.643 \| HD Request # 17 \| Completion time: 6s. 2024-07-16 16:47:22.643 \| HD Request # 17 \| Intraday data download complete for ESU24_FUT_CME. Unique request ID: 6 2024-07-16 16:47:22.643 \| Removing historical data download ID 6. 2024-07-16 16:47:22.643 \| Real-time Intraday chart data file updates started for ESU24_FUT_CME 2024-07-16 16:47:22.643 \| Intraday chart data file opened for ESU24_FUT_CME 2024-07-16 16:47:22.643 \| HD Request # 17 \| Enabling Intraday chart updating for symbol. 2024-07-16 16:47:22.643 \| No download requests in the queue to start downloads for. 2024-07-16 16:47:22.694 \| DTC Client socket (1) \| Socket gracefully closed by remote side. 2024-07-16 16:47:22.694 \| DTC Client socket (1) \| Closed.

[2024-07-16 17:00:01] #45 [Go To First Post]
User301641 - Posts: 14
From Houston, Texas Can't connect to Rithmic since morning Tracing route to ds28.sierracharts.com [67.214.125.5] over a maximum of 30 hops: 1 3 ms 1 ms 16 ms 192.168.40.1 2 3 ms 3 ms 2 ms conr-cor2-ge1-14.consolidated.net [207.70.185.213] 3 13 ms 14 ms 13 ms 207.70.187.190 4 12 ms * * conrtxxahr8-207-70-186-120.consolidated.net [207.70.186.120] 5 15 ms * 13 ms dllstxldhre-207-70-186-60.consolidated.net [207.70.186.60] 6 * * 14 ms 209.34.53.238 7 15 ms 15 ms 13 ms 209.34.53.233 8 15 ms 14 ms 15 ms 209.34.53.242 9 * * 16 ms 209.34.53.95 10 * * * Request timed out. 11 15 ms 14 ms 13 ms be2664.ccr31.dfw01.atlas.cogentco.com [154.54.41.201] 12 24 ms 28 ms 23 ms be2432.ccr21.mci01.atlas.cogentco.com [154.54.3.134] 13 35 ms 34 ms 35 ms be2831.ccr41.ord01.atlas.cogentco.com [154.54.42.166] 14 42 ms 41 ms 42 ms be2717.ccr21.cle04.atlas.cogentco.com [154.54.6.222] 15 47 ms 44 ms 43 ms be3744.rcr51.tol01.atlas.cogentco.com [154.54.0.146] 16 45 ms 45 ms 45 ms be2123.rcr21.dtw04.atlas.cogentco.com [154.54.82.138] 17 43 ms 42 ms 41 ms gi0-0-0-18.204.nr11.b015471-1.dtw04.atlas.cogentco.com [38.122.60.13] 18 43 ms 42 ms 41 ms 67.214.125.193 Date Time Of Last Edit: 2024-07-16 17:00:44

[2024-07-16 17:02:10] #46 [Go To First Post]
Sierra_Chart Engineering - Posts: 16387
For the solution refer to post #4 here: Notice: Internet Connectivity Issues for Some Users Affecting Rithmic/Denali Data 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: 2024-07-16 17:02:26

[2024-07-16 17:40:24] #47 [Go To First Post]
User936941 - Posts: 20
@User301641 I am also in Houston. Any luck yet with rithmic? I have the same issue.

[2024-07-16 17:57:22] #48 [Go To First Post]
John - SC Support - Posts: 34456
You need to check with Rithmic as to when they will have this resolved. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing

[2024-07-16 19:17:23] #49 [Go To First Post]
User214239 - Posts: 26
I'm in San Diego, CA and haven't been able to connect to rithmic since yesterday. I've updated to the latest sierra. I have a sub instance that seems to have connected to Denali I guess because the box is green, but the charts don't update and the main instance has the yellow Reconnect wait issue. Posting the trace info just in case it helps. I've sent an email to rithmic, but I'm not expecting a reply anytime soon. I realize this is a rithmic issue and not a sierra issue but I appreciate any help as I'm guessing they might pay more attention to your emails than mine. Please let me know if you need any other info. Thank you. Tracing route to ds28.sierracharts.com [67.214.125.5] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms dsldevice.attlocal.net [192.168.1.254] 2 3 ms 4 ms 2 ms 107-217-8-1.lightspeed.sndgca.sbcglobal.net [107.217.8.1] 3 2 ms 2 ms 4 ms 71.157.16.98 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 18 ms 9 ms 15 ms 32.130.25.175 8 15 ms 9 ms 7 ms ggr2.la2ca.ip.att.net [12.122.129.105] 9 13 ms 5 ms 7 ms ae7.mpr1.lax12.us.zip.zayo.com [64.125.12.153] 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 69 ms 62 ms 63 ms ae9.mpr1.cle2.us.zip.zayo.com [64.125.22.1] 15 74 ms 69 ms 67 ms ae11.mpr2.dtw3.us.zip.zayo.com [64.125.24.227] 16 64 ms 57 ms 59 ms 64.124.32.66.IDIA-385104-ZYO.zip.zayo.com [64.124.32.66] 17 63 ms 57 ms 55 ms 67.214.125.193 18 57 ms 60 ms 58 ms 67.214.125.5 Trace complete. Date Time Of Last Edit: 2024-07-16 19:18:45

[2024-07-16 19:29:29] #50 [Go To First Post]
Sierra_Chart Engineering - Posts: 16387
Regarding post #49, so we can understand what the current issue is follow the instructions below: Follow the instructions here to clear the Message Log: Message Log: Clearing the Message Log Connect to the data feed: Select "File >> Disconnect" Select "File >> Connect to Data Feed" After about 30 seconds, provide a copy of the Message Log following these instructions: Support Board Posting Information: How to Post Your Message Log (Required In Some Cases) We will then determine what the problem is. ---- To at least get the charts to update, follow the instructions below : To access historical and streaming market data independent from your Trading service. Follow these instructions. Set "Global Settings >> Data/Trade Service Settings >> Current Selected Service" to "SC Data-All Services". Press "OK" And then translate the symbols in your Chartbooks and Sierra Chart using this "Edit' menu command: Edit Menu: Edit >> Translate Symbols To Current Service (Translate Symbols to Current Service) You can then use the data provided by Sierra Chart independent of your trading service. 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: 2024-07-16 19:30:07

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