I get this error when trying to add a log to the database:
The error appears at the last step of adding the log. Everything verifies and looks good until I click the “Submit” button.
First, I tried uploading the ADI log file. When that failed, I started from scratch and added the QSOs manually, but I still received the same error. I tried in two browsers, Safari and Firefox (on macOS).
Any ideas what to do next?
Attach log you want to upload. Maybe some of us will spot an error.
You could try manually adding the activation with only one QSO and then try editing to add additional QSO to see where the error is occurring.
Check if you have a QSO with an invalid (non SOTA) summit reference (like GMA).
Hit the down-arrow on the right so see the list of QSOs.
Also the same problem for me.
Looks is database problem, i try to log online from sotawatch and got same error.
Same message “object Object” when you want to remove or put a contact in the database.
73 Chris F4WBN
I have the same problem and have it not for the first time
When this has happened to me its usually that I’ve used a semi-colon ; in the time field instead of a colon : and its often not easy to spot.
If the database can identify an error when trying to upload it would be very helpful if it would identify the error with a highlight, perhaps on the next upgrade.
I’m sure you’ll kick yourself when you eventually spot the error
GL
Declan EI6FR
Thank you for the repair. Works very well now.
73 Chris
Indeed, it looks like the error is gone now. Thanks!
Something happened. What? I don’t know I’ve not looked in detail yet. Normally things will recover after a short period (15-30mins). Sometimes longer. I’m not able to check the logs right now but will look later.
The problem we have is Andrew VK3ARR has written some rather fault-tolerant code and it’s so reliable now and just keeps working that I don’t keep as much as a watchful eye as in the past. There’s no need any more!
I was only alerted to this because someone posted a problem report using the contact MT form. You should not rely on MT members checking every post on here all the time and so faults can be missed. Use the contact form.
Ironically Andrew VK3ARR probably broke it with a data transfer for some upcoming changes 
Basically it wedged while I was off doing real work, filled a transaction log, so any write actions would fail. Some auto-recovery stuff we have in place probably kicked it back into gear after a few hours (I think it runs every 6 hours), but I double clue-hammered it manually just before in case it still wasn’t working.
