Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Fri, 10 May 2024 15:12:57 +0000
Unable to connect to Rithmic Trading
View Count: 741
| [2018-10-15 20:59:35] |
| User975649 - Posts: 9 |
|
Hi! I'm on version 1821 and I'm unable to connect to Rithmic Trading. I keep getting the same message log over and over. It keeps running. As I try to read it, it appears it's continuing to attempt to connect. It's saying "the target machine actively refused it." Would greatly appreciate your assistance. I will be sending the message log.
|
| [2018-10-15 21:09:25] |
| |
|
We have now released version 1822. This is a prerelease. We want you to update with Help >> Download Prerelease. When you are running 1822 and if you still have trouble connecting to Rithmic, follow the instructions here to provide the Message Log: https://www.sierrachart.com/index.php?page=PostingInformation.php#MessageLog 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-10-15 21:29:40] |
| User975649 - Posts: 9 |
|
Rithmic Trading | Port for executable: 61050 | 2018-10-15 21:24:53 Listening socket (1892). Port 61050 | Closed. | 2018-10-15 21:24:53 Rithmic Trading | Starting server: C:\SierraChart\Rim\DTCBridge.exe | 2018-10-15 21:24:53 Created process C:\SierraChart\Rim\DTCBridge.exe. Parameters: /Port:61050. Current folder: C:\SierraChart\Rim | 2018-10-15 21:24:53 Rithmic Trading | Bridge process is running. | 2018-10-15 21:24:55 Rithmic Trading | Connecting to the server 127.0.0.1. Port 61050 | 2018-10-15 21:24:55 DTC Client socket (2) | Creating socket. | 2018-10-15 21:24:55 DTC Client socket (2) | Connecting to IP: 127.0.0.1. | 2018-10-15 21:24:55 Rithmic Trading | Connected to server. | 2018-10-15 21:24:55 Rithmic Trading | Starting socket receive thread. | 2018-10-15 21:24:55 Rithmic Trading | Sending encoding request to server: Binary VLS | 2018-10-15 21:24:55 Rithmic Trading | Setting DTC encoding to Binary VLS | 2018-10-15 21:24:55 Rithmic Trading | Sending logon request message. | 2018-10-15 21:24:55 Rithmic Trading | Message from server: Starting the connection process to data and trading service. | 2018-10-15 21:24:55 Rithmic Trading | Message from server: Logging is enabled. Log file: C:\SierraChart\Rim\Rithmic.log | 2018-10-15 21:24:55 Rithmic Trading | Message from server: Connecting to Rithmic Paper Trading server. | 2018-10-15 21:24:55 Rithmic Trading | Message from server: Server Alert: Market Data Connection Opened | 2018-10-15 21:24:56 Rithmic Trading | Message from server: Server Alert: Market Data Connection Login Complete. Result text: "ok" | 2018-10-15 21:24:56 Rithmic Trading | Message from server: Server Alert: Trading System Connection Opened | 2018-10-15 21:24:56 Rithmic Trading | Message from server: Server Alert: Trading System Connection Login Complete. Result text: "ok" | 2018-10-15 21:24:56 Rithmic Trading | Message from server: Server Alert: PnL Connection Opened | 2018-10-15 21:24:57 Rithmic Trading | Message from server: Server Alert: PnL Connection Login Complete. Result text: "ok" | 2018-10-15 21:24:57 Rithmic Trading | Message from server: Server Alert: Intraday History Connection Opened | 2018-10-15 21:24:57 Rithmic Trading | Message from server: Server Alert: Intraday History Connection Login Complete. Result text: "ok" | 2018-10-15 21:24:57 Rithmic Trading | Received logon response. | 2018-10-15 21:24:57 Rithmic Trading | Server Name: SC DTC Bridge. | 2018-10-15 21:24:57 Rithmic Trading | Server protocol version: 8. Client protocol version: 8 | 2018-10-15 21:24:57 Rithmic Trading | Successfully connected. IB='OneUpTrader', Firm='OneUpTrader'. | 2018-10-15 21:24:57 Rithmic Trading | Trading is supported. | 2018-10-15 21:24:57 Rithmic Trading | Order cancel and replace is supported. | 2018-10-15 21:24:58 Rithmic Trading | OCO Orders supported. | 2018-10-15 21:24:58 Rithmic Trading | Connected to data and trading server. | 2018-10-15 21:24:58 Rithmic Trading | Connection to non-affiliated broker not allowed. | 2018-10-15 21:24:58 * Connection to the external service has been lost. | 2018-10-15 21:24:58 DTC Client socket (2) | Signaling to core to close socket | 2018-10-15 21:24:58 DTC Client socket (2) | Shutdown started. Waiting for graceful close. | 2018-10-15 21:24:58 Rithmic Trading | Disconnected. | 2018-10-15 21:24:58 Will reconnect to the server in 2.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2018-10-15 21:24:58 Date Time Of Last Edit: 2018-10-15 22:15:45
|
| [2018-10-16 00:15:45] |
| User975649 - Posts: 9 |
|
Hi again! Can you tell me what "Connection to non-affiliated broker not allowed" means? I have an account with AMP and One Up. I use Sierra and have one account with Sierra. Do I need to open a second account with Sierra to trade with One Up? They didn't seem to think so. They said all I needed to do was go under Data/Trade Service Settings and choose Rithmic Trading and make sure the server was set to Paper Trading Server. Any help you can provide will be greatly appreciated.
|
| [2018-10-16 00:58:56] |
| |
|
This is the relevant message: Rithmic Trading | Connection to non-affiliated broker not allowed. | 2018-10-15 21:24:58 * You need to have your own direct account for this: Direct Sierra Chart Account 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-10-16 00:59:12
|
To post a message in this thread, you need to log in with your Sierra Chart account: