Support Board
Date/Time: Thu, 09 Jan 2025 08:58:51 +0000
Loading Issues
View Count: 1025
| [2016-08-01 13:42:03] |
| infpz - Posts: 826 |
|
On Monday July 25 I had issues when I started Sierra Charts (on both the systems I run it on). I thought it had hung but it turns out that it was just taking a long time to download data and merge it into the intraday data files. I eventually realized that SC had pegged one of the processor cores in my computer (Task Manager performance tab showed SC at about 17% CPU usage for several minutes). I tried closing SC and deleting all the scid and dly files but that did not help. Eventually by loading each symbol and forcing data downloads I was able to get running ok. Each morning on startup I would have some minor problems with the downloads but it seemed to be ok as long as I did not try to display a symbol that I don’t normally use – like 6E as an example. Today it again took forever to get both systems running OK. Attached is the SC log file from one of my computers – note the entries of “DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:36:39”. I don’t see them when things seem to be running normally. Both computers I am using have Intel Core I7 4 core processors with hyperthreading (8 effective cores), 16GB of RAM and I am running Windows 10. My Internet provider is Verizon FIOS (fiber optic) and the speed is 75/75 mbs. DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 HD Request # 36 | Error downloading historical Intraday data for 6EU6. The download timed out. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 Socket (33) | Shutdown error. Windows error code 10054: An existing connection was forcibly closed by the remote host. | 2016-08-01 07:41:28 * Socket (33) | Shutdown and closed. | 2016-08-01 07:41:28 HD Request # 36 | Received 5342 records from 2016-07-29 02:35:03 to 0-00-00 00:00:00 (146009162771.9 years) and wrote 5342 records for 6EU6 | 2016-08-01 07:41:28 HD Request # 36 | Intraday download COMPLETE for 6EU6. Completion time: 4m 54s. Unique request ID: 34 | 2016-08-01 07:41:28 Removed historical data download ID 34 | 2016-08-01 07:41:28 Real-time Intraday chart data file updates started for 6EU6 | 2016-08-01 07:41:28 Opened cached Intraday file: C:\SierraChart\SierraChartTransActMA\Data\6EU6.scid | 2016-08-01 07:41:28 Intraday chart data file opened for 6EU6 | 2016-08-01 07:41:28 HD Request # 36 | Enabling Intraday chart updating for symbol. | 2016-08-01 07:41:28 HD Request # 36 | Reloading Intraday charts for 6EU6 | 2016-08-01 07:41:28 Reloading all charts with filename: 6EU6.scid | 2016-08-01 07:41:28 6EU6 5 Min #9 | Reloading chart. | 2016-08-01 07:41:32 Chart #9 has tagged chart #1 for full recalculation. Chartbook: Overlay.cht | 2016-08-01 07:41:32 Chart #9 has tagged chart #1 for full recalculation. Chartbook: Overlay.cht | 2016-08-01 07:41:32 Chart #9 has tagged chart #1 for full recalculation. Chartbook: Overlay.cht | 2016-08-01 07:41:32 ESU6 5 Min #1 | Performing a full recalculation because it has been tagged. Chartbook: Overlay.cht | 2016-08-01 07:41:32 Intraday data recording state for symbol 6EU6 is set to download 'Pending'. | 2016-08-01 07:43:09 Reloading all charts with filename: 6EU6.scid | 2016-08-01 07:43:09 HD Request # 37 | Downloading Intraday chart data for 6EU6 to the file 6EU6.scid. Service: ta | 2016-08-01 07:43:09 HD Request # 37 | Download start Date-Time: 2016-06-17 03:19:20.000 | 2016-08-01 07:43:09 HD Request # 37 | Using server: ds5.sierracharts.com port 10149 | 2016-08-01 07:43:09 Socket (0) | Resolved address ds5.sierracharts.com to IP 204.15.192.106. | 2016-08-01 07:43:09 Socket (36) | Connected. | 2016-08-01 07:43:10 HD Request # 37 | Sending historical data logon request message. | 2016-08-01 07:43:10 6EU6 5 Min #9 | Reloading chart. | 2016-08-01 07:43:10 Chart #9 has tagged chart #1 for full recalculation. Chartbook: Overlay.cht | 2016-08-01 07:43:10 Chart #9 has tagged chart #1 for full recalculation. Chartbook: Overlay.cht | 2016-08-01 07:43:10 HD Request # 37 | Requesting Intraday data. Start Date-Time: 2016-06-17 03:19:20. Record interval: 1. Symbol: 6EU6 | 2016-08-01 07:43:10 ESU6 5 Min #1 | Performing a full recalculation because it has been tagged. Chartbook: Overlay.cht | 2016-08-01 07:43:10 HD Request # 37 | Decompressing data. | 2016-08-01 07:43:10 HD Request # 37 | Receiving Intraday data for 6EU6 starting at 2016-06-17 03:19:20 | 2016-08-01 07:43:11 HD Request # 37 | Timestamp of first Intraday data file record written: 2016-06-17 03:19:20 | 2016-08-01 07:43:11 Socket (36) | Shutdown and closed. | 2016-08-01 07:43:12 The network socket for historical data has been closed. | 2016-08-01 07:43:12 HD Request # 37 | Received 530638 records from 2016-06-17 03:19:20 to 2016-08-01 07:43:05 (45.2 days) and wrote 530636 records for 6EU6 | 2016-08-01 07:43:12 Added 3 Time and Sales records to Intraday data file for 6EU6 after download. | 2016-08-01 07:43:12 HD Request # 37 | Intraday download COMPLETE for 6EU6. Completion time: 3s. Unique request ID: 35 | 2016-08-01 07:43:12 Removed historical data download ID 35 | 2016-08-01 07:43:12 Real-time Intraday chart data file updates started for 6EU6 | 2016-08-01 07:43:12 Opened cached Intraday file: C:\SierraChart\SierraChartTransActMA\Data\6EU6.scid | 2016-08-01 07:43:12 Intraday chart data file opened for 6EU6 | 2016-08-01 07:43:12 Chart #9 has tagged chart #1 for full recalculation. Chartbook: Overlay.cht | 2016-08-01 07:43:13 ESU6 5 Min #1 | Performing a full recalculation because it has been tagged. Chartbook: Overlay.cht | 2016-08-01 07:43:13 |
| [2016-08-01 16:44:29] |
| |
|
The first step is to not use any of the existing Chartbooks because possibly there is a certain configuration you are using which is causing the problem. Only open a small number of new charts to see of that rules out some problem with a Chartbook. At this point we are not totally sure what the cause is. Refer to these help topics: https://www.sierrachart.com/index.php?l=doc/helpdetails30.html#h30.8 https://www.sierrachart.com/index.php?l=doc/helpdetails30.html#h30.5 This is very unusual to see and indicates a data corruption: DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 We will put a limit on the number of times this message can be added to the Message Log to see if it is this message causing the problem. Also use Safe Mode: https://www.sierrachart.com/index.php?page=doc/helpdetails17.html#h17.1 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 |
| [2016-08-01 18:22:47] |
| |
|
We think we have more of an understanding about this error message: DTC - Unrecognized message. Size: 0. Type: 0. | 2016-08-01 07:41:28 It may be caused by a server problem on our side. It is a large number of these messages added to the Message Log causing the freezing. This has now been solved. Update as soon as possible to Prerelease 1449 following these instructions: https://www.sierrachart.com/index.php?page=doc/download.php#FastUpdate 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 |
| [2016-08-01 18:50:11] |
| |
|
If this user still has a problem we need contact information from them so we can look into this more closely.
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 |
| [2016-08-01 18:50:47] |
| infpz - Posts: 826 |
|
OK will update soon
|
| [2016-08-02 00:28:13] |
| |
|
The best conclusion we can come to at this time is that this problem is apparently due to some kind of problem your ISP is having or some Internet service provider they are working with where network data is getting corrupted from our server. We only have 2 known instances of this. This is quite an unusual problem. Who is your Internet service provider? What we want you to do is to go to one of the charts that does not have complete or accurate data and select "Edit >> Delete All Data and Download". The chart data should re-download without any problem in less than a minute. If not, there continues to be a problem. However, the problem with Sierra Chart freezing and using high CPU usage is solved in the latest prerelease. This will no longer happen. But that was only a side effect of this data corruption. 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: 2016-08-02 00:29:07
|
| [2016-08-02 11:05:46] |
| infpz - Posts: 826 |
|
I will follow up
|
| [2016-08-02 18:01:32] |
| infpz - Posts: 826 |
|
He was using Verizon FIOS. He changed to a new ISP and it works fine. Patrick, Two possible causes immediately come to mind (although why the problem just started last week is unclear): - The Verizon FIOS backbone is corrupting and/or deleting some of the data traffic from the data server - The data is arriving faster than Sierra Chart (or whatever) can handle it and something internal to SC is losing/corrupting the data I’m sure there might be a whole host of other possible causes but these two seem reasonable first start. Date Time Of Last Edit: 2016-08-02 18:01:39
|
| [2016-08-02 19:07:24] |
| |
|
It definitely could not be this: - The data is arriving faster than Sierra Chart (or whatever) can handle it and something internal to SC is losing/corrupting the 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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2016-08-02 19:15:59] |
| infpz - Posts: 826 |
|
Understood thanks.
|
To post a message in this thread, you need to log in with your Sierra Chart account: