DTN_Steve_S has contributed to 2096 posts out of 21251 total posts
(9.86%) in 6,956 days (0.30 posts per day).
20 Most recent posts:
Hello, we are beginning the process of shutting down these forums as a support resource.
All existing threads have been locked and new posts are now disabled to anyone but DTN staff. In future updates to the IQFeed website, we will be moving information that is still frequently referenced on our forums to other parts of our website. Eventually, the forum pages themselves will be taken offline as well.
As you know, these forums are only one of many options for getting support for IQFeed. Please continue to use the existing email/phone/chat support options in the future. The official home for this contact information is our help site here: https://iqhelp.dtn.com/contact-us
Hello, we are beginning the process of shutting down these forums as a support resource.
All existing threads have been locked and new posts are now disabled to anyone but DTN staff. In future updates to the IQFeed website, we will be moving information that is still frequently referenced on our forums to other parts of our website. Eventually, the forum pages themselves will be taken offline as well.
As you know, these forums are only one of many options for getting support for IQFeed. Please continue to use the existing email/phone/chat support options in the future. The official home for this contact information is our help site here: https://iqhelp.dtn.com/contact-us
Hello, we are beginning the process of shutting down these forums as a support resource.
All existing threads have been locked and new posts are now disabled to anyone but DTN staff. In future updates to the IQFeed website, we will be moving information that is still frequently referenced on our forums to other parts of our website. Eventually, the forum pages themselves will be taken offline as well.
As you know, these forums are only one of many options for getting support for IQFeed. Please continue to use the existing email/phone/chat support options in the future. The official home for this contact information is our help site here: https://iqhelp.dtn.com/contact-us
Hello, we are beginning the process of shutting down these forums as a support resource.
All existing threads have been locked and new posts are now disabled to anyone but DTN staff. In future updates to the IQFeed website, we will be moving information that is still frequently referenced on our forums to other parts of our website. Eventually, the forum pages themselves will be taken offline as well.
As you know, these forums are only one of many options for getting support for IQFeed. Please continue to use the existing email/phone/chat support options in the future. The official home for this contact information is our help site here: https://iqhelp.dtn.com/contact-us Edited by DTN_Steve_S on Jul 30, 2024 at 02:16 PM
Hello, we are beginning the process of shutting down these forums as a support resource. All existing threads have been locked and new posts are now disabled to anyone but DTN staff. In future updates to the IQFeed website, we will be moving information that is still frequently referenced on our forums to other parts of our website. Eventually, the forum pages themselves will be taken offline as well. As you know, these forums are only one of many options for getting support for IQFeed. Please continue to use the existing email/phone/chat support options in the future. The official home for this contact information is our help site here: https://iqhelp.dtn.com/contact-us
There seems to be some confusion here and I just want to make sure everything is clear (and for future readers). We have always preferred that your software launch the feed directly instead of using a launching app.
Here is the documentation page for how to launch the feed directly from your app using your registered productID: https://www.iqfeed.net/dev/api/docs//InitializingTheFeed.cfm
In the long distant past, we required your app load a DLL which then launched the feed with a function call but it was still directly from the app connecting to the feed.
In this particular case, I checked the server logs and it appears that your software has been doing this incorrectly for a very long time. I believe the confusion comes from our, now designated as End Of Life, DDE server (iqlink). The DDE server used to have a launching app (iqlinklauncher) because it was designed to be used with Excel and Excel did not reliably launch the DDE server when invoked. The launching app was removed when we designated the DDE server as EOL (and because it was confusing to new customers).
This message was posted in a secure forum.
Click here to access the topic where message was posted.
This message was posted in a secure forum.
Click here to access the topic where message was posted.
Quote: do you know if Kinetick connection is more reliable now? I do not keep up with their development very closely. You will need to contact Kinetick support for those discussions.
Quote: Since both are owned by DTN, Kinetick is not owned by DTN. It is owned by NinjaTrader and they do all of the support/development for it. DTN's role here is a data provider.
mrez114,
Quote: I have Kinetick data but use it with IQFeed.
This is the source of the issue. This was never intended to work and that loophole has been closed.
If you are only using your account with NT software (as intended with Kinetick data accounts), then changing your adapter settings is all you need to keep working as you always have.
If you were using your Kinetick account with other 3rd party software, then you will need a full IQFeed account to continue at the same level of service going forward.
taa_dtn, it looks like you're running 6.2.0.23. There was a bug fixed in IQFeed 6.2.0.25 relating to your description of the issue, and it most often triggers on reconnections, so you're likely correct it's related to local connection issues but it's was a bug in our code. I recommend upgrading and seeing if the issue still persists for you.
This message was posted in a secure forum.
Click here to access the topic where message was posted.
This message was posted in a secure forum.
Click here to access the topic where message was posted.
Hello all, Saturdays are our routine maintenance days. This involves server reboots and software restarts and, on occasion, can cause requests to fail. We typically try to keep it limited to the morning on Saturdays but sometimes it runs longer. Trying to avoid Saturday mornings for data downloads would be recommended if possible and keeping in mind that request failures should be expected during this time if you are working with our API.
This weekend has been a fairly large bit of maintenance compared to normal with some key infrastructure pieces getting a rare restart/reboot. I believe those would explain the news request failures in this thread. As a result, I was online yesterday morning and again yesterday afternoon verifying that things seemed to be working correctly. We have had users connected and using the system all weekend (with limited success as demonstrated in this thread during the previously mentioned saturday morning maintenance). I have not seen anything yet to indicate further issues.
If you are still experiencing problems. please contact our support group for assistance so we can help identify the issue.
Craig, can you give me a bit more detail on the timeframe you were seeing the errors? Looks like this was likely saturday sometime and/or early sunday? If so, the source of the issues was most likely standard weekend system maintenance causing a backend server to not respond or not respond quick enough to the request. OS patches/software upgrades/etc almost always happen on saturdays since the markets are closed.
This format for the data is only available back through May 21st, 2018.
You are correct. We found the same results and I was just typing up a response when you posted. All the symbols are in the system, just not getting to the chains server currently. We are still investigating an will let you know when we have a fix available. Edited by DTN_Steve_S on Feb 28, 2022 at 03:46 PM
I can replicate the issue with your request.
Here is the request that our chains app uses (pulled from the IQFeed Logfile).
CFO,@ESH22,pc,,23,1,LookupChains
It appears the server is not handling the case where you are not sending the year codes. I have alerted our server team about this but the workaround is to send that field.
-edit- Just noticed your second post. I'll take a closer look at the contracts returned. I don't believe this behavior should have changed since last week. Edited by DTN_Steve_S on Feb 28, 2022 at 11:03 AM
Sorry for the delay here.
We do not have date fields for bid/ask in the feed. As a result, you cannot be certain that bid/ask values in a summary message are from the current day (especially true if you are requesting around midnight Eastern for symbols that update across midnight). However, any update message that indicates a bid or ask update occurred (based on the Message Contents field) can safely be assumed that the date for the bid/ask is the current date (again, based on Midnight Eastern).
Hello, can you give us the exact request you are sending to the feed?
Also, is the issue still occurring? If so, does it also happen with our chains app that is included with IQFeed (the app sorts symbols by position in the return message in relation to the : field)?
This morning, I do not seem to be able to duplicate the issue.
Hello, the official release version is 6.2.0.23 currently (not 6.1). The version field in the S,CUST message also controls the IQFeed version Upgrade Nag so it has always lagged the actual release date by a bit of time to allow a small number of customers to upgrade naturally before we turn on the nag. Unfortunately, with the timing of data center move, we didn't want to have both happening at once so we are delaying the upgrade nag until after the datacenter move is complete.
However, the current version field in this message does not indicate (and never has indicated) the installed version. For example, once we update this field after the move, customers running 6.1 or older versions will still get a 6.2 version number in this field.
The installed version would either have to be pulled out of the registry (documented here: https://www.iqfeed.net/dev/api/docs//RegistrySettings.cfm) or by examining the file information of IQConnect.exe.
|