Login Page - Create Account

Support Board


Date/Time: Tue, 26 Nov 2024 02:29:57 +0000



Connection problems using one SC live trading install, and SC data services install

View Count: 247

[2024-01-08 13:49:45]
User624595 - Posts: 207
v2570, Live IB install is working fine. SC Data install was working fine last week, but not this morning.

Not getting real-time connection/quotes, even though status bar is connected and green.

Continuous contract charts are still updating realtime price, but individual contract charts are not.


Errors in log:

1. "Logon error received from server: Data service (sc_exchange2.datafeed) is disabled or unsupported. A software update may be necessary."

2. "Listening socket (2524). Port 0 | Failed to bind socket to 0.0.0.0:11099. Windows error code 10048: Only one usage of each socket address (protocol/network address/port) is normally permitted. | 2024-01-08 08:12:35.663 *

3. "Encountered unknown field code when reading Trade Account Data file. Code: 2148 | 2024-01-08 08:38:31.465
"

4. "Listening socket (0). Port 0 | Closed listening socket. | 2024-01-08 08:12:35.663
DTC Protocol Server failed to start listening on port 11099. The DTC Protocol server is being disabled. | 2024-01-08 08:12:35.664 *"
[2024-01-08 18:17:12]
John - SC Support - Posts: 36286
To fix the particular error you are getting set "Global Settings >> Sierra Chart Server Settings >> DTC Protocol Server >> Additional Listening Port" to "0".

Let us know if you continue to have any issues after this.
For the most reliable, advanced, and zero cost futures order routing, use the Teton service:
Sierra Chart Teton Futures Order Routing
[2024-01-09 04:30:24]
User624595 - Posts: 207
Are all 4 errors due to that? Which of the options shown in the menu attached are the correct setting to change?

Which installs and subinstances should this be changed in?
image2024-01-08_23h28_44.png / V - Attached On 2024-01-09 04:28:59 UTC - Size: 29.17 KB - 48 views
[2024-01-09 18:19:55]
John - SC Support - Posts: 36286
The version you are running does not have that option, so this is due to something else.

If you have multiple installations of Sierra Chart running on the same computer, then these different installations can not all be accessing the TWS software at the same time - the TWS software is not setup for this. Make sure you have one installation running and that it can connect to TWS without any issue.

And when we refer to installations, we do mean separate installations, and not sub-instances. Sub-instances are started by selecting "File >> New Instance".
For the most reliable, advanced, and zero cost futures order routing, use the Teton service:
Sierra Chart Teton Futures Order Routing
[2024-01-09 18:53:06]
User624595 - Posts: 207
We are running a separate installation connecting to SC Data Services, with it's own set of subinstances. It is not connecting to TWS. This is the new setup/change, creating this, it was copied from the TWS installation (which also has it's own set of subinstances), then changed the DTS connection setting in the new install to SC Data services.

These errors all occurred in the SC Data Services installation. No issues with the TWS installation.
Date Time Of Last Edit: 2024-01-09 19:03:18
[2024-01-09 20:49:07]
John - SC Support - Posts: 36286
Error #1 can be ignored. That is a message that does not mean anything.

Error #2 should be related to what we had stated previously. Are you running the same version of Sierra Chart on both installations?

Error #3 can be ignored. It is stating that there is a problem reading a field in one of the Trade Activity files, but it is self-correcting in this case (i.e. it will just skip that entry). If there was a further problem, you would be given the filename and you would have to delete it.

Error #4 - is this coming from a Sub-Instance?
For the most reliable, advanced, and zero cost futures order routing, use the Teton service:
Sierra Chart Teton Futures Order Routing
[2024-01-10 04:03:24]
User624595 - Posts: 207
Yes both installs are v2570. Is the " Additional Listening Port" to "0" option in a newer version?

Yes we believe this error was from a sub-instance.
[2024-01-10 16:10:38]
John - SC Support - Posts: 36286
The option for "Additional Listening Port" is only on the last few releases.

Refer to the following, as this should explain and resolve the socket conflict errors:
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:

Login

Login Page - Create Account