Support Board
Date/Time: Sat, 11 Jan 2025 14:49:46 +0000
Can't log
View Count: 1409
| [2016-12-12 13:16:11] |
| User550674 - Posts: 14 |
|
Can't get data feed. When I was able to. I saved my set up and it would never save. I would have to re-create my whole platform.
|
| [2016-12-12 13:21:23] |
| |
|
We want you to restart Sierra Chart and then connect with File >> Connect to Data Feed. After that provide a copy of the Message Log following these instructions here: https://www.sierrachart.com/index.php?page=PostingInformation.php#MessageLog I saved my set up and it would never save.
Charts are saved as part of Chartbooks which are documented here:Chartbooks (Workspaces) Here are the specific instructions to save a Chartbook: Chartbooks (Workspaces): To Save a Chartbook If there is an error saving the Chartbook it will be given in Window >> Message Log. If so, what is the error message? It is also unheard of to have an issue saving Chartbooks. So it is unlikely that is 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: 2016-12-12 13:22:19
|
| [2016-12-12 13:32:14] |
| User550674 - Posts: 14 |
|
I have tried to do as you wish numerous times prior to reaching out and after and caught in an endless loop trying to log on.
|
| [2016-12-12 13:38:21] |
| User550674 - Posts: 14 |
|
Reading Internal Order ID file. | 2016-12-12 08:37:09 Reading Trade Orders file. | 2016-12-12 08:37:09 Reading Trade Positions file. | 2016-12-12 08:37:09 Software version: 1490 | 2016-12-12 08:37:09 Uses New Spreadsheets | 2016-12-12 08:37:09 Usage end date: 2016-12-15 | 2016-12-12 08:37:09 Enabled for: Advanced Features. | 2016-12-12 08:37:09 Enabled for: Advanced Features 2. | 2016-12-12 08:37:09 Enabled for: Sierra Chart Historical Data Service. | 2016-12-12 08:37:09 Allow Support for Sierra Chart Data Feeds is enabled. | 2016-12-12 08:37:09 Current selected Data/Trading service: CQG WebAPI | 2016-12-12 08:37:09 Chart Update Interval: 500 | 2016-12-12 08:37:09 Time Zone: -05:00:00 (EST-05EDT+01,M3.2.0/02:00,M11.1.0/02:00) | 2016-12-12 08:37:09 2016-12-12 08:37:12 Local computer time | 2016-12-12 08:37:09 2016-12-12 13:37:12 Local computer time in UTC | 2016-12-12 08:37:09 2016-12-12 08:37:12 Local computer time in SC Time Zone | 2016-12-12 08:37:09 2016-12-12 13:36:45 Server time in UTC | 2016-12-12 08:37:09 Local computer UTC time and Server UTC time difference: 27 seconds. | 2016-12-12 08:37:09 Program path: C:\SierraChart\ | 2016-12-12 08:37:09 Data Files path: C:\SierraChart\Data\ | 2016-12-12 08:37:09 OS Version Number: 6.1 | 2016-12-12 08:37:09 Locale Setting: C | 2016-12-12 08:37:09 Created the DTC Protocol server. | 2016-12-12 08:37:09 DTC Protocol Server listening on port 11099. | 2016-12-12 08:37:09 Created the DTC Protocol historical data server. | 2016-12-12 08:37:09 HD Server Manager | Listening on port 11098 | 2016-12-12 08:37:09 Checking for new symbol settings for cqg | 2016-12-12 08:37:09 HTTPS connection to www.sierrachart.com:443 (0) | Resolved address sierrachart.com to IP 5.9.8.236. | 2016-12-12 08:37:09 HTTPS connection to www.sierrachart.com:443 (3) | Connected. | 2016-12-12 08:37:09 HTTPS connection to www.sierrachart.com:443 (3) | Starting TLS 1.2 connection. | 2016-12-12 08:37:09 HTTPS connection to www.sierrachart.com:443 (3) | SSL connection established. | 2016-12-12 08:37:09 Symbol settings are up-to-date for cqg | 2016-12-12 08:37:13 CQG WebAPI | Connecting to market data server demoapi.cqg.com | 2016-12-12 08:37:18 CQG WebAPI | Connecting to websocket server. | 2016-12-12 08:37:18 CQG WebAPI websocket (0) | Resolved address demoapi.cqg.com to IP 208.48.16.32. | 2016-12-12 08:37:18 CQG WebAPI websocket (4) | Connected. | 2016-12-12 08:37:18 CQG WebAPI websocket (4) | Starting SSL 3/2 connection. | 2016-12-12 08:37:18 CQG WebAPI websocket (4) | SSL connection established. | 2016-12-12 08:37:18 CQG WebAPI | Opening websocket. | 2016-12-12 08:37:18 CQG WebAPI | Sending websocket handshake. | 2016-12-12 08:37:18 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-12-12 08:37:18 CQG WebAPI | Web socket state is now open. | 2016-12-12 08:37:18 CQG WebAPI | Websocket connected. | 2016-12-12 08:37:18 CQG WebAPI | Sending market data logon message. | 2016-12-12 08:37:18 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:37:18 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2016-12-12 08:37:18 To prevent further connection attempts, select 'File >> Disconnect'. | 2016-12-12 08:37:18 CQG WebAPI websocket (4) | SSL shutdown indicates not able to send 'close notify'. | 2016-12-12 08:37:18 CQG WebAPI websocket (4) | SSL has been shut down. | 2016-12-12 08:37:18 CQG WebAPI websocket (4) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:37:18 CQG WebAPI websocket (4) | Shutdown and closed. | 2016-12-12 08:37:18 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:18 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:18 CQG WebAPI | Disconnected. | 2016-12-12 08:37:18 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-12-12 08:37:18 HTTPS connection to www.sierrachart.com:443 (3) | SSL connection closed by remote side. | 2016-12-12 08:37:19 HTTPS connection to www.sierrachart.com:443 (3) | Connection gracefully closed by remote side. | 2016-12-12 08:37:19 HTTPS connection to www.sierrachart.com:443 (3) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:37:19 HTTPS connection to www.sierrachart.com:443 (3) | Shutdown and closed. | 2016-12-12 08:37:19 CQG WebAPI | Connecting to market data server demoapi.cqg.com | 2016-12-12 08:37:21 CQG WebAPI | Connecting to websocket server. | 2016-12-12 08:37:21 CQG WebAPI websocket (0) | Resolved address demoapi.cqg.com to IP 208.48.16.32. | 2016-12-12 08:37:21 Service is currently connecting. | 2016-12-12 08:37:21 * CQG WebAPI websocket (5) | Connected. | 2016-12-12 08:37:21 CQG WebAPI websocket (5) | Starting SSL 3/2 connection. | 2016-12-12 08:37:21 CQG WebAPI websocket (5) | SSL connection established. | 2016-12-12 08:37:21 CQG WebAPI | Opening websocket. | 2016-12-12 08:37:21 CQG WebAPI | Sending websocket handshake. | 2016-12-12 08:37:21 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-12-12 08:37:21 CQG WebAPI | Web socket state is now open. | 2016-12-12 08:37:21 CQG WebAPI | Websocket connected. | 2016-12-12 08:37:21 CQG WebAPI | Sending market data logon message. | 2016-12-12 08:37:21 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:37:21 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2016-12-12 08:37:21 To prevent further connection attempts, select 'File >> Disconnect'. | 2016-12-12 08:37:21 CQG WebAPI websocket (5) | SSL shutdown indicates not able to send 'close notify'. | 2016-12-12 08:37:21 CQG WebAPI websocket (5) | SSL has been shut down. | 2016-12-12 08:37:21 CQG WebAPI websocket (5) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:37:21 CQG WebAPI websocket (5) | Shutdown and closed. | 2016-12-12 08:37:21 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:21 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:21 CQG WebAPI | Disconnected. | 2016-12-12 08:37:21 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-12-12 08:37:21 CQG WebAPI | Connecting to market data server demoapi.cqg.com | 2016-12-12 08:37:24 CQG WebAPI | Connecting to websocket server. | 2016-12-12 08:37:24 CQG WebAPI websocket (0) | Resolved address demoapi.cqg.com to IP 208.48.16.32. | 2016-12-12 08:37:24 CQG WebAPI websocket (6) | Connected. | 2016-12-12 08:37:24 CQG WebAPI websocket (6) | Starting SSL 3/2 connection. | 2016-12-12 08:37:24 CQG WebAPI websocket (6) | SSL connection established. | 2016-12-12 08:37:25 CQG WebAPI | Opening websocket. | 2016-12-12 08:37:25 CQG WebAPI | Sending websocket handshake. | 2016-12-12 08:37:25 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-12-12 08:37:25 CQG WebAPI | Web socket state is now open. | 2016-12-12 08:37:25 CQG WebAPI | Websocket connected. | 2016-12-12 08:37:25 CQG WebAPI | Sending market data logon message. | 2016-12-12 08:37:25 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:37:25 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2016-12-12 08:37:25 To prevent further connection attempts, select 'File >> Disconnect'. | 2016-12-12 08:37:25 CQG WebAPI websocket (6) | SSL shutdown indicates not able to send 'close notify'. | 2016-12-12 08:37:25 CQG WebAPI websocket (6) | SSL has been shut down. | 2016-12-12 08:37:25 CQG WebAPI websocket (6) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:37:25 CQG WebAPI websocket (6) | Shutdown and closed. | 2016-12-12 08:37:25 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:25 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:25 CQG WebAPI | Disconnected. | 2016-12-12 08:37:25 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-12-12 08:37:25 CQG WebAPI | Connecting to market data server demoapi.cqg.com | 2016-12-12 08:37:28 CQG WebAPI | Connecting to websocket server. | 2016-12-12 08:37:28 CQG WebAPI websocket (0) | Resolved address demoapi.cqg.com to IP 208.48.16.32. | 2016-12-12 08:37:28 CQG WebAPI websocket (7) | Connected. | 2016-12-12 08:37:28 CQG WebAPI websocket (7) | Starting SSL 3/2 connection. | 2016-12-12 08:37:28 CQG WebAPI websocket (7) | SSL connection established. | 2016-12-12 08:37:28 CQG WebAPI | Opening websocket. | 2016-12-12 08:37:28 CQG WebAPI | Sending websocket handshake. | 2016-12-12 08:37:28 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-12-12 08:37:28 CQG WebAPI | Web socket state is now open. | 2016-12-12 08:37:28 CQG WebAPI | Websocket connected. | 2016-12-12 08:37:28 CQG WebAPI | Sending market data logon message. | 2016-12-12 08:37:28 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:37:28 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2016-12-12 08:37:28 To prevent further connection attempts, select 'File >> Disconnect'. | 2016-12-12 08:37:28 CQG WebAPI websocket (7) | SSL shutdown indicates not able to send 'close notify'. | 2016-12-12 08:37:28 CQG WebAPI websocket (7) | SSL has been shut down. | 2016-12-12 08:37:28 CQG WebAPI websocket (7) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:37:28 CQG WebAPI websocket (7) | Shutdown and closed. | 2016-12-12 08:37:28 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:28 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:28 CQG WebAPI | Disconnected. | 2016-12-12 08:37:28 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-12-12 08:37:28 CQG WebAPI | Connecting to market data server demoapi.cqg.com | 2016-12-12 08:37:31 CQG WebAPI | Connecting to websocket server. | 2016-12-12 08:37:31 CQG WebAPI websocket (0) | Resolved address demoapi.cqg.com to IP 208.48.16.32. | 2016-12-12 08:37:31 CQG WebAPI websocket (8) | Connected. | 2016-12-12 08:37:31 CQG WebAPI websocket (8) | Starting SSL 3/2 connection. | 2016-12-12 08:37:31 CQG WebAPI websocket (8) | SSL connection established. | 2016-12-12 08:37:31 CQG WebAPI | Opening websocket. | 2016-12-12 08:37:31 CQG WebAPI | Sending websocket handshake. | 2016-12-12 08:37:31 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-12-12 08:37:31 CQG WebAPI | Web socket state is now open. | 2016-12-12 08:37:31 CQG WebAPI | Websocket connected. | 2016-12-12 08:37:31 CQG WebAPI | Sending market data logon message. | 2016-12-12 08:37:31 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:37:31 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2016-12-12 08:37:31 To prevent further connection attempts, select 'File >> Disconnect'. | 2016-12-12 08:37:31 CQG WebAPI websocket (8) | SSL shutdown indicates not able to send 'close notify'. | 2016-12-12 08:37:31 CQG WebAPI websocket (8) | SSL has been shut down. | 2016-12-12 08:37:31 CQG WebAPI websocket (8) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:37:31 CQG WebAPI websocket (8) | Shutdown and closed. | 2016-12-12 08:37:31 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:31 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:31 CQG WebAPI | Disconnected. | 2016-12-12 08:37:31 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-12-12 08:37:31 CQG WebAPI | Connecting to market data server demoapi.cqg.com | 2016-12-12 08:37:34 CQG WebAPI | Connecting to websocket server. | 2016-12-12 08:37:34 CQG WebAPI websocket (0) | Resolved address demoapi.cqg.com to IP 208.48.16.32. | 2016-12-12 08:37:34 CQG WebAPI websocket (9) | Connected. | 2016-12-12 08:37:34 CQG WebAPI websocket (9) | Starting SSL 3/2 connection. | 2016-12-12 08:37:34 CQG WebAPI websocket (9) | SSL connection established. | 2016-12-12 08:37:34 CQG WebAPI | Opening websocket. | 2016-12-12 08:37:34 CQG WebAPI | Sending websocket handshake. | 2016-12-12 08:37:34 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-12-12 08:37:34 CQG WebAPI | Web socket state is now open. | 2016-12-12 08:37:34 CQG WebAPI | Websocket connected. | 2016-12-12 08:37:34 CQG WebAPI | Sending market data logon message. | 2016-12-12 08:37:34 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:37:34 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2016-12-12 08:37:34 To prevent further connection attempts, select 'File >> Disconnect'. | 2016-12-12 08:37:34 CQG WebAPI websocket (9) | SSL shutdown indicates not able to send 'close notify'. | 2016-12-12 08:37:34 CQG WebAPI websocket (9) | SSL has been shut down. | 2016-12-12 08:37:34 CQG WebAPI websocket (9) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:37:34 CQG WebAPI websocket (9) | Shutdown and closed. | 2016-12-12 08:37:34 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:34 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:34 CQG WebAPI | Disconnected. | 2016-12-12 08:37:34 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-12-12 08:37:34 CQG WebAPI | Connecting to market data server demoapi.cqg.com | 2016-12-12 08:37:37 CQG WebAPI | Connecting to websocket server. | 2016-12-12 08:37:37 CQG WebAPI websocket (0) | Resolved address demoapi.cqg.com to IP 208.48.16.32. | 2016-12-12 08:37:37 CQG WebAPI websocket (10) | Connected. | 2016-12-12 08:37:37 CQG WebAPI websocket (10) | Starting SSL 3/2 connection. | 2016-12-12 08:37:37 CQG WebAPI websocket (10) | SSL connection established. | 2016-12-12 08:37:37 CQG WebAPI | Opening websocket. | 2016-12-12 08:37:37 CQG WebAPI | Sending websocket handshake. | 2016-12-12 08:37:37 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-12-12 08:37:37 CQG WebAPI | Web socket state is now open. | 2016-12-12 08:37:37 CQG WebAPI | Websocket connected. | 2016-12-12 08:37:37 CQG WebAPI | Sending market data logon message. | 2016-12-12 08:37:37 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:37:37 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2016-12-12 08:37:37 To prevent further connection attempts, select 'File >> Disconnect'. | 2016-12-12 08:37:37 CQG WebAPI websocket (10) | SSL shutdown indicates not able to send 'close notify'. | 2016-12-12 08:37:37 CQG WebAPI websocket (10) | SSL has been shut down. | 2016-12-12 08:37:37 CQG WebAPI websocket (10) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:37:37 CQG WebAPI websocket (10) | Shutdown and closed. | 2016-12-12 08:37:37 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:37 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:37 CQG WebAPI | Disconnected. | 2016-12-12 08:37:37 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-12-12 08:37:37 CQG WebAPI | Connecting to market data server demoapi.cqg.com | 2016-12-12 08:37:40 CQG WebAPI | Connecting to websocket server. | 2016-12-12 08:37:40 CQG WebAPI websocket (0) | Resolved address demoapi.cqg.com to IP 208.48.16.32. | 2016-12-12 08:37:40 CQG WebAPI websocket (11) | Connected. | 2016-12-12 08:37:40 CQG WebAPI websocket (11) | Starting SSL 3/2 connection. | 2016-12-12 08:37:40 CQG WebAPI websocket (11) | SSL connection established. | 2016-12-12 08:37:41 CQG WebAPI | Opening websocket. | 2016-12-12 08:37:41 CQG WebAPI | Sending websocket handshake. | 2016-12-12 08:37:41 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-12-12 08:37:41 CQG WebAPI | Web socket state is now open. | 2016-12-12 08:37:41 CQG WebAPI | Websocket connected. | 2016-12-12 08:37:41 CQG WebAPI | Sending market data logon message. | 2016-12-12 08:37:41 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:37:41 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2016-12-12 08:37:41 To prevent further connection attempts, select 'File >> Disconnect'. | 2016-12-12 08:37:41 CQG WebAPI websocket (11) | SSL shutdown indicates not able to send 'close notify'. | 2016-12-12 08:37:41 CQG WebAPI websocket (11) | SSL has been shut down. | 2016-12-12 08:37:41 CQG WebAPI websocket (11) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:37:41 CQG WebAPI websocket (11) | Shutdown and closed. | 2016-12-12 08:37:41 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:41 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:41 CQG WebAPI | Disconnected. | 2016-12-12 08:37:41 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-12-12 08:37:41 CQG WebAPI | Connecting to market data server demoapi.cqg.com | 2016-12-12 08:37:44 CQG WebAPI | Connecting to websocket server. | 2016-12-12 08:37:44 CQG WebAPI websocket (0) | Resolved address demoapi.cqg.com to IP 208.48.16.32. | 2016-12-12 08:37:44 CQG WebAPI websocket (12) | Connected. | 2016-12-12 08:37:44 CQG WebAPI websocket (12) | Starting SSL 3/2 connection. | 2016-12-12 08:37:44 CQG WebAPI websocket (12) | SSL connection established. | 2016-12-12 08:37:44 CQG WebAPI | Opening websocket. | 2016-12-12 08:37:44 CQG WebAPI | Sending websocket handshake. | 2016-12-12 08:37:44 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-12-12 08:37:44 CQG WebAPI | Web socket state is now open. | 2016-12-12 08:37:44 CQG WebAPI | Websocket connected. | 2016-12-12 08:37:44 CQG WebAPI | Sending market data logon message. | 2016-12-12 08:37:44 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:37:44 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2016-12-12 08:37:44 To prevent further connection attempts, select 'File >> Disconnect'. | 2016-12-12 08:37:44 CQG WebAPI websocket (12) | SSL shutdown indicates not able to send 'close notify'. | 2016-12-12 08:37:44 CQG WebAPI websocket (12) | SSL has been shut down. | 2016-12-12 08:37:44 CQG WebAPI websocket (12) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:37:44 CQG WebAPI websocket (12) | Shutdown and closed. | 2016-12-12 08:37:44 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:44 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:44 CQG WebAPI | Disconnected. | 2016-12-12 08:37:44 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-12-12 08:37:44 CQG WebAPI | Connecting to market data server demoapi.cqg.com | 2016-12-12 08:37:47 CQG WebAPI | Connecting to websocket server. | 2016-12-12 08:37:47 CQG WebAPI websocket (0) | Resolved address demoapi.cqg.com to IP 208.48.16.32. | 2016-12-12 08:37:47 CQG WebAPI websocket (13) | Connected. | 2016-12-12 08:37:47 CQG WebAPI websocket (13) | Starting SSL 3/2 connection. | 2016-12-12 08:37:47 CQG WebAPI websocket (13) | SSL connection established. | 2016-12-12 08:37:48 CQG WebAPI | Opening websocket. | 2016-12-12 08:37:48 CQG WebAPI | Sending websocket handshake. | 2016-12-12 08:37:48 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-12-12 08:37:48 CQG WebAPI | Web socket state is now open. | 2016-12-12 08:37:48 CQG WebAPI | Websocket connected. | 2016-12-12 08:37:48 CQG WebAPI | Sending market data logon message. | 2016-12-12 08:37:48 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:37:48 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2016-12-12 08:37:48 To prevent further connection attempts, select 'File >> Disconnect'. | 2016-12-12 08:37:48 CQG WebAPI websocket (13) | SSL shutdown indicates not able to send 'close notify'. | 2016-12-12 08:37:48 CQG WebAPI websocket (13) | SSL has been shut down. | 2016-12-12 08:37:48 CQG WebAPI websocket (13) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:37:48 CQG WebAPI websocket (13) | Shutdown and closed. | 2016-12-12 08:37:48 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:48 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:48 CQG WebAPI | Disconnected. | 2016-12-12 08:37:48 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-12-12 08:37:48 CQG WebAPI | Connecting to market data server demoapi.cqg.com | 2016-12-12 08:37:51 CQG WebAPI | Connecting to websocket server. | 2016-12-12 08:37:51 CQG WebAPI websocket (0) | Resolved address demoapi.cqg.com to IP 208.48.16.32. | 2016-12-12 08:37:51 CQG WebAPI websocket (14) | Connected. | 2016-12-12 08:37:51 CQG WebAPI websocket (14) | Starting SSL 3/2 connection. | 2016-12-12 08:37:51 CQG WebAPI websocket (14) | SSL connection established. | 2016-12-12 08:37:51 CQG WebAPI | Opening websocket. | 2016-12-12 08:37:51 CQG WebAPI | Sending websocket handshake. | 2016-12-12 08:37:51 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-12-12 08:37:51 CQG WebAPI | Web socket state is now open. | 2016-12-12 08:37:51 CQG WebAPI | Websocket connected. | 2016-12-12 08:37:51 CQG WebAPI | Sending market data logon message. | 2016-12-12 08:37:51 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:37:51 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2016-12-12 08:37:51 To prevent further connection attempts, select 'File >> Disconnect'. | 2016-12-12 08:37:51 CQG WebAPI websocket (14) | SSL shutdown indicates not able to send 'close notify'. | 2016-12-12 08:37:51 CQG WebAPI websocket (14) | SSL has been shut down. | 2016-12-12 08:37:51 CQG WebAPI websocket (14) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:37:51 CQG WebAPI websocket (14) | Shutdown and closed. | 2016-12-12 08:37:51 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:51 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:51 CQG WebAPI | Disconnected. | 2016-12-12 08:37:51 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-12-12 08:37:51 CQG WebAPI | Connecting to market data server demoapi.cqg.com | 2016-12-12 08:37:54 CQG WebAPI | Connecting to websocket server. | 2016-12-12 08:37:54 CQG WebAPI websocket (0) | Resolved address demoapi.cqg.com to IP 208.48.16.32. | 2016-12-12 08:37:54 CQG WebAPI websocket (15) | Connected. | 2016-12-12 08:37:54 CQG WebAPI websocket (15) | Starting SSL 3/2 connection. | 2016-12-12 08:37:54 CQG WebAPI websocket (15) | SSL connection established. | 2016-12-12 08:37:54 CQG WebAPI | Opening websocket. | 2016-12-12 08:37:54 CQG WebAPI | Sending websocket handshake. | 2016-12-12 08:37:54 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-12-12 08:37:54 CQG WebAPI | Web socket state is now open. | 2016-12-12 08:37:54 CQG WebAPI | Websocket connected. | 2016-12-12 08:37:54 CQG WebAPI | Sending market data logon message. | 2016-12-12 08:37:54 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:37:54 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2016-12-12 08:37:54 To prevent further connection attempts, select 'File >> Disconnect'. | 2016-12-12 08:37:54 CQG WebAPI websocket (15) | SSL shutdown indicates not able to send 'close notify'. | 2016-12-12 08:37:54 CQG WebAPI websocket (15) | SSL has been shut down. | 2016-12-12 08:37:54 CQG WebAPI websocket (15) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:37:54 CQG WebAPI websocket (15) | Shutdown and closed. | 2016-12-12 08:37:54 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:54 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:54 CQG WebAPI | Disconnected. | 2016-12-12 08:37:54 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-12-12 08:37:54 CQG WebAPI | Connecting to market data server demoapi.cqg.com | 2016-12-12 08:37:57 CQG WebAPI | Connecting to websocket server. | 2016-12-12 08:37:57 CQG WebAPI websocket (0) | Resolved address demoapi.cqg.com to IP 208.48.16.32. | 2016-12-12 08:37:57 CQG WebAPI websocket (16) | Connected. | 2016-12-12 08:37:57 CQG WebAPI websocket (16) | Starting SSL 3/2 connection. | 2016-12-12 08:37:57 CQG WebAPI websocket (16) | SSL connection established. | 2016-12-12 08:37:57 CQG WebAPI | Opening websocket. | 2016-12-12 08:37:57 CQG WebAPI | Sending websocket handshake. | 2016-12-12 08:37:57 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-12-12 08:37:57 CQG WebAPI | Web socket state is now open. | 2016-12-12 08:37:57 CQG WebAPI | Websocket connected. | 2016-12-12 08:37:57 CQG WebAPI | Sending market data logon message. | 2016-12-12 08:37:57 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:37:57 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2016-12-12 08:37:57 To prevent further connection attempts, select 'File >> Disconnect'. | 2016-12-12 08:37:57 CQG WebAPI websocket (16) | SSL shutdown indicates not able to send 'close notify'. | 2016-12-12 08:37:57 CQG WebAPI websocket (16) | SSL has been shut down. | 2016-12-12 08:37:57 CQG WebAPI websocket (16) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:37:57 CQG WebAPI websocket (16) | Shutdown and closed. | 2016-12-12 08:37:57 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:57 CQG WebAPI | Websocket closed. | 2016-12-12 08:37:57 CQG WebAPI | Disconnected. | 2016-12-12 08:37:57 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-12-12 08:37:57 CQG WebAPI | Connecting to market data server demoapi.cqg.com | 2016-12-12 08:38:00 CQG WebAPI | Connecting to websocket server. | 2016-12-12 08:38:00 CQG WebAPI websocket (0) | Resolved address demoapi.cqg.com to IP 208.48.16.32. | 2016-12-12 08:38:00 CQG WebAPI websocket (17) | Connected. | 2016-12-12 08:38:00 CQG WebAPI websocket (17) | Starting SSL 3/2 connection. | 2016-12-12 08:38:00 CQG WebAPI websocket (17) | SSL connection established. | 2016-12-12 08:38:00 CQG WebAPI | Opening websocket. | 2016-12-12 08:38:00 CQG WebAPI | Sending websocket handshake. | 2016-12-12 08:38:00 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-12-12 08:38:00 CQG WebAPI | Web socket state is now open. | 2016-12-12 08:38:00 CQG WebAPI | Websocket connected. | 2016-12-12 08:38:00 CQG WebAPI | Sending market data logon message. | 2016-12-12 08:38:00 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:38:01 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2016-12-12 08:38:01 To prevent further connection attempts, select 'File >> Disconnect'. | 2016-12-12 08:38:01 CQG WebAPI websocket (17) | SSL shutdown indicates not able to send 'close notify'. | 2016-12-12 08:38:01 CQG WebAPI websocket (17) | SSL has been shut down. | 2016-12-12 08:38:01 CQG WebAPI websocket (17) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:38:01 CQG WebAPI websocket (17) | Shutdown and closed. | 2016-12-12 08:38:01 CQG WebAPI | Websocket closed. | 2016-12-12 08:38:01 CQG WebAPI | Websocket closed. | 2016-12-12 08:38:01 CQG WebAPI | Disconnected. | 2016-12-12 08:38:01 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-12-12 08:38:01 CQG WebAPI | Connecting to market data server demoapi.cqg.com | 2016-12-12 08:38:03 CQG WebAPI | Connecting to websocket server. | 2016-12-12 08:38:03 CQG WebAPI websocket (0) | Resolved address demoapi.cqg.com to IP 208.48.16.32. | 2016-12-12 08:38:03 CQG WebAPI websocket (18) | Connected. | 2016-12-12 08:38:04 CQG WebAPI websocket (18) | Starting SSL 3/2 connection. | 2016-12-12 08:38:04 CQG WebAPI websocket (18) | SSL connection established. | 2016-12-12 08:38:04 CQG WebAPI | Opening websocket. | 2016-12-12 08:38:04 CQG WebAPI | Sending websocket handshake. | 2016-12-12 08:38:04 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-12-12 08:38:04 CQG WebAPI | Web socket state is now open. | 2016-12-12 08:38:04 CQG WebAPI | Websocket connected. | 2016-12-12 08:38:04 CQG WebAPI | Sending market data logon message. | 2016-12-12 08:38:04 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:38:04 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2016-12-12 08:38:04 To prevent further connection attempts, select 'File >> Disconnect'. | 2016-12-12 08:38:04 CQG WebAPI websocket (18) | SSL shutdown indicates not able to send 'close notify'. | 2016-12-12 08:38:04 CQG WebAPI websocket (18) | SSL has been shut down. | 2016-12-12 08:38:04 CQG WebAPI websocket (18) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:38:04 CQG WebAPI websocket (18) | Shutdown and closed. | 2016-12-12 08:38:04 CQG WebAPI | Websocket closed. | 2016-12-12 08:38:04 CQG WebAPI | Websocket closed. | 2016-12-12 08:38:04 CQG WebAPI | Disconnected. | 2016-12-12 08:38:04 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-12-12 08:38:04 CQG WebAPI | Connecting to market data server demoapi.cqg.com | 2016-12-12 08:38:07 CQG WebAPI | Connecting to websocket server. | 2016-12-12 08:38:07 CQG WebAPI websocket (0) | Resolved address demoapi.cqg.com to IP 208.48.16.32. | 2016-12-12 08:38:07 CQG WebAPI websocket (19) | Connected. | 2016-12-12 08:38:07 CQG WebAPI websocket (19) | Starting SSL 3/2 connection. | 2016-12-12 08:38:07 CQG WebAPI websocket (19) | SSL connection established. | 2016-12-12 08:38:08 CQG WebAPI | Opening websocket. | 2016-12-12 08:38:08 CQG WebAPI | Sending websocket handshake. | 2016-12-12 08:38:08 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-12-12 08:38:08 CQG WebAPI | Web socket state is now open. | 2016-12-12 08:38:08 CQG WebAPI | Websocket connected. | 2016-12-12 08:38:08 CQG WebAPI | Sending market data logon message. | 2016-12-12 08:38:08 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:38:08 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2016-12-12 08:38:08 To prevent further connection attempts, select 'File >> Disconnect'. | 2016-12-12 08:38:08 CQG WebAPI websocket (19) | SSL shutdown indicates not able to send 'close notify'. | 2016-12-12 08:38:08 CQG WebAPI websocket (19) | SSL has been shut down. | 2016-12-12 08:38:08 CQG WebAPI websocket (19) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:38:08 CQG WebAPI websocket (19) | Shutdown and closed. | 2016-12-12 08:38:08 CQG WebAPI | Websocket closed. | 2016-12-12 08:38:08 CQG WebAPI | Websocket closed. | 2016-12-12 08:38:08 CQG WebAPI | Disconnected. | 2016-12-12 08:38:08 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-12-12 08:38:08 CQG WebAPI | Connecting to market data server demoapi.cqg.com | 2016-12-12 08:38:11 CQG WebAPI | Connecting to websocket server. | 2016-12-12 08:38:11 CQG WebAPI websocket (0) | Resolved address demoapi.cqg.com to IP 208.48.16.32. | 2016-12-12 08:38:11 CQG WebAPI websocket (20) | Connected. | 2016-12-12 08:38:11 CQG WebAPI websocket (20) | Starting SSL 3/2 connection. | 2016-12-12 08:38:11 CQG WebAPI websocket (20) | SSL connection established. | 2016-12-12 08:38:11 CQG WebAPI | Opening websocket. | 2016-12-12 08:38:11 CQG WebAPI | Sending websocket handshake. | 2016-12-12 08:38:11 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-12-12 08:38:11 CQG WebAPI | Web socket state is now open. | 2016-12-12 08:38:11 CQG WebAPI | Websocket connected. | 2016-12-12 08:38:11 CQG WebAPI | Sending market data logon message. | 2016-12-12 08:38:11 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:38:12 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2016-12-12 08:38:12 To prevent further connection attempts, select 'File >> Disconnect'. | 2016-12-12 08:38:12 CQG WebAPI websocket (20) | SSL shutdown indicates not able to send 'close notify'. | 2016-12-12 08:38:12 CQG WebAPI websocket (20) | SSL has been shut down. | 2016-12-12 08:38:12 CQG WebAPI websocket (20) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:38:12 CQG WebAPI websocket (20) | Shutdown and closed. | 2016-12-12 08:38:12 CQG WebAPI | Websocket closed. | 2016-12-12 08:38:12 CQG WebAPI | Websocket closed. | 2016-12-12 08:38:12 CQG WebAPI | Disconnected. | 2016-12-12 08:38:12 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-12-12 08:38:12 CQG WebAPI | Connecting to market data server demoapi.cqg.com | 2016-12-12 08:38:15 CQG WebAPI | Connecting to websocket server. | 2016-12-12 08:38:15 CQG WebAPI websocket (0) | Resolved address demoapi.cqg.com to IP 208.48.16.32. | 2016-12-12 08:38:15 CQG WebAPI websocket (21) | Connected. | 2016-12-12 08:38:15 CQG WebAPI websocket (21) | Starting SSL 3/2 connection. | 2016-12-12 08:38:15 CQG WebAPI websocket (21) | SSL connection established. | 2016-12-12 08:38:15 CQG WebAPI | Opening websocket. | 2016-12-12 08:38:15 CQG WebAPI | Sending websocket handshake. | 2016-12-12 08:38:15 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-12-12 08:38:16 CQG WebAPI | Web socket state is now open. | 2016-12-12 08:38:16 CQG WebAPI | Websocket connected. | 2016-12-12 08:38:16 CQG WebAPI | Sending market data logon message. | 2016-12-12 08:38:16 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:38:16 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2016-12-12 08:38:16 To prevent further connection attempts, select 'File >> Disconnect'. | 2016-12-12 08:38:16 CQG WebAPI websocket (21) | SSL shutdown indicates not able to send 'close notify'. | 2016-12-12 08:38:16 CQG WebAPI websocket (21) | SSL has been shut down. | 2016-12-12 08:38:16 CQG WebAPI websocket (21) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:38:16 CQG WebAPI websocket (21) | Shutdown and closed. | 2016-12-12 08:38:16 CQG WebAPI | Websocket closed. | 2016-12-12 08:38:16 CQG WebAPI | Websocket closed. | 2016-12-12 08:38:16 CQG WebAPI | Disconnected. | 2016-12-12 08:38:16 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-12-12 08:38:16 CQG WebAPI | Connecting to market data server demoapi.cqg.com | 2016-12-12 08:38:20 CQG WebAPI | Connecting to websocket server. | 2016-12-12 08:38:20 CQG WebAPI websocket (0) | Resolved address demoapi.cqg.com to IP 208.48.16.32. | 2016-12-12 08:38:20 CQG WebAPI websocket (22) | Connected. | 2016-12-12 08:38:20 CQG WebAPI websocket (22) | Starting SSL 3/2 connection. | 2016-12-12 08:38:20 CQG WebAPI websocket (22) | SSL connection established. | 2016-12-12 08:38:20 CQG WebAPI | Opening websocket. | 2016-12-12 08:38:20 CQG WebAPI | Sending websocket handshake. | 2016-12-12 08:38:20 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-12-12 08:38:20 CQG WebAPI | Web socket state is now open. | 2016-12-12 08:38:20 CQG WebAPI | Websocket connected. | 2016-12-12 08:38:20 CQG WebAPI | Sending market data logon message. | 2016-12-12 08:38:20 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:38:21 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2016-12-12 08:38:21 To prevent further connection attempts, select 'File >> Disconnect'. | 2016-12-12 08:38:21 CQG WebAPI websocket (22) | SSL shutdown indicates not able to send 'close notify'. | 2016-12-12 08:38:21 CQG WebAPI websocket (22) | SSL has been shut down. | 2016-12-12 08:38:21 CQG WebAPI websocket (22) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:38:21 CQG WebAPI websocket (22) | Shutdown and closed. | 2016-12-12 08:38:21 CQG WebAPI | Websocket closed. | 2016-12-12 08:38:21 CQG WebAPI | Websocket closed. | 2016-12-12 08:38:21 CQG WebAPI | Disconnected. | 2016-12-12 08:38:21 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-12-12 08:38:21 CQG WebAPI | Connecting to market data server demoapi.cqg.com | 2016-12-12 08:38:24 CQG WebAPI | Connecting to websocket server. | 2016-12-12 08:38:24 CQG WebAPI websocket (0) | Resolved address demoapi.cqg.com to IP 208.48.16.32. | 2016-12-12 08:38:24 CQG WebAPI websocket (23) | Connected. | 2016-12-12 08:38:24 CQG WebAPI websocket (23) | Starting SSL 3/2 connection. | 2016-12-12 08:38:24 CQG WebAPI websocket (23) | SSL connection established. | 2016-12-12 08:38:24 CQG WebAPI | Opening websocket. | 2016-12-12 08:38:24 CQG WebAPI | Sending websocket handshake. | 2016-12-12 08:38:24 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-12-12 08:38:24 CQG WebAPI | Web socket state is now open. | 2016-12-12 08:38:24 CQG WebAPI | Websocket connected. | 2016-12-12 08:38:24 CQG WebAPI | Sending market data logon message. | 2016-12-12 08:38:24 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:38:24 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2016-12-12 08:38:24 To prevent further connection attempts, select 'File >> Disconnect'. | 2016-12-12 08:38:24 CQG WebAPI websocket (23) | SSL shutdown indicates not able to send 'close notify'. | 2016-12-12 08:38:24 CQG WebAPI websocket (23) | SSL has been shut down. | 2016-12-12 08:38:24 CQG WebAPI websocket (23) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:38:24 CQG WebAPI websocket (23) | Shutdown and closed. | 2016-12-12 08:38:24 CQG WebAPI | Websocket closed. | 2016-12-12 08:38:24 CQG WebAPI | Websocket closed. | 2016-12-12 08:38:24 CQG WebAPI | Disconnected. | 2016-12-12 08:38:24 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-12-12 08:38:24 CQG WebAPI | Connecting to market data server demoapi.cqg.com | 2016-12-12 08:38:27 CQG WebAPI | Connecting to websocket server. | 2016-12-12 08:38:27 CQG WebAPI websocket (0) | Resolved address demoapi.cqg.com to IP 208.48.16.32. | 2016-12-12 08:38:27 CQG WebAPI websocket (24) | Connected. | 2016-12-12 08:38:27 CQG WebAPI websocket (24) | Starting SSL 3/2 connection. | 2016-12-12 08:38:27 CQG WebAPI websocket (24) | SSL connection established. | 2016-12-12 08:38:27 CQG WebAPI | Opening websocket. | 2016-12-12 08:38:27 CQG WebAPI | Sending websocket handshake. | 2016-12-12 08:38:27 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-12-12 08:38:27 CQG WebAPI | Web socket state is now open. | 2016-12-12 08:38:27 CQG WebAPI | Websocket connected. | 2016-12-12 08:38:27 CQG WebAPI | Sending market data logon message. | 2016-12-12 08:38:27 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:38:27 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2016-12-12 08:38:27 To prevent further connection attempts, select 'File >> Disconnect'. | 2016-12-12 08:38:27 CQG WebAPI websocket (24) | SSL shutdown indicates not able to send 'close notify'. | 2016-12-12 08:38:27 CQG WebAPI websocket (24) | SSL has been shut down. | 2016-12-12 08:38:27 CQG WebAPI websocket (24) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:38:27 CQG WebAPI websocket (24) | Shutdown and closed. | 2016-12-12 08:38:27 CQG WebAPI | Websocket closed. | 2016-12-12 08:38:27 CQG WebAPI | Websocket closed. | 2016-12-12 08:38:27 CQG WebAPI | Disconnected. | 2016-12-12 08:38:27 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-12-12 08:38:27 CQG WebAPI | Connecting to market data server demoapi.cqg.com | 2016-12-12 08:38:30 CQG WebAPI | Connecting to websocket server. | 2016-12-12 08:38:30 CQG WebAPI websocket (0) | Resolved address demoapi.cqg.com to IP 208.48.16.32. | 2016-12-12 08:38:30 CQG WebAPI websocket (25) | Connected. | 2016-12-12 08:38:30 CQG WebAPI websocket (25) | Starting SSL 3/2 connection. | 2016-12-12 08:38:30 CQG WebAPI websocket (25) | SSL connection established. | 2016-12-12 08:38:30 CQG WebAPI | Opening websocket. | 2016-12-12 08:38:30 CQG WebAPI | Sending websocket handshake. | 2016-12-12 08:38:30 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-12-12 08:38:30 CQG WebAPI | Web socket state is now open. | 2016-12-12 08:38:30 CQG WebAPI | Websocket connected. | 2016-12-12 08:38:30 CQG WebAPI | Sending market data logon message. | 2016-12-12 08:38:30 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:38:31 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2016-12-12 08:38:31 To prevent further connection attempts, select 'File >> Disconnect'. | 2016-12-12 08:38:31 CQG WebAPI websocket (25) | SSL shutdown indicates not able to send 'close notify'. | 2016-12-12 08:38:31 CQG WebAPI websocket (25) | SSL has been shut down. | 2016-12-12 08:38:31 CQG WebAPI websocket (25) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:38:31 CQG WebAPI websocket (25) | Shutdown and closed. | 2016-12-12 08:38:31 CQG WebAPI | Websocket closed. | 2016-12-12 08:38:31 CQG WebAPI | Websocket closed. | 2016-12-12 08:38:31 CQG WebAPI | Disconnected. | 2016-12-12 08:38:31 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-12-12 08:38:31 CQG WebAPI | Connecting to market data server demoapi.cqg.com | 2016-12-12 08:38:33 CQG WebAPI | Connecting to websocket server. | 2016-12-12 08:38:33 CQG WebAPI websocket (0) | Resolved address demoapi.cqg.com to IP 208.48.16.32. | 2016-12-12 08:38:33 CQG WebAPI websocket (26) | Connected. | 2016-12-12 08:38:34 CQG WebAPI websocket (26) | Starting SSL 3/2 connection. | 2016-12-12 08:38:34 CQG WebAPI websocket (26) | SSL connection established. | 2016-12-12 08:38:34 CQG WebAPI | Opening websocket. | 2016-12-12 08:38:34 CQG WebAPI | Sending websocket handshake. | 2016-12-12 08:38:34 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-12-12 08:38:34 CQG WebAPI | Web socket state is now open. | 2016-12-12 08:38:34 CQG WebAPI | Websocket connected. | 2016-12-12 08:38:34 CQG WebAPI | Sending market data logon message. | 2016-12-12 08:38:34 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:38:34 * Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2016-12-12 08:38:34 To prevent further connection attempts, select 'File >> Disconnect'. | 2016-12-12 08:38:34 CQG WebAPI websocket (26) | SSL shutdown indicates not able to send 'close notify'. | 2016-12-12 08:38:34 CQG WebAPI websocket (26) | SSL has been shut down. | 2016-12-12 08:38:34 CQG WebAPI websocket (26) | SSL object has been freed. SSL state is now disconnected. | 2016-12-12 08:38:34 CQG WebAPI websocket (26) | Shutdown and closed. | 2016-12-12 08:38:34 CQG WebAPI | Websocket closed. | 2016-12-12 08:38:34 CQG WebAPI | Websocket closed. | 2016-12-12 08:38:34 CQG WebAPI | Disconnected. | 2016-12-12 08:38:34 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-12-12 08:38:34 |
| [2016-12-12 13:44:46] |
| |
|
This is the relevant message: CQG WebAPI | Sending market data logon message. | 2016-12-12 08:37:37 CQG WebAPI | Market data logon unsuccessful. Server message: Username or password is incorrect | 2016-12-12 08:37:37 * Do you have a live or demo CQG account? Who is your futures broker? 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 |
| [2016-12-12 13:47:56] |
| User550674 - Posts: 14 |
|
Demo. I don't know who my broker is.
|
| [2016-12-12 14:15:03] |
| User550674 - Posts: 14 |
|
Can someone pls help me cannot. I have tried using resources provided and of no help.
|
| [2016-12-12 15:29:00] |
| User550674 - Posts: 14 |
|
After referring to resources I am able to connect to data feed, but only get historical feed, not live trading. PLEASE HELP!
|
| [2016-12-12 15:33:47] |
| |
|
No, we cannot help you connect to CQG because you do not have a CQG account if you do not know who your futures broker is. Follow the instructions here to use the Sierra Chart Historical Data Service for now: Sierra Chart Historical Data Service What markets do you need data for or want to trade? For example, what particular futures, Forex or stock symbols. You can also give us the exchanges that the particular symbol or symbols trade on. If you require real-time futures data, then refer to: https://www.sierrachart.com/index.php?page=doc/doc_FuturesData.php 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 |
| [2016-12-12 15:42:15] |
| User550674 - Posts: 14 |
|
This is a demo account. I am evaluating for a mass purchase. It was working fine last week and for some reason my saved settings were reset. I tried to recreate and believe I did so correctly. I am able to recreate but there is some problem with my feed that I am not correctly getting the right feed (only, historical, live feed). Can someone pls reach out to me 917-566-5844 in order to make sure I am s/u correctly? I already wasted the morning. Thanks, Mark |
| [2016-12-12 15:43:32] |
| sewinn - Posts: 4 |
|
I will join in on this because I am having the exact same problem. I have connected to SC Data - all services. Only historical, no streaming. Does this provide US stock live data or not? Otherwise I have an IB account, or would be willing to purchase the data on the trial account. |
| [2016-12-12 15:54:27] |
| User550674 - Posts: 14 |
|
I have a demo a/c that worked fine last week. I downloaded online so I don't have a broker. There is something going on whereby I am now only to get to get historical data, not streaming and unable to trade. This s/b be an easy fix and hours later I am still in the same situation. Tech support isn't able to help or else not willing. Perhaps I should take my business elsewhere.
|
| [2016-12-12 15:56:59] |
| sewinn - Posts: 4 |
|
This is my first day using the demo and trying this out. I set a layout over the weekend, which reset to blank. I too am getting no streaming data for US stocks (not futures). It seems to be the exact same issue. |
| [2016-12-12 16:24:36] |
| sewinn - Posts: 4 |
|
Yaaa, it looks like I've learned all I need to know here about SC. I will find another charting provider. |
| [2016-12-12 16:32:24] |
| User550674 - Posts: 14 |
|
After giving me the run around all morning. I was finally steered to the Amp Futures where I downloaded it. Apparently, the demo was for 14 days, which hasn't come yet, not the month I had been told. I am being told on Sierra's platform that I still have days left and Amp said there isn't such a notification. Strange as I am able to log on and trade (off old data), but not able to get live data.
|
| [2016-12-12 16:46:46] |
| |
|
In response to post #15, we do not control the length of a CQG demo. It makes sense at this time you cannot get live data if the CQG demo is expired.
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 |
| [2016-12-12 16:49:52] |
| |
|
This is my first day using the demo and trying this out.
I set a layout over the weekend, which reset to blank. I too am getting no streaming data for US stocks (not futures). It seems to be the exact same issue. Yaaa, it looks like I've learned all I need to know here about SC.
No, you are not having the same issue. Your case is completely unrelated to this thread and you should have started a separate support request instead of interfering in this one. The Sierra Chart service packages do not provide real-time stock data. You need to use the Sierra Chart Exchange Data Feed for that:I will find another charting provider. Sierra Chart Exchange Data Feed This is made clear on these pages: https://www.sierrachart.com/index.php?page=doc/Data.php Description of Service Packages and Pricing What is Included in the Free Trial? The real-time stock data is a separate cost. It really surprises us that people think they are going to get real-time exchange data for free just by creating a Sierra Chart account. It does not work that way because the exchanges do not allow that. And now you say you want to leave because you have no patience, and you did not read the information provided to you. We are not the ones making this difficult. I set a layout over the weekend, which reset to blank.
Did you save your charts as a Chartbook as explained here:Chartbooks (Workspaces) We do not know exactly what you did and what you are seeing so it is hard for us to answer this. However, if there is a blank chart, this is going to be the relevant help topic: Data/Trading Service Connection and Symbol Issues Do not post further in this thread, start a new Support Request if you have further questions and you decide to stay: Support Board Posting Information So to conclude, you think somehow there is something wrong with Sierra Chart, or maybe our service is not very good when none of this is true. The problem is you are not taking the time to understand what it is you are working with, to understand exchange policies, to have some patience. If you want to leave, that is up to you. It is your failure to read the information provided and to have some patience which is the source of 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: 2016-12-12 16:54:15
|
| [2016-12-12 16:59:19] |
| sewinn - Posts: 4 |
|
Interfering, thanks for that. When I saw nobody respond to my ticket and found an exact same end result issue on the board. GFY and your shitty software. |
| [2016-12-12 17:01:20] |
| |
|
This is a demo account. I am evaluating for a mass purchase. It was working fine last week and for some reason my saved settings were reset. I tried to recreate and believe I did so correctly. I am able to recreate but there is some problem with my feed that I am not correctly getting the right feed (only, historical, live feed). Can someone pls reach out to me 917-566-5844 in order to make sure I am s/u correctly? I already wasted the morning.
For the record, we called them about this.I have a demo a/c that worked fine last week. I downloaded online so I don't have a broker. There is something going on whereby I am now only to get to get historical data, not streaming and unable to trade. This s/b be an easy fix and hours later I am still in the same situation. Tech support isn't able to help or else not willing. Perhaps I should take my business elsewhere.
The problem is your CQG demo account expired. We do not have any control over this. If you want real-time futures data feed, you can use this data feed:Sierra Chart Exchange Data Feed I will join in on this because I am having the exact same problem. If you have an Interactive Brokers account, then follow the instructions here to use it:I have connected to SC Data - all services. Only historical, no streaming. Does this provide US stock live data or not? Otherwise I have an IB account, or would be willing to purchase the data on the trial account. Interactive Brokers Trading Service: Setup Instructions Furthermore, do not post in this thread which belongs to someone else and is about a completely different issue. You are creating a confusion and interference. 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: 2016-12-12 17:10:18
|
| [2016-12-12 17:01:54] |
| |
|
Interfering, thanks for that. When I saw nobody respond to my ticket and found an exact same end result issue on the board. We want you to leave and not come back. And we mean that. Get lost. You are the problem.
GFY and your shitty software. 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: 2016-12-12 17:02:56
|
| [2016-12-12 17:05:09] |
| |
|
Also in regards to your support ticket, we have not yet gotten to that. We have a lot of support to do this morning. And with the way you are talking to us, get lost. 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 |
| [2016-12-12 20:06:26] |
| |
|
I already wasted the morning.
For more information about this subject, refer to:Is Historical and Real-time Futures Data Included?: Is Historical and Real-time Futures Data Included? As you read, this is not something that is within our control. So this kind of comment is inappropriate especially coming from a trial user using trials from external services and with strict limitations for real-time data imposed by exchanges. 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: 2016-12-12 20:07:04
|
| [2016-12-12 23:19:53] |
| |
|
One other thing, if you opened a Chartbook and it does not have the configuration that it had previously, then there are backup Chartbooks available: Chartbooks (Workspaces): Accessing a Backup Chartbook File What the reason was for the problem, we do not know because we do not know exactly what you were doing and what you did. And what kind of system issues you may have had. I am using your platform for an evaluation for a mass purchase. I have used your platform successfully last week and over the week had to rebuild my set up. In doing so, I am now not able to get live/streaming data in order to trade. I have wasted my entire morning trying to fix this problem (w/o a chance to trade and successfully trade/use the platform). Tech support has been slow to respond, and when they have have been have not provided useful information to fix the problem. Now I am being told they can't help as I don't have a broker. Can you help me or should I take my business elsewhere?
Please refer to this page: Is Historical and Real-time Futures Data Included? For an understanding about futures data. 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: 2016-12-13 00:03:49
|
| [2016-12-13 00:06:01] |
| |
|
Additionally, on this page it explains that you can use the Sierra Chart Exchange Data Feed for real-time futures data: Is Historical and Real-time Futures Data Included?: Is Historical and Real-time Futures Data Included? So you have the ability to activate this data feed on your account and for the first month the cost will be only 5 USD. But you also have to activate the exchanges as well. But the CME ones are free for the first month. And this is the correct link for backup Chartbooks. Chartbooks (Workspaces): Accessing a Backup Chartbook File The link we put previously was not exactly correct. 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: