Support Board
Date/Time: Tue, 26 Nov 2024 04:28:00 +0000
Wrong trading account when connected to Rithmic
View Count: 587
| [2023-12-27 18:18:28] |
| Tofer - Posts: 38 |
|
Hello, I started today a new account with UProfit, and I can not manage to link the correct trading account, so I can not open orders from Sierra. My Data/Trade Service Settings is as indicated on the screenshot. I manage to connect, but when checking Trade -> Open Trade Window for Chart the account displayed there is my CQG account. Using RTrader Pro with the same settings works just fine. Never had an issue with other firms when connecting with Rithmic. Support on their side told me to contact Sierra, as they see everything correctly setup. I hope you can give me an advice. Thank you |
 Screenshot 2023-12-27 191539.png / V - Attached On 2023-12-27 18:16:21 UTC - Size: 36.04 KB - 133 views |
| [2023-12-27 20:30:03] |
| John - SC Support - Posts: 36286 |
|
Your image shows the server you are connected to as "Rithmic Paper Trading - Chicago Area - Aggregated". Are you certain that this is the correct server? UProfit, and other Prop Firms that use Rithmic, have their own set of servers listed in the list of servers. We assume that you would need to connect to one of the "UProfit" servers.
For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2023-12-28 08:03:16] |
| Tofer - Posts: 38 |
|
Hi John, yes I am, I also tried with the specific UProfit ones, however the official documentation (https://help.uprofittrader.com/hc/en-us/articles/6619815534484-How-do-I-set-up-my-Uprofit-account-) and the way I connect to RTrade Pro is using that specific server. Thanks |
| [2023-12-28 16:11:17] |
| John - SC Support - Posts: 36286 |
|
Even though your CQG account is showing in the Trade Window, open that section for the Account and see if your UProfit account is listed, and if so, then select it. If it is still not showing, then there must be something about the connection you are making that is not bringing in the account information. Check your Message Log and see if you are getting a "Permission Denied" error from Rithmic. If you are, then refer to the following: Rithmic Trading Platform Service: Permission Denied Resolution Procedure For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2023-12-29 17:14:45] |
| Tofer - Posts: 38 |
|
hi John their account doesn’t appear on the list, and I dont see a Permission Denied message. I contacted them back, after checking what you said, and I got what Im sharing on the screenshot. What do you say? Thank you |
Private File |
| [2023-12-29 17:57:42] |
| John - SC Support - Posts: 36286 |
|
Ok, then let's go through all of the items to check, one by one: - On the "Global Settings >> Data/Trade Service Settings" make sure you have Rithmic selected for the Current Selected Service and that you have the right server selected an that your Account Name and Password are correct. - Make sure you are connected to the service by selecting "File >> Connect". If this is greyed out and not selectable, then you are already connected. - Check the Message Log for possible errors by selecting "File >> Disconnect" and then selecting "Wiondow >> Message Log". Then do the following: - Select "File >> Disconnect". - On the Message Log select "Edit >> Clear Log". When prompted with "Clear Log Lines" answer "yes". - Select "File >> Connect". - Check the log to see if there are any messages about issues connecting to Rithmic. - Post the log here for us to see. - On an open chart, if the Trade Window for that chart is not already open, then select "Trade >> Open Trade Window for Chart". On the Trade Window, select the "Trade Accounts" field and see if the Rithmic Trading Account is showing in there. Refer to the following for where this item is located: Basic Trading and the Trade Window: Main/C >> Trade Account (Selecting Trade Account for Chart / Trade DOM) ------ There isn't anything else we can try. Hopefully one of these will resolve it. We definitely would like to see your Message Log from the instructions above, as hopefully that will have something in it that gives us a clue as to why there is an issue. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-01-01 19:55:33] |
| Tofer - Posts: 38 |
|
Hello! This is the full log, thanks!: Created the DTC Protocol server. | 2024-01-01 14:53:37.751 DTC Protocol Server listening on port 11099. | 2024-01-01 14:53:37.752 Reading Internal Order ID file. | 2024-01-01 14:53:37.752 HTTPS connection ID:1 to www.rithmic.com:443 for request ID:1 (4) | Creating socket. Using TLS 1.2. | 2024-01-01 14:53:37.837 HTTPS connection ID:1 to www.rithmic.com:443 for request ID:1 (4) | New receive buffer size: 0 | 2024-01-01 14:53:37.837 HTTPS connection ID:1 to www.rithmic.com:443 for request ID:1 (4) | Connecting to IP: 38.79.0.89. | 2024-01-01 14:53:37.837 Reading Trade Orders file. | 2024-01-01 14:53:37.913 Reading Trade Positions file. | 2024-01-01 14:53:37.914 Reading Trade Account Data files. | 2024-01-01 14:53:37.915 UDPListener (1628). Port 22904 | Listening on UDP port 22904. | 2024-01-01 14:53:37.921 Software version: 2568 64-bit | 2024-01-01 14:53:37.921 Primary Thread ID: 14684 | 2024-01-01 14:53:37.921 Usage end date: 2024-02-23 | 2024-01-01 14:53:37.921 Enabled for: Advanced Features 2. | 2024-01-01 14:53:37.921 Enabled for: Sierra Chart Historical Data Service. | 2024-01-01 14:53:37.921 Enabled for: Denali Real-Time Exchange Data Feed. | 2024-01-01 14:53:37.921 Enabled for: Delayed Denali Exchange Data Feed. | 2024-01-01 14:53:37.921 Enabled for exchange2: CME (Trading Account Required) | 2024-01-01 14:53:37.921 Enabled for exchange2: CBOT (Trading Account Required) | 2024-01-01 14:53:37.921 Enabled for exchange2: COMEX (Trading Account Required) | 2024-01-01 14:53:37.921 Enabled for exchange2: NYMEX (Trading Account Required) | 2024-01-01 14:53:37.921 Allow Support for Sierra Chart Data Feeds is enabled. | 2024-01-01 14:53:37.921 Current selected Data/Trading service: Rithmic Direct - DTC | 2024-01-01 14:53:37.921 Custom symbol settings values: enabled | 2024-01-01 14:53:37.921 Chart Update Interval: 300 | 2024-01-01 14:53:37.921 Intraday Data Storage Time Unit: 0 | 2024-01-01 14:53:37.921 Time Zone: -05:00:00 (EST-05EDT+01,M3.2.0/02:00,M11.1.0/02:00) | 2024-01-01 14:53:37.921 2024-01-01 19:53:37 Local computer time in UTC | 2024-01-01 14:53:37.921 2024-01-01 14:53:37 Local computer time in SC Time Zone | 2024-01-01 14:53:37.921 2024-01-01 19:53:35 Server time in UTC | 2024-01-01 14:53:37.921 Local computer UTC time and Server UTC time difference: 0 seconds. | 2024-01-01 14:53:37.921 Program path: C:\SierraChart\ | 2024-01-01 14:53:37.921 Data Files path: C:\SierraChart\Data\ | 2024-01-01 14:53:37.921 OS Version Number: 10.0 | 2024-01-01 14:53:37.921 Locale Setting: C | 2024-01-01 14:53:37.921 DLLs: Convergent_64.dll, cris-vwap-multiple_64.dll, cris-vwap_64.dll, UserContributedStudies_64.dll | 2024-01-01 14:53:37.958 Allowed protected custom studies: | 2024-01-01 14:53:37.958 Crash reporter started: true | 2024-01-01 14:53:37.958 Created the DTC Protocol historical data server. | 2024-01-01 14:53:37.987 HD Server Manager | Listening on port 11098. | 2024-01-01 14:53:37.989 Checking for new symbol settings. Requested symbol settings MD5 for service code rithmic_v2.trading. Request ID: 1. | 2024-01-01 14:53:37.990 HTTPS connection ID:1 to login.sierrachart.com:443 for request ID:1 (1) | Shutdown started. Waiting for graceful close. | 2024-01-01 14:53:38.092 HTTPS connection ID:1 to login.sierrachart.com:443 for request ID:1 (1) | Socket gracefully closed by remote side. | 2024-01-01 14:53:38.264 HTTPS connection ID:1 to login.sierrachart.com:443 for request ID:1 (1) | Closed. | 2024-01-01 14:53:38.264 Received 5 login tokens. | 2024-01-01 14:53:38.607 HTTPS connection ID:1 to www.rithmic.com:443 for request ID:1 (4) | Socket gracefully closed by remote side. | 2024-01-01 14:53:38.713 HTTPS connection ID:1 to www.rithmic.com:443 for request ID:1 (4) | CloseSocket call. | 2024-01-01 14:53:38.713 HTTPS connection ID:1 to www.rithmic.com:443 for request ID:1 (4) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2024-01-01 14:53:38.713 HTTPS connection ID:1 to www.rithmic.com:443 for request ID:1 (4) | Closed. | 2024-01-01 14:53:38.713 Symbol settings MD5 received. Request ID: 1. | 2024-01-01 14:53:40.228 Symbol settings are up-to-date for rithmic_v2.trading. | 2024-01-01 14:53:40.228 Requested user files to download. | 2024-01-01 14:53:40.480 Rithmic Direct - DTC | Using server connection: Rithmic Paper Trading-Chicago Area-Aggregated | 2024-01-01 14:54:09.321 Rithmic Direct - DTC | Connecting to the server rsc.rithmic.com. Port 50500 | 2024-01-01 14:54:09.323 DTC Client socket (1) | Creating socket. Using TLS 1.2. | 2024-01-01 14:54:09.435 DTC Client socket (1) | New receive buffer size: 0 | 2024-01-01 14:54:09.436 DTC Client socket (1) | Connecting to IP: 216.57.156.163. | 2024-01-01 14:54:09.436 Rithmic Direct - DTC | Network connection to server complete. | 2024-01-01 14:54:09.563 Rithmic Direct - DTC | Starting socket receive thread. | 2024-01-01 14:54:09.563 Rithmic Direct - DTC | Setting DTC encoding to Binary | 2024-01-01 14:54:09.564 Rithmic Direct - DTC | Sending logon request message. | 2024-01-01 14:54:09.564 Rithmic Direct - DTC | Received logon response. | 2024-01-01 14:54:09.948 Rithmic Direct - DTC | Server Name: . | 2024-01-01 14:54:09.948 Rithmic Direct - DTC | Server protocol version: 8. Client protocol version: 8 | 2024-01-01 14:54:09.948 Rithmic Direct - DTC | Successfully connected. | 2024-01-01 14:54:09.948 Rithmic Direct - DTC | Trading is supported. | 2024-01-01 14:54:09.948 Rithmic Direct - DTC | Order cancel and replace is supported. | 2024-01-01 14:54:09.948 Rithmic Direct - DTC | OCO Orders supported. | 2024-01-01 14:54:09.948 Rithmic Direct - DTC | Symbol and Exchange Delimiter: . | 2024-01-01 14:54:09.948 Rithmic Direct - DTC | Connected to server complete. | 2024-01-01 14:54:09.948 No download requests in the queue to start downloads for. | 2024-01-01 14:54:09.948 No download requests in the queue to start downloads for. | 2024-01-01 14:54:09.948 No download requests in the queue to start downloads for. | 2024-01-01 14:54:09.948 No download requests in the queue to start downloads for. | 2024-01-01 14:54:09.948 Subscribing to symbol for symbol alert. ZNZ0.CBOT | 2024-01-01 14:54:09.948 Mapping ZNZ0.CBOT to ZNZ20. Service code: cbot | 2024-01-01 14:54:09.948 Using symbol data fast lookup vector | 2024-01-01 14:54:09.948 Denali Data Feed | Starting real-time market data updates for: ZNZ0.CBOT (ZNZ20). ID: 1 Service code: cbot | 2024-01-01 14:54:09.948 Denali Data Feed | Connecting to the server ds28-2.sierracharts.com. Port 10048 | 2024-01-01 14:54:09.950 Denali Data Feed | Requesting security definition data for: ZNZ0.CBOT (ZNZ20). ID: 1 | 2024-01-01 14:54:09.953 Subscribing to symbol for symbol alert. ZNZ0.CBOT | 2024-01-01 14:54:09.953 Subscribing to symbol for symbol alert. TNZ0.CBOT | 2024-01-01 14:54:09.953 Mapping TNZ0.CBOT to TNZ20. Service code: cbot | 2024-01-01 14:54:09.953 Denali Data Feed | Starting real-time market data updates for: TNZ0.CBOT (TNZ20). ID: 2 Service code: cbot | 2024-01-01 14:54:09.953 Denali Data Feed | Requesting security definition data for: TNZ0.CBOT (TNZ20). ID: 2 | 2024-01-01 14:54:09.953 Subscribing to symbol for symbol alert. ZNH1.CBOT | 2024-01-01 14:54:09.953 Mapping ZNH1.CBOT to ZNH21. Service code: cbot | 2024-01-01 14:54:09.953 Denali Data Feed | Starting real-time market data updates for: ZNH1.CBOT (ZNH21). ID: 3 Service code: cbot | 2024-01-01 14:54:09.953 Denali Data Feed | Requesting security definition data for: ZNH1.CBOT (ZNH21). ID: 3 | 2024-01-01 14:54:09.953 Subscribing to symbol for symbol alert. ZNZ0.CBOT | 2024-01-01 14:54:09.953 Subscribing to symbol for symbol alert. ESZ0.CME | 2024-01-01 14:54:09.953 Mapping ESZ0.CME to ESZ20. Service code: cme | 2024-01-01 14:54:09.953 Denali Data Feed | Starting real-time market data updates for: ESZ0.CME (ESZ20). ID: 4 Service code: cme | 2024-01-01 14:54:09.954 Denali Data Feed | Requesting security definition data for: ESZ0.CME (ESZ20). ID: 4 | 2024-01-01 14:54:09.954 Subscribing to symbol for symbol alert. ESZ0.CME | 2024-01-01 14:54:09.954 Subscribing to symbol for symbol alert. CLX0.NYMEX | 2024-01-01 14:54:09.954 Mapping CLX0.NYMEX to CLX20. Service code: nymex | 2024-01-01 14:54:09.954 Denali Data Feed | Starting real-time market data updates for: CLX0.NYMEX (CLX20). ID: 5 Service code: nymex | 2024-01-01 14:54:09.954 Denali Data Feed | Requesting security definition data for: CLX0.NYMEX (CLX20). ID: 5 | 2024-01-01 14:54:09.954 Subscribing to symbol for symbol alert. CLX0.NYMEX | 2024-01-01 14:54:09.954 Subscribing to symbol for symbol alert. CLZ0.NYMEX | 2024-01-01 14:54:09.954 Mapping CLZ0.NYMEX to CLZ20. Service code: nymex | 2024-01-01 14:54:09.954 Denali Data Feed | Starting real-time market data updates for: CLZ0.NYMEX (CLZ20). ID: 6 Service code: nymex | 2024-01-01 14:54:09.955 Denali Data Feed | Requesting security definition data for: CLZ0.NYMEX (CLZ20). ID: 6 | 2024-01-01 14:54:09.955 Subscribing to symbol for symbol alert. CLZ0.NYMEX | 2024-01-01 14:54:09.955 Subscribing to symbol for symbol alert. CLZ0.NYMEX | 2024-01-01 14:54:09.955 Subscribing to symbol for symbol alert. ESH1.CME | 2024-01-01 14:54:09.955 Mapping ESH1.CME to ESH21. Service code: cme | 2024-01-01 14:54:09.955 Denali Data Feed | Starting real-time market data updates for: ESH1.CME (ESH21). ID: 7 Service code: cme | 2024-01-01 14:54:09.955 Denali Data Feed | Requesting security definition data for: ESH1.CME (ESH21). ID: 7 | 2024-01-01 14:54:09.955 Subscribing to symbol for symbol alert. ESM1.CME | 2024-01-01 14:54:09.955 Mapping ESM1.CME to ESM21. Service code: cme | 2024-01-01 14:54:09.955 Denali Data Feed | Starting real-time market data updates for: ESM1.CME (ESM21). ID: 8 Service code: cme | 2024-01-01 14:54:09.955 Denali Data Feed | Requesting security definition data for: ESM1.CME (ESM21). ID: 8 | 2024-01-01 14:54:09.955 Subscribing to symbol for symbol alert. ESU1.CME | 2024-01-01 14:54:09.955 Mapping ESU1.CME to ESU21. Service code: cme | 2024-01-01 14:54:09.955 Denali Data Feed | Starting real-time market data updates for: ESU1.CME (ESU21). ID: 9 Service code: cme | 2024-01-01 14:54:09.956 Denali Data Feed | Requesting security definition data for: ESU1.CME (ESU21). ID: 9 | 2024-01-01 14:54:09.956 Subscribing to symbol for symbol alert. ESU1.CME | 2024-01-01 14:54:09.956 Subscribing to symbol for symbol alert. ESU1.CME | 2024-01-01 14:54:09.956 DTC Client socket (2) | Creating socket. | 2024-01-01 14:54:10.053 DTC Client socket (2) | New receive buffer size: 0 | 2024-01-01 14:54:10.053 DTC Client socket (2) | Connecting to IP: 38.103.112.188. | 2024-01-01 14:54:10.053 Denali Data Feed | Network connection to server complete. | 2024-01-01 14:54:10.174 Denali Data Feed | Starting socket receive thread. | 2024-01-01 14:54:10.174 Denali Data Feed | Sending encoding request to server: Binary VLS. Compression: standard | 2024-01-01 14:54:10.174 Denali Data Feed | Setting DTC encoding to Binary VLS | 2024-01-01 14:54:10.312 Denali Data Feed | Sending logon request message. | 2024-01-01 14:54:10.312 Denali Data Feed | Received logon response. | 2024-01-01 14:54:10.937 Denali Data Feed | Server Name: SC Realtime Server. | 2024-01-01 14:54:10.937 Denali Data Feed | Server protocol version: 8. Client protocol version: 8 | 2024-01-01 14:54:10.937 Denali Data Feed | Successfully connected. | 2024-01-01 14:54:10.937 Denali Data Feed | Trading is not supported. | 2024-01-01 14:54:10.937 Denali Data Feed | Restarting real-time data updates for symbol: CLX0.NYMEX -> CLX20 | 2024-01-01 14:54:10.937 Denali Data Feed | Restarting real-time data updates for symbol: CLZ0.NYMEX -> CLZ20 | 2024-01-01 14:54:10.937 Denali Data Feed | Restarting real-time data updates for symbol: ESH1.CME -> ESH21 | 2024-01-01 14:54:10.937 Denali Data Feed | Restarting real-time data updates for symbol: ESM1.CME -> ESM21 | 2024-01-01 14:54:10.937 Denali Data Feed | Restarting real-time data updates for symbol: ESU1.CME -> ESU21 | 2024-01-01 14:54:10.937 Denali Data Feed | Restarting real-time data updates for symbol: ESZ0.CME -> ESZ20 | 2024-01-01 14:54:10.937 Denali Data Feed | Restarting real-time data updates for symbol: TNZ0.CBOT -> TNZ20 | 2024-01-01 14:54:10.937 Denali Data Feed | Restarting real-time data updates for symbol: ZNH1.CBOT -> ZNH21 | 2024-01-01 14:54:10.937 Denali Data Feed | Restarting real-time data updates for symbol: ZNZ0.CBOT -> ZNZ20 | 2024-01-01 14:54:10.937 Denali Data Feed | Real-time data for symbol CLX0.NYMEX is currently unavailable. | 2024-01-01 14:54:11.156 Denali Data Feed | Received security definition for symbol CLX0.NYMEX | 2024-01-01 14:54:11.156 Denali Data Feed | Real-time data for symbol CLZ0.NYMEX is currently unavailable. | 2024-01-01 14:54:11.156 Denali Data Feed | Received security definition for symbol CLZ0.NYMEX | 2024-01-01 14:54:11.156 Starting DelayedDownloadMonitoringTimer | 2024-01-01 14:54:11.156 Starting HDTimeoutTimer | 2024-01-01 14:54:11.156 Added historical Market depth data request for ESH1.CME to the queue. | 2024-01-01 14:54:11.156 Market depth data recording state for symbol ESH1.CME is set to download 'Pending'. | 2024-01-01 14:54:11.156 Triggering next historical data download in queue. | 2024-01-01 14:54:11.157 Historical Market depth data request for ESH1.CME is discarded because a matching download is already pending and the new one is not for earlier data. | 2024-01-01 14:54:11.158 Added historical Market depth data request for ESM1.CME to the queue. | 2024-01-01 14:54:11.158 Market depth data recording state for symbol ESM1.CME is set to download 'Pending'. | 2024-01-01 14:54:11.158 Historical Market depth data request for ESM1.CME is discarded because a matching download is already pending and the new one is not for earlier data. | 2024-01-01 14:54:11.158 Added historical Market depth data request for ESU1.CME to the queue. | 2024-01-01 14:54:11.158 Market depth data recording state for symbol ESU1.CME is set to download 'Pending'. | 2024-01-01 14:54:11.158 Historical Market depth data request for ESU1.CME is discarded because a matching download is already pending and the new one is not for earlier data. | 2024-01-01 14:54:11.158 Added historical Market depth data request for ESZ0.CME to the queue. | 2024-01-01 14:54:11.158 Market depth data recording state for symbol ESZ0.CME is set to download 'Pending'. | 2024-01-01 14:54:11.158 Historical Market depth data request for ESZ0.CME is discarded because a matching download is already pending and the new one is not for earlier data. | 2024-01-01 14:54:11.158 Denali Data Feed | Real-time data for symbol ESH1.CME is currently unavailable. | 2024-01-01 14:54:11.158 Denali Data Feed | Received security definition for symbol ESH1.CME | 2024-01-01 14:54:11.158 Denali Data Feed | Real-time data for symbol ESM1.CME is currently unavailable. | 2024-01-01 14:54:11.158 Denali Data Feed | Received security definition for symbol ESM1.CME | 2024-01-01 14:54:11.158 Denali Data Feed | Real-time data for symbol ESU1.CME is currently unavailable. | 2024-01-01 14:54:11.158 Denali Data Feed | Received security definition for symbol ESU1.CME | 2024-01-01 14:54:11.158 Denali Data Feed | Real-time data for symbol ESZ0.CME is currently unavailable. | 2024-01-01 14:54:11.158 Denali Data Feed | Received security definition for symbol ESZ0.CME | 2024-01-01 14:54:11.158 Denali Data Feed | Real-time data for symbol TNZ0.CBOT is currently unavailable. | 2024-01-01 14:54:11.158 Denali Data Feed | Received security definition for symbol TNZ0.CBOT | 2024-01-01 14:54:11.158 Denali Data Feed | Real-time data for symbol ZNH1.CBOT is currently unavailable. | 2024-01-01 14:54:11.158 Denali Data Feed | Received security definition for symbol ZNH1.CBOT | 2024-01-01 14:54:11.158 Denali Data Feed | Real-time data for symbol ZNZ0.CBOT is currently unavailable. | 2024-01-01 14:54:11.158 Denali Data Feed | Received security definition for symbol ZNZ0.CBOT | 2024-01-01 14:54:11.158 HD Request # 1 | Downloading Market depth data for ESH1.CME. Service: cme.marketdepth. | 2024-01-01 14:54:11.158 HD Request # 1 | Download start date-time: 2023-12-29 09:56:29.298557. | 2024-01-01 14:54:13.090 HD Request # 1 | Error downloading historical Market Depth data for ESH1.CME. Not downloading depth data earlier than 1 year ago | 2024-01-01 14:54:13.090 Historical data download thread signaled to stop. | 2024-01-01 14:54:13.090 HD Request # 1 | Received 0 Market depth data records from 00:00:00.000000 to 00:00:00.000000 (0.0 seconds and wrote 0 records for ESH1.CME | 2024-01-01 14:54:13.090 HD Request # 1 | Completion time: 2s. | 2024-01-01 14:54:13.090 HD Request # 1 | Market depth data download complete for ESH1.CME. Unique request ID: 1 | 2024-01-01 14:54:13.090 Removing historical data download ID 1. | 2024-01-01 14:54:13.090 Real-time market depth file updates started for ESH1.CME | 2024-01-01 14:54:13.090 Opened cached Depth file: C:\SierraChart\Data\MarketDepthData\ESH1.CME.2024-01-01.depth | 2024-01-01 14:54:13.091 Triggering next historical data download in queue. | 2024-01-01 14:54:13.091 HD Request # 2 | Downloading Market depth data for ESM1.CME. Service: cme.marketdepth. | 2024-01-01 14:54:13.091 HD Request # 2 | Download start date-time: 2023-12-29 09:56:29.298794. | 2024-01-01 14:54:13.149 HD Request # 2 | Error downloading historical Market Depth data for ESM1.CME. Not downloading depth data earlier than 1 year ago | 2024-01-01 14:54:13.149 Historical data download thread signaled to stop. | 2024-01-01 14:54:13.149 HD Request # 2 | Received 0 Market depth data records from 00:00:00.000000 to 00:00:00.000000 (0.0 seconds and wrote 0 records for ESM1.CME | 2024-01-01 14:54:13.149 HD Request # 2 | Completion time: 0s. | 2024-01-01 14:54:13.149 HD Request # 2 | Market depth data download complete for ESM1.CME. Unique request ID: 3 | 2024-01-01 14:54:13.149 Removing historical data download ID 3. | 2024-01-01 14:54:13.149 Real-time market depth file updates started for ESM1.CME | 2024-01-01 14:54:13.149 Opened cached Depth file: C:\SierraChart\Data\MarketDepthData\ESM1.CME.2024-01-01.depth | 2024-01-01 14:54:13.150 Triggering next historical data download in queue. | 2024-01-01 14:54:13.150 HD Request # 3 | Downloading Market depth data for ESU1.CME. Service: cme.marketdepth. | 2024-01-01 14:54:13.150 HD Request # 3 | Download start date-time: 2023-12-29 09:56:29.298964. | 2024-01-01 14:54:13.206 HD Request # 3 | Error downloading historical Market Depth data for ESU1.CME. Not downloading depth data earlier than 1 year ago | 2024-01-01 14:54:13.206 Historical data download thread signaled to stop. | 2024-01-01 14:54:13.206 HD Request # 3 | Received 0 Market depth data records from 00:00:00.000000 to 00:00:00.000000 (0.0 seconds and wrote 0 records for ESU1.CME | 2024-01-01 14:54:13.206 HD Request # 3 | Completion time: 0s. | 2024-01-01 14:54:13.206 HD Request # 3 | Market depth data download complete for ESU1.CME. Unique request ID: 5 | 2024-01-01 14:54:13.206 Removing historical data download ID 5. | 2024-01-01 14:54:13.206 Real-time market depth file updates started for ESU1.CME | 2024-01-01 14:54:13.206 Opened cached Depth file: C:\SierraChart\Data\MarketDepthData\ESU1.CME.2024-01-01.depth | 2024-01-01 14:54:13.207 Triggering next historical data download in queue. | 2024-01-01 14:54:13.207 HD Request # 4 | Downloading Market depth data for ESZ0.CME. Service: cme.marketdepth. | 2024-01-01 14:54:13.207 HD Request # 4 | Download start date-time: 2023-12-29 09:56:29.298323. | 2024-01-01 14:54:13.260 HD Request # 4 | Error downloading historical Market Depth data for ESZ0.CME. Not downloading depth data earlier than 1 year ago | 2024-01-01 14:54:13.260 Historical data download thread signaled to stop. | 2024-01-01 14:54:13.261 HD Request # 4 | Received 0 Market depth data records from 00:00:00.000000 to 00:00:00.000000 (0.0 seconds and wrote 0 records for ESZ0.CME | 2024-01-01 14:54:13.261 HD Request # 4 | Completion time: 0s. | 2024-01-01 14:54:13.261 HD Request # 4 | Market depth data download complete for ESZ0.CME. Unique request ID: 7 | 2024-01-01 14:54:13.261 Removing historical data download ID 7. | 2024-01-01 14:54:13.261 Real-time market depth file updates started for ESZ0.CME | 2024-01-01 14:54:13.261 Opened cached Depth file: C:\SierraChart\Data\MarketDepthData\ESZ0.CME.2024-01-01.depth | 2024-01-01 14:54:13.262 No download requests in the queue to start downloads for. | 2024-01-01 14:54:13.262 Requesting market depth updates for: ESH1.CME if supported. NumLevels=100 | 2024-01-01 14:54:14.932 Requesting market depth updates for: ESM1.CME if supported. NumLevels=100 | 2024-01-01 14:54:14.932 Requesting market depth updates for: ESU1.CME if supported. NumLevels=100 | 2024-01-01 14:54:14.932 Requesting market depth updates for: ESZ0.CME if supported. NumLevels=100 | 2024-01-01 14:54:14.932 Denali Data Feed | Market Depth data has been rejected for symbol: ESH1.CME. Not authorized for market depth. | 2024-01-01 14:54:15.156 Denali Data Feed | Market Depth data has been rejected for symbol: ESM1.CME. Not authorized for market depth. | 2024-01-01 14:54:15.156 Denali Data Feed | Market Depth data has been rejected for symbol: ESU1.CME. Not authorized for market depth. | 2024-01-01 14:54:15.156 Denali Data Feed | Market Depth data has been rejected for symbol: ESZ0.CME. Not authorized for market depth. | 2024-01-01 14:54:15.156 |
| [2024-01-02 15:23:44] |
| John - SC Support - Posts: 36286 |
|
Everything in your log looks good. You are connecting to the server "Rithmic Paper Trading-Chicago Area-Aggregated" just fine. Please select "Trade >> Trade Service Log". It's possible that there is something in this log that shows an error, but we are not hopeful. If none of these are working, then our only conclusion is that Rithmic does not have you setup for the account your are trying to find with that server. We do not know how they handle their accounts, so we do not know if this is per server or not, but somehow the account is not showing up for it to be shown in the list. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-01-03 10:47:26] |
| Tofer - Posts: 38 |
|
Hello I have this on the Trade Service Log === TradeActivity files query time: 0.761338 seconds. Entries: 0. Current queries: 2 | 2024-01-03 05:06:39.063 TradeActivity files query time: 0.033632 seconds. Entries: 103. Current queries: 1 | 2024-01-03 05:06:39.097 Rithmic Direct - DTC | Requesting trade accounts from server. | 2024-01-03 05:06:43.257 Rithmic Direct - DTC | Received 0 accounts from service. | 2024-01-03 05:06:43.382 Rithmic Direct - DTC | Requesting Trade Positions data. | 2024-01-03 05:06:43.512 Denali Data Feed | MaxConnectionsDifferentDevices = 1, NumCurrentConnectionsDifferentDevices = 1 | 2024-01-03 05:06:44.125 Denali Data Feed | MaxConnectionsForSameDevice = 3, NumCurrentConnectionsForSameDevice = 1 | 2024-01-03 05:06:44.125 TradeActivity files query time: 0.006352 seconds. Entries: 0. Current queries: 1 | 2024-01-03 05:06:57.621 TradeActivity files query time: 0.002574 seconds. Entries: 0. Current queries: 1 | 2024-01-03 05:06:59.421 TradeActivity files query time: 0.001994 seconds. Entries: 0. Current queries: 1 | 2024-01-03 05:07:07.027 TradeActivity files query time: 0.001847 seconds. Entries: 0. Current queries: 1 | 2024-01-03 05:07:12.683 TradeActivity files query time: 0.001103 seconds. Entries: 0. Current queries: 1 | 2024-01-03 05:07:21.790 TradeActivity files query time: 0.000684 seconds. Entries: 0. Current queries: 1 | 2024-01-03 05:07:29.811 TradeActivity files query time: 0.050539 seconds. Entries: 0. Current queries: 1 | 2024-01-03 05:09:13.435 === so that "Received 0 accounts from service" is telling that something is wrong on their side? thanks |
| [2024-01-03 13:31:36] |
| Sierra_Chart Engineering - Posts: 17179 |
|
Yes this is correct: so that "Received 0 accounts from service" is telling that something is wrong on their side? 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, use 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: