SOTA database crash

looks like the database crashed. This is what I see trying to enter an activation:

Server Error in ‘/’ Application.

Object reference not set to an instance of an object.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[NullReferenceException: Object reference not set to an instance of an object.]
SOTA.AddActivation2.Page_Load(Object sender, EventArgs e) in D:\SOTADATABASE\AddActivation2.aspx.cs:39
System.Web.UI.Control.OnLoad(EventArgs e) +92
System.Web.UI.Control.LoadRecursive() +54
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +772

Hermann, DF2DR

In reply to DF2DR:
Hello Herman…
It´s running again…the same here but after 5min it works.

73 de Tom

In reply to DF2DR:
Guess its the same that happens to me, sometimes, when i try to add a activation.
Just log off, get a new cup of coffe, and log on, and everything is there (maybe notthe last qso you added).

In reply to DF2DR:

It doesn’t matter how many times I write it, it will still happen.


The problem may be to do with you or maybe to do with the database host. Putting a message on the reflector will cause lots of people to go and check if the database is broken. This can often make any problem at the host worse as lots of users start trying things.

If you have a problem then contact me. My details are on the SOTA webpage “About”. There is a link at the top and bottom of every SOTAwatch page to the SOTA website. There is a specific form on the website to contact one or all of the MT. You can email me directly at mm0fmf_sota (AT) and put the word DATABASE in the title.

You logged on at “14/04/2013 15:43:09 - Logon OK. callsign=df2dr” and from this point you have 10 mins to access another webpage or you will be logged out. For the next 10 mins, the database log shows lots of people committing chaser entries and S2S entries but no activation commits. Your error occurred on AddActivation2 which is where you click the “I agree” box and submit the log.

Possibly you waited more than 10mins between finishing entering your data and clicking “I agree”. You will have been logged out. Maybe the webserver host shifted the task to a different server. The database software runs on a farm of servers and shifting to another should be transparent but sadly sometimes it isn’t. Maybe you have multiple windows open in your browser and you entered data in some and have been checking things on the database in another. This causes the session data to sometimes get screwed.

Whatever happened and wherever the problem was, the database continued to run and is still up and running. Your data has not been lost. It is currently held in a suspense table. As soon as you log back in and try to enter another activation you will be prompted about the incomplete activation and will get a chance to continue entering the data.


In reply to MM0FMF:

Hi Andy,

This already a well known feature of the SOTA database since years. Maybe there should be a list of frequently asked question on such issues? Just an idea - I do not intend to push you and there could be also some other solution.

73, Jaakko OH7BF/F5VGL