Product specifications

Version 2.6.1 ReadMe

 MosAdmin.exe - Optional. Only required if you wish to configure MOS item replication

remotely over the network.

 MosAdminService.exe - Optional. Only required if you wish to configure MOS item

replication remotely over the network.

 MosConfigService.exe - Exception not required.

 RegRGS.exe - Exception not required.

 regtlb.exe - Exception not required.

 TraceLogService.exe - Exception not required.

Hardware and Software Changes

The following changes were made to this version of iNEWS MOS Gateway.

Addressed Problems

 Messages sent to a Unicode iNEWS Server are not readable

In MOS Gateway 2.6.1, messages sent to iNEWS 2.5 or later would show up as random characters and

were not readable. This problem has been addressed in this release.

Known Limitations

This section provides information on known limitations that were not addressed in this release. Any

available workaround procedures are also documented, when possible.

Note: For limitations related to compatibility of this release with previous versions/other products,

see the section of this document entitled, “Compatibility Issues”.

iNEWS

iNEWS does not get "Download Complete" message from MOS Gateway

This is caused by the MOS device not including a roID with its roAck to the Avid MOS Gateway after a

show has been loaded. If the roID is not included in the message, the MOS Gateway does not know

where to send the "Download Complete" message.

iNEWS installer overwrites inewscom.dll registration used by MOS Gateway

The registration of the inewscom.dll installed with MOS Gateway 2.6.1 and 2.6.2 will be overwritten

by the iNEWS client install program. When this occurs an incorrect version of the inewscom.dll will

be used by MOS Gateway which can cause parts of the MOS Gateway functionality to fail, specifically

roStorySend.

Workaround: Do not install iNEWS client software on the MOS Gateway computer. Or install MOS

Gateway after the iNEWS client software.

MOS Gateway

Unused MOS devices will generate reqMachineInfo errors in the log file

If a MOS device is specified in the mosconfig.xml file and it is not present on the network, there will

be errors indicating that the device is not reachable during start up of the MOS Gateway. This is normal

behavior.

Workaround: Remove any unused MOS device configurations from the mosconfig.xml file.