Home >> Support Board

Support Board

Date/Time: Tue, 25 Feb 2025 07:43:16 +0000

How to Post a Message for Support

Problems with Receiving Data for Forex Symbols

View Count: 897

[2021-03-27 13:09:58] #1 [Go To First Post]
Botan626 - Posts: 294
SC v2239, this was first mentioned around 4 p.m. UTC on Thursday. Data receiving speed was extremely slow, took more than 30 mins to download data for around 30 forex FXCM symbols after less than 1 day of non-usage time, and data itself was corrupt. Yesterday it took more than 5 minutes for SC to update data for symbols which get quotes every 15 minutes, like EURZAR. This happened just now: I changed From date for AUDUSD to 2020-03-01, this is how SC downloaded data for it: http://www.sierrachart.com/image.php?Image=161685045849.png Date Time Of Last Edit: 2021-03-27 13:11:42

[2021-03-27 13:18:23] #2 [Go To First Post]
Botan626 - Posts: 294
I changed From date to 2020-02-01 for AUDUSD, now SC is downloading data correctly. This is the second time I see SC downloads data properly from the second try, yesterday was the same case for another symbol.

[2021-03-27 13:43:17] #3 [Go To First Post]
Botan626 - Posts: 294
SC had no problems with downloading data after I deleted all scid files in the Data folder on Friday morning. My guess is v2239 has some issues with re-writing/updating data files on the disk. Tried just now: Data for AUDJPY was downloaded from 2021-01-25 up to date, I changed From date to 2021-01-01. SC was like this for several minutes: https://i.imgur.com/5CagSY3.png And after it finished downloading data: https://i.imgur.com/mr5LWg2.png

[2021-03-27 14:56:54] #4 [Go To First Post]
Botan626 - Posts: 294
Now it doesn't download data even from 4-th and 5-th try: https://i.imgur.com/cQA2s8V.png https://i.imgur.com/DOkwf6T.png

[2021-03-29 04:01:50] #5 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Sounds like you have some connectivity issue with the downloading of historical data. Refer to: Historical Intraday Data (Missing Data / Download Errors / Viewing More Data): Error when Downloading Historical Intraday Data from the Sierra Chart Historical Data Server 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: 2021-03-29 04:01:57

[2021-03-29 06:16:24] #6 [Go To First Post]
Botan626 - Posts: 294
This setting is in different place now: Historical Intraday Data (Missing Data / Download Errors / Viewing More Data): Using Port 80 Date Time Of Last Edit: 2021-03-29 06:19:16

[2021-03-29 06:24:02] #7 [Go To First Post]
Botan626 - Posts: 294
Sounds like you have some connectivity issue with the downloading of historical data. Refer to: Historical Intraday Data (Missing Data / Download Errors / Viewing More Data): Error when Downloading Historical Intraday Data from the Sierra Chart Historical Data Server This topic says: Sierra Chart needs to be provided access to ports 10149, 10150 to connect to the historical data server. How can I check manually, that SC has access to ports 10149, 10150? I have only Windows Defender Firewall running, I don't use a router.

[2021-03-29 06:29:40] #8 [Go To First Post]
Botan626 - Posts: 294
I set 'Use Port 80 For Historical Data' to true. The downloading speed is still terrible, close to 0.

[2021-03-29 06:51:41] #9 [Go To First Post]
Botan626 - Posts: 294
I set 'Use Port 80 For Historical Data' back to false. This is how SC was downloading data for CADJPY: Triggering next historical data download in queue. \| 2021-03-29 09:44:23.951 HD Request # 4 \| Downloading Intraday chart data for CADJPY to the file CADJPY.scid. Service: fxcm \| 2021-03-29 09:44:23.951 HD Request # 4 \| Download start date-time: 2021-03-29 08:55:23.000000. File last date-time: 2021-03-29 08:55:23.389000 \| 2021-03-29 09:44:23.951 HD Request # 4 \| Using server: ds4.sierracharts.com port 10149 \| 2021-03-29 09:44:23.951 Socket (2) \| Creating socket. \| 2021-03-29 09:44:23.952 Socket (2) \| New receive buffer size: 5242880 \| 2021-03-29 09:44:23.952 Socket (2) \| Connecting to IP: 192.81.56.146. \| 2021-03-29 09:44:23.952 Chart #3 has tagged chart #2 for full recalculation. Chartbook: 01.Cht \| 2021-03-29 09:44:24.123 Socket (4) \| Socket gracefully closed by remote side. \| 2021-03-29 09:44:24.145 Socket (4) \| Closed. \| 2021-03-29 09:44:24.146 HD Request # 4 \| Setting DTC encoding to Binary VLS \| 2021-03-29 09:44:24.364 HD Request # 4 \| Sending historical data logon request message. \| 2021-03-29 09:44:24.364 HD Request # 4 \| Requesting Intraday data. Start date-time: 2021-03-29 08:55:23. Record interval: 0. Symbol: CADJPY \| 2021-03-29 09:44:24.564 CHFJPY[M] 0.120 Range #2 \| Performing a full recalculation because it has been tagged. Chartbook: 01.Cht \| 2021-03-29 09:44:24.605 HD Request # 4 \| Decompressing data. \| 2021-03-29 09:44:24.765 HD Request # 4 \| Receiving Intraday data for CADJPY starting at 2021-03-29 08:55:23.389000 \| 2021-03-29 09:44:25.293 Opened cached Intraday file: C:\SierraChart\Data\CHFJPY.scid. Thread ID: 10524 \| 2021-03-29 09:44:26.772 Socket (2) \| Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine. \| 2021-03-29 09:45:08.113 Socket (2) \| Socket gracefully closed by remote side. \| 2021-03-29 09:45:08.113 Socket (2) \| CloseSocket call. \| 2021-03-29 09:45:08.113 Socket (0) \| CloseSocket call. \| 2021-03-29 09:45:08.113 Socket (2) \| Graceful close received or receive error. Shutdown complete. Closing socket now. \| 2021-03-29 09:45:08.113 Socket (2) \| Closed. \| 2021-03-29 09:45:08.113 HD Request # 4 \| Error downloading historical Intraday data for CADJPY. The network socket has been closed. Retrying download. \| 2021-03-29 09:45:08.116 Added historical Intraday data request for CADJPY to the queue. \| 2021-03-29 09:45:08.116 Triggering next historical data download in queue. \| 2021-03-29 09:45:08.116 Historical data download thread signaled to stop. \| 2021-03-29 09:45:08.116 HD Request # 4 \| Timestamp of first Intraday data file record written: 2021-03-29 08:55:40.307000 \| 2021-03-29 09:45:08.116 HD Request # 4 \| Received 132 records from 2021-03-29 08:55:23.389000 to 2021-03-29 08:58:16.254000 (2.9 minutes) and wrote 131 records for CADJPY \| 2021-03-29 09:45:08.117 HD Request # 4 \| Completion time: 45s \| 2021-03-29 09:45:08.121 HD Request # 5 \| Downloading Intraday chart data for CADJPY to the file CADJPY.scid. Service: fxcm \| 2021-03-29 09:45:08.121 HD Request # 5 \| Download start date-time: 2021-03-29 08:58:16.000000. File last date-time: 2021-03-29 08:58:16.254000 \| 2021-03-29 09:45:08.122 HD Request # 5 \| Using server: ds12.sierracharts.com port 10150 \| 2021-03-29 09:45:08.122 Socket (2) \| Creating socket. \| 2021-03-29 09:45:08.122 Socket (2) \| New receive buffer size: 5242880 \| 2021-03-29 09:45:08.122 Socket (2) \| Connecting to IP: 204.15.197.14. \| 2021-03-29 09:45:08.122 HD Request # 5 \| Setting DTC encoding to Binary VLS \| 2021-03-29 09:45:08.543 HD Request # 5 \| Sending historical data logon request message. \| 2021-03-29 09:45:08.543 HD Request # 5 \| Requesting Intraday data. Start date-time: 2021-03-29 08:58:16. Record interval: 0. Symbol: CADJPY \| 2021-03-29 09:45:09.227 HD Request # 5 \| Decompressing data. \| 2021-03-29 09:45:09.444 HD Request # 5 \| Receiving Intraday data for CADJPY starting at 2021-03-29 08:58:16.041000 \| 2021-03-29 09:45:09.967 Socket (2) \| Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine. \| 2021-03-29 09:45:57.017 Socket (2) \| Socket gracefully closed by remote side. \| 2021-03-29 09:45:57.017 Socket (2) \| CloseSocket call. \| 2021-03-29 09:45:57.017 Socket (0) \| CloseSocket call. \| 2021-03-29 09:45:57.017 Socket (2) \| Graceful close received or receive error. Shutdown complete. Closing socket now. \| 2021-03-29 09:45:57.017 Socket (2) \| Closed. \| 2021-03-29 09:45:57.017 HD Request # 5 \| Error downloading historical Intraday data for CADJPY. The network socket has been closed. Retrying download. \| 2021-03-29 09:45:57.017 Added historical Intraday data request for CADJPY to the queue. \| 2021-03-29 09:45:57.017 Triggering next historical data download in queue. \| 2021-03-29 09:45:57.017 Historical data download thread signaled to stop. \| 2021-03-29 09:45:57.017 HD Request # 5 \| Timestamp of first Intraday data file record written: 2021-03-29 08:58:17.352000 \| 2021-03-29 09:45:57.017 HD Request # 5 \| Received 308 records from 2021-03-29 08:58:16.041000 to 2021-03-29 09:00:49.856000 (2.6 minutes) and wrote 303 records for CADJPY \| 2021-03-29 09:45:57.018 HD Request # 5 \| Completion time: 49s \| 2021-03-29 09:45:57.023 HD Request # 6 \| Downloading Intraday chart data for CADJPY to the file CADJPY.scid. Service: fxcm \| 2021-03-29 09:45:57.024 HD Request # 6 \| Download start date-time: 2021-03-29 09:00:49.000000. File last date-time: 2021-03-29 09:00:49.856000 \| 2021-03-29 09:45:57.024 HD Request # 6 \| Using server: ds4.sierracharts.com port 10149 \| 2021-03-29 09:45:57.024 Socket (2) \| Creating socket. \| 2021-03-29 09:45:57.024 Socket (2) \| New receive buffer size: 5242880 \| 2021-03-29 09:45:57.024 Socket (2) \| Connecting to IP: 192.81.56.146. \| 2021-03-29 09:45:57.025 HD Request # 6 \| Setting DTC encoding to Binary VLS \| 2021-03-29 09:45:58.069 HD Request # 6 \| Sending historical data logon request message. \| 2021-03-29 09:45:58.069 HD Request # 6 \| Requesting Intraday data. Start date-time: 2021-03-29 09:00:49. Record interval: 0. Symbol: CADJPY \| 2021-03-29 09:45:58.803 HD Request # 6 \| Decompressing data. \| 2021-03-29 09:45:59.007 Socket (2) \| Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine. \| 2021-03-29 09:45:59.225 HD Request # 6 \| Receiving Intraday data for CADJPY starting at 2021-03-29 09:00:49.024000 \| 2021-03-29 09:45:59.226 Socket (2) \| Socket receive error. Windows error code 10054: An existing connection was forcibly closed by the remote host. \| 2021-03-29 09:45:59.227 Socket (2) \| CloseSocket call. \| 2021-03-29 09:45:59.227 Socket (0) \| CloseSocket call. \| 2021-03-29 09:45:59.227 Socket (2) \| Graceful close received or receive error. Shutdown complete. Closing socket now. \| 2021-03-29 09:45:59.227 Socket (2) \| Closed. \| 2021-03-29 09:45:59.227 HD Request # 6 \| Error downloading historical Intraday data for CADJPY. The network socket has been closed. Retrying download. \| 2021-03-29 09:45:59.232 Historical data download thread signaled to stop. \| 2021-03-29 09:45:59.232 HD Request # 6 \| Timestamp of first Intraday data file record written: 2021-03-29 09:00:49.919000 \| 2021-03-29 09:45:59.232 HD Request # 6 \| Received 136 records from 2021-03-29 09:00:49.024000 to 2021-03-29 09:01:42.351000 (53.3 seconds) and wrote 130 records for CADJPY \| 2021-03-29 09:45:59.232 HD Request # 6 \| Add time&sales data \| Remembered last file record date-time: 2021-03-29 06:01:42.351000 \| 2021-03-29 09:45:59.241 Added 241 Time and Sales records to Intraday data file for CADJPY after download. \| 2021-03-29 09:45:59.241 HD Request # 6 \| Completion time: 2s \| 2021-03-29 09:45:59.248 HD Request # 6 \| Intraday data download complete for CADJPY. Unique request ID: 35 \| 2021-03-29 09:45:59.248 Removing historical data download ID 35. \| 2021-03-29 09:45:59.248 Real-time Intraday chart data file updates started for CADJPY \| 2021-03-29 09:45:59.248 Intraday chart data file opened for CADJPY \| 2021-03-29 09:45:59.248 HD Request # 6 \| Enabling Intraday chart updating for symbol. \| 2021-03-29 09:45:59.248

[2021-03-29 06:59:38] #10 [Go To First Post]
Botan626 - Posts: 294
HD Request # 4 \| Using server: ds4.sierracharts.com port 10149 \| 2021-03-29 09:44:23.951 I just saw this line in the log and I tried telnet ds4.sierracharts.com 10149 telnet ds4.sierracharts.com 10150 telnet ds4.sierracharts.com 80 commands in Command Prompt. All ports are opened, I saw only a cursor after executing them. So I guess the problem is on SC side.

[2021-03-29 07:29:19] #11 [Go To First Post]
Botan626 - Posts: 294
Also I saw these messages in the log while updating to a newer SC version for the last couple of updates. https://i.imgur.com/FYXaYmw.png https://i.imgur.com/x5JWwDZ.png Date Time Of Last Edit: 2021-03-29 07:32:36

[2021-03-29 16:18:06] #12 [Go To First Post]
John - SC Support - Posts: 38150
With regards to your data, you have multiple of the following errors in your log: Socket (2) \| Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine. So you definitely have a connectivity problem of some kind. Refer to the following: Data/Trading Service Connection and Symbol Issues: 1.2. Network Communication or Server Problem The errors when updating are telling you the same thing, there is a connectivity issue. Although that one is related to HTTP requests, therefore also review the following: Historical Intraday Data (Missing Data / Download Errors / Viewing More Data): Error when Downloading Historical Intraday Data from the Sierra Chart Historical Data Server For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing

[2021-03-29 18:10:56] #13 [Go To First Post]
Botan626 - Posts: 294
I tried to do this: Data/Trading Service Connection and Symbol Issues: 1.8. Checking Connection Quality to Remote Server by Using Ping I used two different internet connections, but the result is the same in both cases: https://i.imgur.com/ISc6JDu.png Are you sure it's not a problem on your side with something, maybe some connections need to be reseted or refreshed? I see other support requests re this issue with slow/delayed connection, like this one: Binance - Slow data download ETH and BTC And the 1-st time I noticed it was as well around 1 week ago, when I tried to update to a newer version, it was way slower and I saw same messages I showed you in post #11.

[2021-03-29 18:18:11] #14 [Go To First Post]
Botan626 - Posts: 294
Or here: Bitmex Intraday data not loading more than 2 weeks on CQG WebAPI He was using the same server ds12.sierracharts.com and had the same Windows error code 10053 today.

[2021-03-29 18:37:19] #15 [Go To First Post]
Botan626 - Posts: 294
Btw, not all ping tests fail. Pinging ds1.sierracharts.com, ds3.sierracharts.com, ds5.sierracharts.com, ds7.sierracharts.com servers were fully successful. Date Time Of Last Edit: 2021-03-29 18:39:31

[2021-03-30 19:03:29] #16 [Go To First Post]
Botan626 - Posts: 294
I changed my internet connection one more time this morning, and it seems like all downloads came back to normal so far. I don't see 10053 error codes anymore. But my ping tests still fail, 100% loss. I see in message log SC uses ds4.sierracharts.com and ds12.sierracharts.com servers for historical data downloads. This section Data/Trading Service Connection and Symbol Issues: 1.8. Checking Connection Quality to Remote Server by Using Ping says: A useful way to check the quality of the connectivity between your computer and the server being connected to, is by using the network Ping command from the operating system command line. You will use the server address name with the Ping command. So it's not good, that my ping tests fail, right? Can you try ping tests to these servers too? And the link in this line 'Refer to this Internet article for instructions to use Ping.' is dead. Date Time Of Last Edit: 2021-03-30 21:14:24

[2021-04-01 18:39:38] #17 [Go To First Post]
Botan626 - Posts: 294
?

[2021-04-01 19:12:50] #18 [Go To First Post]
John - SC Support - Posts: 38150
But my ping tests still fail, 100% loss. I see in message log SC uses ds4.sierracharts.com and ds12.sierracharts.com servers for historical data downloads. That is because those servers are not setup to respond to ping requests. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing

[2021-04-01 19:42:44] #19 [Go To First Post]
Botan626 - Posts: 294
Why do you suggest checking the quality of the connectivity between computer and the server by using ping command then?

[2021-04-01 21:09:04] #20 [Go To First Post]
John - SC Support - Posts: 38150
There are some servers, such as ds1.sierracharts.com that is mentioned in that section of documentation, that does support a ping. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing

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