Join the 80,000 other DTN customers who enjoy the fastest, most reliable data available. There is no better value than DTN!

(Move your cursor to this area to pause scrolling)




"I'm very glad I switched to IQFeed. It's working perfectly with no lag, even during fast market conditions." - Comment from Andy via Email
"IQ feed works very well, does not have all of the normal interruptions I have grown used to on *******" - Comment from Mark
"You are much better than lawyers or the phone company because you answer the phone when I call! I just love your customer service." - Comment from Isreal
"I am very pleased with the DTNIQ system for quotes and news." - Comment from Larry
"The people at Nirvana have very nice things to say about your company and I can see why! Price and service is a potent combination." - Comment from Ed
"For anyone considering using DTN.IQ for a data feed, my experience with the quality of data and the tech support has been very positive." - Comment from Public Forum
"I use IQ Feed, Great stuff as far as data analysis information, storage and retrieval is concerned." - Comment from Public Forum
"Awesome response, as usual. It is a sincere and refreshing pleasure to do business with DTN, compared to your competition." - Comment from Ryan
"It’s so nice to be working with real professionals!" - Comment from Len
"Everything is working great with the API. I love it." - Comment from Calvin
Home  Search  Register  Login  Recent Posts

Information on DTN's Industries:
DTN Oil & Gas | DTN Trading | DTN Agriculture | DTN Weather
Follow DTNMarkets on Twitter
DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter
»Forums Index »Archive (2017 and earlier) »Data and Content Support »Anyone else having problems with history fetch?
Author Topic: Anyone else having problems with history fetch? (5 messages, Page 1 of 1)

taa_dtn
-DTN Evangelist-
Posts: 154
Joined: May 7, 2004


Posted: Sep 29, 2011 07:10 PM          Msg. 1 of 5
About an hour ago my app stopped receiving data in response to history requests. Instead, it receives "!ERROR! Unauthorized user ID."

I've tried closing and restarting the app, independently stopping and restarting the feed. Login works correctly and I'm receiving summary messages properly. The app itself hasn't been changed. It's just history that seems to be failing all of a sudden.

Anyone else seeing something similar?

Allen

LonnieS
-King of IQ Development-
Posts: 127
Joined: Jun 2, 2004


Posted: Sep 29, 2011 08:18 PM          Msg. 2 of 5
It appears that you have made 22000 requests for invalid symbols. For instance the symbols RNWKD and CCTYQ do not exist in the IQ System.
We have a new software release and are investigating why the error you are receiving indicates an unauthorized user id.

Lonnie Shumate
Development Manager, IQ Systems
Telvent DTN

taa_dtn
-DTN Evangelist-
Posts: 154
Joined: May 7, 2004


Posted: Sep 29, 2011 10:06 PM          Msg. 3 of 5
Hmm. I see trades as of yesterday on both RNWKD and CCTYQ that I fetched from IQFeed, and both of them appear in the IQFeed symbol list that I download from http://www.dtniq.com/product/mktsymbols_v2.zip every night. So they do seem to be in the IQ system.

As for 22000 requests, that's possible. When my app fetches history at the end of the day, if the attempt fails for an unknown reason, the app retries starting at the first symbols that failed. The app had been running for an hour before I noticed that it wasn't making progress, so it certainly tried a large number of times to get either data or an error message that it understood, and it tried the same small set of symbols every time.

I was able to restart the app later and have the history fetch finish normally. So the problem was fixed or maybe it was limited to a small number of servers.

Allen

taa_dtn
-DTN Evangelist-
Posts: 154
Joined: May 7, 2004


Posted: Sep 29, 2011 10:18 PM          Msg. 4 of 5
Followup: I just grabbed a fresh copy of mktsymbols_v2.zip, and I see that RNWKD changed to RNWK today and CCTYQ was discontinued. That's why you were under the impression that they didn't exist, but IQFeed was providing data for them as of yesterday.

Since you guys don't send notice of symbol changes over the feed, my app "discovers" this sort of change by noticing the error message or lack of data when it fetches history for the old version of the symbol name.

So it sounds like the main problem here is just figuring out why the app is being sent the wrong error message.

Allen

DTN_Nathan_Bartsch
-IQ Developer-
Posts: 33
Joined: May 3, 2004

Telvent DTN


Posted: Sep 30, 2011 10:14 AM          Msg. 5 of 5
The appropriate error message is now being returned for invalid symbols.

Nathan W. Bartsch - Senior Software Engineer - Telvent DTN
 

 

Time: Wed April 24, 2024 2:42 PM CFBB v1.2.0 10 ms.
© AderSoftware 2002-2003