Support Board
Date/Time: Thu, 16 Jan 2025 08:53:24 +0000
SC Historical Data
View Count: 909
| [2017-10-25 08:01:51] |
| User630996 - Posts: 25 |
|
Is this problem on your side or mine? Reading Internal Order ID file. | 2017-10-25 09:55:15 Reading Trade Orders file. | 2017-10-25 09:55:15 Reading Trade Positions file. | 2017-10-25 09:55:15 Listening on UDP port 22903. | 2017-10-25 09:55:15 Software version: 1617 | 2017-10-25 09:55:15 Enabled for: Advanced Features. | 2017-10-25 09:55:15 Enabled for: Sierra Chart Historical Data Service. | 2017-10-25 09:55:15 Allow Support for Sierra Chart Data Feeds is enabled. | 2017-10-25 09:55:15 Current selected Data/Trading service: Rithmic Trading | 2017-10-25 09:55:15 Chart Update Interval: 100 | 2017-10-25 09:55:15 Data/Trade Service Settings automatically set. | 2017-10-25 09:55:15 Time Zone: +02:00:00 (SAST+02) | 2017-10-25 09:55:15 2017-10-25 09:55:20 Local computer time | 2017-10-25 09:55:15 2017-10-25 07:55:20 Local computer time in UTC | 2017-10-25 09:55:15 2017-10-25 09:55:20 Local computer time in SC Time Zone | 2017-10-25 09:55:15 2017-10-25 07:55:19 Server time in UTC | 2017-10-25 09:55:15 Local computer UTC time and Server UTC time difference: 0 seconds. | 2017-10-25 09:55:15 Program path: C:\SierraChartTrading\ | 2017-10-25 09:55:15 Data Files path: C:\SierraChartTrading\Data\ | 2017-10-25 09:55:15 OS Version Number: 6.1 | 2017-10-25 09:55:15 Locale Setting: C | 2017-10-25 09:55:15 Created the DTC Protocol server. | 2017-10-25 09:55:15 DTC Protocol Server listening on port 11099. | 2017-10-25 09:55:15 Created the DTC Protocol historical data server. | 2017-10-25 09:55:15 HD Server Manager | Listening on port 11098 | 2017-10-25 09:55:15 Checking for new symbol settings for service code rim | 2017-10-25 09:55:15 HTTPS connection to www.sierrachart.com:443 (4) | Creating socket. Using TLS 1.2. | 2017-10-25 09:55:15 HTTPS connection to www.sierrachart.com:443 (4) | Connecting to IP: 204.15.192.108. | 2017-10-25 09:55:15 Received 5 login tokens. | 2017-10-25 09:55:21 Symbol settings are up-to-date for rim | 2017-10-25 09:55:21 HTTPS connection to www.sierrachart.com:443 (5) | Creating socket. Using TLS 1.2. | 2017-10-25 09:55:22 HTTPS connection to www.sierrachart.com:443 (5) | Connecting to IP: 204.15.192.108. | 2017-10-25 09:55:22 Rithmic Trading | Port for executable: 50724 | 2017-10-25 09:55:24 Listening socket (884). Port 50724 | Closed. | 2017-10-25 09:55:24 Rithmic Trading | Starting server: C:\SierraChartTrading\Rim\DTCBridge.exe | 2017-10-25 09:55:24 Rithmic Trading | Bridge process is running. | 2017-10-25 09:55:26 Rithmic Trading | Connecting to the server 127.0.0.1. Port 50724 | 2017-10-25 09:55:26 DTC Client socket (6) | Creating socket. | 2017-10-25 09:55:26 DTC Client socket (6) | Connecting to IP: 127.0.0.1. | 2017-10-25 09:55:26 Rithmic Trading | Connected to server. | 2017-10-25 09:55:26 Rithmic Trading | Starting socket receive thread. | 2017-10-25 09:55:26 Rithmic Trading | Sending Encoding Request to server | 2017-10-25 09:55:26 Rithmic Trading | Setting DTC encoding to Binary VLS | 2017-10-25 09:55:26 Rithmic Trading | Sending logon request message. | 2017-10-25 09:55:26 Rithmic Trading | Message from server: Starting the connection process to data and trading service. | 2017-10-25 09:55:26 Rithmic Trading | Message from server: Logging is enabled. Log file: C:\SierraChartTrading\Rim\Rithmic.log | 2017-10-25 09:55:26 Rithmic Trading | Message from server: Connecting to Rithmic 01 US server. | 2017-10-25 09:55:26 HTTPS connection to www.sierrachart.com:443 (2) | Socket gracefully closed by remote side. | 2017-10-25 09:55:27 HTTPS connection to www.sierrachart.com:443 (2) | Received socket Close event. | 2017-10-25 09:55:27 HTTPS connection to www.sierrachart.com:443 (2) | Initiating close of socket by core. | 2017-10-25 09:55:27 HTTPS connection to www.sierrachart.com:443 (2) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2017-10-25 09:55:27 HTTPS connection to www.sierrachart.com:443 (2) | Closed. | 2017-10-25 09:55:27 HTTPS connection to www.sierrachart.com:443 (4) | Socket gracefully closed by remote side. | 2017-10-25 09:55:27 HTTPS connection to www.sierrachart.com:443 (4) | Received socket Close event. | 2017-10-25 09:55:27 HTTPS connection to www.sierrachart.com:443 (4) | Initiating close of socket by core. | 2017-10-25 09:55:27 HTTPS connection to www.sierrachart.com:443 (4) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2017-10-25 09:55:27 HTTPS connection to www.sierrachart.com:443 (4) | Closed. | 2017-10-25 09:55:27 HTTPS connection to www.sierrachart.com:443 (5) | Socket gracefully closed by remote side. | 2017-10-25 09:55:29 HTTPS connection to www.sierrachart.com:443 (5) | Received socket Close event. | 2017-10-25 09:55:29 HTTPS connection to www.sierrachart.com:443 (5) | Initiating close of socket by core. | 2017-10-25 09:55:29 HTTPS connection to www.sierrachart.com:443 (5) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2017-10-25 09:55:29 HTTPS connection to www.sierrachart.com:443 (5) | Closed. | 2017-10-25 09:55:29 Rithmic Trading | Message from server: Server Alert: Market Data Connection Opened | 2017-10-25 09:55:29 Rithmic Trading | Message from server: Server Alert: Market Data Connection Login Complete. Result text: "ok" | 2017-10-25 09:55:29 Rithmic Trading | Message from server: Server Alert: Trading System Connection Opened | 2017-10-25 09:55:31 Rithmic Trading | Message from server: Server Alert: Trading System Connection Login Complete. Result text: "ok" | 2017-10-25 09:55:31 Rithmic Trading | Message from server: Server Alert: PnL Connection Opened | 2017-10-25 09:55:33 Rithmic Trading | Message from server: Server Alert: PnL Connection Login Complete. Result text: "ok" | 2017-10-25 09:55:33 Rithmic Trading | Message from server: Server Alert: Intraday History Connection Opened | 2017-10-25 09:55:35 Rithmic Trading | Message from server: Server Alert: Intraday History Connection Login Complete. Result text: "ok" | 2017-10-25 09:55:35 Rithmic Trading | Received logon response. | 2017-10-25 09:55:36 Rithmic Trading | Server Name: SC DTC Bridge. | 2017-10-25 09:55:36 Rithmic Trading | Server protocol version: 8. Client protocol version: 8 | 2017-10-25 09:55:36 Rithmic Trading | Successfully connected. IB='AMP', Firm='AMPClearing'. | 2017-10-25 09:55:36 Rithmic Trading | Trading is supported. | 2017-10-25 09:55:36 Rithmic Trading | Order cancel and replace is supported. | 2017-10-25 09:55:36 Rithmic Trading | OCO Orders supported. | 2017-10-25 09:55:36 Rithmic Trading | Connected to data and trading server. | 2017-10-25 09:55:36 RTYZ7-CME [CV] 200 Trades #1 | Reloading chart. | 2017-10-25 09:55:39 RTYZ7-CME [CV] 200 Trades #1 | Performing historical Daily data download for symbol RJZ17 starting at last date in file. | 2017-10-25 09:55:39 RTYZ7-CME [CV] 200 Trades #1 | Waiting for historical downloads to complete with the IDs: 1, | 2017-10-25 09:55:39 RTYZ7-CME [CV] 1000 Trades #2 | Reloading chart. | 2017-10-25 09:55:39 RTYZ7-CME [CV] 1000 Trades #2 | Waiting for historical downloads to complete with the IDs: 1, | 2017-10-25 09:55:39 RTYZ7-CME [CV] 5 Min #3 | Reloading chart. | 2017-10-25 09:55:39 RTYZ7-CME [CV] 5 Min #3 | Waiting for historical downloads to complete with the IDs: 1, | 2017-10-25 09:55:39 RTYZ7-CME [CV] 100 Trades #5 | Reloading chart. | 2017-10-25 09:55:39 RTYZ7-CME [CV] 100 Trades #5 | Waiting for historical downloads to complete with the IDs: 1, | 2017-10-25 09:55:39 RTYZ7-CME [CV] 5 Min #11 | Reloading chart. | 2017-10-25 09:55:39 RTYZ7-CME [CV] 5 Min #11 | Waiting for historical downloads to complete with the IDs: 1, | 2017-10-25 09:55:39 RTYZ7-CME [CV] 1000 Trades #4 | Reloading chart. | 2017-10-25 09:55:39 RTYZ7-CME [CV] 1000 Trades #4 | Waiting for historical downloads to complete with the IDs: 1, | 2017-10-25 09:55:39 RTYZ7-CME [CV] Daily #6 | Reloading chart. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJU09.dly, RJZ09.dly | 2017-10-25 09:55:39 The RJZ09.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJZ09.dly, RJH10.dly | 2017-10-25 09:55:39 The RJH10.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJH10.dly, RJM10.dly | 2017-10-25 09:55:39 The RJM10.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJM10.dly, RJU10.dly | 2017-10-25 09:55:39 The RJU10.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJU10.dly, RJZ10.dly | 2017-10-25 09:55:39 The RJZ10.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJZ10.dly, RJH11.dly | 2017-10-25 09:55:39 The RJH11.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJH11.dly, RJM11.dly | 2017-10-25 09:55:39 The RJM11.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJM11.dly, RJU11.dly | 2017-10-25 09:55:39 The RJU11.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJU11.dly, RJZ11.dly | 2017-10-25 09:55:39 The RJZ11.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJZ11.dly, RJH12.dly | 2017-10-25 09:55:39 The RJH12.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJH12.dly, RJM12.dly | 2017-10-25 09:55:39 The RJM12.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJM12.dly, RJU12.dly | 2017-10-25 09:55:39 The RJU12.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJU12.dly, RJZ12.dly | 2017-10-25 09:55:39 The RJZ12.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJZ12.dly, RJH13.dly | 2017-10-25 09:55:39 The RJH13.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJH13.dly, RJM13.dly | 2017-10-25 09:55:39 The RJM13.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJM13.dly, RJU13.dly | 2017-10-25 09:55:39 The RJU13.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJU13.dly, RJZ13.dly | 2017-10-25 09:55:39 The RJZ13.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJZ13.dly, RJH14.dly | 2017-10-25 09:55:39 The RJH14.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJH14.dly, RJM14.dly | 2017-10-25 09:55:39 The RJM14.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJM14.dly, RJU14.dly | 2017-10-25 09:55:39 The RJU14.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJU14.dly, RJZ14.dly | 2017-10-25 09:55:39 The RJZ14.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJZ14.dly, RJH15.dly | 2017-10-25 09:55:39 The RJH15.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJH15.dly, RJM15.dly | 2017-10-25 09:55:39 The RJM15.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJM15.dly, RJU15.dly | 2017-10-25 09:55:39 The RJU15.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJU15.dly, RJZ15.dly | 2017-10-25 09:55:39 The RJZ15.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJZ15.dly, RJH16.dly | 2017-10-25 09:55:39 The RJH16.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJH16.dly, RJM16.dly | 2017-10-25 09:55:39 The RJM16.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJM16.dly, RJU16.dly | 2017-10-25 09:55:39 The RJU16.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 Unable to determine transition date based on volume from files: RJU16.dly, RJZ16.dly | 2017-10-25 09:55:39 The RJZ16.dly symbol may not be the active contract month. | 2017-10-25 09:55:39 HD Request # 2 | Downloading Historical Daily chart data for RJZ17. Starting date: 2017-10-12. Service: rim | 2017-10-25 09:55:39 HD Request # 2 | Requesting historical Daily data for RJZ17 starting at 2017-10-11 | 2017-10-25 09:55:39 HTTP connection to ds01.ddfplus.com:80 (7) | Creating socket. | 2017-10-25 09:55:39 HTTP connection to ds01.ddfplus.com:80 (7) | Connecting to IP: 8.18.161.123. | 2017-10-25 09:55:39 Rithmic Trading | Starting real-time market data updates for: RTYZ7-CME. ID: 2 | 2017-10-25 09:55:40 Rithmic Trading | Requesting security definition data for: RTYZ7-CME. ID: 2 | 2017-10-25 09:55:40 HTTP connection to ds01.ddfplus.com:80 (7) | 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. | 2017-10-25 09:56:01 * HTTP connection to ds01.ddfplus.com:80 (7) | Initiating close of socket by core. | 2017-10-25 09:56:01 HD Request # 2 | Error downloading historical Daily data for RJZ17. HTTP error when downloading from SC Historical Data service | 2017-10-25 09:56:01 HTTP connection to ds01.ddfplus.com:80 (7) | Closed. | 2017-10-25 09:56:01 HD Request # 2 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for RJZ17 | 2017-10-25 09:56:01 HD Request # 2 | Daily download COMPLETE for RJZ17. Completion time: 21s. Unique request ID: 1 | 2017-10-25 09:56:01 Removed historical data download ID 1 | 2017-10-25 09:56:01 HD Request # 3 | Downloading Historical Daily chart data for RTYZ7-CME. Starting date: 1967-10-25. Service: rim | 2017-10-25 09:56:01 HD Request # 3 | Requesting historical Daily data for RJZ17 starting at 1967-10-24 | 2017-10-25 09:56:01 HTTP connection to ds01.ddfplus.com:80 (8) | Creating socket. | 2017-10-25 09:56:01 HTTP connection to ds01.ddfplus.com:80 (8) | Connecting to IP: 8.18.161.123. | 2017-10-25 09:56:01 RTYZ7-CME [CV] 5 Min #3 | Download is complete for all contract months in chart. Proceeding with data load. | 2017-10-25 09:56:01 RTYZ7-CME [CV] 5 Min #3 | Reloading chart. | 2017-10-25 09:56:01 RTYZ7-CME [CV] 200 Trades #1 | Download is complete for all contract months in chart. Proceeding with data load. | 2017-10-25 09:56:01 RTYZ7-CME [CV] 200 Trades #1 | Reloading chart. | 2017-10-25 09:56:01 RTYZ7-CME [CV] 100 Trades #5 | Download is complete for all contract months in chart. Proceeding with data load. | 2017-10-25 09:56:01 RTYZ7-CME [CV] 100 Trades #5 | Reloading chart. | 2017-10-25 09:56:01 RTYZ7-CME [CV] 5 Min #11 | Download is complete for all contract months in chart. Proceeding with data load. | 2017-10-25 09:56:01 RTYZ7-CME [CV] 5 Min #11 | Reloading chart. | 2017-10-25 09:56:01 RTYZ7-CME [CV] 1000 Trades #2 | Download is complete for all contract months in chart. Proceeding with data load. | 2017-10-25 09:56:01 RTYZ7-CME [CV] 1000 Trades #2 | Reloading chart. | 2017-10-25 09:56:01 RTYZ7-CME [CV] 1000 Trades #4 | Download is complete for all contract months in chart. Proceeding with data load. | 2017-10-25 09:56:01 RTYZ7-CME [CV] 1000 Trades #4 | Reloading chart. | 2017-10-25 09:56:01 RTYZ7-CME [CV] 5 Min #3 | Reloading chart. | 2017-10-25 09:56:01 RTYZ7-CME [CV] 5 Min #11 | Reloading chart. | 2017-10-25 09:56:01 RTYZ7-CME [CV] 100 Trades #5 | Reloading chart. | 2017-10-25 09:56:01 RTYZ7-CME [CV] 200 Trades #1 | Reloading chart. | 2017-10-25 09:56:01 RTYZ7-CME [CV] 1000 Trades #2 | Reloading chart. | 2017-10-25 09:56:01 Starting first historical Intraday data download. When complete another download will be done from the primary service. Symbol: RTYZ7-CME | 2017-10-25 09:56:01 Intraday data recording state for symbol RTYZ7-CME is set to download 'Pending'. | 2017-10-25 09:56:01 HD Request # 4 | Downloading Intraday chart data for RTYZ7-CME to the file RTYZ7-CME.scid. Service: cme | 2017-10-25 09:56:01 HD Request # 4 | Download start date-time: 2017-10-25 09:54:28.000 | 2017-10-25 09:56:01 HD Request # 4 | Using server: ds7.sierracharts.com port 10149 | 2017-10-25 09:56:01 Socket (9) | Creating socket. | 2017-10-25 09:56:01 Socket (9) | Connecting to IP: 8.18.161.133. | 2017-10-25 09:56:01 RTYZ7-CME [CV] 1000 Trades #4 | Reloading chart. | 2017-10-25 09:56:01 Chart #11 has tagged chart #1 for full recalculation. Chartbook: RTY-Single Chart2b-Trading.cht | 2017-10-25 09:56:01 Chart #11 has tagged chart #3 for full recalculation. Chartbook: RTY-Single Chart2b-Trading.cht | 2017-10-25 09:56:01 Chart #11 has tagged chart #1 for full recalculation. Chartbook: RTY-Single Chart2b-Trading.cht | 2017-10-25 09:56:01 Chart #11 has tagged chart #3 for full recalculation. Chartbook: RTY-Single Chart2b-Trading.cht | 2017-10-25 09:56:01 RTYZ7-CME [CV] 200 Trades #1 | Performing a full recalculation because it has been tagged. Chartbook: RTY-Single Chart2b-Trading.cht | 2017-10-25 09:56:01 RTYZ7-CME [CV] 5 Min #3 | Performing a full recalculation because it has been tagged. Chartbook: RTY-Single Chart2b-Trading.cht | 2017-10-25 09:56:01 HD Request # 4 | Setting DTC encoding to Binary VLS | 2017-10-25 09:56:02 HD Request # 4 | Sending historical data logon request message. | 2017-10-25 09:56:02 HD Request # 4 | Requesting Intraday data. Start date-time: 2017-10-25 09:54:28. Record interval: 1. Symbol: RTYZ17 | 2017-10-25 09:56:02 HD Request # 4 | Decompressing data. | 2017-10-25 09:56:02 Socket (9) | Initiating close of socket by core. | 2017-10-25 09:56:02 Socket (9) | Shutdown started. Waiting for graceful close. | 2017-10-25 09:56:02 Historical data download thread signaled to stop. | 2017-10-25 09:56:02 HD Request # 4 | Received 1 record from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for RTYZ7-CME | 2017-10-25 09:56:02 HD Request # 4 | Intraday download COMPLETE for RTYZ7-CME. Completion time: 0s. Unique request ID: 3 | 2017-10-25 09:56:02 Removed historical data download ID 3 | 2017-10-25 09:56:02 Real-time Intraday chart data file updates started for RTYZ7-CME | 2017-10-25 09:56:02 Intraday chart data file opened for RTYZ7-CME | 2017-10-25 09:56:02 Rithmic Trading | Using primary service for historical data for RTYZ7-CME | 2017-10-25 09:56:02 Intraday data recording state for symbol RTYZ7-CME is set to download 'Pending'. | 2017-10-25 09:56:02 HD Request # 5 | Downloading Intraday chart data for RTYZ7-CME to the file RTYZ7-CME.scid. Service: rim | 2017-10-25 09:56:02 HD Request # 5 | Download start date-time: 2017-10-25 09:54:28.000 | 2017-10-25 09:56:02 HD Request # 5 | Sending historical data request. Start date-time: 2017-10-25 09:54:28. Record interval: 0. Symbol: RTYZ7-CME | 2017-10-25 09:56:02 Rithmic Trading | Message from server: Requesting historical Tick data. | 2017-10-25 09:56:02 Chart #11 has tagged chart #1 for full recalculation. Chartbook: RTY-Single Chart2b-Trading.cht | 2017-10-25 09:56:02 Chart #11 has tagged chart #3 for full recalculation. Chartbook: RTY-Single Chart2b-Trading.cht | 2017-10-25 09:56:02 RTYZ7-CME [CV] 200 Trades #1 | Performing a full recalculation because it has been tagged. Chartbook: RTY-Single Chart2b-Trading.cht | 2017-10-25 09:56:02 RTYZ7-CME [CV] 5 Min #3 | Performing a full recalculation because it has been tagged. Chartbook: RTY-Single Chart2b-Trading.cht | 2017-10-25 09:56:02 Socket (9) | Socket gracefully closed by remote side. | 2017-10-25 09:56:03 Socket (9) | Closed. | 2017-10-25 09:56:03 HD Request # 5 | Receiving Intraday data for RTYZ7-CME starting at 2017-10-25 09:54:28 | 2017-10-25 09:56:03 HD Request # 5 | Timestamp of first Intraday data file record written: 2017-10-25 09:55:04 | 2017-10-25 09:56:03 HD Request # 5 | Received 6 records from 2017-10-25 09:54:28 to 2017-10-25 09:55:55 (87.0 seconds) and wrote 5 records for RTYZ7-CME | 2017-10-25 09:56:03 HD Request # 5 | Intraday download COMPLETE for RTYZ7-CME. Completion time: 0s. Unique request ID: 4 | 2017-10-25 09:56:03 Removed historical data download ID 4 | 2017-10-25 09:56:03 Real-time Intraday chart data file updates started for RTYZ7-CME | 2017-10-25 09:56:03 Intraday chart data file opened for RTYZ7-CME | 2017-10-25 09:56:03 Chart #11 has tagged chart #1 for full recalculation. Chartbook: RTY-Single Chart2b-Trading.cht | 2017-10-25 09:56:03 Chart #11 has tagged chart #3 for full recalculation. Chartbook: RTY-Single Chart2b-Trading.cht | 2017-10-25 09:56:03 RTYZ7-CME [CV] 200 Trades #1 | Performing a full recalculation because it has been tagged. Chartbook: RTY-Single Chart2b-Trading.cht | 2017-10-25 09:56:03 RTYZ7-CME [CV] 5 Min #3 | Performing a full recalculation because it has been tagged. Chartbook: RTY-Single Chart2b-Trading.cht | 2017-10-25 09:56:03 HTTP connection to ds01.ddfplus.com:80 (8) | 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. | 2017-10-25 09:56:21 * HTTP connection to ds01.ddfplus.com:80 (8) | Initiating close of socket by core. | 2017-10-25 09:56:21 HD Request # 3 | Error downloading historical Daily data for RTYZ7-CME. HTTP error when downloading from SC Historical Data service | 2017-10-25 09:56:21 HD Request # 3 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for RTYZ7-CME | 2017-10-25 09:56:21 HD Request # 3 | Daily download COMPLETE for RTYZ7-CME. Completion time: 21s. Unique request ID: 2 | 2017-10-25 09:56:21 HTTP connection to ds01.ddfplus.com:80 (8) | Closed. | 2017-10-25 09:56:21 Removed historical data download ID 2 | 2017-10-25 09:56:21 RTYZ7-CME [CV] Daily #6 | Reloading chart. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJU09.dly, RJZ09.dly | 2017-10-25 09:56:21 The RJZ09.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJZ09.dly, RJH10.dly | 2017-10-25 09:56:21 The RJH10.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJH10.dly, RJM10.dly | 2017-10-25 09:56:21 The RJM10.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJM10.dly, RJU10.dly | 2017-10-25 09:56:21 The RJU10.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJU10.dly, RJZ10.dly | 2017-10-25 09:56:21 The RJZ10.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJZ10.dly, RJH11.dly | 2017-10-25 09:56:21 The RJH11.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJH11.dly, RJM11.dly | 2017-10-25 09:56:21 The RJM11.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJM11.dly, RJU11.dly | 2017-10-25 09:56:21 The RJU11.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJU11.dly, RJZ11.dly | 2017-10-25 09:56:21 The RJZ11.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJZ11.dly, RJH12.dly | 2017-10-25 09:56:21 The RJH12.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJH12.dly, RJM12.dly | 2017-10-25 09:56:21 The RJM12.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJM12.dly, RJU12.dly | 2017-10-25 09:56:21 The RJU12.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJU12.dly, RJZ12.dly | 2017-10-25 09:56:21 The RJZ12.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJZ12.dly, RJH13.dly | 2017-10-25 09:56:21 The RJH13.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJH13.dly, RJM13.dly | 2017-10-25 09:56:21 The RJM13.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJM13.dly, RJU13.dly | 2017-10-25 09:56:21 The RJU13.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJU13.dly, RJZ13.dly | 2017-10-25 09:56:21 The RJZ13.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJZ13.dly, RJH14.dly | 2017-10-25 09:56:21 The RJH14.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJH14.dly, RJM14.dly | 2017-10-25 09:56:21 The RJM14.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJM14.dly, RJU14.dly | 2017-10-25 09:56:21 The RJU14.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJU14.dly, RJZ14.dly | 2017-10-25 09:56:21 The RJZ14.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJZ14.dly, RJH15.dly | 2017-10-25 09:56:21 The RJH15.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJH15.dly, RJM15.dly | 2017-10-25 09:56:21 The RJM15.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJM15.dly, RJU15.dly | 2017-10-25 09:56:21 The RJU15.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJU15.dly, RJZ15.dly | 2017-10-25 09:56:21 The RJZ15.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJZ15.dly, RJH16.dly | 2017-10-25 09:56:21 The RJH16.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJH16.dly, RJM16.dly | 2017-10-25 09:56:21 The RJM16.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJM16.dly, RJU16.dly | 2017-10-25 09:56:21 The RJU16.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 Unable to determine transition date based on volume from files: RJU16.dly, RJZ16.dly | 2017-10-25 09:56:21 The RJZ16.dly symbol may not be the active contract month. | 2017-10-25 09:56:21 HD Request # 6 | Downloading Historical Daily chart data for RJU09. Starting date: 1967-10-25. Service: rim | 2017-10-25 09:56:50 HD Request # 6 | Requesting historical Daily data for RJU09 starting at 1967-10-24 | 2017-10-25 09:56:50 HTTP connection to ds01.ddfplus.com:80 (11) | Creating socket. | 2017-10-25 09:56:50 HTTP connection to ds01.ddfplus.com:80 (11) | Connecting to IP: 8.18.161.123. | 2017-10-25 09:56:50 HTTP connection to ds01.ddfplus.com:80 (11) | 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. | 2017-10-25 09:57:10 * HTTP connection to ds01.ddfplus.com:80 (11) | Initiating close of socket by core. | 2017-10-25 09:57:10 HD Request # 6 | Error downloading historical Daily data for RJU09. HTTP error when downloading from SC Historical Data service | 2017-10-25 09:57:10 HTTP connection to ds01.ddfplus.com:80 (11) | Closed. | 2017-10-25 09:57:10 HD Request # 6 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for RJU09 | 2017-10-25 09:57:10 HD Request # 6 | Daily download COMPLETE for RJU09. Completion time: 21s. Unique request ID: 5 | 2017-10-25 09:57:10 Removed historical data download ID 5 | 2017-10-25 09:57:10 HD Request # 7 | Downloading Historical Daily chart data for RJZ09. Starting date: 1967-10-25. Service: rim | 2017-10-25 09:57:10 HD Request # 7 | Requesting historical Daily data for RJZ09 starting at 1967-10-24 | 2017-10-25 09:57:10 HTTP connection to ds01.ddfplus.com:80 (12) | Creating socket. | 2017-10-25 09:57:10 HTTP connection to ds01.ddfplus.com:80 (12) | Connecting to IP: 8.18.161.123. | 2017-10-25 09:57:10 HTTP connection to ds01.ddfplus.com:80 (12) | 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. | 2017-10-25 09:57:31 * HTTP connection to ds01.ddfplus.com:80 (12) | Initiating close of socket by core. | 2017-10-25 09:57:31 HD Request # 7 | Error downloading historical Daily data for RJZ09. HTTP error when downloading from SC Historical Data service | 2017-10-25 09:57:31 HD Request # 7 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for RJZ09 | 2017-10-25 09:57:31 HD Request # 7 | Daily download COMPLETE for RJZ09. Completion time: 21s. Unique request ID: 6 | 2017-10-25 09:57:31 Removed historical data download ID 6 | 2017-10-25 09:57:31 HTTP connection to ds01.ddfplus.com:80 (12) | Closed. | 2017-10-25 09:57:31 HD Request # 8 | Downloading Historical Daily chart data for RJH10. Starting date: 1967-10-25. Service: rim | 2017-10-25 09:57:31 HD Request # 8 | Requesting historical Daily data for RJH10 starting at 1967-10-24 | 2017-10-25 09:57:31 HTTP connection to ds01.ddfplus.com:80 (14) | Creating socket. | 2017-10-25 09:57:31 HTTP connection to ds01.ddfplus.com:80 (14) | Connecting to IP: 8.18.161.123. | 2017-10-25 09:57:31 HTTP connection to ds01.ddfplus.com:80 (14) | 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. | 2017-10-25 09:57:53 * HTTP connection to ds01.ddfplus.com:80 (14) | Initiating close of socket by core. | 2017-10-25 09:57:53 HD Request # 8 | Error downloading historical Daily data for RJH10. HTTP error when downloading from SC Historical Data service | 2017-10-25 09:57:53 HD Request # 8 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for RJH10 | 2017-10-25 09:57:53 HD Request # 8 | Daily download COMPLETE for RJH10. Completion time: 21s. Unique request ID: 7 | 2017-10-25 09:57:53 Removed historical data download ID 7 | 2017-10-25 09:57:53 HTTP connection to ds01.ddfplus.com:80 (14) | Closed. | 2017-10-25 09:57:53 HD Request # 9 | Downloading Historical Daily chart data for RJM10. Starting date: 1967-10-25. Service: rim | 2017-10-25 09:57:53 HD Request # 9 | Requesting historical Daily data for RJM10 starting at 1967-10-24 | 2017-10-25 09:57:53 HTTP connection to ds01.ddfplus.com:80 (15) | Creating socket. | 2017-10-25 09:57:53 HTTP connection to ds01.ddfplus.com:80 (15) | Connecting to IP: 8.18.161.123. | 2017-10-25 09:57:53 HTTP connection to ds01.ddfplus.com:80 (15) | 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. | 2017-10-25 09:58:13 * HTTP connection to ds01.ddfplus.com:80 (15) | Initiating close of socket by core. | 2017-10-25 09:58:13 HD Request # 9 | Error downloading historical Daily data for RJM10. HTTP error when downloading from SC Historical Data service | 2017-10-25 09:58:13 HD Request # 9 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for RJM10 | 2017-10-25 09:58:13 HD Request # 9 | Daily download COMPLETE for RJM10. Completion time: 21s. Unique request ID: 8 | 2017-10-25 09:58:13 HTTP connection to ds01.ddfplus.com:80 (15) | Closed. | 2017-10-25 09:58:13 Removed historical data download ID 8 | 2017-10-25 09:58:13 HD Request # 10 | Downloading Historical Daily chart data for RJU10. Starting date: 1967-10-25. Service: rim | 2017-10-25 09:58:13 HD Request # 10 | Requesting historical Daily data for RJU10 starting at 1967-10-24 | 2017-10-25 09:58:13 HTTP connection to ds01.ddfplus.com:80 (16) | Creating socket. | 2017-10-25 09:58:13 HTTP connection to ds01.ddfplus.com:80 (16) | Connecting to IP: 8.18.161.123. | 2017-10-25 09:58:13 HTTP connection to ds01.ddfplus.com:80 (16) | 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. | 2017-10-25 09:58:34 * HTTP connection to ds01.ddfplus.com:80 (16) | Initiating close of socket by core. | 2017-10-25 09:58:34 HD Request # 10 | Error downloading historical Daily data for RJU10. HTTP error when downloading from SC Historical Data service | 2017-10-25 09:58:34 HTTP connection to ds01.ddfplus.com:80 (16) | Closed. | 2017-10-25 09:58:34 HD Request # 10 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for RJU10 | 2017-10-25 09:58:34 HD Request # 10 | Daily download COMPLETE for RJU10. Completion time: 21s. Unique request ID: 9 | 2017-10-25 09:58:34 Removed historical data download ID 9 | 2017-10-25 09:58:34 HD Request # 11 | Downloading Historical Daily chart data for RJZ10. Starting date: 1967-10-25. Service: rim | 2017-10-25 09:58:34 HD Request # 11 | Requesting historical Daily data for RJZ10 starting at 1967-10-24 | 2017-10-25 09:58:34 HTTP connection to ds01.ddfplus.com:80 (18) | Creating socket. | 2017-10-25 09:58:34 HTTP connection to ds01.ddfplus.com:80 (18) | Connecting to IP: 8.18.161.123. | 2017-10-25 09:58:34 HTTP connection to ds01.ddfplus.com:80 (18) | 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. | 2017-10-25 09:58:56 * HTTP connection to ds01.ddfplus.com:80 (18) | Initiating close of socket by core. | 2017-10-25 09:58:56 HD Request # 11 | Error downloading historical Daily data for RJZ10. HTTP error when downloading from SC Historical Data service | 2017-10-25 09:58:56 HTTP connection to ds01.ddfplus.com:80 (18) | Closed. | 2017-10-25 09:58:56 HD Request # 11 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for RJZ10 | 2017-10-25 09:58:56 HD Request # 11 | Daily download COMPLETE for RJZ10. Completion time: 21s. Unique request ID: 10 | 2017-10-25 09:58:56 Removed historical data download ID 10 | 2017-10-25 09:58:56 HD Request # 12 | Downloading Historical Daily chart data for RJH11. Starting date: 1967-10-25. Service: rim | 2017-10-25 09:58:56 HD Request # 12 | Requesting historical Daily data for RJH11 starting at 1967-10-24 | 2017-10-25 09:58:56 HTTP connection to ds01.ddfplus.com:80 (19) | Creating socket. | 2017-10-25 09:58:56 HTTP connection to ds01.ddfplus.com:80 (19) | Connecting to IP: 8.18.161.123. | 2017-10-25 09:58:56 Opened cached Intraday file: C:\SierraChartTrading\Data\RTYZ7-CME.scid | 2017-10-25 09:59:03 HTTP connection to ds01.ddfplus.com:80 (19) | 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. | 2017-10-25 09:59:17 * HTTP connection to ds01.ddfplus.com:80 (19) | Initiating close of socket by core. | 2017-10-25 09:59:17 HD Request # 12 | Error downloading historical Daily data for RJH11. HTTP error when downloading from SC Historical Data service | 2017-10-25 09:59:17 HTTP connection to ds01.ddfplus.com:80 (19) | Closed. | 2017-10-25 09:59:17 HD Request # 12 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for RJH11 | 2017-10-25 09:59:17 HD Request # 12 | Daily download COMPLETE for RJH11. Completion time: 21s. Unique request ID: 11 | 2017-10-25 09:59:17 Removed historical data download ID 11 | 2017-10-25 09:59:17 HD Request # 13 | Downloading Historical Daily chart data for RJM11. Starting date: 1967-10-25. Service: rim | 2017-10-25 09:59:17 HD Request # 13 | Requesting historical Daily data for RJM11 starting at 1967-10-24 | 2017-10-25 09:59:17 HTTP connection to ds01.ddfplus.com:80 (20) | Creating socket. | 2017-10-25 09:59:17 HTTP connection to ds01.ddfplus.com:80 (20) | Connecting to IP: 8.18.161.123. | 2017-10-25 09:59:17 HTTP connection to ds01.ddfplus.com:80 (20) | 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. | 2017-10-25 09:59:37 * HTTP connection to ds01.ddfplus.com:80 (20) | Initiating close of socket by core. | 2017-10-25 09:59:37 HD Request # 13 | Error downloading historical Daily data for RJM11. HTTP error when downloading from SC Historical Data service | 2017-10-25 09:59:37 HTTP connection to ds01.ddfplus.com:80 (20) | Closed. | 2017-10-25 09:59:37 HD Request # 13 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for RJM11 | 2017-10-25 09:59:37 HD Request # 13 | Daily download COMPLETE for RJM11. Completion time: 21s. Unique request ID: 12 | 2017-10-25 09:59:37 Removed historical data download ID 12 | 2017-10-25 09:59:37 HD Request # 14 | Downloading Historical Daily chart data for RJU11. Starting date: 1967-10-25. Service: rim | 2017-10-25 09:59:37 HD Request # 14 | Requesting historical Daily data for RJU11 starting at 1967-10-24 | 2017-10-25 09:59:37 HTTP connection to ds01.ddfplus.com:80 (22) | Creating socket. | 2017-10-25 09:59:37 HTTP connection to ds01.ddfplus.com:80 (22) | Connecting to IP: 8.18.161.123. | 2017-10-25 09:59:37 HTTP connection to ds01.ddfplus.com:80 (22) | 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. | 2017-10-25 09:59:58 * HTTP connection to ds01.ddfplus.com:80 (22) | Initiating close of socket by core. | 2017-10-25 09:59:58 HD Request # 14 | Error downloading historical Daily data for RJU11. HTTP error when downloading from SC Historical Data service | 2017-10-25 09:59:58 HTTP connection to ds01.ddfplus.com:80 (22) | Closed. | 2017-10-25 09:59:58 HD Request # 14 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for RJU11 | 2017-10-25 09:59:58 HD Request # 14 | Daily download COMPLETE for RJU11. Completion time: 21s. Unique request ID: 13 | 2017-10-25 09:59:58 Removed historical data download ID 13 | 2017-10-25 09:59:58 HD Request # 15 | Downloading Historical Daily chart data for RJZ11. Starting date: 1967-10-25. Service: rim | 2017-10-25 09:59:58 HD Request # 15 | Requesting historical Daily data for RJZ11 starting at 1967-10-24 | 2017-10-25 09:59:58 HTTP connection to ds01.ddfplus.com:80 (23) | Creating socket. | 2017-10-25 09:59:58 HTTP connection to ds01.ddfplus.com:80 (23) | Connecting to IP: 8.18.161.123. | 2017-10-25 09:59:58 HTTP connection to ds01.ddfplus.com:80 (23) | 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. | 2017-10-25 10:00:19 * HTTP connection to ds01.ddfplus.com:80 (23) | Initiating close of socket by core. | 2017-10-25 10:00:19 HD Request # 15 | Error downloading historical Daily data for RJZ11. HTTP error when downloading from SC Historical Data service | 2017-10-25 10:00:19 HTTP connection to ds01.ddfplus.com:80 (23) | Closed. | 2017-10-25 10:00:19 HD Request # 15 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for RJZ11 | 2017-10-25 10:00:19 HD Request # 15 | Daily download COMPLETE for RJZ11. Completion time: 21s. Unique request ID: 14 | 2017-10-25 10:00:19 Removed historical data download ID 14 | 2017-10-25 10:00:19 HD Request # 16 | Downloading Historical Daily chart data for RJH12. Starting date: 1967-10-25. Service: rim | 2017-10-25 10:00:19 HD Request # 16 | Requesting historical Daily data for RJH12 starting at 1967-10-24 | 2017-10-25 10:00:19 HTTP connection to ds01.ddfplus.com:80 (25) | Creating socket. | 2017-10-25 10:00:19 HTTP connection to ds01.ddfplus.com:80 (25) | Connecting to IP: 8.18.161.123. | 2017-10-25 10:00:19 HTTP connection to ds01.ddfplus.com:80 (25) | 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. | 2017-10-25 10:00:41 * HTTP connection to ds01.ddfplus.com:80 (25) | Initiating close of socket by core. | 2017-10-25 10:00:41 HD Request # 16 | Error downloading historical Daily data for RJH12. HTTP error when downloading from SC Historical Data service | 2017-10-25 10:00:41 HD Request # 16 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for RJH12 | 2017-10-25 10:00:41 HD Request # 16 | Daily download COMPLETE for RJH12. Completion time: 21s. Unique request ID: 15 | 2017-10-25 10:00:41 HTTP connection to ds01.ddfplus.com:80 (25) | Closed. | 2017-10-25 10:00:41 Removed historical data download ID 15 | 2017-10-25 10:00:41 HD Request # 17 | Downloading Historical Daily chart data for RJM12. Starting date: 1967-10-25. Service: rim | 2017-10-25 10:00:41 HD Request # 17 | Requesting historical Daily data for RJM12 starting at 1967-10-24 | 2017-10-25 10:00:41 HTTP connection to ds01.ddfplus.com:80 (26) | Creating socket. | 2017-10-25 10:00:41 HTTP connection to ds01.ddfplus.com:80 (26) | Connecting to IP: 8.18.161.123. | 2017-10-25 10:00:41 HTTP connection to ds01.ddfplus.com:80 (26) | 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. | 2017-10-25 10:01:02 * HTTP connection to ds01.ddfplus.com:80 (26) | Initiating close of socket by core. | 2017-10-25 10:01:02 HD Request # 17 | Error downloading historical Daily data for RJM12. HTTP error when downloading from SC Historical Data service | 2017-10-25 10:01:02 HD Request # 17 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for RJM12 | 2017-10-25 10:01:02 HD Request # 17 | Daily download COMPLETE for RJM12. Completion time: 21s. Unique request ID: 16 | 2017-10-25 10:01:02 HTTP connection to ds01.ddfplus.com:80 (26) | Closed. | 2017-10-25 10:01:02 Removed historical data download ID 16 | 2017-10-25 10:01:02 HD Request # 18 | Downloading Historical Daily chart data for RJU12. Starting date: 1967-10-25. Service: rim | 2017-10-25 10:01:02 HD Request # 18 | Requesting historical Daily data for RJU12 starting at 1967-10-24 | 2017-10-25 10:01:02 HTTP connection to ds01.ddfplus.com:80 (27) | Creating socket. | 2017-10-25 10:01:02 HTTP connection to ds01.ddfplus.com:80 (27) | Connecting to IP: 8.18.161.123. | 2017-10-25 10:01:02 |
| [2017-10-25 09:03:51] |
| User792599 - Posts: 3 |
|
Same problem. HTTP error when downloading from SC Historical Data service.
|
| [2017-10-25 09:21:07] |
| |
|
We are aware of this. We have told our data provider about it. They should be resolving it shortly. 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: 2017-10-25 09:21:21
|
To post a message in this thread, you need to log in with your Sierra Chart account: