Support Board
Date/Time: Mon, 25 Nov 2024 10:59:45 +0000
Unable to connect to data feed
View Count: 350
| [2024-02-07 11:48:04] |
| ciaranclear1982 - Posts: 5 |
|
Hi, I am having issues connecting to my date feed. When I click 'Connect to Data feed' a service connection error shows up. I have tried restarting Sierra and checking that there is a data feed connected but I am still having the same issue? Thanks in advance |
| [2024-02-07 14:30:12] |
| Sierra_Chart Engineering - Posts: 17172 |
|
Follow the instructions here to clear the Message Log: Message Log: Clearing the Message Log Connect to the data feed: Select "File >> Disconnect" Select "File >> Connect to Data Feed" After about 30 seconds, provide a copy of the Message Log following these instructions: Support Board Posting Information: How to Post Your Message Log (Required In Some Cases) We will then determine what the problem is. 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, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-02-07 17:01:47] |
| ciaranclear1982 - Posts: 5 |
|
2024-02-07 16:56:51.515 | Software version: 2597 64-bit 2024-02-07 16:56:51.515 | Primary Thread ID: 8316 2024-02-07 16:56:51.515 | Usage end date: 2024-02-25 2024-02-07 16:56:51.515 | Enabled for: Advanced Features 2. 2024-02-07 16:56:51.515 | Enabled for: Sierra Chart Historical Data Service. 2024-02-07 16:56:51.515 | Enabled for: Denali Real-Time Exchange Data Feed. 2024-02-07 16:56:51.515 | Enabled for: Delayed Denali Exchange Data Feed. 2024-02-07 16:56:51.515 | Enabled for exchange2: CME (Trading Account Required) 2024-02-07 16:56:51.515 | Enabled for exchange2: CBOT (Trading Account Required) 2024-02-07 16:56:51.515 | Enabled for exchange2: COMEX (Trading Account Required) 2024-02-07 16:56:51.515 | Enabled for exchange2: NYMEX (Trading Account Required) 2024-02-07 16:56:51.515 | Allow Support for Sierra Chart Data Feeds is enabled. 2024-02-07 16:56:51.515 | Current selected Data/Trading service: CQG WebAPI 2024-02-07 16:56:51.515 | Custom symbol settings values: enabled 2024-02-07 16:56:51.515 | Chart Update Interval: 500 2024-02-07 16:56:51.515 | Intraday Data Storage Time Unit: 0 2024-02-07 16:56:51.515 | Time Zone: +00:00:00 (UTC+00) 2024-02-07 16:56:51.515 | 2024-02-07 16:56:51 Local computer time in UTC 2024-02-07 16:56:51.515 | 2024-02-07 16:56:51 Local computer time in SC Time Zone 2024-02-07 16:56:51.515 | 2024-02-07 15:18:01 Server time in UTC 2024-02-07 16:56:51.515 | Local computer UTC time and Server UTC time difference: 1 seconds. 2024-02-07 16:56:51.515 | Program path: C:\SierraChart\ 2024-02-07 16:56:51.515 | Data Files path: C:\SierraChart\Data\ 2024-02-07 16:56:51.516 | OS Version Number: 10.0 2024-02-07 16:56:51.516 | Locale Setting: C 2024-02-07 16:56:51.516 | DLLs: UserContributedStudies_64.dll 2024-02-07 16:56:51.516 | Allowed protected custom studies: 2024-02-07 16:56:51.516 | Crash reporter started: true 2024-02-07 16:56:51.516 | 2024-02-07 16:57:18.334 | 2024-02-07 16:57:18.335 | CQG WebAPI | Connecting to server api.cqg.com 2024-02-07 16:57:18.335 | CQG WebSocket | Connecting to WebSocket server api.cqg.com:443 2024-02-07 16:57:18.658 | CQG WebSocket socket (1) | Creating socket. Using TLS 1.2. 2024-02-07 16:57:18.658 | CQG WebSocket socket (1) | New receive buffer size: 0 2024-02-07 16:57:18.658 | CQG WebSocket socket (1) | Connecting to IP: 195.166.124.175. 2024-02-07 16:57:19.678 | CQG WebSocket | Opening WebSocket. 2024-02-07 16:57:19.678 | CQG WebSocket | Sending WebSocket handshake. 2024-02-07 16:57:22.697 | CQG WebSocket | Server header | HTTP/1.1 101 Switching Protocols 2024-02-07 16:57:22.697 | CQG WebSocket | Server header | Connection: Upgrade 2024-02-07 16:57:22.697 | CQG WebSocket | Server header | Sec-WebSocket-Accept: teS5oSnYMg5HvLX55qLbDg3Js2c= 2024-02-07 16:57:22.697 | CQG WebSocket | Server header | Server: WebSocket++/0.8.2 2024-02-07 16:57:22.697 | CQG WebSocket | Server header | Upgrade: websocket 2024-02-07 16:57:22.697 | CQG WebSocket | Server header | 2024-02-07 16:57:22.697 | CQG WebSocket | Web socket state is now open. 2024-02-07 16:57:22.697 | CQG WebAPI | WebSocket connected. 2024-02-07 16:57:22.697 | CQG WebAPI | Sending market data logon message. 2024-02-07 16:57:23.708 | CQG WebAPI | Logon unsuccessful. Server message: Your logon is disabled. Contact your FCM. 2024-02-07 16:57:23.766 | CQG WebSocket socket (1) | CloseSocket call. 2024-02-07 16:57:23.767 | CQG WebAPI | Disconnected. 2024-02-07 16:57:23.767 | CQG WebAPI | Not reconnecting due to connection error condition. 2024-02-07 16:57:23.767 | CQG WebSocket | WebSocket closed. 2024-02-07 16:57:23.767 | CQG WebAPI | WebSocket closed. 2024-02-07 16:57:23.767 | CQG WebSocket socket (1) | Write in progress. Shutdown being delayed. PendingSize=0 2024-02-07 16:57:24.717 | CQG WebSocket socket (1) | Write has completed. Shutdown being performed. 2024-02-07 16:57:24.718 | CQG WebSocket socket (1) | Shutdown started. Waiting for graceful close. 2024-02-07 16:57:25.727 | CQG WebSocket socket (1) | Socket gracefully closed by remote side. 2024-02-07 16:57:25.728 | CQG WebSocket socket (1) | Closed. 2024-02-07 16:57:54.616 | 2024-02-07 16:57:54.616 | CQG WebAPI | Connecting to server api.cqg.com 2024-02-07 16:57:54.616 | CQG WebSocket | Connecting to WebSocket server api.cqg.com:443 2024-02-07 16:57:54.620 | CQG WebSocket socket (1) | Creating socket. Using TLS 1.2. 2024-02-07 16:57:54.620 | CQG WebSocket socket (1) | New receive buffer size: 0 2024-02-07 16:57:54.620 | CQG WebSocket socket (1) | Connecting to IP: 195.166.124.175. 2024-02-07 16:57:55.018 | CQG WebSocket | Opening WebSocket. 2024-02-07 16:57:55.018 | CQG WebSocket | Sending WebSocket handshake. 2024-02-07 16:57:58.048 | CQG WebSocket | Server header | HTTP/1.1 101 Switching Protocols 2024-02-07 16:57:58.048 | CQG WebSocket | Server header | Connection: Upgrade 2024-02-07 16:57:58.048 | CQG WebSocket | Server header | Sec-WebSocket-Accept: RaIT/ZKhw2/A+S75x8fLBamjfe8= 2024-02-07 16:57:58.048 | CQG WebSocket | Server header | Server: WebSocket++/0.8.2 2024-02-07 16:57:58.048 | CQG WebSocket | Server header | Upgrade: websocket 2024-02-07 16:57:58.048 | CQG WebSocket | Server header | 2024-02-07 16:57:58.048 | CQG WebSocket | Web socket state is now open. 2024-02-07 16:57:58.048 | CQG WebAPI | WebSocket connected. 2024-02-07 16:57:58.048 | CQG WebAPI | Sending market data logon message. 2024-02-07 16:57:59.059 | CQG WebAPI | Logon unsuccessful. Server message: Your logon is disabled. Contact your FCM. 2024-02-07 16:57:59.123 | CQG WebSocket socket (1) | CloseSocket call. 2024-02-07 16:57:59.123 | CQG WebAPI | Disconnected. 2024-02-07 16:57:59.123 | CQG WebAPI | Not reconnecting due to connection error condition. 2024-02-07 16:57:59.123 | CQG WebSocket | WebSocket closed. 2024-02-07 16:57:59.123 | CQG WebAPI | WebSocket closed. 2024-02-07 16:57:59.124 | CQG WebSocket socket (1) | Write in progress. Shutdown being delayed. PendingSize=0 2024-02-07 16:58:00.068 | CQG WebSocket socket (1) | Write has completed. Shutdown being performed. 2024-02-07 16:58:00.068 | CQG WebSocket socket (1) | Shutdown started. Waiting for graceful close. 2024-02-07 16:58:01.077 | CQG WebSocket socket (1) | Socket gracefully closed by remote side. 2024-02-07 16:58:01.077 | CQG WebSocket socket (1) | Closed. 2024-02-07 16:58:59.127 | 2024-02-07 16:58:59.128 | CQG WebAPI | Connecting to server api.cqg.com 2024-02-07 16:58:59.128 | CQG WebSocket | Connecting to WebSocket server api.cqg.com:443 2024-02-07 16:58:59.129 | CQG WebSocket socket (1) | Creating socket. Using TLS 1.2. 2024-02-07 16:58:59.129 | CQG WebSocket socket (1) | New receive buffer size: 0 2024-02-07 16:58:59.129 | CQG WebSocket socket (1) | Connecting to IP: 195.166.124.175. 2024-02-07 16:58:59.658 | CQG WebSocket | Opening WebSocket. 2024-02-07 16:58:59.658 | CQG WebSocket | Sending WebSocket handshake. 2024-02-07 16:59:02.688 | CQG WebSocket | Server header | HTTP/1.1 101 Switching Protocols 2024-02-07 16:59:02.688 | CQG WebSocket | Server header | Connection: Upgrade 2024-02-07 16:59:02.688 | CQG WebSocket | Server header | Sec-WebSocket-Accept: XFT9BEK+qffomMDUCTDk4ABuNa8= 2024-02-07 16:59:02.688 | CQG WebSocket | Server header | Server: WebSocket++/0.8.2 2024-02-07 16:59:02.688 | CQG WebSocket | Server header | Upgrade: websocket 2024-02-07 16:59:02.688 | CQG WebSocket | Server header | 2024-02-07 16:59:02.688 | CQG WebSocket | Web socket state is now open. 2024-02-07 16:59:02.688 | CQG WebAPI | WebSocket connected. 2024-02-07 16:59:02.688 | CQG WebAPI | Sending market data logon message. 2024-02-07 16:59:03.698 | CQG WebAPI | Logon unsuccessful. Server message: Your logon is disabled. Contact your FCM. 2024-02-07 16:59:03.738 | CQG WebSocket socket (1) | CloseSocket call. 2024-02-07 16:59:03.738 | CQG WebAPI | Disconnected. 2024-02-07 16:59:03.738 | CQG WebAPI | Not reconnecting due to connection error condition. 2024-02-07 16:59:03.738 | CQG WebSocket | WebSocket closed. 2024-02-07 16:59:03.738 | CQG WebAPI | WebSocket closed. 2024-02-07 16:59:03.738 | CQG WebSocket socket (1) | Write in progress. Shutdown being delayed. PendingSize=0 2024-02-07 16:59:04.708 | CQG WebSocket socket (1) | Write has completed. Shutdown being performed. 2024-02-07 16:59:04.708 | CQG WebSocket socket (1) | Shutdown started. Waiting for graceful close. 2024-02-07 16:59:05.717 | CQG WebSocket socket (1) | Socket gracefully closed by remote side. 2024-02-07 16:59:05.717 | CQG WebSocket socket (1) | Closed. |
| [2024-02-07 17:02:40] |
| ciaranclear1982 - Posts: 5 |
|
Hi. I have just sent through the message log for analysis. Thanks
|
| [2024-02-07 17:26:04] |
| John - SC Support - Posts: 36238 |
|
The issue is the following from your log: 2024-02-07 16:57:23.708 | CQG WebAPI | Logon unsuccessful. Server message: Your logon is disabled. Contact your FCM.
Your CQG account has been disabled by your broker. You need to ask your broker about this. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-03-10 21:55:18] |
| Sierra_Chart Engineering - Posts: 17172 |
|
To access historical and streaming market data independent from your Trading service. Follow these instructions. Set "Global Settings >> Data/Trade Service Settings >> Current Selected Service" to "SC Data-All Services". Press "OK" And then translate the symbols in your Chartbooks and Sierra Chart using this "Edit' menu command: Edit Menu: Edit >> Translate Symbols To Current Service (Translate Symbols to Current Service) You can then use the data provided by Sierra Chart independent of your trading 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, 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: