Support Board
Date/Time: Sat, 18 Jan 2025 19:44:59 +0000
CQG Fix not connecting
View Count: 1188
| [2018-02-26 21:23:03] |
| User190501 - Posts: 96 |
|
CQG FIX is not connecting - though on the same machine Tradingview can connect to CQG. The following is the log: ------------------------------------------------------------------------------ Reading Internal Order ID file. | 2018-02-26 21:18:41 Reading Trade Orders file. | 2018-02-26 21:18:41 Reading Trade Positions file. | 2018-02-26 21:18:41 Listening on UDP port 22904. | 2018-02-26 21:18:41 Software version: 1706 32-bit | 2018-02-26 21:18:41 Enabled for: Advanced Features. | 2018-02-26 21:18:41 Enabled for: Sierra Chart Historical Data Service. | 2018-02-26 21:18:41 Allow Support for Sierra Chart Data Feeds is enabled. | 2018-02-26 21:18:41 Current selected Data/Trading service: CQG FIX Trading | 2018-02-26 21:18:41 Chart Update Interval: 500 | 2018-02-26 21:18:41 Data/Trade Service Settings automatically set. | 2018-02-26 21:18:41 Time Zone: +00:00:00 (UTC+00) | 2018-02-26 21:18:41 2018-02-26 16:18:41 Local computer time | 2018-02-26 21:18:41 2018-02-26 21:18:41 Local computer time in UTC | 2018-02-26 21:18:41 2018-02-26 21:18:41 Local computer time in SC Time Zone | 2018-02-26 21:18:41 2018-02-26 21:18:39 Server time in UTC | 2018-02-26 21:18:41 Local computer UTC time and Server UTC time difference: 0 seconds. | 2018-02-26 21:18:41 Program path: C:\SierraChart\ | 2018-02-26 21:18:41 Data Files path: C:\SierraChart\Data\ | 2018-02-26 21:18:41 OS Version Number: 6.1 | 2018-02-26 21:18:41 Locale Setting: C | 2018-02-26 21:18:41 Checking for new symbol settings for service code cqg | 2018-02-26 21:18:41 HTTPS connection to www.sierrachart.com:443 (4) | Creating socket. Using TLS 1.2. | 2018-02-26 21:18:41 HTTPS connection to www.sierrachart.com:443 (4) | Connecting to IP: 204.15.192.108. | 2018-02-26 21:18:41 Symbol settings are up-to-date for cqg | 2018-02-26 21:18:41 Received 5 login tokens. | 2018-02-26 21:18:42 HTTPS connection to www.sierrachart.com:443 (5) | Creating socket. Using TLS 1.2. | 2018-02-26 21:18:43 HTTPS connection to www.sierrachart.com:443 (5) | Connecting to IP: 204.15.192.108. | 2018-02-26 21:18:43 HTTPS connection to www.sierrachart.com:443 (4) | Socket gracefully closed by remote side. | 2018-02-26 21:18:46 HTTPS connection to www.sierrachart.com:443 (4) | Received socket Close event. | 2018-02-26 21:18:46 HTTPS connection to www.sierrachart.com:443 (4) | Initiating close of socket by core. | 2018-02-26 21:18:46 HTTPS connection to www.sierrachart.com:443 (4) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2018-02-26 21:18:46 HTTPS connection to www.sierrachart.com:443 (4) | Closed. | 2018-02-26 21:18:46 HTTPS connection to www.sierrachart.com:443 (2) | Socket gracefully closed by remote side. | 2018-02-26 21:18:47 HTTPS connection to www.sierrachart.com:443 (2) | Received socket Close event. | 2018-02-26 21:18:47 HTTPS connection to www.sierrachart.com:443 (2) | Initiating close of socket by core. | 2018-02-26 21:18:47 HTTPS connection to www.sierrachart.com:443 (2) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2018-02-26 21:18:47 HTTPS connection to www.sierrachart.com:443 (2) | Closed. | 2018-02-26 21:18:47 HTTPS connection to www.sierrachart.com:443 (5) | Socket gracefully closed by remote side. | 2018-02-26 21:18:48 HTTPS connection to www.sierrachart.com:443 (5) | Received socket Close event. | 2018-02-26 21:18:48 HTTPS connection to www.sierrachart.com:443 (5) | Initiating close of socket by core. | 2018-02-26 21:18:48 HTTPS connection to www.sierrachart.com:443 (5) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2018-02-26 21:18:48 HTTPS connection to www.sierrachart.com:443 (5) | Closed. | 2018-02-26 21:18:48 CQG FIX: Connecting to fixapi.cqgtrader.com. Port: 6925. | 2018-02-26 21:18:51 CQG FIX socket (6) | Creating socket. Using TLS 1.2. | 2018-02-26 21:18:51 CQG FIX socket (6) | Connecting to IP: 208.48.16.214. | 2018-02-26 21:18:51 CQG FIX: Sending the Logon message. | 2018-02-26 21:18:52 CQG FIX socket (6) | Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine. | 2018-02-26 21:19:11 * CQG FIX socket (6) | Socket gracefully closed by remote side. | 2018-02-26 21:19:11 CQG FIX socket (6) | Received socket Close event. | 2018-02-26 21:19:11 CQG FIX socket (6) | Initiating close of socket by core. | 2018-02-26 21:19:11 CQG FIX: Socket connection was closed without any logout messages sent or received. | 2018-02-26 21:19:11 CQG FIX socket (6) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2018-02-26 21:19:11 CQG FIX socket (6) | Closed. | 2018-02-26 21:19:11 CQG FIX Trading | Disconnected. | 2018-02-26 21:19:11 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2018-02-26 21:19:11 Select 'File >> Disconnect' to prevent further connection attempts. | 2018-02-26 21:19:11 CQG FIX Trading | Disconnected. | 2018-02-26 21:19:11 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2018-02-26 21:19:11 CQG FIX: Connecting to fixapi.cqgtrader.com. Port: 6925. | 2018-02-26 21:19:14 CQG FIX socket (7) | Creating socket. Using TLS 1.2. | 2018-02-26 21:19:14 CQG FIX socket (7) | Connecting to IP: 208.48.16.214. | 2018-02-26 21:19:14 CQG FIX: Sending the Logon message. | 2018-02-26 21:19:14 CQG FIX socket (7) | Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine. | 2018-02-26 21:19:33 * CQG FIX socket (7) | Socket gracefully closed by remote side. | 2018-02-26 21:19:33 CQG FIX socket (7) | Received socket Close event. | 2018-02-26 21:19:33 CQG FIX socket (7) | Initiating close of socket by core. | 2018-02-26 21:19:33 CQG FIX: Socket connection was closed without any logout messages sent or received. | 2018-02-26 21:19:33 CQG FIX socket (7) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2018-02-26 21:19:33 CQG FIX socket (7) | Closed. | 2018-02-26 21:19:33 CQG FIX Trading | Disconnected. | 2018-02-26 21:19:33 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2018-02-26 21:19:33 Select 'File >> Disconnect' to prevent further connection attempts. | 2018-02-26 21:19:33 CQG FIX Trading | Disconnected. | 2018-02-26 21:19:33 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2018-02-26 21:19:33 CQG FIX: Connecting to fixapi.cqgtrader.com. Port: 6925. | 2018-02-26 21:19:36 CQG FIX socket (8) | Creating socket. Using TLS 1.2. | 2018-02-26 21:19:36 CQG FIX socket (8) | Connecting to IP: 208.48.16.214. | 2018-02-26 21:19:36 CQG FIX: Sending the Logon message. | 2018-02-26 21:19:36 |
| [2018-02-26 23:00:24] |
| |
|
This is very unusual: CQG FIX: Sending the Logon message. | 2018-02-26 21:19:14 CQG FIX socket (7) | Close event error. Windows error code 10053: An established connection was aborted by the software in your host machine. | 2018-02-26 Can you provide us your CQG username through an Account Support Ticket: https://www.sierrachart.com/usercp.php?page=SupportTickets We will then contact CQG about this. 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 |
| [2018-02-27 02:18:13] |
| |
|
This is what CQG said: I checked our server and we didn’t receive your logon request. this Windows error code 10053 could be caused by data transmission timeout or protocol error. Could you please first try to ping to fixapi.cqgtrader.com port 6925 and see if the connection is stable. If the connection is fine, please send me your logon message. Thinking about this, this does make sense. We do think this problem is caused by some firewall software on your side. Are you running any firewall software on your computer other than the standard Windows firewall? 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: 2018-02-27 02:18:23
|
To post a message in this thread, you need to log in with your Sierra Chart account: