This problem has been corrected and should not be a problem in the latest release of SeeSOR. If you find that this occurs, please go to the Request Support tab and create a ticket.