Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Fri, 19 Apr 2024 13:38:57 +0000
protocol mismatch - one connection per username
View Count: 893
| [2014-11-26 12:38:15] |
| jesslinn - Posts: 108 |
|
I signed up for a second connection to SC datafeed, and it worked for a few days, but now it is not connecting and giving me both a protocol mismatch message and a login error message. Any ideas? |
| [2014-11-26 14:37:20] |
| jesslinn - Posts: 108 |
|
It is working now, so no need to respond. It is possible that I had a third SC open that was enabled for SC datafeed. Perhaps at some point it would be worth cleaning up the error message since it was not a protocol error and was not that only one connection per username was allowed. |
| [2014-11-26 14:38:32] |
| |
|
We need to actually see the messages from the Message Log. Post them here.
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 |
| [2014-11-26 15:08:02] |
| jesslinn - Posts: 108 |
|
Using username 0 | 2014-11-26 15:06:05 SC Exchange Data | Connecting to the server scdf2.sierracharts.com. Port 10047 | 2014-11-26 15:06:05 Socket (0) | Resolved address ds7.sierracharts.com to IP 8.18.161.133 | 2014-11-26 15:06:05 Socket (1672) | Connected. | 2014-11-26 15:06:06 SC Exchange Data | Connected to server. | 2014-11-26 15:06:06 SC Exchange Data | Sending logon request message. | 2014-11-26 15:06:06 SC Exchange Data | Server Name: SC Real-Time Server. | 2014-11-26 15:06:06 SC Exchange Data | Server protocol version: 4. Client protocol version: 4. There is a protocol match. | 2014-11-26 15:06:06 SC Exchange Data | Logon error from server : Limited to one connection per username for the requested data source. | 2014-11-26 15:06:06 Socket (1672) | Shutdown and closed. | 2014-11-26 15:06:06 SC Exchange Data | Disconnected from the server. | 2014-11-26 15:06:06 SC Exchange Data | Data feed disconnected. Will reconnect. | 2014-11-26 15:06:06 |
| [2014-11-26 15:09:40] |
| jesslinn - Posts: 108 |
|
I do get the above if I start up a third copy of SC that is enabled for the SC datafeed, so it seems to be working as it should. It is just that the error message is misleading. |
| [2014-11-26 16:33:32] |
| |
|
This looks correct to us: SC Exchange Data | Server protocol version: 4. Client protocol version: 4. There is a protocol match. | 2014-11-26 15:06:06 It is indicating there is a match and not a mismatch. 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 |
To post a message in this thread, you need to log in with your Sierra Chart account: