KB357: Cleaning up Moxie 7.05 database of duplicate player entries

Moxie 7.05.7635 fixes a bug that was inadvertently introduced in earlier Moxie 7.05 releases, as a by-product of some of the performance improvements. When Players with metadata assigned are restarted, at the time of reconnection to the Moxie Data Server, the Server is unable to detect the Player Data and Settings folders, causing it create new ones. However, once the Players finish reconnecting, the old folders still exist, so there are now duplicate folders, causing conflicting settings. This conflict results in symptoms such as:

KB353: Moxie 7.04 Sync Service stops due to incorrect credentials

Symptoms

After upgrading to Moxie 7.04, the Sync Service stops repeatedly. 

Cause

If the folder the Sync Service is attempting to sync files from or to does not have permissions for the user account under which the Sync Service is running, it'll stop. 

Solution

Make sure all the folders from which the Sync service syncs files from and to have read and write permissions for the user account under which the Sync Service is running. 

KB352: Remote Player upgrade results in “Not a valid Omnivex signed upgrade file” error

Symptoms

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"

Cause

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.

KB350: Specifications for Video Capture with Moxie

For Moxie 7.03 and lower

Note: Moxie 7.03 64-bit does not have video capture

For Moxie 7.03 and lower the tested Video Capture USB devices are:

  1. Hauppauge WinTV-HVR-1950
  2. Hauppauge WinTV-HVR-1955

PCI versions of these devices are 1600 and 1800.

These devices use MPEG-2, which is not installed by default on Windows 10. However, the codecs are available for installation from Hauppauge.

KB348: Moxie Player or Studio restarts unexpectedly and throws an “OutOfMemoryException”

Symptom

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.

Subscribe to Moxie Player