Thanks for the info, Martin. I managed to upload my log. I have no idea what was wrong before …
p.s.
Thanks for the S2S QSO. I was working with special callsign S515SOTA.
73, Milos S57D
Milos,
I am having some trouble uploading activator logs. When I open the log to verify it only part of the log is there.
Using Manage Logs I was able to delete the incomplete upload.
Uploading a second time showed the complete log and the submission completed.
This has happened a few other times. Once there was an invalid summit reference which I didn’t spot, or see the error message. Once that was fixed the upload went through.
I still like the older version of Mapping.
In the new one it’s curious to see N6PKT, Smokey, now living in Japan. No worries.
The new system shows countless hours of care and toil. Thank you!
I would never have known otherwise to activate on May 4th to earn my crossed light sabers!
73, David N6AN
1 Like
My log uploads are not always right either first try.
Last 4 log uploads put the log in the data base but gives a zero score for the activation.
I then delete the log and try another upload and it succeeds by giving me the value of the summit and updates my overall Activation points.
Regards
Ian vk5cz …
Whilst we look into what is causing some of these issues there somethings you can try if you get 0 points for an activation that should score.
First just make sure it really should score. We had a problem reported where an activator reported 0 points and had only activated the summit once in the year. When we looked he was uploading two activations, one for before 0000Z and one for after. That’s two activations for one ascent of the summit.
If you really should have got the points you can do the following.
Find the activation and click the pencil by it to edit it.
Click “Verify Log”
Assuming it verifies then click submit.
This should re-score the activation without you having to delete and upload again.
2 Likes
Thanks Andy I only visit my summits once per calendar year.
It’s probably op error my end as I am not really very good at the PC if it does not work right off. I just noticed someone else had a similar problem getting the summit score to show in the list of activated summits.
Regards
Ian vk5cz …
Regarding incorrect locators (sorry both off-topic and I’m a bit behind reading). Reminds me of one of my favourite code comments - from the wsjtx pskreporter code in this case:
# this is a valid locator in theory, but it's somewhere in the arctic ocean, near the north pole, so it's very
# likely this just means roger roger goodbye.
We are, of course, referring to ‘RR73’
2 Likes
Last 4 log uploads put the log in the data base but gives a zero score for the activation.
I’ve experienced this bug a couple of times too. I filed a bug report via the ‘contact us’ form (database administrator) on the SOTA website a week or two back. I ended up using the same workaround as you.
Also having issues where the ‘submit wheel’ just spins forever (10 mins+) and never submits the log. Seen this a number of times, on different days/times, different browsers, different PCs etc.
On my activation today I had 10 S2S (and 51 QSO in total):
I noticed that at the QSO map there are only 5 S2S showing:
So I did a quick check of the complete log and found out that these calls are missing on the map:
S2S
- SP15OTA
- MW0JKS/P
- HB9/IK2LEY/P
- OE/HB9BCK/P
- HB9HBV/P (HB9HBU/P is showing … same summit)
CHASER
- EA8DKV
- F4FTJ
- SQ9NOT (SQ9MDF is showing … same QTH)
- SV2CNE
- F/DD6DO
- SQ9BQW
- 9A8RA
- DD7UW
- OE5GFI
Probably the chasers don’t have any locator information on their profile and/or qrz.com page. But I wonder why only half of the S2S contacts are displayed on the map?
1 Like
Hi Martin,
Many thanks for S2S QSO 
I was very happy because on my summit I had no mobile signal and SSB spots were sent by Wiesław @SQ9IAW after our communication on 2m FM 
Below photo taken form my operating position:
Thank you for your participating in SP15SOTA award
73, Jarek
I haven’t uploaded my activator logs for a few weeks. I didn’t matter (I foolishly thought) as I’d not done “all that many” activations lately.
Typed up my CSV file yesterday. Turns out it was around 1200 QSOs worth of activations!
Busy gigging the next three nights, so maybe finally submit the upload on Sunday evening. Wonder if I’ll get any new badges…?
Is there a “Broke the Server” badge?
6 Likes
Dunno about that, but there should definitely be an “Old Curmudgeon” badge
I’d be sure to get a few of those…
Rob
3 Likes
Hi Andy
I have noticed that for the S2S Roll of Honour when the chaser callsign begins with a number e.g. 2E0ABC then you try to view the S2S log the following screen is displayed.
I tried it for other numbers and get the same. I think it is a T-SQL issue it doesn’t like objects beginning with a number, they have to be bracketed. The fault doesn’t appear on the other Honour Rolls.
It all works fine on the old SOTA database.
73 de
Andrew G4VFL
It’s a Javascript issue that i’ve seen on other pages - basically we test to see if we’re a number (User ID) or a callsign. The test for numbers is aggressive enough that it allows a starting number, drops the remaining non-numeric text and then assumes it’s a UserID. There’s no corresponding user ID, so you get the error.
I’ll dig into it later.
2 Likes
Best to check for both formats - all-numerical ID or callsign - using regexes. Then you can be sure - here’s one in PHP which I used in the SMP to check callsign format:
preg_match('=^[1-9]?[a-z]{1,2}\d{1,4}[a-z]{1,4}$=i', $callsign);
Works for 99.99% of callsigns…
1 Like
I’ve just uploaded my logs from today and I’ve received the chaser 2500 badge - twice. I think I should just have one badge:
1 Like
Yes, this appears to be a subtle bug where you have a 0 point chase that corresponds with your 2500 point chase, so it has multiple “2500” point chase levels, if that makes sense. I’ll push a fix sometime later tonight.
2 Likes
Thanks Andrew.
If you want me to break anything else let me know 
5 Likes
Hi Andrew
Sorry to trouble you. It appears that there is the old problem of callsigns beginning with numbers on the Completes Roll of Honour.
I have also noticed that if a band is entered in the “Completes” the “Loading” does not terminate. On the old database it used to just ignore I had put a band in. I assumed this to keep the load on the database low. The way I reset this is to clear the browsing data.
Many thanks for all your efforts with the database.
73 de
Andrew G4VFL
1 Like
I have this fixed already, but I haven’t pushed it live yet as I have a bunch of other changes included in that batch that I don’t want to inflict on SOTA until they’ve had more testing.
So this hasn’t worked forever. I also have a fix for this that will be part of the other batch of changes, but actually is broken on the API side and has been from the get-go. Any combination of band or mode for completes does not function correctly at present (other than in our dev environment where the other stuff is undergoing testing).
Expect both to be released (along with the rest) in a week or two.
2 Likes