When performing a remote Player upgrade from Moxie Studio, one or more Moxie Player upgrades fail with the following error message "Not a valid Omnivex signed upgrade file"
When a remote Player upgrade is initiated, the upgrade file is sent over to the Player PC and its signature is verified to ensure the file is not corrupted. Sometimes, due to certain security reasons if the Player PC can not verify the file's certificate, it aborts executing the installation file.
Moxie Player or Studio will restart automatically if certain conditions are encountered such as repeated failures to render video files or when unexpected exceptions are thrown. As part of the Moxie’s process to recover, it will write a timestamped incident log file to C:\ProgramData\Omnivex\System for analysis and then trigger a process restart.
When Moxie Studio is launched, the Script Editor does not load or launching modules throws an exception:
“FileFormatException: No FontFamily element found in FontFamilyCollection that matches current OS or greater: Win7SP1”.
Inner exception originates from: CompositeFontParser