Login Page - Create Account

Support Board


Date/Time: Sat, 23 Nov 2024 20:38:11 +0000



DATA DELAYED 10 MIN

View Count: 1445

[2022-03-02 14:59:56]
marwhitt - Posts: 29
My data is delayed 10 min. I am using TransAct, my TA DOM has real time data.
I have set data services to SC All Data. Please advise.



Software version: 2362 64-bit | 2022-03-02 14:49:27.677
Primary Thread ID: 12324 | 2022-03-02 14:49:27.678
Usage end date: 2022-08-19 | 2022-03-02 14:49:27.678
Enabled for: Sierra Chart Historical Data Service. | 2022-03-02 14:49:27.678
Enabled for: Delayed Denali Exchange Data Feed. | 2022-03-02 14:49:27.678
Allow Support for Sierra Chart Data Feeds is enabled. | 2022-03-02 14:49:27.678
Current selected Data/Trading service: TransAct WS | 2022-03-02 14:49:27.678
Custom symbol settings values: disabled | 2022-03-02 14:49:27.678
Chart Update Interval: 500 | 2022-03-02 14:49:27.678
Intraday Data Storage Time Unit: 1 | 2022-03-02 14:49:27.678
Time Zone: +00:00:00 (UTC+00) | 2022-03-02 14:49:27.678
2022-03-02 14:49:27 Local computer time in UTC | 2022-03-02 14:49:27.678
2022-03-02 14:49:27 Local computer time in SC Time Zone | 2022-03-02 14:49:27.678
2022-03-02 14:36:09 Server time in UTC | 2022-03-02 14:49:27.678
Local computer UTC time and Server UTC time difference: 0 seconds. | 2022-03-02 14:49:27.678
Program path: C:\SierraChart\ | 2022-03-02 14:49:27.678
Data Files path: C:\SierraChart\Data\ | 2022-03-02 14:49:27.678
OS Version Number: 10.0 | 2022-03-02 14:49:27.678
Locale Setting: C | 2022-03-02 14:49:27.678
DLLs: UserContributedStudies_64.dll | 2022-03-02 14:49:27.678
Allowed protected custom studies: | 2022-03-02 14:49:27.678

File >> Disconnect selected. | 2022-03-02 14:49:52.978
DTC Client socket (0) | CloseSocket call. | 2022-03-02 14:49:52.978
| Waiting for socket receive thread to end | 2022-03-02 14:49:52.978
DTC Client socket (2) | CloseSocket call. | 2022-03-02 14:49:52.979
| Disconnected from the server. | 2022-03-02 14:49:52.979
TransAct WS | Disconnected. | 2022-03-02 14:49:52.979
DTC Client socket (2) | Shutdown started. Waiting for graceful close. | 2022-03-02 14:49:52.979

TransAct WS | Connected to server complete. | 2022-03-02 14:49:58.008
Triggering next historical data download in queue. | 2022-03-02 14:49:58.009
Triggering next historical data download in queue. | 2022-03-02 14:49:58.009
Triggering next historical data download in queue. | 2022-03-02 14:49:58.009
Triggering next historical data download in queue. | 2022-03-02 14:49:58.009
No download requests in the queue to start downloads for. | 2022-03-02 14:49:58.009
No download requests in the queue to start downloads for. | 2022-03-02 14:49:58.010
No download requests in the queue to start downloads for. | 2022-03-02 14:49:58.010
No download requests in the queue to start downloads for. | 2022-03-02 14:49:58.010
Mapping ESH22_FUT_CME to ESH22. Service code: cme | 2022-03-02 14:49:58.296
Using symbol data fast lookup vector | 2022-03-02 14:49:58.296
| Starting real-time market data updates for: ESH22_FUT_CME (ESH22). ID: 1 Service code: cme | 2022-03-02 14:49:58.296
| Connecting to the server ds12-2.sierracharts.com. Port 10043 | 2022-03-02 14:49:58.296
| Requesting security definition data for: ESH22_FUT_CME (ESH22). ID: 1 | 2022-03-02 14:49:58.296
Added historical Intraday data request for ESH22_FUT_CME to the queue. | 2022-03-02 14:49:58.296
Intraday data recording state for symbol ESH22_FUT_CME is set to download 'Pending'. | 2022-03-02 14:49:58.296
Triggering next historical data download in queue. | 2022-03-02 14:49:58.296
Delaying start of download for ESH22_FUT_CME | 2022-03-02 14:49:58.309
DTC Client socket (1) | Creating socket. | 2022-03-02 14:49:58.324
DTC Client socket (1) | New receive buffer size: 5242880 | 2022-03-02 14:49:58.324
DTC Client socket (1) | Connecting to IP: 204.15.197.13. | 2022-03-02 14:49:58.324
| Network connection to server complete. | 2022-03-02 14:49:58.368
| Starting socket receive thread. | 2022-03-02 14:49:58.368
| Sending encoding request to server: Binary VLS. Compression: standard | 2022-03-02 14:49:58.368
| Setting DTC encoding to Binary VLS | 2022-03-02 14:49:58.494
| Sending logon request message. | 2022-03-02 14:49:58.494
| Received logon response. | 2022-03-02 14:49:59.182
| Server Name: SC Realtime Server. | 2022-03-02 14:49:59.182
| Server protocol version: 8. Client protocol version: 8 | 2022-03-02 14:49:59.182
| Successfully connected. | 2022-03-02 14:49:59.182
| Trading is not supported. | 2022-03-02 14:49:59.182
| Restarting real-time data updates for symbol: ESH22_FUT_CME -> ESH22 | 2022-03-02 14:49:59.182
| Received security definition for symbol ESH22_FUT_CME | 2022-03-02 14:49:59.308
HD Request # 16 | Downloading Intraday chart data for ESH22_FUT_CME to the file ESH22_FUT_CME.scid. Service: cme | 2022-03-02 14:50:04.393
HD Request # 16 | Download start date-time: 2022-03-02 14:39:42.000000. File last date-time: 2022-03-02 14:39:42.000000 | 2022-03-02 14:50:04.393
HD Request # 16 | Using server: ds21.sierracharts.com port 10150 | 2022-03-02 14:50:04.393
Socket (3) | Creating socket. | 2022-03-02 14:50:04.393
Socket (3) | New receive buffer size: 5242880 | 2022-03-02 14:50:04.393
Socket (3) | Connecting to IP: 216.1.90.129. | 2022-03-02 14:50:04.393
HD Request # 16 | Setting DTC encoding to Binary VLS | 2022-03-02 14:50:04.518
HD Request # 16 | Sending historical data logon request message. | 2022-03-02 14:50:04.518
HD Request # 16 | Requesting Intraday data. Start date-time: 2022-03-02 14:39:42. Record interval: 1. Symbol: ESH22 | 2022-03-02 14:50:05.096
HD Request # 16 | Decompressing data. | 2022-03-02 14:50:05.450
HD Request # 16 | Receiving Intraday data for ESH22_FUT_CME starting at 2022-03-02 14:39:42.123000 | 2022-03-02 14:50:05.451
Socket (3) | CloseSocket call. | 2022-03-02 14:50:05.451
Socket (3) | Shutdown started. Waiting for graceful close. | 2022-03-02 14:50:05.451
Historical data download thread signaled to stop. | 2022-03-02 14:50:05.451
HD Request # 16 | Timestamp of first Intraday data file record written: 2022-03-02 14:39:42.123000 | 2022-03-02 14:50:05.452
HD Request # 16 | Received 22 Intraday data records from 2022-03-02 14:39:42.123000 to 2022-03-02 14:40:03.004000 (20.9 seconds) and wrote 22 records for ESH22_FUT_CME | 2022-03-02 14:50:05.452
HD Request # 16 | Add time&sales data | Remembered last file record date-time: 2022-03-02 14:40:03.004000 | 2022-03-02 14:50:05.452
HD Request # 16 | Completion time: 1s | 2022-03-02 14:50:05.452
HD Request # 16 | Intraday data download complete for ESH22_FUT_CME. Unique request ID: 16 | 2022-03-02 14:50:05.452
Removing historical data download ID 16. | 2022-03-02 14:50:05.452
Real-time Intraday chart data file updates started for ESH22_FUT_CME | 2022-03-02 14:50:05.452
Opened cached Intraday file: C:\SierraChart\Data\ESH22_FUT_CME.scid. Thread ID: 12324 | 2022-03-02 14:50:05.453
Intraday chart data file opened for ESH22_FUT_CME | 2022-03-02 14:50:05.453
HD Request # 16 | Enabling Intraday chart updating for symbol. | 2022-03-02 14:50:05.453

Triggering next historical data download in queue. | 2022-03-02 14:50:05.453
No download requests in the queue to start downloads for. | 2022-03-02 14:50:05.453
Socket (3) | Socket gracefully closed by remote side. | 2022-03-02 14:50:05.505
Socket (3) | Closed. | 2022-03-02 14:50:05.505
DTC Client socket (2) | Timed out waiting for shutdown. Performing an immediate socket close. | 2022-03-02 14:52:03.825
DTC Client socket (2) | Closed. | 2022-03-02 14:52:03.825
DTC Client socket (2) | Deleting network socket now after delay. | 2022-03-02 14:52:33.836
Saved Chartbook: KevinChartbook1.Cht. Time: 0.0045 seconds. | 2022-03-02 14:53:00.042
Saved Chartbook: KevinChartbook1.Cht. Time: 0.0019 seconds. | 2022-03-02 14:53:03.490
[2022-03-02 16:41:58]
Sierra Chart Engineering - Posts: 104368
We see you are using Transact. Therefore, the reason the data is delayed is explained here:

Information for Transact Users for Versions 2354 and Higher
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
[2022-03-02 16:49:21]
marwhitt - Posts: 29
So, "ending support" for TransAct not only means that you can no longer help with any problems, but that you are also FORCING TA users to either use one of your connected brokers, or find another charting service?
[2022-03-02 17:01:30]
Sierra Chart Engineering - Posts: 104368
Yes we are not helping with Transact problems! Why would we do that? Where is that going to lead to? Nowhere. We cannot help with this problem. It is not within our control. Transact was advised about it over two weeks ago and it is not solved. They do not care about you!

Why would we spend our valuable time and intelligence, on a substandard system. We want to give you the best service.

And we do want you to move on to Teton and a broker that is supporting Teton (Transact/Ninja does not):
Sierra Chart Teton Futures Order Routing


Why not?

We have nothing to gain by moving you to a new broker. We want you to move to our Teton order routing service and a broker that supports Teton. Transact/ninja does not. That is their choice. Nothing against that. They have to work with the systems they work with.

We are trying to help you and give you superior services. Instead of dealing with all kinds of problems involving Transact.

With Teton we are giving you a full end-to-end solution, that is massively superior to transact, for less money. One in which we fully control, and which we can properly support for you.

Understand we are working in your interest. Not against you.

This is the method by which we are helping you. Transact is a dead-end. Free for you and for us.

There is no reason for you to move to another charting service. The process to move your account, from Transact to another broker is very simple. The broker will make this very easy for you. Look at the testimonials here:
Sierra Chart Teton Futures Order Routing: Testimonials (Stage 5)

The process of moving to a new charting platform is much more involved because you have to learn another program. The choice is clear. Please move to a new broker because Transact is not supporting our Teton service.

This morning we have numerous reports, about our Transact users unable to connect to Transact. We can infer from that, that our entire transact user base cannot connect to the transact system and yet Transact is not solving this problem. Why would you stay with that broker and system?
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: 2022-03-02 17:15:17
[2022-03-02 17:05:24]
Sierra Chart Engineering - Posts: 104368
Prior post has been updated. Reload this page and look at the prior post again please.
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: 2022-03-02 17:05:31
[2022-03-02 17:42:43]
Stage 5 Trading - Posts: 155
Hi Marwhitt,

Sorry to hear you are going through these issues with your Transact connectivity. You are not being forced to stop using TransAct (TA) as a connection. Sierra simply isn't supporting TA for software versions 2354 and higher. You can install previous Sierra Chart versions from your help menu and keep using version 2353 or lower. That should keep your TransAct connection working. I myself am an ex-Infinity Broker and certainly understand where you are coming from.

Personally, I believe the best solution for you would be to switch to Sierra Teton Order Routing with Denali for real time and historical data. I believe this complete A-Z solution maintained by Sierra Chart. is a major benefit from multiple third party connections, like TransAct, that Sierra cannot control. On top of that, I feel it is the best overall quality and value for traders. Additionally, I believe traders should be able to save a lot of money from the reduced commissions as well!

If you open an account at Stage 5 using Sierra Chart Teton Order Routing, you will receive $0.20 per side commissions on the micros and $0.45 commissions on non-micros plus exchange and regulatory fees.

If you have questions or would like to speak to an assigned personal broker for details, please call us at 1-312-896-9897 or 1-800-258-6675. You can email us at sierrachart@s5trading.com and can also contact us here: https://stage5trading.com/contact/

Please feel free to contact us and we will gladly assist you with any questions you may have and/or the process of transitioning your account and hopefully helping you improve your current trading solution. We would be able to provide some DOM chartbook layouts that will hopefully be more in line with what you are accustomed to. In addition, we would be more than happy to have a remote session to help get you setup with the new layouts.

We are here to help, so please let us know how we can best assist you!

Thank you,
Anthony Giacomin
Stage 5 Trading

Trading derivatives carries a high degree of risk, and may not be suitable for all investors. Past performance is not necessarily indicative of future results.
[2022-03-02 19:44:49]
Sierra Chart Engineering - Posts: 104368
Anthony thank you for this. The problem with this though is that they (Transact users) were not able to connect to Transact this morning:
You can install previous Sierra Chart versions from your help menu and keep using version 2353 or lower. That should keep your TransAct connection working
We are not wanting to perpetuate the problem.
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: 2022-03-03 01:11:18
[2022-03-02 20:29:12]
marwhitt - Posts: 29
Yes. thanks for the suggestion - I rolled back to 2348, and could connect but still has 10-min delay.

And thank you, Seirra, for your last response above, as it was the most polite, concise, and sensical explanation I have received about this problem. If you would like to help more people remain with SC, a little polite customer service (as above) goes a long way and will automatically generate loyalty.
[2022-03-03 01:12:42]
Sierra Chart Engineering - Posts: 104368
That is because you are using SC Data-All Services. You have to set this setting to Transact:
Data/Trade Service Settings: Current Selected Service (Global Settings >> Data/Trade Service Settings >> Main Settings >> Service)
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: 2022-03-03 01:12:48
[2022-03-03 15:44:32]
marwhitt - Posts: 29
I am stil on version 2348. I have changed the Data Service selection back to TransAct - still 10-minute delay. I deleted all data and redownloaded - still 10-minute delay.

Thanks to SC Engineering explanation above, I will be transferring to a supported broker. It would be nice in the meantime if I could have my real-time data back.

Suggestions?
[2022-03-03 16:48:40]
John - SC Support - Posts: 36238
marwhitt:

Please get us your message log by following these instructions:

Follow the instructions here to clear the Message Log:
Message Log: Clearing the Message Log

Reconnect to the data feed:
File Menu: Procedure to Reconnect to the Data and Trade Servers

After about 30 seconds, provide a copy of the Message Log following these instructions:
https://www.sierrachart.com/index.php?page=PostingInformation.php#MessageLog

We will then determine what the problem is.
For the most reliable, advanced, and zero cost futures order routing, use the Teton service:
Sierra Chart Teton Futures Order Routing
[2022-03-03 17:05:14]
marwhitt - Posts: 29
Software version: 2348 64-bit | 2022-03-03 17:03:58.618
Primary Thread ID: 7744 | 2022-03-03 17:03:58.618
Usage end date: 2022-08-19 | 2022-03-03 17:03:58.618
Enabled for: Sierra Chart Historical Data Service. | 2022-03-03 17:03:58.618
Enabled for: Delayed Denali Exchange Data Feed. | 2022-03-03 17:03:58.618
Allow Support for Sierra Chart Data Feeds is enabled. | 2022-03-03 17:03:58.618
Current selected Data/Trading service: SC Data - All Services | 2022-03-03 17:03:58.618
Custom symbol settings values: disabled | 2022-03-03 17:03:58.618
Chart Update Interval: 500 | 2022-03-03 17:03:58.618
Intraday Data Storage Time Unit: 1 | 2022-03-03 17:03:58.618
Time Zone: +00:00:00 (UTC+00) | 2022-03-03 17:03:58.618
2022-03-03 17:03:58 Local computer time in UTC | 2022-03-03 17:03:58.618
2022-03-03 17:03:58 Local computer time in SC Time Zone | 2022-03-03 17:03:58.618
2022-03-03 15:28:30 Server time in UTC | 2022-03-03 17:03:58.618
Local computer UTC time and Server UTC time difference: 2 seconds. | 2022-03-03 17:03:58.618
Program path: C:\SierraChart\ | 2022-03-03 17:03:58.618
Data Files path: C:\SierraChart\Data\ | 2022-03-03 17:03:58.618
OS Version Number: 10.0 | 2022-03-03 17:03:58.619
Locale Setting: C | 2022-03-03 17:03:58.619
DLLs: UserContributedStudies_64.dll | 2022-03-03 17:03:58.619
Allowed protected custom studies: | 2022-03-03 17:03:58.619


SC Data - All Services | Connected to server complete. | 2022-03-03 17:04:05.943
Triggering next historical data download in queue. | 2022-03-03 17:04:05.943
Triggering next historical data download in queue. | 2022-03-03 17:04:05.943
Triggering next historical data download in queue. | 2022-03-03 17:04:05.943
Triggering next historical data download in queue. | 2022-03-03 17:04:05.943
No download requests in the queue to start downloads for. | 2022-03-03 17:04:05.943
No download requests in the queue to start downloads for. | 2022-03-03 17:04:05.943
No download requests in the queue to start downloads for. | 2022-03-03 17:04:05.944
No download requests in the queue to start downloads for. | 2022-03-03 17:04:05.944
Mapping ESH22-CME to ESH22. Service code: cme | 2022-03-03 17:04:06.416
Using symbol data fast lookup vector | 2022-03-03 17:04:06.416
SC DTC Delayed Exchange Data | Starting real-time market data updates for: ESH22-CME (ESH22). ID: 1 Service code: cme | 2022-03-03 17:04:06.417
SC DTC Delayed Exchange Data | Connecting to the server ds13.sierracharts.com. Port 10043 | 2022-03-03 17:04:06.417
SC DTC Delayed Exchange Data | Requesting security definition data for: ESH22-CME (ESH22). ID: 1 | 2022-03-03 17:04:06.417
Added historical Intraday data request for ESH22-CME to the queue. | 2022-03-03 17:04:06.417
Intraday data recording state for symbol ESH22-CME is set to download 'Pending'. | 2022-03-03 17:04:06.417
Triggering next historical data download in queue. | 2022-03-03 17:04:06.417
Delaying start of download for ESH22-CME | 2022-03-03 17:04:06.452
DTC Client socket (2) | Creating socket. | 2022-03-03 17:04:06.460
DTC Client socket (2) | New receive buffer size: 5242880 | 2022-03-03 17:04:06.460
DTC Client socket (2) | Connecting to IP: 64.38.174.178. | 2022-03-03 17:04:06.460
SC DTC Delayed Exchange Data | Network connection to server complete. | 2022-03-03 17:04:06.545
SC DTC Delayed Exchange Data | Starting socket receive thread. | 2022-03-03 17:04:06.545
SC DTC Delayed Exchange Data | Sending encoding request to server: Binary VLS. Compression: standard | 2022-03-03 17:04:06.545
SC DTC Delayed Exchange Data | Setting DTC encoding to Binary VLS | 2022-03-03 17:04:06.641
SC DTC Delayed Exchange Data | Sending logon request message. | 2022-03-03 17:04:06.641
SC DTC Delayed Exchange Data | Received logon response. | 2022-03-03 17:04:07.526
SC DTC Delayed Exchange Data | Server Name: SC Realtime Server. | 2022-03-03 17:04:07.526
SC DTC Delayed Exchange Data | Server protocol version: 8. Client protocol version: 8 | 2022-03-03 17:04:07.526
SC DTC Delayed Exchange Data | Successfully connected. | 2022-03-03 17:04:07.526
SC DTC Delayed Exchange Data | Trading is not supported. | 2022-03-03 17:04:07.526
SC DTC Delayed Exchange Data | Restarting real-time data updates for symbol: ESH22-CME -> ESH22 | 2022-03-03 17:04:07.527
SC DTC Delayed Exchange Data | Received security definition for symbol ESH22-CME | 2022-03-03 17:04:07.704
HD Request # 5 | Downloading Intraday chart data for ESH22-CME to the file ESH22-CME.scid. Service: cme | 2022-03-03 17:04:12.320
HD Request # 5 | Download start date-time: 2022-03-03 16:53:33.000000. File last date-time: 2022-03-03 16:53:33.000000 | 2022-03-03 17:04:12.321
HD Request # 5 | Using server: ds23.sierracharts.com port 10150 | 2022-03-03 17:04:12.321
Socket (3) | Creating socket. | 2022-03-03 17:04:12.323
Socket (3) | New receive buffer size: 5242880 | 2022-03-03 17:04:12.323
Socket (3) | Connecting to IP: 216.1.90.130. | 2022-03-03 17:04:12.323
HD Request # 5 | Setting DTC encoding to Binary VLS | 2022-03-03 17:04:12.413
HD Request # 5 | Sending historical data logon request message. | 2022-03-03 17:04:12.413
HD Request # 5 | Requesting Intraday data. Start date-time: 2022-03-03 16:53:33. Record interval: 1. Symbol: ESH22 | 2022-03-03 17:04:12.909
HD Request # 5 | Decompressing data. | 2022-03-03 17:04:12.952
HD Request # 5 | Receiving Intraday data for ESH22-CME starting at 2022-03-03 16:53:33.093000 | 2022-03-03 17:04:12.967
Socket (3) | CloseSocket call. | 2022-03-03 17:04:12.969
Socket (3) | Shutdown started. Waiting for graceful close. | 2022-03-03 17:04:12.969
Historical data download thread signaled to stop. | 2022-03-03 17:04:12.985
HD Request # 5 | Timestamp of first Intraday data file record written: 2022-03-03 16:53:33.093000 | 2022-03-03 17:04:12.985
HD Request # 5 | Received 39 Intraday data records from 2022-03-03 16:53:33.093000 to 2022-03-03 16:54:11.715000 (38.6 seconds) and wrote 39 records for ESH22-CME | 2022-03-03 17:04:12.985
HD Request # 5 | Add time&sales data | Remembered last file record date-time: 2022-03-03 16:54:11.715000 | 2022-03-03 17:04:12.986
HD Request # 5 | Completion time: 0s | 2022-03-03 17:04:12.986
HD Request # 5 | Intraday data download complete for ESH22-CME. Unique request ID: 5 | 2022-03-03 17:04:12.986
Removing historical data download ID 5. | 2022-03-03 17:04:12.986
Real-time Intraday chart data file updates started for ESH22-CME | 2022-03-03 17:04:12.986
Opened cached Intraday file: C:\SierraChart\Data\ESH22-CME.scid. Thread ID: 7744 | 2022-03-03 17:04:12.987
Intraday chart data file opened for ESH22-CME | 2022-03-03 17:04:12.987
HD Request # 5 | Enabling Intraday chart updating for symbol. | 2022-03-03 17:04:12.987

Triggering next historical data download in queue. | 2022-03-03 17:04:12.987
No download requests in the queue to start downloads for. | 2022-03-03 17:04:12.987
Socket (3) | Socket gracefully closed by remote side. | 2022-03-03 17:04:13.010
Socket (3) | Closed. | 2022-03-03 17:04:13.010
[2022-03-03 17:21:55]
John - SC Support - Posts: 36238
Your Global Settings >> Data/Trade Service Settings >> Current Selected Service is set to SC Data - All Services. You need to set this to TransAct WS and enter your trading information in the section below after you apply the change.
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:

Login

Login Page - Create Account