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.
[Solved] Quick Sightings Search Feature Failed then eBird data server message
Received Oops! '0' ." Notify Support@BirdersDiary.com with details when I tried to use Quick Sightings Search feature. I then exited Birder's Diary and started again. Received message Network Request to eBird Timed Out! The attempt to contact the eBird data server has timed out. Please try again later. Notify support@Birder'sDiary.com if this issue continues. '35761' - Request timed out.
Tried to start Birder's Diary several times and I received the above "eBid " error message each time.
Interesting. Multiple failures in different areas.
What version of BD are you running please? If v5.2, make sure you are up to the latest Build (v5.2.51). Download the installer on this site and run it please. Then test again.
The time out issue is either your internet or eBird's server responding slowly. You should be able to continue from this error.
The Ooops! error is odd and completely unexpected. Did you try it again after the eBird network timeout?
This is where we should start.
Let me know please,
I was running v5.2.50. Downloaded the installer and ran it again. The first time was a success, no messages appeared and I was able to add a few sightings. Ran a backup and closed the program. Then reopened BD and received the '35761' - Request timed out message again. Exited the program normally.
Started BD and dismissed the eBird Worldwide Sightings Search Box. Received the Ooops message. I closed and retarted BD and received the '35761' message again. I dismissed the Ebird box. I then tried the Quick Sightings Search feature which worked. I exited BD. So, it seems the Quick Sightings Search feature works, I just get these two messages.
Ok, Jeff, that would be great. How about anytime between 10-11 am or 4-5 pm CDT tomorrow?
I got on Pam's computer this morning and saw the problem right away. She was asking for All Sightings to be returned for the entire USA. She had not specified a State or County. This amount of data was taking longer than 20 seconds (the timeout period) to return. And therefore the timeout.
Once we specified Illinois as the state, it returned 254 species in 1.43s.
I have updated the timeout for future releases (Build 52 and later) to be 40 seconds instead of 20.