Sorry - it isn't an issue of being parked - it is that it is not tracking. Your message in your log is the same as in mine.
Since both problem reports were related to EQASCOM, it seems like it has some propensity to be in a non-tracking mode.
You can create the same behavior and message with the ascom mount simulator, with tracking off.
From my log:
[8/11/2016 10:45:34 PM] [DEBUG] [Sequence Thread] ********** Run sequence started **********
[8/11/2016 10:45:34 PM] [DEBUG] [Sequence Thread] Checking if observatory requires auto slaving...
[8/11/2016 10:45:34 PM] [DEBUG] [Sequence Thread] Observatory does not require auto slave...
[8/11/2016 10:45:34 PM] [DEBUG] [Sequence Thread] Attempting to find next event...
[8/11/2016 10:45:34 PM] [DEBUG] [Sequence Thread] Current event[0] frame count: 0/4...
[8/11/2016 10:45:34 PM] [DEBUG] [Sequence Thread] Looking at event[0]...
[8/11/2016 10:45:34 PM] [DEBUG] [Sequence Thread] Found event event[0] with remaining frames.
[8/11/2016 10:45:34 PM] [DEBUG] [Sequence Thread] Event[0] frame count: 0/4...
[8/11/2016 10:45:34 PM] [DEBUG] [Sequence Thread] Getting first event (0)...
[8/11/2016 10:45:34 PM] [DEBUG] [Main Thread] PopulateDataModel: Transferring view to the data model...
[8/11/2016 10:45:34 PM] [DEBUG] [Sequence Thread] Running capture event...
[8/11/2016 10:45:34 PM] [DEBUG] [Sequence Thread] Mount is not tracking! Aborting capture event (and sequence... recovery is not allowed here... assuming mount is not tracking for safety).
[8/11/2016 10:45:34 PM] [DEBUG] [Sequence Thread] Run event requested sequence abort...
[8/11/2016 10:45:34 PM] [DEBUG] [Sequence Thread] Clearing timed monitoring events...
[8/11/2016 10:45:34 PM] [DEBUG] [Sequence Thread] Checking RunEndOfSequenceEquipmentOptions, force = True
[8/11/2016 10:45:34 PM] [DEBUG] [Sequence Thread] In RunEndOfSequenceEquipmentOptions
[8/11/2016 10:45:39 PM] [DEBUG] [Sequence Thread] User prevented end of sequence actions from running.
Frank