This section explains some common challenges users have when configuring and running the Gateway server with connections to newsroom systems, Viz Pilot databases and content control applications like Viz Pilot and Viz Trio.

Common Sources of Error

• NCS, MOS IDs, and MSE IDs are case-sensitive (check the newsroom system and Gateway).

• Gateway must be restarted after configuration changes.

• Software or hardware firewalls are blocking connections. Verify that the gateway has connections to all newsroom systems and control stations.

Tips and Tricks

Here are some useful fixes and workarounds.

Running Orders from the Newsroom System Are Not Visible in Viz Pilot or Viz Trio

• Check the configuration on the newsroom system. Is the Gateway configured with the correct IP or websocket URL, as well as MOS/NCS-id? Remember that these IDs are case-sensitive.

• Check the logs on the newsroom system. Is the system sending anything to the Gateway when a new running order is created? If not, make sure that no firewall (software or hardware) is blocking the connections, and that the configurations are correct.

• In the Gateway Controller Client, check that there are at least two connections to the newsroom system. If no connections are shown, verify that the IP address entered for the system is correct, and that no firewall (software or hardware) is blocking the connections. Check the log window for errors and warnings.

• In the Gateway Controller client, check that there is exactly one connection to each control station (media sequencer) that you wish to use.

• Enable logging of traffic, and set the log level to “notice” in the controller client:

  • Is the gateway receiving any traffic from the newsroom system? If not, the source of the problem is likely to be the communication between the newsroom system and the gateway.

  • If the gateway is receiving traffic (like a “roCreate” when creating a rundown and MOS activating it), is the gateway sending any traffic to the control stations after receiving such a message?

  • If messages are sent to the correct IP (control station), check the media sequencer logs on this computer for errors.

Auto Activation (Routing) Enabled for Running Orders, but Are Not Automatically Enabled or Forwarded to the Control Station

If routing is used, either based on roChannel or “default routing”, make sure that every newsroom system the control stations should receive running orders from, check the enable autoactivation checkbox in Advanced Settings.

Data Elements (MOS Objects) Are Not Showing up in the Newsroom System

• The Gateway pushes a list of MOS objects to each connected newsroom system, only if the checkbox pushmoslist is checked.

• The Gateway sends MOS object messages each time a Viz Pilot data element is created, modified or deleted, only if the checkbox send mosObj is checked.

• The Viz Pilot Database section of the Gateway must be enabled in order to send MOS objects, and the “DB connected” indicator must be green. If the indicator is red, and the “enable Viz Pilot Database” is checked, check for errors and warnings in the log window.

• Some common errors:

  • Is an Oracle client installed on the computer running Gateway with a version matching the configured database?

  • Is it possible to log onto the Oracle server using the same credentials as entered in Gateway Controller Client, using the SQL Plus interface?

• Check Gateway’s log messages to see if MOS messages are sent to the newsroom system.

• Database schema names are case sensitive. The default Viz Pilot database schema name is PILOT (all upper case). Check the database installation to see if this is correct, or if another schema name is used.

• Check that the database is running by logging onto the database using SQL Plus.

• Check that the Oracle client’s environment path is correctly set. Run the Media Sequencer in console mode and check the console’s output for problems related to the Oracle Call Interface (OCI) library.

• See also Advanced Queuing (AQ) is not working properly.

Gateway Server Is Not Running (Running Status Is Red)

• Check for error and warning messages in the log window.

• Gateway fails to start if another Gateway is running on the same computer, for example an old Gateway version 1.x.

Ports and Connections Are Irregularly Opened and Closed

• Check firewall settings for ports that need to be open.

• Check typical router and routing issues.

Advanced Queuing (AQ) Is Not Working Properly

• An XML parser failure may be an indicator that the wrong AQ protocol is in use on the database.

• Check if the Extended AQ is in use on the database. Gateway should detect if AQ is in use or not and set the correct parameters.

Changes Are Not Taking Effect

Most changes on the Gateway server require a restart of the server. Use the Gateway Controller Client to check the settings again, and restart the Gateway server by clicking the Restart button.