Support Board
Date/Time: Tue, 04 Feb 2025 01:53:35 +0000
CTS T4 data feed not connecting, Rithmic will connect
View Count: 1281
| [2019-12-20 20:21:58] |
| michael225 - Posts: 2 |
|
I've read through a few of the other threads and tried to troubleshoot but can't get CTS to connect. SC has referenced error code 10060 as a firewall issue, so I turned off the firewall and reattempted and failed. I've connected to Rithmic feed with no problems at all. I've already called CTS and they say everything is good to go on their side, SC is "on". The attempts in the log listed below are me toggling through firewall on/off and then switching over to Rithmic (I do think I had to hit "connect to data feed" twice to get that up and running). Please advise. Reading Internal Order ID file. | 2019-12-20 13:56:27.192 Reading Trade Orders file. | 2019-12-20 13:56:27.488 Reading Trade Positions file. | 2019-12-20 13:56:27.489 Reading Account Balance file. | 2019-12-20 13:56:27.490 UDPListener (1556). Port 22904 | Listening on UDP port 22904. | 2019-12-20 13:56:27.529 Software version: 2028 32-bit | 2019-12-20 13:56:27.529 Usage end date: 2020-08-15 | 2019-12-20 13:56:27.529 Enabled for: Advanced Features 2. | 2019-12-20 13:56:27.529 Enabled for: Sierra Chart Historical Data Service. | 2019-12-20 13:56:27.529 Enabled for: Delayed Denali Real-Time Exchange Data Feed. | 2019-12-20 13:56:27.529 Allow Support for Sierra Chart Data Feeds is enabled. | 2019-12-20 13:56:27.529 Current selected Data/Trading service: CTS T4 FIX | 2019-12-20 13:56:27.529 Custom symbol settings values: enabled | 2019-12-20 13:56:27.529 Chart Update Interval: 500 | 2019-12-20 13:56:27.529 Intraday Data Storage Time Unit: 0 | 2019-12-20 13:56:27.529 Time Zone: -06:00:00 (CST-06CDT+01,M3.2.0/02:00,M11.1.0/02:00) | 2019-12-20 13:56:27.529 2019-12-20 13:56:27 Local computer time | 2019-12-20 13:56:27.529 2019-12-20 19:56:27 Local computer time in UTC | 2019-12-20 13:56:27.529 2019-12-20 13:56:27 Local computer time in SC Time Zone | 2019-12-20 13:56:27.529 2019-12-20 19:56:26 Server time in UTC | 2019-12-20 13:56:27.529 Local computer UTC time and Server UTC time difference: 0 seconds. | 2019-12-20 13:56:27.529 Program path: C:\SierraChart\ | 2019-12-20 13:56:27.529 Data Files path: C:\SierraChart\Data\ | 2019-12-20 13:56:27.529 OS Version Number: 10.0 | 2019-12-20 13:56:27.529 Locale Setting: C | 2019-12-20 13:56:27.529 DLLs: UserContributedStudies.dll, UserContributedStudies_64.dll | 2019-12-20 13:56:27.531 Checking for new symbol settings. Requested symbol settings MD5 for service code cts. Request ID: 1. | 2019-12-20 13:56:27.565 HTTPS connection ID:1 to login.sierrachart.com:443 for request ID:1 (1) | Shutdown started. Waiting for graceful close. | 2019-12-20 13:56:27.654 HTTPS connection ID:1 to login.sierrachart.com:443 for request ID:1 (1) | Socket gracefully closed by remote side. | 2019-12-20 13:56:27.783 HTTPS connection ID:1 to login.sierrachart.com:443 for request ID:1 (1) | Closed. | 2019-12-20 13:56:27.783 Received 5 login tokens. | 2019-12-20 13:56:28.049 Symbol settings MD5 received. Request ID: 1. | 2019-12-20 13:56:28.151 Symbol settings are up-to-date for cts. | 2019-12-20 13:56:28.151 CTS T4 FIX | Connecting to CTS Live server fix.t4login.com:10443 | 2019-12-20 13:56:33.144 CTS T4 FIX | Firm: 895 | 2019-12-20 13:56:33.144 CTS FIX socket (1) | Creating socket. Using TLS 1.0. | 2019-12-20 13:56:33.237 CTS FIX socket (1) | Connecting to IP: 74.201.6.106. | 2019-12-20 13:56:33.237 CTS FIX socket (1) | Connect event error. Windows error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | 2019-12-20 13:56:54.283 * CTS FIX socket (1) | CloseSocket call. | 2019-12-20 13:56:54.283 CTS FIX: Socket connection was closed without any logout messages sent or received. | 2019-12-20 13:56:54.283 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2019-12-20 13:56:54.283 Select 'File >> Disconnect' to prevent further connection attempts. | 2019-12-20 13:56:54.283 CTS FIX socket (1) | Closed. | 2019-12-20 13:56:54.283 CTS T4 FIX | Disconnected. | 2019-12-20 13:56:54.310 CTS T4 FIX | Connecting to CTS Live server fix.t4login.com:10443 | 2019-12-20 13:57:57.625 CTS T4 FIX | Firm: 895 | 2019-12-20 13:57:57.625 CTS FIX socket (1) | Creating socket. Using TLS 1.0. | 2019-12-20 13:57:58.164 CTS FIX socket (1) | Connecting to IP: 74.201.6.106. | 2019-12-20 13:57:58.165 CTS FIX socket (1) | Connect event error. Windows error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | 2019-12-20 13:58:19.207 * CTS FIX socket (1) | CloseSocket call. | 2019-12-20 13:58:19.207 CTS FIX: Socket connection was closed without any logout messages sent or received. | 2019-12-20 13:58:19.207 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2019-12-20 13:58:19.207 Select 'File >> Disconnect' to prevent further connection attempts. | 2019-12-20 13:58:19.207 CTS FIX socket (1) | Closed. | 2019-12-20 13:58:19.207 CTS T4 FIX | Disconnected. | 2019-12-20 13:58:19.222 CTS T4 FIX | Connecting to CTS Live server fix.t4login.com:10443 | 2019-12-20 13:59:06.962 CTS T4 FIX | Firm: 895 | 2019-12-20 13:59:06.962 CTS FIX socket (1) | Creating socket. Using TLS 1.0. | 2019-12-20 13:59:07.092 CTS FIX socket (1) | Connecting to IP: 74.201.6.106. | 2019-12-20 13:59:07.092 CTS FIX socket (1) | Connect event error. Windows error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | 2019-12-20 13:59:28.151 * CTS FIX socket (1) | CloseSocket call. | 2019-12-20 13:59:28.152 CTS FIX: Socket connection was closed without any logout messages sent or received. | 2019-12-20 13:59:28.152 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2019-12-20 13:59:28.152 Select 'File >> Disconnect' to prevent further connection attempts. | 2019-12-20 13:59:28.152 CTS FIX socket (1) | Closed. | 2019-12-20 13:59:28.152 CTS T4 FIX | Disconnected. | 2019-12-20 13:59:28.167 Checking for new symbol settings. Requested symbol settings MD5 for service code rithmic.trading. Request ID: 2. | 2019-12-20 13:59:40.167 Current selected Data/Trading service: Rithmic Trading | 2019-12-20 13:59:40.167 Symbol settings MD5 received. Request ID: 2. | 2019-12-20 13:59:40.853 Requested symbol settings for service code rithmic.trading. Request ID: 3. | 2019-12-20 13:59:40.854 Symbol settings received. Request ID: 3. | 2019-12-20 13:59:41.665 Rithmic Trading | Port for executable: 50127 | 2019-12-20 14:00:27.261 Listening socket (1604). Port 50127 | Closed. | 2019-12-20 14:00:27.261 Rithmic Trading | Starting server: C:\SierraChart\Rim\DTCBridge.exe | 2019-12-20 14:00:27.262 Created process C:\SierraChart\Rim\DTCBridge.exe. Parameters: /Port:50127. Current folder: C:\SierraChart\Rim | 2019-12-20 14:00:27.272 Rithmic Trading | Bridge process is running. | 2019-12-20 14:00:29.274 Rithmic Trading | Connecting to the server 127.0.0.1. Port 50127 | 2019-12-20 14:00:29.275 DTC Client socket (1) | Creating socket. | 2019-12-20 14:00:29.275 DTC Client socket (1) | Connecting to IP: 127.0.0.1. | 2019-12-20 14:00:29.275 Rithmic Trading | Connected to server. | 2019-12-20 14:00:29.276 Rithmic Trading | Starting socket receive thread. | 2019-12-20 14:00:29.276 Rithmic Trading | Sending encoding request to server: Binary VLS | 2019-12-20 14:00:29.276 Rithmic Trading | Setting DTC encoding to Binary VLS | 2019-12-20 14:00:29.277 Rithmic Trading | Sending logon request message. | 2019-12-20 14:00:29.277 Rithmic Trading | Message from server: Starting the connection process to data and trading service. | 2019-12-20 14:00:29.278 Rithmic Trading | Message from server: Logging is enabled. Log file: C:\SierraChart\Rim\Rithmic.log | 2019-12-20 14:00:29.280 Rithmic Trading | Message from server: Connecting to Rithmic 01 US server. | 2019-12-20 14:00:29.280 Rithmic Trading | Message from server: Server Alert: Market Data Connection Opened | 2019-12-20 14:00:31.834 Rithmic Trading | Message from server: Server Alert: Market Data Connection Login Complete. Result text: "ok" | 2019-12-20 14:00:31.884 Rithmic Trading | Message from server: Server Alert: Trading System Connection Opened | 2019-12-20 14:00:32.113 Rithmic Trading | Message from server: Server Alert: Trading System Connection Login Complete. Result text: "ok" | 2019-12-20 14:00:32.170 Rithmic Trading | Message from server: Server Alert: PnL Connection Opened | 2019-12-20 14:00:32.413 Rithmic Trading | Message from server: Server Alert: PnL Connection Login Complete. Result text: "ok" | 2019-12-20 14:00:32.461 Rithmic Trading | Message from server: Server Alert: Intraday History Connection Opened | 2019-12-20 14:00:32.703 Rithmic Trading | Message from server: Server Alert: Intraday History Connection Login Complete. Result text: "ok" | 2019-12-20 14:00:32.750 Rithmic Trading | Received logon response. | 2019-12-20 14:00:33.271 Rithmic Trading | Server Name: SC DTC Bridge. | 2019-12-20 14:00:33.271 Rithmic Trading | Server protocol version: 8. Client protocol version: 8 | 2019-12-20 14:00:33.271 Rithmic Trading | Successfully connected. IB='AMP', Firm='AMPClearing'. | 2019-12-20 14:00:33.271 Rithmic Trading | Trading is supported. | 2019-12-20 14:00:33.271 Rithmic Trading | Order cancel and replace is supported. | 2019-12-20 14:00:33.271 Rithmic Trading | OCO Orders supported. | 2019-12-20 14:00:33.271 Rithmic Trading | Connected to data and trading server. | 2019-12-20 14:00:33.271 Triggering next historical data download in queue. | 2019-12-20 14:00:33.271 Triggering next historical data download in queue. | 2019-12-20 14:00:33.271 Triggering next historical data download in queue. | 2019-12-20 14:00:33.271 Triggering next historical data download in queue. | 2019-12-20 14:00:33.271 Rithmic Trading | Message from server: Received unknown message type from DTC client. Type = 603 | 2019-12-20 14:00:33.395 |
| [2019-12-20 22:06:37] |
| |
|
Is there anything unusual about the network your computer is connected to? CTS T4 FIX | Connecting to CTS Live server fix.t4login.com:10443 | 2019-12-20 13:59:06.962 Quite clearly there is some network connectivity problem.
CTS T4 FIX | Firm: 895 | 2019-12-20 13:59:06.962 CTS FIX socket (1) | Creating socket. Using TLS 1.0. | 2019-12-20 13:59:07.092 CTS FIX socket (1) | Connecting to IP: 74.201.6.106. | 2019-12-20 13:59:07.092 CTS FIX socket (1) | Connect event error. Windows error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. | 2019-12-20 13:59:28.151 * 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: 2019-12-20 22:06:49
|
| [2019-12-20 22:47:26] |
| michael225 - Posts: 2 |
|
You nailed it. Left for the weekend and brought computer home. Fired right up. I have not noticed anything at office and seems to be working fine, but this is obviously the problem now... any suggestions on where to go next with this? Thanks an have a great weekend!
|
To post a message in this thread, you need to log in with your Sierra Chart account: