Support Board
Date/Time: Mon, 15 Sep 2025 12:08:38 +0000
Post From: Keep getting disconnected -- No Historical Data Download
| [2020-11-16 06:42:59] |
| User99582 - Posts: 8 |
|
I usually have zero problems with your software, but when things change on the backend I usually find out through the error log. Maybe I missed an announcement, I don't know. I require 32 bit support because my custom indicators were compiled for it, and to do so for x64 is outside my grasp. I've been running v2086 with zero problems up to today (Nov 16 2020), and now, all of a sudden the server disconnects, and I don't get any historical data downloaded for my intraday chart despite having an active service package for it. Thinking that I had missed something in an update, I bumped up the version to v2175 - one of the last that has 32 bit support - and tried again, same messages, same server-side closed connections. It isn't my ISP, everything has been rock solid as far as I can tell. My local network is functioning and I don't have local connection issues. Its only happening with the Sierra chart software. Some specific messages are: (on startup) "SC Data - All Services | Connected to server complete" <-- means I can hit your servers fine and get authorized by my login "Separate subscription for market depth updates is not supported. BTC-BSTMP" I then go through a cycle of resolving the below server and trying to connect, but it fails: ds12.sierracharts.com resolves to 204.15.197.14 -- which I can't ping and traceroute times out, so I'm not sure what is going on there. (Its more than a few hops, so it isn't dying inside my ISP's infrastructure.) Please help, I rely on these charts and my custom studies. Thank you. -------------- I just tried installing the latest version -- v2192 -- and it connects and downloads historical, but my studies fail. I'm really dependent on 32-bit support for my studies .dll -- is there any way to support it? Compiling for 64-bit is outside my technical level, I'm afraid. Have mercy on a older dude just trying to trade. -------------- And to make things even more confusing -- v2086 works just fine on my Win10 box. I'm just beside myself on this one. I haven't changed anything on the machine that runs it full time - a Win7 box - so I'm not sure what is happening here. Date Time Of Last Edit: 2020-11-16 07:00:49
|