We try to actively deter users from using disk space on our forum. It is expensive for us to host all these files and there is a whole slew of free cloud storage software available.
I'm not 100% certain what you are reporting. Don't get me wrong, I definitely see the error to which you are referring, but it seems like it was well outside the context of any sequence. We might just be having a vocabulary issue and you may mean something different when using "Session".
The connection to the telescope was successful at 17:44. Then, external to SGPro, at 20:23, the mount seems to have disconnected (cable unplugged, hub disconnected, mount lost power... any number of things). At 21:04, you corrected this issue by reconnecting (or the sequence start auto connected) and started the sequence.
Seems like everything worked fairly normally...
As for why end of sequence actions did not run:
5-10-2016 5:56:56] [DEBUG] [Sequence Thread] ASCOM Telescope: Park message received.
[5-10-2016 5:56:56] [DEBUG] [Sequence Thread] ASCOM Telescope: Dome slave set to park mount first, parking mount.
[5-10-2016 5:56:57] [DEBUG] [Sequence Thread] ASCOM Telescope: Sending park...
[5-10-2016 6:01:57] [DEBUG] [Sequence Thread] Mount failed to report that it was parked!
[5-10-2016 6:01:57] [DEBUG] [Sequence Thread] Error parking scope, aborting observatory options, cannot verify scope position...
Looks like the scope failed to report it was parked. To ensure that we do not starting banging scopes and domes together, we do not execute dome park since the scope position cannot be verified. We sent the message to park. As to why the mount did not park, we would need to have a look at the corresponding mount ASCOM logs for that same timer period to see what was going on.