On March 14 all of a sudden I'm getting a lot of "Invalid symbol" errors. For example pulling history for "APPS" returns invalid symbol even though it's not. I'm not sure if they're all NASDAQ but many of them seem to be.

Maybe I need to update my IQFeed client because I think I'm out of date or maybe my machine has been corrupted.

I'm looking in to the issue on my side but figured I would post to ask if something changed.

I ran a check on our history for APPS and do not see any issues.

Please feel free to contact us at support@iqfeed.net or join us in chat from www.iqfeed.net with your Login information so that we can research your account.

---

Stephen Shockey
Customer Support Representative

DTN
800-779-7299
stephen.shockey@dtn.com

9110 W Dodge Rd
Omaha NE 68114, USA
www.dtn.com

Thanks for checking. Seems to be working fine now during the day but I just updated from 6.0.0.5 to 6.0.1.1 so I'll see how that goes tonight too.

Looking at version 6.0.1.1 I see: Added support for 64bit (8+ decimals) precision prices in streaming (Level 1) data and History data (as soon as the history servers support rolls out).

Any chance the history servers updated to this new 64bit precision on March 14?

Just trying to figure out what happened. I'll keep testing to make sure the problem is not on my side.

No, the history servers were updated quite a while ago (at least a couple weeks before that). I'll get the release notes updated to indicate that has been completed.

I just realized something not-quite right here.

A long while back (at least a year or two), the history servers stopped sending the Invalid Symbol error code so there is no way you should have been getting that specific error. Are you certain this is the case? If so, please let me know your loginID so I can look at the server logs. Feel free to send it to me in a PM or an email to dev support.

OK, another update. After searching through the server logs a bit, it appears that this error has been re-implemented for obviously bad symbols (stuff not allowed by our symbology).

However, with that said. There were only 13 requests total on March 14th that returned this error and none of them were for valid symbols.

After digging in to it, that error is actually one of my internal errors and kind of generic (ie. it can be caused by a number of things). I'm not sure what the IQ client is returning but I am running the latest now 6.0.1.1.

I'm still investigating this. I have a lot of things I need to upgrade including the OS. I managed to get some history pulls yesterday without errors so it obviously CAN work. I'm thinking the problem is probably on my side. Though I'm not sure why this started all of a sudden. Anyway, I'm going to rework some of my code making that error less generic so I can see was is going on in case this happens again.

Thanks for the help!