Support Board
Date/Time: Fri, 26 Dec 2025 11:39:51 +0000
Sub Instances Connect To The Wrong
View Count: 32
| [2025-12-26 02:05:53] |
| User450463 - Posts: 130 |
|
I have a rather odd problem. I fire up an instance of Sierra and open a couple charts. Call this Inst1. Then I fire up another instance (Inst2), open a chart, and create two sub-instances. I then open a few chartbooks in each sub-instance.I noticed that the subinstances indicate they are connected to the data feed, but nothing is changing. It turns out that these subinstances are CONNECTING TO Inst1, and NOT Inst2 that they were created from. So they connect, but nothing is being processed. The charts in the subinstances never change - they appear "frozen" as far as incoming data goes. Sure enough, if I shut down Inst1 at this point, both subinstances complain they lost the data connection. I can work around this by firing up Inst2 and creating the subinstances, then fire up Inst1. This works fine. Anyhow, thought I would report this - as I say, I have a workaround, so it's not a big issue to me. It just looks like wires are getting crossed somewhere. By the way, I have two instances running because one is a prop firm, and the other is my personal AMP account. |
| [2025-12-26 02:31:45] |
| Sierra_Chart Engineering - Posts: 21989 |
|
This is managed by the server port numbers in each of the primary/server instances of Sierra Chart. Go through these instructions here to resolve: Using DTC Server for Data and Trading in Another Sierra Chart Instance: Resolving DTC Protocol Server Port Number Conflicts Make sure each instance, uses a different port number. And then reconnect the sub instances (File >> Reconnect). 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 Date Time Of Last Edit: 2025-12-26 02:33:14
|
| [2025-12-26 03:14:45] |
| User450463 - Posts: 130 |
|
What I called "Inst1" above already has DTC Server set to "No". Inst2 has it set to Yes, and the ports are 11099/11098. It seems that this is the correct setup. One of them has it enabled, the other one does not. This is already the way it's set up yet I still get the undesirable behavior. Just for fun, I tried turning DTC Server to "Yes" in Inst1. I change the setting, and hit Apply All. The parameter immediately changes to "No". So it won't let me turn it on anyway. I was going to turn it on and then change the port numbers to avoid any conflict with Inst2. Am I doing something wrong? |
| [2025-12-26 04:15:19] |
| Sierra_Chart Engineering - Posts: 21989 |
|
. It turns out that these subinstances are CONNECTING TO Inst1, If the DTC server in instance 1 is disabled, then this is an impossibility.Make sure the DTC Server is disabled in all of the sub instances. 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 Date Time Of Last Edit: 2025-12-26 04:15:38
|
To post a message in this thread, you need to log in with your Sierra Chart account: