Support Board
Date/Time: Mon, 27 Jan 2025 19:26:13 +0000
Post From: Sierra Chart Close itself when market open
| [2019-02-23 00:11:06] |
| smeb - Posts: 10 |
|
Hi, I have a Sierrachart open all day connected to US market. Approximately 1 day on 3, when the US market open, Sierra Chart close itself ? Markets open at 14:30:00, and at 14:32:30, it says : "SC Data - All Services | Disconnected from the server", then close itself. Here is the full LOG of today, last time it happened : Reading Internal Order ID file. | 2019-02-22 00:02:20 Reading Trade Orders file. | 2019-02-22 00:02:20 Reading Trade Positions file. | 2019-02-22 00:02:20 Account Balance file. | 2019-02-22 00:02:20 Listening on UDP port 22903. | 2019-02-22 00:02:20 Software version: 1842 32-bit | 2019-02-22 00:02:20 Usage end date: 2019-03-25 | 2019-02-22 00:02:20 Enabled for: Advanced Features. | 2019-02-22 00:02:20 Enabled for: Sierra Chart Historical Data Service. | 2019-02-22 00:02:20 Enabled for: Sierra Chart Real-Time Exchange Data Feed. | 2019-02-22 00:02:20 Enabled for: INDEXES_DATA_BARCHART | 2019-02-22 00:02:20 Enabled for: U.S. Equities (NYSE, NASDAQ, AMEX, BATS) | 2019-02-22 00:02:20 Enabled for: BATS (NYSE, NASDAQ) | 2019-02-22 00:02:20 Received 1 data feed usernames. | 2019-02-22 00:02:20 Allow Support for Sierra Chart Data Feeds is enabled. | 2019-02-22 00:02:20 Current selected Data/Trading service: SC Data - All Services | 2019-02-22 00:02:20 Chart Update Interval: 500 | 2019-02-22 00:02:20 Time Zone: +00:00:00 (UTC+00) | 2019-02-22 00:02:20 2019-02-22 00:02:19 Local computer time | 2019-02-22 00:02:20 2019-02-22 00:02:19 Local computer time in UTC | 2019-02-22 00:02:20 2019-02-22 00:02:19 Local computer time in SC Time Zone | 2019-02-22 00:02:20 2019-02-22 00:02:19 Server time in UTC | 2019-02-22 00:02:20 Local computer UTC time and Server UTC time difference: 0 seconds. | 2019-02-22 00:02:20 Program path: C:\Sc_Server3_US\ | 2019-02-22 00:02:20 Data Files path: C:\Sc_Server3_US\Data\ | 2019-02-22 00:02:20 OS Version Number: 6.3 | 2019-02-22 00:02:20 Locale Setting: C | 2019-02-22 00:02:20 DLLs: UserContributedStudies.dll, UserContributedStudies_64.dll | 2019-02-22 00:02:20 Created the DTC Protocol server. | 2019-02-22 00:02:20 DTC Protocol Server listening on port 11099. | 2019-02-22 00:02:20 Created the DTC Protocol historical data server. | 2019-02-22 00:02:20 HD Server Manager | Listening on port 11098 | 2019-02-22 00:02:20 Checking for new symbol settings for service code scdataallservices | 2019-02-22 00:02:20 HTTPS www.sierrachart.com:443 (4) | Creating socket. Using TLS 1.2. | 2019-02-22 00:02:20 HTTPS www.sierrachart.com:443 (4) | Connecting to IP: 46.4.97.203. | 2019-02-22 00:02:20 Received 5 login tokens. | 2019-02-22 00:02:20 HTTPS www.sierrachart.com:443 (5) | Creating socket. Using TLS 1.2. | 2019-02-22 00:02:22 HTTPS www.sierrachart.com:443 (5) | Connecting to IP: 46.4.97.203. | 2019-02-22 00:02:22 Files to Open on Start up | Opening file: CDC_US_1.cht | 2019-02-22 00:02:23 JNJ 5 Min #4 | Reloading chart. | 2019-02-22 00:02:23 JNJ 60 Min #5 | Reloading chart. | 2019-02-22 00:02:23 JNJ 240 Min #6 | Reloading chart. | 2019-02-22 00:02:24 JNJ Daily #7 | Reloading chart. | 2019-02-22 00:02:24 HTTPS login.sierrachart.com:443 (1) | Socket gracefully closed by remote side. | 2019-02-22 00:02:24 HTTPS login.sierrachart.com:443 (1) | Received socket Close event. | 2019-02-22 00:02:24 SC Data - All Services | Disconnected from the server. | 2019-02-22 14:32:30 SC Data - All Services | Disconnected. | 2019-02-22 14:32:30 HD Server | HD Request #85 | Socket: 10 | Symbol: ABT | ServiceCode: DTCSubInstance | RecordInterval: 86400 | Records Served: 3 | Error - Error reading records from daily data file C:\Sc_Server3_US\Data\ABT.dly. Error: No Data for read. End of file. | ClientRequestID: 85 | Username: XXX. | 2019-02-22 14:32:30 DTCServer (3) | 16 bytes remaining in receive buffer when socket closed. | 2019-02-22 14:32:30 DTCServer (3) | Signaling to core to close socket | 2019-02-22 14:32:30 DTCServer (3) | Shutdown started. Waiting for graceful close. | 2019-02-22 14:32:30 DTCServer (8) | Signaling to core to close socket | 2019-02-22 14:32:30 DTCServer (8) | Shutdown started. Waiting for graceful close. | 2019-02-22 14:32:30 DTCServer (9) | Signaling to core to close socket | 2019-02-22 14:32:30 DTCServer (9) | Shutdown started. Waiting for graceful close. | 2019-02-22 14:32:30 DTCServer (8) | Socket gracefully closed by remote side. | 2019-02-22 14:32:30 DTCServer (8) | Closed. | 2019-02-22 14:32:30 Listening socket (896). Port 11099 | Closed. | 2019-02-22 14:32:30 DTCServer (9) | Socket gracefully closed by remote side. | 2019-02-22 14:32:30 DTCServer (9) | Closed. | 2019-02-22 14:32:30 HD Server Manager | Starting exit sequence. | 2019-02-22 14:32:30 HD Server Manager | Closing listening socket for port 11098 | 2019-02-22 14:32:30 Listening socket (900). Port 11098 | Closed. | 2019-02-22 14:32:30 Socket (10) | Socket gracefully closed by remote side. | 2019-02-22 14:32:30 Socket (10) | Received socket Close event. | 2019-02-22 14:32:30 Socket (10) | Signaling to core to close socket | 2019-02-22 14:32:30 Socket (10) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2019-02-22 14:32:30 Socket (10) | Closed. | 2019-02-22 14:32:30 HD Server | Server thread ending. Socket closed. | Username: XXX. | 2019-02-22 14:32:30 HD Server Manager | Signaling the client threads for the historical data server to end. | 2019-02-22 14:32:30 HD Server | Server thread ending. Socket closed. | 2019-02-22 14:32:30 DTCServer (3) | Socket gracefully closed by remote side. | 2019-02-22 14:32:30 DTCServer (3) | Closed. | 2019-02-22 14:32:30 HD Server Manager | All individual server threads successfully ended. | 2019-02-22 14:32:31 HD Server Manager | All client threads have ended. | 2019-02-22 14:32:31 HTTPS historicaldata.sierrachart.com:443 (2) | Signaling to core to close socket | 2019-02-22 14:32:31 HTTPS historicaldata.sierrachart.com:443 (2) | Shutdown started. Waiting for graceful close. | 2019-02-22 14:32:31 This is the last line for the message log because it is being deleted in ExitInstance. | 2019-02-22 14:32:31 Any idea what might cause this ? Regards |