Product specifications
Version 2.6.1 ReadMe
5
MOS devices on the network but not specified in the mosconfig.xml file generates errors
in the log file
If a MOS device is present on the network and is configure to communicate with the MOS Gateway
computer it will cause error messages to be logged in the MOS Gateway logging if it is not also specified in
the mosconfig.xml file. This is normal behavior.
Workaround: Remove from the network or reconfigure any unused MOS devices that are configured to
talk to the MOS Gateway but are not going to be used.
Additional download time overhead when using handlesRoStorySend option
Because of the amount of data being processed and sent with this option enabled, the amount of time to
load MOS devices will be significant. Unless required by the MOS device, Avid recommend that this
option be set to NO.
Upgrades require uninstall first
MOS Gateway does not support upgrades over existing installations. All upgrades of MOS Gateway
require that previous versions of the software be uninstalled first.
License key removed when uninstalling MOS Gateway 2.0
When uninstalling MOS Gateway 2.0 in preparation to upgrade to MOS Gateway 2.6.1 or later, the license
key is deleted. The license key must be re-entered during the MOS Gateway installation.
Workaround: Be sure that a copy of the existing license key is available for the MOS Gateway 2.6.2
install prior to uninstalling MOS Gateway 2.0. To save a copy of the current license key, run the iNEWS
MOS Gateway License Manager (LicenseManager.exe) found in the MOS Gateway install directory.
Documentation Correction or Clarification
Steps 10 and 11 on pages 29 and 30 of the Avid iNEWS MOS Gateway Installation and Operations Manual
indicate that if the correct version or any version of the Microsoft Java VM is not on the computer, the
MOS Gateway installation program will “automatically install” it. This is no longer correct. The
appropriate version of Java VM must be manually installed prior to running the setup program for MOS
Gateway. See “Compatibility Notes and Issues” in this Read Me file for more about which version of Java
VM is qualified and supported.