Log4OM

I am running V1.26. I am able to successfully upload QSO's to EQSL but not download. I currently have 66 QSL's waiting on EQSL. I have successfully logged into the site from a browser.

Here is the log. Password has been removed for security purposes but it is correct

Any help would be greatly appreciated.

73 de N8PWM Craig

2016-12-10 21:10:21.0068 INFO: EqslManagement: Begin receive log (in date range)
2016-12-10 21:10:21.0088 DEBUG: EqslManagement: Request link http://www.eqsl.cc/qslcard/DownloadInBo ... f10%2f2016
2016-12-10 21:10:21.1798 DEBUG: EqslManagement: Request accepted
2016-12-10 21:10:21.4328 ERROR: *** EqslManagement: receiveLogThread_DoWork searching for ADIF file in response ******* [Function: #=q7jGIBeZQg2ItDKJ$YU7_JZhIsEdoUK8IdVCrJiCN0bI=] System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: startIndex
at System.String.IndexOf(String value, Int32 startIndex, Int32 count, StringComparison comparisonType)
at System.String.IndexOf(String value, Int32 startIndex, StringComparison comparisonType)
at LogOM.BL.EqslManagement.#=q7jGIBeZQg2ItDKJ$YU7_JZhIsEdoUK8IdVCrJiCN0bI=(Object #=q3vSzWJcPFrycjlNK$GYTWQ==, DoWorkEventArgs #=qem9xhZ5SM9uE$zdsqrlMZw==)
2016-12-10 21:10:24.7190 DEBUG: Log4OMDataGrid: Initializing grid Log4OM Post Office
2016-12-10 21:10:29.4222 TRACE: ClusterForm: Cluster notification PX2B not fired. No alerts enabled

EQSL Uploads and downloads tests OK here using Windows XP, 7 and 10 machines with Log4OM versions 1.24, 1.25 & 1.26

Therefore considering the above and as there are no other users complaining of this it has to be something set up wrong your end!

Passwords containing special characters cause issues so avoid !"£$%^&*()_+}{~#@?

Always ensure that the Nickname inserted in Log4OM EXACTLY matches that shown in the eqsl "My Profile" page - If it shows just the word 'Home' then only insert that in Log4OM not 'G4POP at Home' or 'G4POP-Home' etc

Of course always check that the download date range selected covers the period in question

According to the error reported, the answer from EQSL doesn't provide QSO back.
In next release (almost ready) i've added a log to manage this kind of errors

With high probability no QSO were present in the period selected.
Let me know what happens increasing the period