Support Board
Date/Time: Wed, 27 Nov 2024 16:48:56 +0000
DTC unrecognized message - Sierra becoming unresponsive
View Count: 1251
| [2014-09-23 13:25:03] |
| gfs117 - Posts: 24 |
|
Hi, Lately I've been seeing the message "DTC - Unrecognized message" in my message log. Today, it happened again after I opened a chartbook. I'm seeing several messages like this: "DTC - Unrecognized message. Size: XXXXX. Type: XXX | Time" The sizes and types vary (see attachment). After that, Sierra Chart became unresponsive, like it usually does. Normally I'm seeing loads of "Unrecognized messages" per second with a size of 0. That causes SC to become unreponsive. I've waited 30 minutes in the past for the program to become responsive again, but it doesn't. I think this occured again today, because of the position of the scrollbar. The problem occured when I was on version 1137 and it still occurs today (version 1192). Could you please solve this issue, or tell me how to solve it (if the issue is on my end)? Thank you. |
 2014-09-23-15-18-53.png / V - Attached On 2014-09-23 13:23:06 UTC - Size: 125.18 KB - 368 views |
| [2014-09-23 16:23:39] |
| |
|
How long have you seen this message? Is it just with version 1137 and 1192? Any other versions? We want you to restart Sierra Chart. Open only one chart without any studies and let us know if you see the message. The chart needs to be one which will use the Sierra Chart data feed. In your case this will be a CME or EUREX symbol. 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: 2014-09-23 16:25:00
|
| [2014-09-23 16:48:49] |
| gfs117 - Posts: 24 |
|
I've had the message on and off for a few weeks now (since the beginning of September, that's when I came back from a 2 month holiday). I've used version 1137 and 1192 this month, so I only had the problem with these versions. I'll try to get the error message the way you requested it, but I doubt I'll see it. The problem only occurs when I'm opening a chartbook with multiple symbols (like 5 or more). |
| [2014-09-23 17:23:51] |
| |
|
It is OK to open 5 charts, but make sure they do not contain any studies and do not open anything else in Sierra Chart.
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 |
| [2014-09-23 18:50:44] |
| gfs117 - Posts: 24 |
|
Hi, I did some testing and it took me a while before I got the unrecognized messages. I first started with a 5 chart chartbook (365 days loaded), then increased it to 20 charts, then I made the charts continuous, but I still didn't see the message. It was only after I increased the number of days to load to 999 that the "unrecognized message" started to appear. In the attached log, the first Unrecognized message appears at 20:37:57 (after the loading of SI-201412-NYMEX-USD-5000 charts). Then after loading the CL-chart, the program receives several unrecognized messages (end of file, starting at 20:38:00). This was my last chance to grab the message log, because after that, the program received loads of Size 0 unrecognized messages and then became unresponsive. I have attached several files: 1 - The chartbook I created 2 - The message log from opening the CB 3 - A screenshot of the message log after the program became unresponsive |
 Test-Unrecognized-Message-2.cht - Attached On 2014-09-23 18:47:54 UTC - Size: 392.98 KB - 443 views unrecognized message log.doc - Attached On 2014-09-23 18:48:15 UTC - Size: 686.5 KB - 448 views 2014-09-23-20-39-18.png / V - Attached On 2014-09-23 18:48:48 UTC - Size: 124.31 KB - 343 views |
| [2014-09-23 19:46:34] |
| |
|
We are fairly certain, there is nothing wrong with the data feed itself and being we have no other reports of this, the only logical conclusion is that a memory corruption is occurring. In the next release, coming out today, a DTC message size of 0 will be filtered out and a disconnection will be made to prevent all of the messages from being added to the log. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2014-09-23 19:48:28] |
| |
|
If you are running any kind of third-party firewall software, then disable 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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2014-09-24 08:16:18] |
| gfs117 - Posts: 24 |
|
the only logical conclusion is that a memory corruption is occurring
I figured it had something to do with memory, as it only occurs when SC is under a high load. Is the memory corruption a problem that's happening with the software or are you saying there might be something wrong with the RAM-memory in my pc? If you are running any kind of third-party firewall software, then disable it.
I only have the Windows firewall that's built in with Windows 7.
|
| [2014-09-25 05:55:26] |
| |
|
Update Sierra Chart to the latest prerelease with Help >> Download Prerelease. A message size of 0 is properly handled and will not freeze Sierra Chart. This will at least not cause a problem with the stability of Sierra Chart in this particular regard. Whatever is causing the memory corruption, is not totally clear at this time. 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 |
To post a message in this thread, you need to log in with your Sierra Chart account: