Support Board
Date/Time: Sun, 19 Jan 2025 19:39:42 +0000
Limited to one connection per username for the requested data source
View Count: 945
| [2018-05-04 15:25:09] |
| Usermb - Posts: 126 |
|
Using 1727 and just now 1738, 32-bit I get the following error message, although I have booked two connections. Could you please look into this and let me know if there's anything I have to change in the configuration? SC Data - All Services | Connected to server. | 2018-05-04 17:20:12 SC Data - All Services | Starting socket receive thread. | 2018-05-04 17:20:12 SC Data - All Services | Sending encoding request to server: Binary VLS | 2018-05-04 17:20:12 SC Data - All Services | Setting DTC encoding to Binary VLS | 2018-05-04 17:20:12 SC Data - All Services | Sending logon request message. | 2018-05-04 17:20:12 SC Data - All Services | Received logon response. | 2018-05-04 17:20:12 SC Data - All Services | Server Name: SC Real-Time Server. | 2018-05-04 17:20:12 SC Data - All Services | Server protocol version: 8. Client protocol version: 8 | 2018-05-04 17:20:12 SC Data - All Services | Logon error received from server: Limited to one connection per username for the requested data source. | 2018-05-04 17:20:12 |
| [2018-05-04 15:44:08] |
| |
|
At this time we show that both of the real-time connections are logged in and in use. So this would seem to be a third connection. How many copies of Sierra Chart are you currently running? 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 |
| [2018-05-04 16:57:13] |
| Usermb - Posts: 126 |
|
Many instances, but only two of them connected to your data feed: one directly to SC Data and one configured as a CQG connection that uses the SC Data feed. To answer differently: the same number of instances I have run for the past 2-3 months without (almost) any issue at all. Almost any, because such an error popped up every now and them, once or twice per day, but today it popped up 100's of times. Anyway, I shut all instances down, upgraded them all, and not it seems stable. I'll let you know if it happens again. Date Time Of Last Edit: 2018-05-04 16:57:47
|
| [2018-05-07 02:00:23] |
| |
|
There really can be no doubt, that error was the result of a third connection attempt.
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: