
Media Processing Server System Operator’s Guide
Page 156 # P0602484 Ver: 2.7
File Synchronization Troubleshooting
Automated MMF file synchronization is provided for all active, designated files
through use of the Z
ero Administration for Prompts (ZAP) utility (see see
Synchronizing MMF Files Across Nodes (ZAP Utility) on page 110.). This utility
generates faults and exception conditions as part of its function. While some causes
can be general in nature and not directly attributable to the utility itself, understanding
the situation surrounding them can help alleviate possible repetition of the condition.
File Synchronization Troubleshooting ( Sheet 1 of 2)
Condition Cause Action
Cannot connect to VMM VMM is not running on the target
node.
• Be sure VMM is up and running on subject node (see
see VMM Status on page 71.).
• Synchronization is rescheduled based on
preconfigured delay interval.
Multiple instances of
VMM have the MMF file
activated
ZAP running on MMF files that are
shared between MPS systems
• zap should not be run on MMF files that are shared
between MPS systems.
• If zap is to run on an MMF, each MPS must have it’s
own copy of the MMF
Update of an element
failed
The target MMF file was not on-
line when the update was
attempted.
Make sure target MMF file is active for update (see see
MultiMedia Format (MMF) File Status on page 72.).
VMM has the MMF file opened in a
read-only state.
Make sure the target MMF file has appropriate write
permissions.
See Multiple instances of VMM
have the MMF file activated.
Don’t activate the same copy of the MMF file for multiple
instances of VMM. Use different copies of the MMF file.
Deletion of an element
failed
The target MMF file was not on-
line when the deletion was
attempted.
Make sure target MMF file is active (see see MultiMedia
Format (MMF) File Status on page 72.).
VMM has the MMF file opened in a
read-only state.
Make sure the target MMF file has write permission
available.
See Multiple instances of VMM
have the MMF file activated
Don’t activate the same copy of the MMF file for multiple
instances of VMM. Use different copies of the MMF file.
Remote node is down Remote node is not active or is
unreachable.
• Synchronization fails after prescribed number of
retries.
• Make sure node is properly configured and running
(see the PeriView Reference Manual).
• Synchronization is rescheduled based on
preconfigured delay interval.
Network connection is
broken
Connectivity between the host and
remote nodes has been lost.
• Resolve network connectivity issue.
• File transfers previously interrupted are retransmitted
once connection is re-established.
• If transfer times-out, synchronization is rescheduled
based on preconfigured delay interval.
Comentarios a estos manuales