Support Board
Date/Time: Sat, 01 Feb 2025 22:47:38 +0000
Unable to connect to Data feed
View Count: 1065
| [2019-08-11 00:37:52] |
| User345195 - Posts: 7 |
|
Hello, I am unable to connect to the data feed, my message log is pasted below. It seems like something I have done with looping the charts or something? Also I have a payment coming due to you on Aug 11th and was about to make the payment but I noticed something that says as of July 1st I am now able to and you recommend doing order routing directly through you instead of CQG. My FCM is Tradovate which is not on the list in your documentation but I am also with CQG so I just wanted so see if this is possible or not? Thanks for you help, this is my first support ticket so I am not sure if I have sent you all the information you need, please let me know if there is anything else I need to send you in regards to the issue, I look forward to hearing back from you,thanks again. Quinn Van Vranken Reading Internal Order ID file. | 2019-08-10 18:31:16.901 Reading Trade Orders file. | 2019-08-10 18:31:16.968 Reading Trade Positions file. | 2019-08-10 18:31:16.968 Reading Account Balance file. | 2019-08-10 18:31:16.969 UDPListener (1344). Port 22903 | Listening on UDP port 22903. | 2019-08-10 18:31:16.985 Software version: 1928 64-bit | 2019-08-10 18:31:16.985 Usage end date: 2019-08-21 | 2019-08-10 18:31:16.985 Enabled for: Advanced Features. | 2019-08-10 18:31:16.985 Enabled for: Advanced Features 2. | 2019-08-10 18:31:16.985 Enabled for: Sierra Chart Historical Data Service. | 2019-08-10 18:31:16.985 Allow Support for Sierra Chart Data Feeds is enabled. | 2019-08-10 18:31:16.985 Current selected Data/Trading service: CQG WebAPI | 2019-08-10 18:31:16.985 Custom symbol settings values: enabled | 2019-08-10 18:31:16.985 Chart Update Interval: 40 | 2019-08-10 18:31:16.985 Intraday Data Storage Time Unit: 0 | 2019-08-10 18:31:16.985 Time Zone: -06:00:00 (MST-07MDT+01,M3.2.0/02:00,M11.1.0/02:00) | 2019-08-10 18:31:16.985 2019-08-10 18:31:16 Local computer time | 2019-08-10 18:31:16.985 2019-08-11 00:31:16 Local computer time in UTC | 2019-08-10 18:31:16.985 2019-08-10 18:31:16 Local computer time in SC Time Zone | 2019-08-10 18:31:16.985 2019-08-11 00:31:41 Server time in UTC | 2019-08-10 18:31:16.985 Local computer UTC time and Server UTC time difference: 25 seconds. | 2019-08-10 18:31:16.985 Program path: C:\SierraChart\SierraChartTransActMA\ | 2019-08-10 18:31:16.985 Data Files path: C:\SierraChart\SierraChartTransActMA\Data\ | 2019-08-10 18:31:16.985 OS Version Number: 10.0 | 2019-08-10 18:31:16.985 Locale Setting: C | 2019-08-10 18:31:16.985 DLLs: UserContributedStudies.dll, UserContributedStudies_64.dll, VCValueLevels.dll | 2019-08-10 18:31:16.986 Created the DTC Protocol server. | 2019-08-10 18:31:16.996 DTC Protocol Server listening on port 11099. | 2019-08-10 18:31:16.997 Created the DTC Protocol historical data server. | 2019-08-10 18:31:16.997 HD Server Manager | Listening on port 11098 | 2019-08-10 18:31:16.997 Checking for new symbol settings. Requested symbol settings MD5 for service code cqg. Request ID: 1. | 2019-08-10 18:31:16.998 HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (4) | Creating socket. Using TLS 1.2. | 2019-08-10 18:31:16.998 HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (4) | Connecting to IP: 46.4.97.203. | 2019-08-10 18:31:16.998 HTTPS connection ID:1 to login.sierrachart.com:443 for request ID:1 (1) | Shutdown started. Waiting for graceful close. | 2019-08-10 18:31:17.020 HTTPS connection ID:1 to login.sierrachart.com:443 for request ID:1 (1) | Socket gracefully closed by remote side. | 2019-08-10 18:31:17.175 HTTPS connection ID:1 to login.sierrachart.com:443 for request ID:1 (1) | Closed. | 2019-08-10 18:31:17.175 Received 5 login tokens. | 2019-08-10 18:31:17.619 Symbol settings MD5 received. Request ID: 1. | 2019-08-10 18:31:17.702 Symbol settings are up-to-date for cqg. | 2019-08-10 18:31:17.702 HTTPS connection ID:2 to www.sierrachart.com:443 for request ID:2 (2) | Shutdown started. Waiting for graceful close. | 2019-08-10 18:31:17.865 HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (4) | Shutdown started. Waiting for graceful close. | 2019-08-10 18:31:17.965 HTTPS connection ID:2 to www.sierrachart.com:443 for request ID:2 (2) | Socket gracefully closed by remote side. | 2019-08-10 18:31:18.027 HTTPS connection ID:2 to www.sierrachart.com:443 for request ID:2 (2) | Closed. | 2019-08-10 18:31:18.027 HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (4) | Socket gracefully closed by remote side. | 2019-08-10 18:31:18.124 HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (4) | Closed. | 2019-08-10 18:31:18.124 HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (1) | Creating socket. Using TLS 1.2. | 2019-08-10 18:31:18.984 HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (1) | Connecting to IP: 46.4.97.203. | 2019-08-10 18:31:18.984 HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (1) | Shutdown started. Waiting for graceful close. | 2019-08-10 18:31:19.933 HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (1) | Socket gracefully closed by remote side. | 2019-08-10 18:31:20.094 HTTPS connection ID:1 to www.sierrachart.com:443 for request ID:1 (1) | Closed. | 2019-08-10 18:31:20.095 CQG WebAPI | Connecting to server api.cqg.com | 2019-08-10 18:31:22.681 CQG WebSocket | Connecting to WebSocket server. | 2019-08-10 18:31:22.681 CQG WebSocket socket (1) | Creating socket. Using TLS 1.2. | 2019-08-10 18:31:22.762 CQG WebSocket socket (1) | Connecting to IP: 208.48.16.35. | 2019-08-10 18:31:22.762 CQG WebSocket | Opening WebSocket. | 2019-08-10 18:31:22.815 CQG WebSocket | Sending WebSocket handshake. | 2019-08-10 18:31:22.815 CQG WebSocket | Server header | HTTP/1.1 101 Switching Protocols | 2019-08-10 18:31:23.032 CQG WebSocket | Server header | Connection: upgrade | 2019-08-10 18:31:23.032 CQG WebSocket | Server header | Sec-WebSocket-Accept: mmkrOOS7tJwXwNON+bJlxiUf8Bc= | 2019-08-10 18:31:23.032 CQG WebSocket | Server header | Server: WebSocket++/0.7.0 | 2019-08-10 18:31:23.032 CQG WebSocket | Server header | Upgrade: websocket | 2019-08-10 18:31:23.032 CQG WebSocket | Server header | | 2019-08-10 18:31:23.032 CQG WebSocket | Web socket state is now open. | 2019-08-10 18:31:23.032 CQG WebAPI | WebSocket connected. | 2019-08-10 18:31:23.032 CQG WebAPI | Sending market data logon message. | 2019-08-10 18:31:23.032 Service connection timed out. Will disconnect and retry. | 2019-08-10 18:32:22.678 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2019-08-10 18:32:22.678 Select 'File >> Disconnect' to prevent further connection attempts. | 2019-08-10 18:32:22.678 CQG WebSocket | WebSocket closed. | 2019-08-10 18:32:22.693 CQG WebAPI | WebSocket closed. | 2019-08-10 18:32:22.693 CQG WebAPI | Disconnected. | 2019-08-10 18:32:22.693 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2019-08-10 18:32:22.693 CQG WebSocket socket (1) | Write in progress. Shutdown being delayed. | 2019-08-10 18:32:22.694 CQG WebSocket socket (1) | Write has completed. Shutdown being performed. | 2019-08-10 18:32:22.745 CQG WebSocket socket (1) | Shutdown started. Waiting for graceful close. | 2019-08-10 18:32:22.745 CQG WebSocket socket (1) | Socket gracefully closed by remote side. | 2019-08-10 18:32:22.801 CQG WebSocket socket (1) | Closed. | 2019-08-10 18:32:22.801 CQG WebAPI | Connecting to server api.cqg.com | 2019-08-10 18:32:25.724 CQG WebSocket | Connecting to WebSocket server. | 2019-08-10 18:32:25.724 CQG WebSocket socket (1) | Creating socket. Using TLS 1.2. | 2019-08-10 18:32:25.726 CQG WebSocket socket (1) | Connecting to IP: 208.48.16.35. | 2019-08-10 18:32:25.726 CQG WebSocket | Opening WebSocket. | 2019-08-10 18:32:25.781 CQG WebSocket | Sending WebSocket handshake. | 2019-08-10 18:32:25.781 CQG WebSocket | Server header | HTTP/1.1 101 Switching Protocols | 2019-08-10 18:32:26.012 CQG WebSocket | Server header | Connection: upgrade | 2019-08-10 18:32:26.012 CQG WebSocket | Server header | Sec-WebSocket-Accept: bO/5tBxedQ7QTM7ghW2ejTkUbUw= | 2019-08-10 18:32:26.012 CQG WebSocket | Server header | Server: WebSocket++/0.7.0 | 2019-08-10 18:32:26.012 CQG WebSocket | Server header | Upgrade: websocket | 2019-08-10 18:32:26.012 CQG WebSocket | Server header | | 2019-08-10 18:32:26.012 CQG WebSocket | Web socket state is now open. | 2019-08-10 18:32:26.012 CQG WebAPI | WebSocket connected. | 2019-08-10 18:32:26.012 CQG WebAPI | Sending market data logon message. | 2019-08-10 18:32:26.012 CQG WebAPI | Market data logon unsuccessful. Server message: Trade routing is not available now. Contact customer support for assistance. | 2019-08-10 18:32:29.260 CQG WebSocket socket (1) | Write in progress. Shutdown being delayed. | 2019-08-10 18:32:29.279 CQG WebAPI | Disconnected. | 2019-08-10 18:32:29.279 CQG WebSocket | WebSocket closed. | 2019-08-10 18:32:29.279 CQG WebAPI | WebSocket closed. | 2019-08-10 18:32:29.279 CQG WebSocket socket (1) | Write has completed. Shutdown being performed. | 2019-08-10 18:32:29.332 CQG WebSocket socket (1) | Shutdown started. Waiting for graceful close. | 2019-08-10 18:32:29.333 CQG WebSocket socket (1) | Socket gracefully closed by remote side. | 2019-08-10 18:32:29.383 CQG WebSocket socket (1) | Closed. | 2019-08-10 18:32:29.383 CQG WebAPI | Connecting to server api.cqg.com | 2019-08-10 18:35:34.100 CQG WebSocket | Connecting to WebSocket server. | 2019-08-10 18:35:34.100 CQG WebSocket socket (1) | Creating socket. Using TLS 1.2. | 2019-08-10 18:35:34.180 CQG WebSocket socket (1) | Connecting to IP: 208.48.16.35. | 2019-08-10 18:35:34.181 CQG WebSocket | Opening WebSocket. | 2019-08-10 18:35:34.233 CQG WebSocket | Sending WebSocket handshake. | 2019-08-10 18:35:34.233 CQG WebSocket | Server header | HTTP/1.1 101 Switching Protocols | 2019-08-10 18:35:34.460 CQG WebSocket | Server header | Connection: upgrade | 2019-08-10 18:35:34.460 CQG WebSocket | Server header | Sec-WebSocket-Accept: 8tdr7SVOjoPAgPqCZdM7BKZq61w= | 2019-08-10 18:35:34.460 CQG WebSocket | Server header | Server: WebSocket++/0.7.0 | 2019-08-10 18:35:34.460 CQG WebSocket | Server header | Upgrade: websocket | 2019-08-10 18:35:34.460 CQG WebSocket | Server header | | 2019-08-10 18:35:34.460 CQG WebSocket | Web socket state is now open. | 2019-08-10 18:35:34.460 CQG WebAPI | WebSocket connected. | 2019-08-10 18:35:34.460 CQG WebAPI | Sending market data logon message. | 2019-08-10 18:35:34.460 CQG WebAPI | Market data logon unsuccessful. Server message: Trade routing is not available now. Contact customer support for assistance. | 2019-08-10 18:36:30.189 CQG WebAPI | Disconnected. | 2019-08-10 18:36:30.209 CQG WebSocket | WebSocket closed. | 2019-08-10 18:36:30.209 CQG WebAPI | WebSocket closed. | 2019-08-10 18:36:30.209 CQG WebSocket socket (1) | Write in progress. Shutdown being delayed. | 2019-08-10 18:36:30.209 CQG WebSocket socket (1) | Write has completed. Shutdown being performed. | 2019-08-10 18:36:30.262 CQG WebSocket socket (1) | Shutdown started. Waiting for graceful close. | 2019-08-10 18:36:30.262 CQG WebSocket socket (1) | Socket gracefully closed by remote side. | 2019-08-10 18:36:30.320 CQG WebSocket socket (1) | Closed. | 2019-08-10 18:36:30.320 |
| [2019-08-11 05:31:59] |
| |
|
In your case you need to stay on CQG. In regards to this error here: CQG WebAPI | Market data logon unsuccessful. Server message: Trade routing is not available now. Contact customer support for assistance. | 2019-08-10 18:36:30.189
Refer to item 11 here: CQG Trading Platform Service: Common Error Messages Your Sierra Chart account does expire August 21, 2019 so you will need to pay for more usage time before then if you want to continue. 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: