Welcome to the Birder's Diary Forum for Support And General Questions
Use the Support forum for all questions or issues.
Use the Wish List forum to leave your ideas for improving Birder’s Diary.
Use the Community Sharing forum for sharing Photos, Trips, Stories, etc.
Setup your Forum photo and profile here.
The above topic title is the title of a dialog box that popped up during upgrading from Build 17 to Build 36 today. I will attach a screenshot of the actual notice. I have not done anything with it. I hesitate to do so. The program seems to work just fine, but it bothers me a little. Do I need to do anything?
Hi Anne,
This is an error from the background worker process attempting to update your eBird data to the latest information. In this case the location data used in various places in BD.
It appears to have gotten all the way to the end and died when attempting to update US/West-Virginia. I see this sometimes. It could happen if you lose internet during this process. Did you disconnect it from the internet after the upgrade at some point. This update takes from 10-30 minutes.
You can continue to use BD without any problems.
Check the file C:\Birder's Diary\BD6036_worker.log. At the end you should see the error. If you close that file and restart BD it might attempt to refresh again. Check the log file again to see if it started and is processing. If not, you can update this manually from the View | Options window, Special Tab. See screenshot below.
Please do let me know, as this is a new way of keeping your ancillary data updated, that keeps various parts of BD working.
The way to know for sure is to view the log file mentioned above until you see that it has completed.
Looking forward to hearing back.
I restarted BD but it did not attempt to refresh it, so I refreshed it manually in the "View|Options" Special tab. It powered through and this time it gave me a similar error message, but it appears to be Canada this time! Iclicked oK and the updating continued. The screenshot of the latest unexpected error is down below in another box. It's unreadable. Sorry. I couldn't get it to paste into this one. 🙁
I looked at the worker log file and the US WV error is still there, but the Canada one appears to be clean.
Now I don't know where the screen shot of the Canada error went. I didn't get a notice of the US WV error this time, but when I looked at the worker file it was still there.
Hi Anne,
Does your internet come and go at times?
It sounds like internet connectivity hiccups to me.
Yes, it does continue if a hiccup/error occurs on one of hundreds of API/web calls, but you will be missing the specific data for that hiccup/error; e.g. US/WV, or CA/??.
Let me know please on the internet issue. I may need to get onto your computer to have a look.
Thanks.
@jeff I don't think we have an issue with internet connectivity. We have WiFi in our house and it's only me (Dan) and Anne using it. You are welcome to get onto my computer and poke around if you would like.
Dan
@jeff i just looked at the Worker file again just now and it is unchanged from when it first sent the error message, which seems kind of weird because I ran the file manually twice and the second time it stopped at Canada, I clicked ok, and it ran all the way through the "Z" countries not stopping at WV. Interestingly the original error was still present after that manual run, plus it showed yesterday's date.
Hi Dan,
Yes, on the manual run, the Canada error would be in the BD6035.log file, not the worker log file as you ran this manually from BD desktop.
I would love to get onto your computer and take a peek at this. Send email to support@birdersdiary.com to schedule a time please. Thanks.
Got onto Dan's computer today. The update to the eBird location data generates several thousand Internet API calls. On both attempts, one of those thousands of calls failed. I am blaming internet hiccups. Otherwise everything looked good. Closing for now.
