QRZ upload issue

[KM4HXI]

New install, Windows 7 and when uploading to QRZ it is not working. I've re-cut and pasted the API key a couple of times. I am an XML subscriber. I'm sure it's some thing simple I missed on my part. Here is the error I'm getting.

2015-10-27 15:27:25.7343 INFO: QrzComUpload: STATUS=FAIL&REASON=missing <eor> in record&EXTENDED=

[G4POP]

Well I just did a QSO upload to QRZ and it worked fine so its something to do with your set up, have you checked with QRZ that your API key is still valid?

[KM4HXI]

I submitted a support request to QRZ. I'll post back if/when I get it fixed.

[KM4HXI]

Here is what I got back from QRZ...

Thomas,
***************
Unfortunately I cant tell you much from the error message you provided. It looks like no content is being sent to our server by Log4OM. Is this a specific QSO you are having issues with or a whole logbook?

I know in the past LOG4OM and our API have had issues with certain special characters in comments and other fields.

73, The QRZ Support Team
****************
For now I can upload to LOTW and then download into QRZ via LOTW to keep everything in sync.

[IW3HMH]

can you send me a file with a single adif row? (the one that give you the trouble?)
To do that:
open QSO manger
select the QSO (using filters if needed)
Press "export to adif" button

you can paste the adif there or in a pvt message.

thanks

[KG5LKV]

I MAY have a solution for you... I was getting a similar (exact) error on 7 records...

MY problem was the "special" character in the COMMENT section of the QSO record.

I had added a comment for each record: "OMISS# 1234" or similar to reflect the member number of each QSO in the organization OMISS. ONLY thing the records had in common AND different from the successful records.

I deleted the "#" from the comment section and they ALL uploaded on the very next try.

Look in your QSO record for any "special" or unusual characters... (e.g. @#$%^&*)
Try removing it/them from one record and re-trying the upload for that record.

[IW3HMH]

This should be fixed in 1.25
I've found the annoying thing.
Thanks!
lele