Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Wed, 15 May 2024 12:46:15 +0000
Connection to non-affiliated broker not allowed
View Count: 1949
| [2017-10-06 17:03:37] |
| User444658 - Posts: 4 |
|
Hello, I'm trying to figure out where's the problem connecting to my live AMP account. I'm using Rithmic data feed/trading route service. Connection using R|Trader works fine with the same credentials, except I'm not receiving actual balance and account info, which is probably caused by AMP servers not providing such feedback as it's been not present since account creation. But that's probably question for Rithmic support. I could connect flawlessly using Sierra Chart as well but about 2 days ago, connection progress always ends up with the fore-mentioned error message. I'd solved that with Rithmic but I have to be sure it's not Sierra Chart connection issue, caused for example by some recent DTCBridge update. Message log follows Reading Internal Order ID file. | 2017-10-06 11:35:36 Reading Trade Orders file. | 2017-10-06 11:35:36 Reading Trade Positions file. | 2017-10-06 11:35:36 Listening on UDP port 22903. | 2017-10-06 11:35:36 Software version: 1621 | 2017-10-06 11:35:36 Enabled for: Advanced Features. | 2017-10-06 11:35:36 Enabled for: Advanced Features 2. | 2017-10-06 11:35:36 Enabled for: Sierra Chart Historical Data Service. | 2017-10-06 11:35:36 Allow Support for Sierra Chart Data Feeds is enabled. | 2017-10-06 11:35:36 Current selected Data/Trading service: Rithmic Trading | 2017-10-06 11:35:36 Chart Update Interval: 10 | 2017-10-06 11:35:36 Data/Trade Service Settings automatically set. | 2017-10-06 11:35:36 Time Zone: -05:00:00 (CST-06CDT+01,M3.2.0/02:00,M11.1.0/02:00) | 2017-10-06 11:35:36 2017-10-06 18:35:40 Local computer time | 2017-10-06 11:35:36 2017-10-06 16:35:40 Local computer time in UTC | 2017-10-06 11:35:36 2017-10-06 11:35:40 Local computer time in SC Time Zone | 2017-10-06 11:35:36 2017-10-06 16:35:39 Server time in UTC | 2017-10-06 11:35:36 Local computer UTC time and Server UTC time difference: 1 seconds. | 2017-10-06 11:35:36 Program path: C:\SierraChart\ | 2017-10-06 11:35:36 Data Files path: C:\SierraChart\Data\ | 2017-10-06 11:35:36 OS Version Number: 10.0 | 2017-10-06 11:35:36 Locale Setting: C | 2017-10-06 11:35:36 Checking for new symbol settings for service code rim | 2017-10-06 11:35:36 HTTPS connection to www.sierrachart.com:443 (4) | Creating socket. Using TLS 1.2. | 2017-10-06 11:35:36 HTTPS connection to www.sierrachart.com:443 (4) | Connecting to IP: 204.15.192.108. | 2017-10-06 11:35:36 Received 5 login tokens. | 2017-10-06 11:35:41 Symbol settings are up-to-date for rim | 2017-10-06 11:35:41 HTTPS connection to www.sierrachart.com:443 (5) | Creating socket. Using TLS 1.2. | 2017-10-06 11:35:43 HTTPS connection to www.sierrachart.com:443 (5) | Connecting to IP: 204.15.192.108. | 2017-10-06 11:35:43 HTTPS connection to www.sierrachart.com:443 (2) | Socket gracefully closed by remote side. | 2017-10-06 11:35:46 HTTPS connection to www.sierrachart.com:443 (2) | Initiating close of socket by core. | 2017-10-06 11:35:46 HTTPS connection to www.sierrachart.com:443 (2) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2017-10-06 11:35:46 HTTPS connection to www.sierrachart.com:443 (2) | Closed. | 2017-10-06 11:35:46 HTTPS connection to www.sierrachart.com:443 (4) | Socket gracefully closed by remote side. | 2017-10-06 11:35:46 HTTPS connection to www.sierrachart.com:443 (4) | Received socket Close event. | 2017-10-06 11:35:46 HTTPS connection to www.sierrachart.com:443 (4) | Initiating close of socket by core. | 2017-10-06 11:35:46 HTTPS connection to www.sierrachart.com:443 (4) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2017-10-06 11:35:46 HTTPS connection to www.sierrachart.com:443 (4) | Closed. | 2017-10-06 11:35:46 HTTPS connection to www.sierrachart.com:443 (5) | Socket gracefully closed by remote side. | 2017-10-06 11:35:48 HTTPS connection to www.sierrachart.com:443 (5) | Received socket Close event. | 2017-10-06 11:35:48 HTTPS connection to www.sierrachart.com:443 (5) | Initiating close of socket by core. | 2017-10-06 11:35:48 HTTPS connection to www.sierrachart.com:443 (5) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2017-10-06 11:35:48 HTTPS connection to www.sierrachart.com:443 (5) | Closed. | 2017-10-06 11:35:48 Rithmic Trading | Port for executable: 51931 | 2017-10-06 11:35:51 Listening socket (1100). Port 51931 | Closed. | 2017-10-06 11:35:51 Rithmic Trading | Starting server: C:\SierraChart\Rim\DTCBridge.exe | 2017-10-06 11:35:51 Rithmic Trading | Bridge process is running. | 2017-10-06 11:35:53 Rithmic Trading | Connecting to the server 127.0.0.1. Port 51931 | 2017-10-06 11:35:53 DTC Client socket (6) | Creating socket. | 2017-10-06 11:35:53 DTC Client socket (6) | Connecting to IP: 127.0.0.1. | 2017-10-06 11:35:53 Rithmic Trading | Connected to server. | 2017-10-06 11:35:53 Rithmic Trading | Starting socket receive thread. | 2017-10-06 11:35:53 Rithmic Trading | Sending Encoding Request to server | 2017-10-06 11:35:53 Rithmic Trading | Setting DTC encoding to Binary VLS | 2017-10-06 11:35:53 Rithmic Trading | Sending logon request message. | 2017-10-06 11:35:53 Rithmic Trading | Message from server: Starting the connection process to data and trading service. | 2017-10-06 11:35:53 Rithmic Trading | Message from server: Logging is enabled. Log file: C:\SierraChart\Rim\Rithmic.log | 2017-10-06 11:35:53 Rithmic Trading | Message from server: Connecting to Rithmic 01 US server. | 2017-10-06 11:35:53 Rithmic Trading | Message from server: Server Alert: Market Data Connection Opened | 2017-10-06 11:35:55 Rithmic Trading | Message from server: Server Alert: Market Data Connection Login Complete. Result text: "ok" | 2017-10-06 11:35:56 Rithmic Trading | Message from server: Server Alert: Trading System Connection Opened | 2017-10-06 11:35:57 Rithmic Trading | Message from server: Server Alert: Trading System Connection Login Complete. Result text: "ok" | 2017-10-06 11:35:57 Rithmic Trading | Message from server: Server Alert: PnL Connection Opened | 2017-10-06 11:35:58 Rithmic Trading | Message from server: Server Alert: PnL Connection Login Complete. Result text: "ok" | 2017-10-06 11:35:58 Rithmic Trading | Message from server: Server Alert: Intraday History Connection Opened | 2017-10-06 11:35:59 Rithmic Trading | Message from server: Server Alert: Intraday History Connection Login Complete. Result text: "ok" | 2017-10-06 11:35:59 Rithmic Trading | Received logon response. | 2017-10-06 11:35:59 Rithmic Trading | Server Name: SC DTC Bridge. | 2017-10-06 11:35:59 Rithmic Trading | Server protocol version: 8. Client protocol version: 8 | 2017-10-06 11:35:59 Rithmic Trading | Successfully connected. IB='', Firm=''. | 2017-10-06 11:35:59 Rithmic Trading | Trading is supported. | 2017-10-06 11:35:59 Rithmic Trading | Order cancel and replace is supported. | 2017-10-06 11:35:59 Rithmic Trading | OCO Orders supported. | 2017-10-06 11:35:59 Rithmic Trading | Connected to data and trading server. | 2017-10-06 11:35:59 Rithmic Trading | Connection to non-affiliated broker not allowed. | 2017-10-06 11:35:59 * Connection to the external service has been lost. | 2017-10-06 11:35:59 DTC Client socket (6) | Initiating close of socket by core. | 2017-10-06 11:35:59 Rithmic Trading | Disconnected. | 2017-10-06 11:35:59 DTC Client socket (6) | Shutdown started. Waiting for graceful close. | 2017-10-06 11:35:59 Will reconnect to the server in 2.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2017-10-06 11:35:59 Rithmic Trading | Port for executable: 51945 | 2017-10-06 11:36:01 Listening socket (1168). Port 51945 | Closed. | 2017-10-06 11:36:01 Rithmic Trading | Starting server: C:\SierraChart\Rim\DTCBridge.exe | 2017-10-06 11:36:01 Rithmic Trading | Bridge process is not running! | 2017-10-06 11:36:03 Rithmic Trading | Connecting to the server 127.0.0.1. Port 51945 | 2017-10-06 11:36:03 DTC Client socket (7) | Creating socket. | 2017-10-06 11:36:03 DTC Client socket (7) | Connecting to IP: 127.0.0.1. | 2017-10-06 11:36:03 DTC Client socket (7) | Connect event error. Windows error code 10061: Nemohlo být vytvořeno žádné připojení, protože cílový počítač je aktivně odmítl. | 2017-10-06 11:36:04 * DTC Client socket (7) | Initiating close of socket by core. | 2017-10-06 11:36:04 DTC Client socket (7) | Closed. | 2017-10-06 11:36:04 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2017-10-06 11:36:04 Select 'File >> Disconnect' to prevent further connection attempts. | 2017-10-06 11:36:04 Rithmic Trading | Disconnected. | 2017-10-06 11:36:04 Will reconnect to the server in 2.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2017-10-06 11:36:04 Rithmic Trading | Port for executable: 51947 | 2017-10-06 11:36:06 Listening socket (1196). Port 51947 | Closed. | 2017-10-06 11:36:06 Rithmic Trading | Starting server: C:\SierraChart\Rim\DTCBridge.exe | 2017-10-06 11:36:06 Rithmic Trading | Bridge process is not running! | 2017-10-06 11:36:08 Rithmic Trading | Connecting to the server 127.0.0.1. Port 51947 | 2017-10-06 11:36:08 DTC Client socket (8) | Creating socket. | 2017-10-06 11:36:08 DTC Client socket (8) | Connecting to IP: 127.0.0.1. | 2017-10-06 11:36:08 DTC Client socket (8) | Connect event error. Windows error code 10061: Nemohlo být vytvořeno žádné připojení, protože cílový počítač je aktivně odmítl. | 2017-10-06 11:36:09 * DTC Client socket (8) | Initiating close of socket by core. | 2017-10-06 11:36:09 DTC Client socket (8) | Closed. | 2017-10-06 11:36:09 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2017-10-06 11:36:09 Select 'File >> Disconnect' to prevent further connection attempts. | 2017-10-06 11:36:09 Rithmic Trading | Disconnected. | 2017-10-06 11:36:09 Will reconnect to the server in 2.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2017-10-06 11:36:09 File >> Disconnect selected. | 2017-10-06 11:36:11 Rithmic Trading | Disconnected. | 2017-10-06 11:36:11 |
| [2017-10-06 17:53:57] |
| |
|
There clearly is something wrong with the configuration of your Rithmic account because it indicates no Introducing Broker or clearing Firm: Rithmic Trading | Successfully connected. IB='', Firm=''. | 2017-10-06 11:35:59 Ask your broker 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 Date Time Of Last Edit: 2017-10-06 17:54:17
|
| [2017-10-06 18:05:35] |
| User444658 - Posts: 4 |
|
Thank you for the response, problem is it looked this way all the time and I had no troubles to connect before It always reported Rithmic Trading | Successfully connected. IB='', Firm='' so it doesn't look to be the major cause of this problem AMP support looks like a bunch of noobs when it comes to account configuration or technical description of anything so I'm trying to figure it out myself |
| [2017-10-06 18:40:21] |
| |
|
We can solve this, but it is just this one isolated case. Just give us about a day to think this through. Another possibility is just to use a direct Sierra Chart account: 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 |
| [2017-10-09 21:52:18] |
| |
|
We apologize. We realize we have taken longer than a day for this. Is it possible for you to use CQG instead of Rithmic. Here is information about CQG: CQG Trading Platform Service That would be the preferred solution. AMP can switch over to CQG. 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 |
| [2017-10-09 22:16:14] |
| User444658 - Posts: 4 |
|
No problem, maybe it can be fixed from AMP side as well but I'm solving it 2 weeks with them with no progress yet. So you are still super responsible in comparison ;) I'd switched to CQG but from the reviews and comparison videos I'm getting impression it lags too much in critical moments to be used as a solid datafeed for orderflow trader over the Rithmic. So if time is not an issue, I'd rather stick with Rithmic. I also plan to implement R|Api in my own trading bot in future and I don't know if CQG offers something similar and well documented. #edit# I found out they offer something similar for common users but it's implementation is far from being optimal, it's based on COM model which I'm not a big fan of as any universal API involves another lags in the processing chain and it requires their platform to run in background #edit# Date Time Of Last Edit: 2017-10-10 00:54:03
|
| [2017-10-10 14:22:43] |
| User444658 - Posts: 4 |
|
Problem solved, it was caused by the broker account not being associated with Rithmic user. Thank you very much for the info provided. |
| [2017-10-10 16:58:54] |
| |
|
I'd switched to CQG but from the reviews and comparison videos I'm getting impression it lags too much in critical moments to be used as a solid datafeed for orderflow trader over the Rithmic. http://www.sierrachart.com/index.php?page=doc/helpdetails4.html You can also use the Sierra Chart Exchange Data Feed: http://www.sierrachart.com/index.php?page=doc/SierraChartRealTimeFuturesStockDataFeed.php I also plan to implement R|Api in my own trading bot in future and I don't know if CQG offers something similar and well documented.
Rather than using either of those APIs you really should use the DTC Protocol which you can use with either CQG or Rithmic.DTC Protocol Various encodings are supported and this is a well-designed API to give you a normalized low latency interface to CQG and Rithmic through a network connection which is the proper way. This is good the problem is resolved. 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 |
| [2017-10-19 07:45:06] |
| User194343 - Posts: 24 |
|
Hello SierraChart! I have same problem with CTS demo account, with AMP SierraChart Login. "Connection to non-affiliated broker not allowed" In 1621 version - it's OK. 1624 already not ok. For CQG Datafeed it's ok! Is it possible to solve issue with CTS demo? Or it will be a permanently? with respect, Anthony Date Time Of Last Edit: 2017-10-19 07:54:47
|
| [2017-10-19 10:08:40] |
| |
|
Update to release 1625 with Help >> Download Prerelease. If you still have a problem, then post a copy of the Message Log after trying to connect with File >> Connect to Data Feed, by following the instructions here: 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 |
| [2017-10-19 10:53:49] |
| User194343 - Posts: 24 |
|
Sorry! Still NOT working Reading Internal Order ID file. | 2017-10-19 06:53:01 Reading Trade Orders file. | 2017-10-19 06:53:01 Reading Trade Positions file. | 2017-10-19 06:53:01 Listening on UDP port 22903. | 2017-10-19 06:53:01 Software version: 1625 | 2017-10-19 06:53:01 Enabled for: Advanced Features. | 2017-10-19 06:53:01 Enabled for: Sierra Chart Historical Data Service. | 2017-10-19 06:53:01 Allow Support for Sierra Chart Data Feeds is enabled. | 2017-10-19 06:53:01 Current selected Data/Trading service: CTS T4 FIX | 2017-10-19 06:53:01 Chart Update Interval: 500 | 2017-10-19 06:53:01 Time Zone: -04:00:00 (EST-05EDT+01,M3.2.0/02:00,M11.1.0/02:00) | 2017-10-19 06:53:01 2017-10-19 06:53:05 Local computer time | 2017-10-19 06:53:01 2017-10-19 10:53:05 Local computer time in UTC | 2017-10-19 06:53:01 2017-10-19 06:53:05 Local computer time in SC Time Zone | 2017-10-19 06:53:01 2017-10-19 10:53:04 Server time in UTC | 2017-10-19 06:53:01 Local computer UTC time and Server UTC time difference: 0 seconds. | 2017-10-19 06:53:01 Program path: C:\System\Market\Terminal\SierraChart.CTS\ | 2017-10-19 06:53:01 Data Files path: C:\System\Market\Terminal\SierraChart.CTS\SCID\ | 2017-10-19 06:53:01 OS Version Number: 6.1 | 2017-10-19 06:53:01 Locale Setting: C | 2017-10-19 06:53:01 Checking for new symbol settings for service code cts | 2017-10-19 06:53:01 HTTPS connection to www.sierrachart.com:443 (4) | Creating socket. Using TLS 1.2. | 2017-10-19 06:53:01 HTTPS connection to www.sierrachart.com:443 (4) | Connecting to IP: 204.15.192.108. | 2017-10-19 06:53:01 Received 5 login tokens. | 2017-10-19 06:53:06 Requesting symbol settings for service code cts. Overwrite = on. | 2017-10-19 06:53:06 Symbol settings received. | 2017-10-19 06:53:07 Processed 1324 symbol settings. | 2017-10-19 06:53:07 HTTPS connection to www.sierrachart.com:443 (5) | Creating socket. Using TLS 1.2. | 2017-10-19 06:53:08 HTTPS connection to www.sierrachart.com:443 (5) | Connecting to IP: 204.15.192.108. | 2017-10-19 06:53:08 HTTPS connection to www.sierrachart.com:443 (2) | Socket gracefully closed by remote side. | 2017-10-19 06:53:12 HTTPS connection to www.sierrachart.com:443 (2) | Received socket Close event. | 2017-10-19 06:53:12 HTTPS connection to www.sierrachart.com:443 (2) | Initiating close of socket by core. | 2017-10-19 06:53:12 HTTPS connection to www.sierrachart.com:443 (2) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2017-10-19 06:53:12 HTTPS connection to www.sierrachart.com:443 (2) | Closed. | 2017-10-19 06:53:12 HTTPS connection to www.sierrachart.com:443 (4) | Socket gracefully closed by remote side. | 2017-10-19 06:53:12 HTTPS connection to www.sierrachart.com:443 (4) | Received socket Close event. | 2017-10-19 06:53:12 HTTPS connection to www.sierrachart.com:443 (4) | Initiating close of socket by core. | 2017-10-19 06:53:12 HTTPS connection to www.sierrachart.com:443 (4) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2017-10-19 06:53:12 HTTPS connection to www.sierrachart.com:443 (4) | Closed. | 2017-10-19 06:53:12 HTTPS connection to www.sierrachart.com:443 (5) | Socket gracefully closed by remote side. | 2017-10-19 06:53:14 HTTPS connection to www.sierrachart.com:443 (5) | Received socket Close event. | 2017-10-19 06:53:14 HTTPS connection to www.sierrachart.com:443 (5) | Initiating close of socket by core. | 2017-10-19 06:53:14 HTTPS connection to www.sierrachart.com:443 (5) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2017-10-19 06:53:14 HTTPS connection to www.sierrachart.com:443 (5) | Closed. | 2017-10-19 06:53:14 CTS T4 FIX | Connection to non-affiliated broker not allowed. | 2017-10-19 06:53:17 * |
| [2017-10-19 17:14:17] |
| |
|
What is Global Settings >> Data/Trade Service Settings >> Service Setting >> Firm set to?
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: 2017-10-19 17:14:28
|
| [2017-10-19 19:17:14] |
| User194343 - Posts: 24 |
|
CTS! With 1621 - it's ok ;(((( |
| [2017-10-19 19:28:53] |
| |
|
Is that a demo account you are using with the CTS firm? In the newer versions, the firm must be AMP if you are using a Sierra Chart account provided by AMP.
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: 2017-10-19 19:29:23
|
| [2017-10-19 19:42:06] |
| User194343 - Posts: 24 |
|
https://cts.sim.t4login.com/register/ i am always use this one. what i need to set as a firm in firm field at newer version for working with this demo? thank u |
| [2017-10-19 20:17:58] |
| |
|
The firm has to remain as CTS in this case. To be able to connect to a firm different than AMP requires a direct account: 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 |
| [2017-10-19 20:20:58] |
| User194343 - Posts: 24 |
|
oh i c! 1621 was last version without that limitation? |
To post a message in this thread, you need to log in with your Sierra Chart account: