Home >> Support Board

Support Board

Date/Time: Mon, 29 Apr 2024 12:19:12 +0000

How to Post a Message for Support

Unknown Server Error

View Count: 1560

[2016-04-29 16:38:59] #1 [Go To First Post]
Rusty - Posts: 38
Opened SC this morning and received the following alert: "Unknown server error: Please contact Sierra Chart support." Clicked OK, and automatic logon completed. Got the typical System Notification Message. WARNING message in Message Log: "Your computer's clock is off by 8 minutes \| 2016-04-29 11:21:29 For help with the DateTime issue, press the Send For Analysis button \| 2016-04-29 11:21:29" Checked the computer's clock, and it is not off by 8 minutes. It's within 5 seconds of the correct NIST time. Searched SC Support Board and found no other posts on this issue. Pressed the Send For Analysis button, but resulting message did not shed any light on the issue. The "Your computer's clock is off…" message has appeared before. See ThreadID=12500. It was caused by code changes that affected old builds. Have previously received permission to use this old copy (v618) of SC for data collection only via TWS. It's worked fine for months. Thank you.

[2016-04-29 18:57:23] #2 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Do you still need to use this older version? There are some changes that we have made which are no longer compatible with this version. What is the reason for using the old version? So we can see if it is reasonable for us to support that in newer versions. 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-04-29 18:57:38

[2016-04-29 19:42:48] #3 [Go To First Post]
Rusty - Posts: 38
There is no specific reason I need to use v618. (It was installed in 2010 because it was the last version to run under W2K.) It still serves my purpose. I avoid upgrades because they always result in lost time when I am in development mode. The chartbook and ASICS are set up a certain way. Sometimes there are incompatibilities with the OS. Sometimes the relevant files and locations change. Sometimes the menus change. Sometimes the list of available features changes. Sometimes the features that used to work one way now work another way. Sometimes the screen layout changes. These changes force me to document the differences so I can set up new chartbooks, etc. without re-reading the documentation. Nevertheless it is unreasonable for you to make a coding change to support one user. If necessary to upgrade I prefer v1293 which I use in another copy to communicate with the SC Real-time and Historical Data Feed. Thank you.

[2016-04-29 20:24:18] #4 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Yes you can use 1293. That will be supported for at least the next three years. 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-05-21 03:53:41] #5 [Go To First Post]
Rusty - Posts: 38
As anticipated, encountered some problems doing the upgrade, but the upgraded copy of SC v1293 has been collecting data since I last posted. There are some vexing issues remaining: symbol conflicts, pacing violations, and MND-files. As an example of symbol conflicts, consider the symbol for the CME GLOBEX NASDAQ-100 futures contract. Currently I employ three different instances of Sierra Chart v1293: Sierra-SC for collecting real-time data via the SCDF, Sierra-SX for collecting historical data via the SCHDS, and Sierra-IB as a backup for collecting data from IB. These configurations use three different symbols for the same contract. Consequently there are three different symbols for the filenames, chart titles, and IFULs: ..Symbol/Config____Sierra-IB______________Sierra-SC_______________Sierra-SX ..Filename________NQM6-FUT-GLOBEX______NQ-201606-GLOBEX______NQM16 ..Chart Title______NQM6-FUT-GLOBEX______NQ-201606-GLOBEX______NQM16 ..IFUL Symbol_____NQM6-FUT-GLOBEX______NQ-201606-GLOBEX______?? ..DTS "Instance"__Interactive Brokers_______Interactive Brokers______SC Historical Data ..Find Symbol_____NQ-201606-GLOBEX_____NQ-201606-GLOBEX______NQM16 The Sierra-IB copy has used the IB standard format for years. Find Symbol » Futures now lists a different format for NQ. Other chart symbols I use are listed with slightly different formats under Find Symbol » IB Indexes: COMP-I-NASDAQ, NDX-I-NASDAQ, SPX-I-CBOE, TICK-NASD-I-NASDAQ, TICK-NYSE-I-NYSE. VXN-I-CBOE isn't listed at all. Find Symbol doesn't map to any of these symbols. I don't understand how IB backfills work if SC doesn't recognize the symbol. Is this how it works? If SC doesn't recognize the chart/IFUL symbol, it asks TWS if it recognizes the symbol. If TWS does, SC either starts a new file with that symbol or starts backfilling an existing file that has that symbol. Beyond confusion, this scheme creates other hassles. You can't append to a GLOBEX file downloaded via the SCHDS using the SCDF in real-time without changing the filename. You can't backfill an IB filename via the SCDF, etc. Which brings me to the next issue. The documentation states that if you have checked "Allow Support for Sierra Chart Data Feeds" then historical data for major futures contract symbols is downloaded from the Sierra Chart Historical Data Service except for the last 10 or 15 minutes which comes from the IB system. Since I got pacing violations trying to backfill the above IB symbols I conclude it was because the symbols weren't in SCHDS-recognizable format and therefore no data was downloaded from the SCHDS, and it was downloaded via TWS from IB. Right? Pacing Violations: Why did you take the old pause-between-data-requests parameter out of the Data/Trade Service settings for IB? I used to set it to 10,000 ms, go away, and let it grind on an IFUL for hours if need be. Now I have to baby-sit the download, watch for pacing violations, and restart the download multiple times. MND-files: SC v1293 won't read any of my intra-day MND-files. I have hundreds of them. Some contain over 10 years of data. This is one reason I stuck with v618 so long. There is no need to incur the extra storage of the SCID-format for indices and market stats that don't have bid/ask volume, etc. Furthermore, there is no easy way to convert MND-format to SCID-format. Exporting to CSV-files and importing is possible but not expeditious.

[2016-05-23 11:17:19] #6 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Give us some time to look this over and follow-up. 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-05-24 09:05:37] #7 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
NQM6-FUT-GLOBEX Do not use this format any longer. Only use the symbols you see in File >> Find Symbol for the particular service being used. COMP-I-NASDAQ, NDX-I-NASDAQ, SPX-I-CBOE, TICK-NASD-I-NASDAQ, TICK-NYSE-I-NYSE. VXN-I-CBOE among these what is missing has been added to File >> Find Symbol. And always use the specific symbols you see listed there. Periodically those formats are updated to properly comply with changes on the Interactive Brokers side. Since I got pacing violations trying to backfill the above IB symbols I conclude it was because the symbols weren't in SCHDS-recognizable format and therefore no data was downloaded from the SCHDS, and it was downloaded via TWS from IB. Right? Yes this is definitely correct. Pacing Violations: Why did you take the old pause-between-data-requests parameter out of the Data/Trade Service settings for IB? I used to set it to 10,000 ms, go away, and let it grind on an IFUL for hours if need be. Now I have to baby-sit the download, watch for pacing violations, and restart the download multiple times. You do not need to do this in newer versions. There is an automatic wait when there is a pacing violation. You do not need to do anything. Just simply let the Historical data download continue on its own and it will manage it properly waiting as necessary and resuming when there is no longer a pacing violation. MND-files: SC v1293 won't read any of my intra-day MND-files. I have hundreds of them. Some contain over 10 years of data. This is one reason I stuck with v618 so long. There is no need to incur the extra storage of the SCID-format for indices and market stats that don't have bid/ask volume, etc. Furthermore, there is no easy way to convert MND-format to SCID-format. Exporting to CSV-files and importing is possible but not expeditious. What we can do is temporarily allow you access to the older versions and then you will need to convert them. Older versions have a function to convert MND to SCID. Once this is done, we will no longer be supporting the older versions or this format. 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-05-24 09:07:19

[2016-05-27 04:45:58] #8 [Go To First Post]
Rusty - Posts: 38
Thank you for the complete reply. I understand your response to all the issues and will take your recommendations. What we can do is temporarily allow you access to the older versions and then you will need to convert them. Older versions have a function to convert MND to SCID. Once this is done, we will no longer be supporting the older versions or this format. I gratefully accept your offer to enable access to older SC versions, specifically v618 and v837. Considering the number of archived files, fragments, and patches, I won't be able to complete the conversion quickly; but I'll write a file manager in Perl script that will perform the conversion and some other functions. If you will give me one week's access, I can convert the longer and immediately useful files, and also use them to validate the file manager. Then I won't be dependent on access to the older SC versions in the future. I have specifications and bookmarks for both the MND and SCID formats.

[2016-05-27 05:10:51] #9 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We will be making access to those versions available starting next week. 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-07-06 21:12:17] #10 [Go To First Post]
Rusty - Posts: 38
Thank you for permitting me access to those older versions of SC. I have completed recording the setups, parameters, and the most important file conversions and my need to access them has been satisfied.

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