Support Board
Date/Time: Tue, 13 Oct 2026 13:18:11 +0000
Current Selected Service remains read-only in sub-instance even when fully disconnected
View Count: 180
| [2026-08-25 09:57:58] |
| User995256 - Posts: 1 |
|
Setup: - Main instance: connected live to CQG (Trading is supported), Trade Simulation Mode Off. - Sub-instance #10, created via File >> New Instance, originally set to Service = DTC - Sub Instance, forwarding data/trading from the main instance (Service=cqg per Message Log). Goal: change Global Settings >> Data/Trade Service Settings >> Current Selected Service in sub-instance #10 from "DTC - Sub Instance" to "SC Data", so this sub-instance can run independently on the Delayed Exchange Data Feed with Trade Simulation Mode On, regardless of the main instance's connection state. Steps already taken, in order: 1. File >> Disconnect in sub-instance #10 — Current Selected Service still read-only. 2. Global Settings >> Data/Trade Service Settings >> Common Settings — set "Connect to Data/Trade Service at Startup" to No and disabled automatic reconnect on failure. Saved (OK). Still read-only after reconnecting/disconnecting. 3. Fully closed and reopened the Data/Trade Service Settings window after confirming disconnected status. No change. 4. Fully exited and restarted sub-instance #10. It still auto-connects to DTC - Sub Instance almost instantly on startup (within ~5ms per Message Log timestamps). 5. To rule out a reconnect race condition, disconnected/closed the MAIN instance entirely (killing the local DTC server on 127.0.0.1:11123), then reconnected sub-instance #10. Sub-instance is now genuinely disconnected (connection attempt fails, no DTC server listening). Current Selected Service is STILL read-only/grayed out in this state. Relevant Message Log excerpt from sub-instance #10 (from before the main instance was shut down, showing the successful DTC forward and full trading permissions): 2026-08-25 05:33:38.264 | DTC - Sub Instance | Connecting to the server 127.0.0.1. Port 11123 2026-08-25 05:33:38.269 | DTC - Sub Instance | Successfully connected. Connected to SC DTC Protocol server. Service=cqg|SymbolSettings=cqg. 2026-08-25 05:33:38.269 | DTC - Sub Instance | Trading is supported. 2026-08-25 05:33:38.269 | DTC - Sub Instance | OCO Orders supported. 2026-08-25 05:33:38.269 | DTC - Sub Instance | Bracket Orders supported. Message log from after exiting main instance: 2026-08-25 05:39:55.581 | DTC - Sub Instance | Market data feed reported to be lost. 2026-08-25 05:39:55.592 | DTC Client socket (1) | Socket gracefully closed by remote side. 2026-08-25 05:39:55.592 | DTC Client socket (1) | CloseSocket call. 2026-08-25 05:39:55.592 | DTC Client socket (1) | Signaling for receive thread to end. Bytes in receive buffer: 0 2026-08-25 05:39:55.592 | DTC Client socket (1) | Socket gracefully closed by remote side. 2026-08-25 05:39:55.593 | DTC Client socket (1) | Graceful close received or receive error. Shutdown complete. Closing socket now. 2026-08-25 05:39:55.593 | DTC Client socket (1) | Closed. 2026-08-25 05:39:55.593 | DTC - Sub Instance | Server has requested a logoff. Reason: Server is being shut down 2026-08-25 05:39:55.593 | Connection to the external service has been lost. 2026-08-25 05:39:55.608 | DTC Client socket (0) | CloseSocket call. 2026-08-25 05:39:55.608 | DTC - Sub Instance | Disconnected. Question: Is Current Selected Service in a File >> New Instance sub-instance permanently locked to DTC - Sub Instance and not changeable via the GUI, or is there a specific additional step required to unlock it for editing (e.g. an ini setting, or something only changeable from the main instance)? If there is a supported way to point a sub-instance directly at SC Data (bypassing DTC - Sub Instance) while keeping it created via File >> New Instance, please advise on the correct procedure. Thank you. |
 SierraVersion.png / V - Attached On 2026-08-25 09:54:12 UTC - Size: 42.46 KB - 40 views |
| [2026-08-25 14:57:00] |
| John - SC Support - Posts: 48184 |
|
Is Current Selected Service in a File >> New Instance sub-instance permanently locked to DTC - Sub Instance and not changeable via the GUI
Yes. Sub-instances started by selecting "File >> New Instance" are always tied to the main instance and thus have the "Current Selected Service" set to "DTC - Sub Instance". There is not a way to change the way a sub-instance is setup to do what you are wanting. We first want to point out that if the sub-instance has the option for "Trade >> Trade Simulation Mode On" enabled, then that sub-instance is only working in Simulation Mode locally. So no orders are going to the Main Instance, everything is contained within that sub-instance. If the above is not what you want, and you really want to have another instance of Sierra Chart connected to "SC Data", then you need to have a separate "Installation" of Sierra Chart (not started using File >> New Instance). A separate installation is completely independent from other Sierra Chart installations/instances. Refer to the following: Using Multiple Data and Trading Services at the Same Time: Step-By-Step Instructions to Install Multiple Copies of Sierra Chart If you plan on using Sub-Instances in this separate installation, then be sure to note that you need to change the port numbers. Refer to the following: Using DTC Server for Data and Trading in Another Sierra Chart Instance: Resolving DTC Protocol Server Port Number Conflicts 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: