® ® Avid Interplay Engine and Avid Interplay Archive Engine Administration Guide Version 2.
Legal Notices Product specifications are subject to change without notice and do not represent a commitment on the part of Avid Technology, Inc. This product is subject to the terms and conditions of a software license agreement provided with the software. The product may only be used in accordance with the license agreement.
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. This software is provided "as is" without express or implied warranty. Copyright 1995, Trinity College Computing Center. Written by David Chappell.
The following disclaimer is required by Ultimatte Corporation: Certain real-time compositing capabilities are provided under a license of such technology from Ultimatte Corporation and are subject to copyright protection. The following disclaimer is required by 3Prong.com Inc.: Certain waveform and vector monitoring capabilities are provided under a license from 3Prong.com Inc. The following disclaimer is required by Interplay Entertainment Corp.
FlexCable, TechFlix, Tel-Ray, Thunder, Titansync, Titan, TL Aggro, TL AutoPan, TL Drum Rehab, TL Everyphase, TL Fauxlder, TL In Tune, TL MasterMeter, TL Metro, TL Space, TL Utilities, tools for storytellers, Torq, Torq Xponent, Transfuser, Transit, TransJammer, Trigger Finger, Trillium Lane Labs, TruTouch, UnityRAID, Vari-Fi, Velvet, Video the Web Way, VideoRAID, VideoSPACE, VideoSpin, VTEM, Work-N-Play, Xdeck, X-Form, Xmon, XPAND!, Xponent, X-Session, and X-Session Pro are either registered trademarks or t
Contents Using This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Symbols and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 If You Need Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Viewing Help and Documentation on the Interplay Portal. . . . . . . . . . . . . . . . . . . . . . . . 14 Interplay Documentation . . . . . .
Managing Databases: Deactivating, Activating, and Migrating . . . . . . . . . . . . . . . . . . . . 64 Deactivating a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Activating a Deactivated Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Migrating a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Moving a Database to Another Server (Non-Clustered Systems).
Adding User Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Adding Users Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Viewing and Setting Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Understanding Standard Roles and Default Rights . . . . . . . . . . . . . . . . . . . . . . . . 120 Viewing and Changing Roles . . . . . . . . . . . . . . . . . .
Archiving Duplicate Versions of Media. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Adding AAF Metadata to an Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Specifying the Archive Server, Segment Size, and Restore Process . . . . . . . . . . 165 Setting the Ownership for New Database Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Setting Options for Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting the Server Execution User Account . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Creating the Server Execution User Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Determining the Server Execution User Name . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Re-creating the Server Execution User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Shutting Down or Locking the Server Process . . . . . . . . . . . . . . . . . . . . . . . . .
Appendix B Interplay Engine Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Configuring the Server Event Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Config.xml File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Supported Actions in Config.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 Supported Events in Config.xml . . . . . . . . . .
Using This Guide Congratulations on your purchase of Avid® Interplay®, a powerful system for managing media in a shared storage environment. This guide describes how to use Avid Interplay Administrator, an Interplay client application that provides tools to configure the Avid Interplay Engine and to manage the database on the server.
Symbols and Conventions Symbols and Conventions Avid documentation uses the following symbols and conventions: Symbol or Convention Meaning or Action n A note provides important related information, reminders, recommendations, and strong suggestions. c A caution means that a specific action you take could cause harm to your computer or cause you to lose data. w > A warning describes an action that could cause you physical harm.
If You Need Help If You Need Help If you are having trouble using your Avid product: 1. Retry the action, carefully following the instructions given for that task in this guide. It is especially important to check each step of your workflow. 2. Check the latest information that might have become available after the documentation was published: - If the latest information for your Avid product is provided as printed release notes, they are shipped with your application and are also available online.
Interplay Documentation The Interplay Help combines information from all Interplay guides in one Help system. It includes a combined index and a full-featured search. From the Interplay Portal, you can run the Help in a browser or download a compiled (.chm) version for use on other systems, such as a laptop. To open the Interplay User Information Center through a browser: 1.
Avid Training Services • Avid Instinct User’s Guide — describes how to use the Avid Instinct application to write iNEWS stories and put together simple audio and video sequences. • Avid Interplay Media Services Setup and User’s Guide — Avid Interplay Media Services lets you control and automate Transcode, Archive, and ProEncode services.
1 Getting Started with the Avid Interplay Administrator The Avid Interplay Administrator provides database administrators and maintenance engineers with the tools required to configure the Avid Interplay Engine and to manage the database on the server.
Understanding the Interplay Engine and Interplay Workgroups An Interplay database consists of two parts: • A metadata database, which holds information about the assets, or metadata. • Source files for the assets, for example, graphics files and Avid media files. The source files for file assets can be stored on the Interplay Engine or on an Avid shared-storage system. The source files for Avid assets are always stored on shared storage.
Understanding the Interplay Engine and Interplay Workgroups Media files for Avid assets are always stored on an Avid shared-storage system. Source files for file assets can be stored on the Interplay Engine or on an Avid shared-storage workspace. The location that holds file assets is called the file repository. When you first install Interplay Engine software, the installation program requires you to set one root folder for the database on a local drive.
Understanding the Interplay Engine and Interplay Workgroups Interplay Archive Engine A facility might also include an Interplay Archive Engine. An Interplay Archive Engine is configured similarly to an Interplay Engine. An Archive Engine is integrated with a third-party archive system. An Interplay Archive database is always named AvidAM. An Interplay database is always named AvidWG.
Using the Avid Interplay Administrator n In this guide, references to the Interplay Engine also refer to the Archive Engine, unless otherwise noted. Central Configuration Server If a production facility includes more than one Interplay workgroup, you can specify one Interplay Engine as the Central Configuration Server (CCS). The CCS is an Interplay Engine module that stores information that is common to all other Interplay Engines.
Starting the Avid Interplay Administrator The Interplay Administrator provides you with the tools you need for the following major tasks: • Setting up a new database. See “Creating an Interplay Database” on page 28. • Backing up the database. Backing up the database regularly protects your data, allowing you to restore the database to a saved state in the event of failure. See “Creating and Restoring Database Backups” on page 33.
Starting the Avid Interplay Administrator The first time you open the Interplay Administrator, the Server text box is empty. If you have already logged into a server, the text box shows the last server you logged in to. 2. Select the server you want to work with by doing one of the following: t Accept the server that is displayed. t Type the name of the server that you want to log in to. You can also use an IP address. t Click the arrow for the Server list and select the server name from the list.
Using the Avid Interplay Administrator Window 3. Type a user name and password for an account with administration rights. On the first start after installing the Avid Interplay Engine, only the user Administrator exists. Type “Administrator” in the dialog box. The password is empty by default. Change the password of the Administrator as soon as possible (see “Viewing and Setting Attributes” on page 119). n The Interplay Administrator account is different from the Server Execution User account.
Using the Avid Interplay Administrator Window Each group contains views for managing components of the Avid Interplay Engine.
Opening an Interplay Administrator View Opening an Interplay Administrator View To open an Interplay Administrator view: t In the Interplay Administrator window, click an icon. The view you select replaces the Interplay Administrator window. Each view includes a path that shows the relative location of that view. The following illustration shows part of the Create Database view.
Exiting the Avid Interplay Administrator t Select Documentation Website on Server. The Avid Interplay User Information Center page opens. You can open the Help, PDF versions of the Interplay user guides, and other useful links. See “Viewing Help and Documentation on the Interplay Portal” on page 14 Exiting the Avid Interplay Administrator When you are finished using the Avid Interplay Administrator, you should log out or close the application.
2 Database Settings The Database settings allow you to create, configure, and manage the Interpla y database.
Creating an Interplay Database n To identify the actual folder, open a Command Prompt window and type net share. If the Interplay Engine server does not have adequate local storage for your Interplay database (for example, if your facility stores a large number of file assets in the Interplay database), you can configure the Interplay Engine to store only the metadata database on the Interplay Engine.
Avid Interplay Databases, Folders, and Files To create an Interplay database: 1. In the Database section of the Interplay Administrator window, click the Create Database icon. The Create Database view opens. 2. In the New Database Information area, leave the default “AvidWG” in the Database Name text box. For an archive database, leave the default “AvidAM.” These are the only two supported database names. 3. Type a description for the database in the Description text box, such as “Main Production Server.
Avid Interplay Databases, Folders, and Files Database File Structure The database file structure is based on the administrative share that was set during the Interplay Engine installation. By default, this administrative share is named WG_Database$ and is associated with the folder D:\Workgroup_Databases (S:\Workgroup_Databases for cluster systems). The “$” indicates a hidden share. To identify the actual folder, open a Command Prompt window and type net share.
Avid Interplay Databases, Folders, and Files Database Directories and Files Directory or File Directory or File Description _Database The main database directory, which contains database files and the database journal. These files contain the database structure and all metadata. All files within this folder contain binary information and cannot be viewed or edited with a text editor.
Creating and Restoring Database Backups Creating and Restoring Database Backups There are two basic approaches to backing up an Interplay database: • Using a combination of backups scheduled through the Interplay Administrator (automatic backups) and manual backups of other parts of the database. This approach should be used as part of a regular backup strategy. • Using a professional backup tool to do a complete backup to offline media.
Creating and Restoring Database Backups Backup Type Description - Incremental Creates copies of database files and streamed properties files that were added to the database since the last Complete Backup, the last Incremental Backup, or the last Differential Backup. - Differential Creates copies of database files and streamed properties files that were added to the database since the last Complete Backup. In most cases, this backup takes longer to perform than an Incremental backup.
Creating and Restoring Database Backups Type of Backup Folders or Files Backed Up Manual backup AvidWG\_Master AvidWG\AvidWG.pro AvidWG\FolderLocations.xml See “Avid Interplay Databases, Folders, and Files” on page 30 for descriptions of these folders and files. It is not necessary to back up AvidWG\_Backup unless you want to make a backup of automated backups. Other folders in AvidWG do not need to be backed up because they are temporary folders that are automatically recreated.
Creating and Restoring Database Backups Recommended Backup Configuration Avid recommends the following backup configuration: • Enable a daily Avid Interplay database backup. The backup should be set to run once daily at night, when the server is not being used or usage is lowest. See “Scheduling Automatic Database Backups” on page 39. • Decide whether to schedule the daily backup as a Complete backup or Fast backup.
Creating and Restoring Database Backups Cluster systems: The default path is - S:\Workgroup_Databases\AvidWG\_Backup On cluster systems, Avid recommends that you specify \\?\d:\backup as the path for Interplay backups. (This syntax, with a question mark, is known as a Long UNC or UNCW path, and allows for more characters than the 260-character limitation of the short UNC path.
Creating and Restoring Database Backups Setting the Number of Database Backups to Keep The Avid Interplay Engine always keeps the last Complete backup and any later Fast backups. If you want to keep more than one Complete backup, change the “number of Backups to keep” setting to be larger than the number of scheduled Fast backups. The default setting is 10. The number of backups to keep includes Complete and Fast backups.
Creating and Restoring Database Backups Scheduling Automatic Database Backups The Schedule Backups view in the Interplay Administrator lets you schedule the type and frequency of your automatic backups. You can schedule two kinds of backups: Complete and Fast. You can schedule one of two different Fast backups: Incremental or Differential. For a description of the different types of backups, see “Types of Interplay Administrator Backups” on page 33.
Creating and Restoring Database Backups c The _PropertyStore folder is critical if you need to completely restore Avid assets. Avid recommends that you schedule a Complete backup once a week and a Fast backup (either Incremental or Differential) daily. By default, backups are stored in the following folder: \\InterplayEngine\workgroup_Databases\AvidWG\_Backup You can specify another location, including shared storage. Make sure the Server Execution User has read/write access this location.
Creating and Restoring Database Backups 2. In the list on the left side of the view, select the database for which you want to view or specify automatic backup settings. The current settings are displayed.
Creating and Restoring Database Backups 3. (Option) In the Backup Information area, change your preferences if necessary. “Backup only if modified” is selected by default to save space and avoid duplicate identical copies. The default number of versions to keep is 10. The Avid Interplay Engine always keeps the last Complete backup and later Fast backups. For more information, see “Recommendations for Backup Configuration” on page 34. 4.
Creating and Restoring Database Backups 10. (Option) Change the Backup time by selecting one of the following: t Select Once at and change the hour and minutes (within 10 minute intervals) on which it occurs using the up and down arrows. t Select Every and set the backup to occur at regular intervals starting at midnight. Use the down arrow to select the interval. t Select Custom and specify custom backup times. Use the up and down arrows to select the time, and then click Add.
Creating and Restoring Database Backups The backup is created in the location you specified. If you navigate to the location, and the backup is still being created, the folder name includes the words “backup in progress.” Using an Archiving Tool for Backup In some circumstances, such as performing a system upgrade, you might want to use an archive tool to create a backup copy of the complete database folder (AvidWG or AvidAM) and the user database folder (_InternalData).
Creating and Restoring Database Backups Interplay Engine (Split Database) Folder Name Default Location AvidWG (_Database folder only) D:\Workgroup_Databases\AvidWG AvidWG (all other database folders) \\SharedStorageServer\WorkspaceName\AvidWG _InternalData (user database if engine is a Central Configuration Server) D:\Workgroup_Databases\_InternalData To make a backup copy of the database on a cluster system: 1. Open the Interplay Administration tool. 2.
Creating and Restoring Database Backups 11. Use a backup tool to make a copy of the following folders and record their location. Interplay Engine or Interplay Archive Engine Folder Name Default Location AvidWG (Interplay Engine database) S:\Workgroup_Databases\AvidWG AvidAM (Archive Engine database) S:\Workgroup_Databases\AvidAM _InternalData (user database if engine is a Central Configuration Server) S:\Workgroup_Databases\_InternalData Interplay Engine (Split Database) Folder Name Default Locati
Creating and Restoring Database Backups • “Database Restore Session Example” on page 54 • “Using the BackupArchive Tool to Restore Files” on page 55 • “Restoring Archived Log Files” on page 58 You cannot restore parts of a backup, for example, a specific sequence or folder. You can restore only a Complete backup or a Fast backup. How the Restore Tool Works with Streamed Properties Files Beginning with Interplay Engine v1.2.
Creating and Restoring Database Backups After you verify that the backup ran successfully and your database is working correctly, you can save storage space by deleting the numbered backup folders ( _Database.x and _PropertyStore.x) created during the restore process. Restoring a Complete Backup or a Fast Backup To restore a database, you need to restore a Complete backup, a Fast backup, or both, depending on the type of backups available.
Creating and Restoring Database Backups Distinguishing Between Types of Backups To distinguish between a Fast Metadata Only backup and the other types of backups, open the backup folder and check if a _PropertyStore folder exists. A Fast Metadata Only backup does not contain a _PropertyStore folder.
Creating and Restoring Database Backups Fast Incremental backup type Example of a Complete Restore Process Imagine that you have a backup schedule of a Complete backup on Saturday and a Fast Differential backup every other day of the week. If there is a failure on Friday in which the _Database folder, the _PropertyStore folder, and other Interplay folders are lost or corrupted, you need to perform the following steps: 1.
Creating and Restoring Database Backups Using the InterplayRestore Tool on the Interplay Engine Server To restore a backup, you need to run the InterplayRestore tool in a Command Prompt window. There are two ways to run the tool: n • Without parameters, in which case the tool prompts you for the necessary entries (interactive mode). • With parameters, in which case the tool runs without prompting, depending on the number of parameters included.
Creating and Restoring Database Backups 7. At the next prompt, select the correct backup from the numbered list of available backups. Complete backups are labeled “full” and Fast backups are labeled “increment” “difference,” or “metadataonly.” After you select the backup, press Enter. The restore process begins. For an example of the process, see “Database Restore Session Example” on page 54. At the end of the process, a message informs you that you need to restore the _Master directory manually. 8.
Creating and Restoring Database Backups t For a split database, navigate to the folder that holds InterplayRestore, type the following, and press Enter: InterplayRestore /m /assets /backupdir For example: InterplayRestore /m d:\Workgroup_Databases\AvidWG /assets \\isis\workspace1\AvidWG /backupdir \\isis\workspace1\AvidWG\_Backup InterplayRestore prompts you to choose from a numbered list of available backups and then re
Creating and Restoring Database Backups Database Restore Session Example The following is an example of an interactive session, which begins with the command for starting the InterplayRestore tool. C:\>”C:\Program Files\Avid\Avid Interplay Engine\Server\InterplayRestore” ******************************************************************** InterplayRestore - Restore Interplay databases from backup A non interactive mode is also available. Run "InterplayRestore.
Creating and Restoring Database Backups Assume you choose 1. The tool locks the project so that no one can access the database and then copies the files: Beginning restore from \\isis\workspace1\avidwg\_Backup\AvidWG_2010-06-10_03-05\ This is a Full backup Restoring split database. Metadata restored to d:\Workgroup_Databases\avidwg\. PropertyStore Assets restored to \\isis\workspace1\avidwg Locked project AvidWG Copying files into d:\Workgroup_Databases\avidwg\_Database Copying file AvidWG.dor ...
Creating and Restoring Database Backups The following illustration shows the corresponding files as they appear in the archive file \AvidWG\_Backup\AvidWG_2008-05-04_01-00\_PropertyStore\streamed_prop1.bar: The .bar file is a file that you can only open by using the BackupArchive tool. n In previous versions of Interplay, you could use Windows Explorer to view and work with the streamed properties files in the _PropertyStore backup folder.
Creating and Restoring Database Backups For example, type the following and press Enter: cd C:\Program Files\Avid\Avid Interplay Engine\Server 3. Type the following and press Enter: backuparchive /L Do not use the file extension when typing the name of the archive file. For example, backuparchive /L \\docisis\workspace3\AvidWG\_Backup\AvidWG_2008-05-04_01-00\_PropertySt ore\streamed_prop Make sure to type the command on a single line.
Performing a Consistency Check Restoring Archived Log Files In Interplay version 1.6 and later, the Interplay Engine compresses and archives log files older than 7 days. The log compression process runs during project backup. (This process runs at most once per day, even if multiple backups are scheduled on the same day.) Archive files (with the extensions .bar and .bin) are stored in the same directory as the log files for 30 days and then are automatically deleted.
Viewing Database Information 2. Select the database name from the list. A summary of information about the database is displayed: - Engine Start Time: The date and time that the Interplay Engine began running. - Name and description: Either AvidWG (Interplay Engine) or AvidAM (Interplay Archive Engine) with a description supplied when the database was first created. - Root folder for database (Meta Data): See “Creating an Interplay Database” on page 28.
Viewing Database Information For information about these tabs, see “Database Information Tabs” on page 60. Database Information Tabs The following sections describe the individual tabs in the Database Information view. n See the Avid Interplay What’s New in Version 2.7 for additional information. Database Statistics Statistics in the Database and Cache Size section of this tab provide information about the number of pages in the database, cache usage, and how they relate to each other.
Viewing Database Information • - Successfully deleted media files: The number of media files deleted from shared-storage. - Size of successfully deleted media files. The cumulative size of the successful deletions based on information in the Interplay Engine database. This information is not necessarily the most recent information from the Media Indexer. Deletion Statistics Since Last Engine Start: These parameters list cumulative totals since the last time the Interplay Engine was started.
Locking and Unlocking Databases Object Statistics Statistics on this tab show totals for objects in the database. • Total number of database objects: A sum of the objects listed below. • Database objects per database page: This statistic is calculated as total number of database objects / total number of database pages • masterclip, sequence, subclip, group, motioneffect, effect, renderedeffect: the number of these object types. • filemob: the number of file locations that are known to the Engine.
Locking and Unlocking Databases 2. Select the database in the Unlocked Databases list. 3. (Option) Type a Lock comment explaining why you are locking the database. This information appears in the Locked Database Information area for the database. 4. Click Lock Database. Your user ID and the time at which you locked the database are filled in, and the database is displayed in Locked Databases. To unlock a database: 1. Select the database in the Locked Databases list. 2. Click Unlock Database.
Managing Databases: Deactivating, Activating, and Migrating Managing Databases: Deactivating, Activating, and Migrating Use the Managing Databases view to remove a database from the list of active databases (deactivate) or to restore it to the list (activate). This view also lets you migrate a database to a new Central Configuration Server (CCS) when necessary.
Managing Databases: Deactivating, Activating, and Migrating 2. Select the database name in the Databases list. 3. Click Deactivate. The database name is removed from the Databases list. Activating a Deactivated Database If a specific database is not listed in the Databases view, it means that it is unknown to the Interplay Engine and users cannot connect to it. If the database exists but is not listed, it is probably deactivated. You activate a database by navigating to the database .pro file (AvidWG.
Managing Databases: Deactivating, Activating, and Migrating 2. Do one of the following: t In the “Database (.pro) file to activate” text box, type the full UNC path to the .pro file. For example: \\IEServer\WG_Database$\AvidWG\AvidWG.pro t Click the Browse button, log in if prompted, navigate to the .pro file using a network, select the file, and click Open. The following illustration shows the path to AvidWG.pro, using the Microsoft Windows smb network and the administrative share WG_Database$.
Managing Databases: Deactivating, Activating, and Migrating The .pro file is displayed in the Activate Database dialog box.
Managing Databases: Deactivating, Activating, and Migrating 3. Make sure the option “Load Database on Activation” is selected. Deselect this option only if directed by Avid support. 4. Click Activate. The database is activated and loaded. The database name is displayed in the Databases list and users can connect to the database. If the option “Load Database on Activation” is selected, the database is automatically unlocked.
Managing Databases: Deactivating, Activating, and Migrating To migrate a database to a new CCS: 1. In the Database section of the Interplay Administrator window, click the Manage Databases icon. The Manage Databases view opens. 2. In the Manage Databases view, click the name of the database that needs migration. The State reads “Database Requires Migration.” A warning explains the consequences of a database migration. 3. Click Migrate Database. After the migration, the State reads “OK.
Moving a Database to Another Server (Non-Clustered Systems) Moving a Database to Another Server (Non-Clustered Systems) Under special circumstances, you might need to move a database to a different server. The following procedure refers to Interplay Engine servers that are not configured as failover clusters. For clustered systems, see “Moving a Database to Another Server (Clustered Systems)” on page 74.
Moving a Database and Users to Another Server (Non-Clustered Systems) 6. Pack the database folder into a zip file or use Robocopy from the Microsoft Windows Resource Kit for path names longer than 256 characters. To save time and storage, you do not need to copy all the backups in the D:\Workgroup_Databases\AvidWG\_Backup folder. One complete backup and the most recent Fast backup are sufficient. If you are moving a split database, create two zip files, one for D:\Workgroup_Databases\AvidWG and the other f
Moving a Database and Users to Another Server (Non-Clustered Systems) c c Avid recommends that you have telephone support from Avid during the process in case complications arise. If you move a database to a server that points to a different CCS, all the old CCS information that was stored, including users, user settings, and local administration settings for the database, will be lost because you will have to migrate the database (see “Migrating a Database” on page 68).
Moving a Database and Users to Another Server (Non-Clustered Systems) The default path is D:\Workgroup_Databases\_InternalData. 9. Copy the zipped file or files and the _InternalData folder to a network server, removable media, laptop, or directly to the target server. 10. Open the Interplay Administrator, log in to the target server, and deactivate the database (AvidWG or AvidAM) using the Manage Databases View. 11.
Moving a Database to Another Server (Clustered Systems) Moving a Database to Another Server (Clustered Systems) Under special circumstances, you might need to move a database to a different server. The following procedure refers to Interplay Engine servers that are configured as failover clusters. For non-clustered systems, see “Moving a Database to Another Server (Non-Clustered Systems)” on page 70.
Moving a Database to Another Server (Clustered Systems) c Make sure that you change the state to offline for the Avid Workgroup Engine Monitor resource only, not the entire Avid Workgroup Server group. d. Close the Cluster Administrator. 5. Locate the database folder on the active node of the source server. The default path is \\virtual_cluster_name\WG_Database$\AvidWG (or AvidAM for an Archive Manager). By default, the administrative share WG_Database$ refers to S:\Workgroup_Databases.
Moving a Database and Users to Another Server (Clustered Systems) 13. (Option) On the source server, rename the original database folder to avoid unwanted future access. Use the Cluster Administrator to bring the source server back online. Right-click the Avid Workgroup Server group (not the resource) and select Bring Online. Moving a Database and Users to Another Server (Clustered Systems) Under special circumstances, you might need to move a database and users to a different server.
Moving a Database and Users to Another Server (Clustered Systems) 5. Make sure the database is unloaded by using the Cluster Administrator on one of the cluster nodes: c a. Select Programs > Administrative Tools > Cluster Administrator. b. Open the Avid Workgroup Server resource group. c. In the list of resources, select Avid Workgroup Engine Monitor and change the state to “Offline.
Moving a Database Under Low Disk Space Conditions 13. Rename the existing _InternalData folder to _InternalData_old. 14. If you are copying a non-split database, copy the zipped file to the target server and unzip the file to the Workgroup_Databases folder. Copy the _InternalData folder to the Workgroup_Databases folder. Make sure the path on the target server matches the path on the source server. If you are copying a split database, copy and unzip both zipped files to the correct locations.
Renaming a Database c Before beginning this procedure, be sure to make a backup of the database. See “Creating and Restoring Database Backups” on page 33 for information on running a backup. Temporarily change the Backup time field to “Once at” and enter or select from the list the time in the future closest to the current time. To move a database under low disk space conditions: 1. Lock the server using NxNServerLock.exe. 2. Shut down the server using NxNServerShutdown.exe, if necessary. 3.
Running Database Maintenance Tools 3. On the server or at the database location, use the Windows desktop to rename the database folder, .pro file, and .nif directory, and all files within the _Database folder, that is, replace the old with the new name for all files fitting the following mask: \.pro \.nif \\_*.pro.jrn \_Database\.* \_Database\_*.
Running Database Maintenance Tools Lost master mobs are assets (such as sequences, master clips, and subclips) that are stored in the database but have no visible representation in a folder. • Delete Lost File Mobs: Use this tool to detect and remove media file information objects containing information about a specific media file, like the resolution, site or location, which are not associated to an asset.
Running Database Maintenance Tools Engine, you can run a command-line program to release Exclusive Access. The file name of the tool is NxNServerExclusiveAccessRelease.exe and it is installed by default on the Interplay Engine in one of the following folders: n • 32-bit OS: C:\Program Files\Avid\Avid Interplay Engine\Server • 64-bit OS: C:\Program Files (x86)\Avid\Avid Interplay Engine\Server For more maintenance information, see “Interplay Maintenance Recommendations” in the Avid Interplay Best Prac
Running Database Maintenance Tools Tool Options Delete Lost File Mobs • Delete File Mobs. Select this option to delete lost media information objects. • Delete Media. Select this option to delete media associated with the lost media information objects. If you do not select these options, the tool reports problems but does not take action to fix them. Validate User Tree (Interplay Engine v2.6 or later) • Verbose Output. Select this option to display the media path. • Fix Invalid Users.
3 Server Settings The Server settings enable you to configure and change server settings and shutdown and restart the server. The following topics describe how to use these settings: • Changing the Database and Data Locations • Viewing Server Information • Locking and Unlocking the Server • Restarting the Server • Managing Licenses Changing the Database and Data Locations The Server Settings view lets you change the default locations for a new database.
Viewing Server Information To change the root folders for a new database: 1. In the Server section of the Interplay Administrator window, click the Server Settings icon. The Server Settings view opens. 2. For the root folder of the database (metadata), keep the folder that was set during the installation of the server (the default is \\IEServer\WG_Database$\). 3.
Viewing Server Information • • The Connected User Information area displays information about the following: - Which database users are connected to - Which user is connected to which database - Which machine the user is connected from - What time a user has been connected since The type of licenses in use (see “License Types and Usage” on page 94) To view information about the Interplay Engine server: t In the Server section of the Interplay Administrator window, click the Server Information
Locking and Unlocking the Server Locking and Unlocking the Server The Lock Server view allows the administrator to lock the Interplay Engine server for a specific period of time. Locking the server is useful when carrying out tasks such as: n • Server maintenance or upgrading the server software. • Maintaining or rebooting the Avid shared-storage server. Whenever a database or data location is unavailable, you should lock the database or the server.
Locking and Unlocking the Server The following table summarizes the differences between a server lock, a database lock, and Exclusive Access: Feature Description Server lock (Lock Server view) Saves and unloads all databases (including _InternalData). Also prevents access by the Interplay Administrator. Should be used for maintenance operations that require access to all database files (in the share WG_Database$). Usually shutting down the Interplay Engine is a better approach than a server lock.
Locking and Unlocking the Server 2. In the Lock Server section, select one of the following for the locking duration: - Indefinitely: An indefinite shutdown. This is a good choice when shutting down the server to carry out any vital maintenance, for example replacing hard drives, or making the first backup of a new database. The server needs to be manually unlocked after maintenance work. - Minutes: Allows you to stipulate when to restart the server (short time frame).
Locking and Unlocking the Server 3. In the “Lock comment” text box, type a comment as to why you are locking the server. This comment is displayed when an Interplay Administrator tries to log into the Interplay Engine. 4. Click Lock Server. The Lock Server view changes to display lock information. You cannot return to the Interplay Administrator window by clicking the Menu button. You can log out of the Interplay Administrator tool and then log in again.
Restarting the Server You can return to the Interplay Administrator window by clicking the Menu button, log out of the Interplay Administrator tool and then log in again, and perform other database tasks. To manually unlock the server after activating Exclusive Access, do one of the following: t t Log in to the Interplay Administrator from the host where you acquired Exclusive Access or on the Engine host itself, click the Lock Server icon, then click Release Exclusive Access.
Managing Licenses Managing Licenses Avid Interplay needs valid licenses in order to function. A license consists of a hardware ID and a license key. The hardware ID is sometimes associated with the physical application key, or dongle. The license key is created by a license file and includes information about the license types for individual applications.
Managing Licenses To view information about your licenses: t In the Server section of the Interplay Administrator window, click the Licenses icon. The Licenses view opens. For information about importing a license file, see “Installing a Permanent License” on page 93. For information about exporting a license file, see “Exporting a License” on page 95.
Managing Licenses A license for an Interplay Engine failover cluster includes two hardware IDs. You only need to install the license on one node of the cluster. To install a permanent license: 1. Start and log in to the Interplay Administrator. 2. Make a folder for the license file on the root directory (C:\) of the Interplay Engine server or another server. For example: C:\Interplay_Licenses 3. Insert the USB flash drive into any USB port. n You can access the license file from the USB flash drive.
Managing Licenses License Types Used for Avid Applications (Continued) Key Product KEY-X Interplay Access KEY-XA Interplay Sphere KEY-XE Avid Editing Applications KEY-XI Avid Instinct KEY-XL Interplay Assist KEY-XP Digidesign™ Pro Tools®Integration One Interplay Streaming Server license (KEY-C) is required for each streaming server in an Interplay workgroup. If you have an editing application running, then no additional license is needed to run Access at the same time.
Managing Licenses To delete the registry key for a dongle: 1. Click Start, then click Run. 2. In the Open text box, type regedit and click OK. The Registry Editor view opens. 3. Locate the registry key for the original dongle, found here: - (32-bit OS) HKEY_LOCAL_MACHINE\SOFTWARE\Avid Technology\Workgroup\Avid Workgroup Server\FeatureKeys\Permanent - (64-bit OS) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Avid Technology\Workgroup\Avid Workgroup Server\FeatureKeys\Permanent 4. Delete the Permanent folder.
4 User Management An administrator controls access to Avid Interplay through user accounts and user roles.
Understanding the Central Configuration Server Depending on the number of Interplay Engines that are installed, several CCS configurations are possible: • One Interplay Engine: Configure this server as the CCS. • Several Interplay Engines: Usually you configure only one Interplay Engine as the CCS. The use of more than one CCS in a company might be useful if there are several independent domains, departments, or sites where there is no need to share users or other settings in Avid Interplay.
Understanding the Central Configuration Server c Server B should be created by a clean installation and should serve as its own CCS. No other database should point to Server B as a CCS, because any existing user data on Server B will be lost. To move a CCS to another server: 1. Back up the database. See “Creating and Restoring Database Backups” on page 33. 2. Make sure that the Interplay Engine on both servers is the same version. See “Viewing Server Information” on page 85. 3.
Understanding the Central Configuration Server The following procedure is based on these assumptions: • Server A is the CCS. • You want server B to be the CCS for server A. You want to use the settings and user information that exists on server B. • You do not want to keep the CCS information that exists on server A. To change the CCS for a server: 1. Back up the database. See “Creating and Restoring Database Backups” on page 33. 2.
Understanding the Central Configuration Server 6. Do one of the following: t To keep the original CCS, click Cancel. t To change to a new CCS, click Change CCS. 7. If you have not moved the original CCS server (see “Moving the CCS to Another Server” on page 98), you need to migrate the database to the new CCS and all of your CCS-related data (such as users and local administration) are lost. Unmigrated databases should not be used; databases should always be migrated to a CCS.
Adding Users to a Central Configuration Server Adding Users to a Central Configuration Server There are several ways to add users to a Central Configuration Server: • Automatically adding Avid Unity (shared-storage) users. These users are added to the CCS the first time they log in. They log in using their Avid Unity username and password. For more information, see “Setting Avid Unity Authentication” on page 104. • Importing users from a Windows domain or LDAP directory.
Setting User Authentication Providers and Importing Users n All special characters are allowed in user names except for \ (backslash), / (forward slash), | (vertical bar), and quotes (" and '). When LDAP and Windows Domain users are imported, these characters are replaced with “_”. If two users have different user names that are mapped to the same converted name (for example, dann/o and dann\o become dann_o), only one converted user name is imported.
Setting User Authentication Providers and Importing Users The users are added to the Imported Users folder in the User Management page, under the respective subfolder for LDAP, Microsoft, or Avid Unity. Users are also added to the Everyone folder. The following illustration shows these subfolders with the LDAP folder selected.
Setting User Authentication Providers and Importing Users This method of authorization is implicit. In other words, there is no active import of users at the time the Avid ISIS Authentication is enabled. Instead, the first time that an Avid Unity user logs in to Avid Interplay, the user is added to the UNITY user group subfolder. By default, this user group has Read rights. If your workgroup includes multiple ISIS systems, you need to specify each additional ISIS server name.
Setting User Authentication Providers and Importing Users An administrator needs to assign suitable roles to the imported users before they can access the database. By default, imported users do not have access rights to the database, which will cause a login to fail even if a user is properly authenticated by the domain. In this case, the following error message is displayed: Note also that for Interplay to import users from an Active Directory, these users must be placed in groups.
Setting User Authentication Providers and Importing Users 4. Do one of the following: t Select the user groups you want to import into the Avid Interplay system. t Click Select All to import all the user groups into the Avid Interplay system. 5. Click OK.
Setting User Authentication Providers and Importing Users OpenLDAP Active Directory LDAP n Details on the LDAP schema objects can be found in RFC1274, “The Cosine and Internet X.500 Schema.” If an Active Directory is made up of multiple OUs (organizational units) in multiple domains, you can select a specific OU for user authentication. See “Authentication from an Active Directory that Includes Multiple Domains” on page 112. To import LDAP users and enable LDAP authentication: 1.
Setting User Authentication Providers and Importing Users 5. Click Import LDAP Users. A warning message tells you that during an import other users will not be able to work with this server. 6. Click OK. Interplay creates a new user group and subfolder called LDAP under Imported Users and imports all the users from the LDAP server that match the filter criteria in the LDAP configuration, and are not currently available in the Avid Interplay user database.
Setting User Authentication Providers and Importing Users Setting Description Password for Searches Password for a user who has the right to query the directory. This password will be used for logging on to the LDAP directory after you click the Import LDAP Users button. Search Root DN DN root for searches in the LDAP database. This DN specifies the search root that will be used after you click the Import LDAP Users button.
Setting User Authentication Providers and Importing Users Setting Description User DN Suffix Suffix that must be appended to the user name to form a valid Distinguished User Name (DN). The resulting DN will be used whenever a user tries to authenticate through LDAP: Interplay will issue a simple ldap_bind request to the directory service, using a DN constructed according to the rule given above, and the clear text password as given by the user.
Setting User Authentication Providers and Importing Users Authentication from an Active Directory that Includes Multiple Domains An organization might have an Active Directory that includes several domains.
Setting User Authentication Providers and Importing Users If a domain includes only one user OU, you can specify that domain as the Search Root DN and the User DN Suffix. In the following illustration, import and authentication is specified for test1.test.avid.com LDAP Authentication from a Single OU A domain might have more than one OU. The following illustration shows three user OUs for test1.test.avid.com.
Setting User Authentication Providers and Importing Users In the LDAP Authentication Settings, you would specify the specific OU as the Search Root DN, and then specify a User DN Suffix to authenticate users in that OU. In this example, the Search Root DN is set for the OU test\userou1 in the domain test1.test.avid.com. The User DN suffix matches this search root.
Managing Users, User Groups, and User Rights Managing Users, User Groups, and User Rights The User Management view lets you create, modify, manage and delete users and user groups. It also lets you define user roles and authentication protocols. If you are working in an environment that includes more than one Interplay Engine, you should manage users through a CCS (see “Understanding the Central Configuration Server” on page 97).
Managing Users, User Groups, and User Rights For more information about managing user roles, with specific examples, see “Setting Up a Folder Structure and a User Database” in the Avid Interplay Best Practices Guide. The following illustration shows the User Management view with the Administrators group selected. In this example, there are three custom user groups: Assistants, Editors, and Graphic Artists.
Managing Users, User Groups, and User Rights Understanding Default User Groups, Users, and Roles The User Management view displays all user groups and users. The user groups created during the server installation are as follows: • Administrators, with the user Administrator: Users with administrator rights. When you first log in after the first installation, if you have not yet imported Windows Domain or LDAP server users, the only user displayed is the user “Administrator” with administrator rights.
Managing Users, User Groups, and User Rights also have a group of assistants that should have Read/Write privileges. In this case you can set up two user groups that have different sets of privileges: one named Editors, and one named Assistants. To create a user group: 1. In the User Management section of the Interplay Administrator window, click the User Management icon. The User Management view opens. 2. In the Users pane, select the group into which you want to add a the new user group.
Managing Users, User Groups, and User Rights 4. Add attributes for the new user: name, description (inherited from the user group by default), password, password confirmation, and email. All special characters are allowed in user and group names except “\”, “/”, “|” and quotes (" and '). For more information, see “Viewing and Setting Attributes” on page 119. 5. (Option) Select a role for the new user. Roles are inherited from the group in which you create the user.
Managing Users, User Groups, and User Rights To set the internal password: 1. In the Users list, select a user. 2. Type the password and the confirmation in the text box. 3. Click Apply. The user can change his or her password anytime in the login dialog box. c If you select the Internal Authentication option and do not set a password, anyone can log in with that user name and no password.
Managing Users, User Groups, and User Rights Viewing and Changing Roles By default, all users in a group inherit the role assigned to the group. You cannot assign rights to specific users in the User Management view. If you want to change a user’s rights, you can move the user to a different group. For more information about setting up roles correctly, see “Managing Database Roles” on page 125.
Managing Users, User Groups, and User Rights To navigate to the Users tree from the Part of Group(s) pane: 1. Select the user group in the Part of Group(s) pane. 2. For any user group other than the Users group, right-click and select one of the following: t Select “Go To” to switch the focus of the Users tree to the group you selected. t Select “Go to user in this group” to switch the focus of the Users tree to the selected user in the selected user group.
Managing Users, User Groups, and User Rights To change the role for a user, do one of the following: t Right-click the user and select Cut, select the group, right-click the group and select Paste. This action moves the user from one group to another. You can also drag the user from one group to another. t Right-click the user and select Copy, select the group, right-click the group and select Paste. This action removes the user from one group and adds it to another.
Managing Users, User Groups, and User Rights To change or add an authentication provider: 1. In the Users list of the User Management view, select the user. 2. In the Authentication Providers pane of the User Management view, select the appropriate options. 3. Click Apply to make the change, or Revert to discard your changes. Deleting Users and User Groups You can delete any user except Administrator and you can delete any user group except Administrators, Migrated Users, and Everyone.
Managing Database Roles To remove a user from a user group: 1. Select the user in the group from which you want it removed. 2. Do one of the following: t Press the Delete key. t Click the Remove User button. Managing Database Roles You set and manage global roles for users in the User Management view (see “Managing Users, User Groups, and User Rights” on page 115). You have the option of limiting or granting rights for specific users on specific folders.
Managing Database Roles 2. Select the General Role Assignment option. General Role Assignment option 3. In the Database pane, select the database or a folder for which you want to view roles.
Managing Database Roles If the database icon has a red X, you are not connected. Click the database icon to connect. The database icon shows a green check mark when you are connected. The following table describes three different states of the database icon. Icon Meaning (Green circle with check mark) Database you are connected to. (Red box with X) Database you are not connected to. (Red box with X and yellow arrow) Database needs migration. See “Migrating a Database” on page 68. 4.
Managing Database Roles Setting or Changing a General Role Assignment Use the Manage Database Roles view to set or change rights to a particular folder. Note the following: • To delete items, the user must have deletion rights for the folder, even if the user is the owner of the item to be deleted. • To move items, the user must have write rights on the object, the folder the object is being moved out of, and the target folder.
Managing Database Roles for Orphan Clips. Administrators have full access to all folders. For more information about the Unchecked-in Avid Assets folder and the Orphan Clips folder, see the Avid Interplay Access User’s Guide. To set or change a role for users of the database or a folder: 1. In the User Management section of the Interplay Administrator window, click the Manage Database Roles icon. The Manage Database Roles view opens. 2. Select the General Role Assignment option. 3.
Managing Database Roles 6. Click Set Role. The role appears in the lower panel. To change a role: t Select the entry in the lower pane, right-click, and select Set Role > role name. To remove a role for users of the database or a folder: 1. Select the database or a folder in the Database column. 2. Select an entry in the list in the lower pane. 3. Do one of the following: t Click the Remove Role button. t Right-click and select Remove Role.
Managing Database Roles Blocking Access by a Group or User When you are trying to block access by a whole group, it is not sufficient to change the user rights for the user group to NoAccess; individual users who have rights assigned to them specifically or through memberships in other user groups could still log in. To block members of an entire group: 1. In the Manage Database Roles view, in the Database pane, select the project from which you want to block users. 2.
Managing Database Roles 3. Click the Apply button for the option “Mark as Special Access Folder: Grant path access and allow to view path.” This option allows users to log in to the database and navigate to the specified location. The tree structure above the folder will be visible, but not the contents of the other folders in the structure. The first option makes the contents of the tree structure accessible as well (not recommended).
Managing Database Roles The following illustration shows that the user jeditor has special access to the folder /Outside Productions/Graphics. To view what specific role jeditor has, select the folder in the Database pane. Special Access Folder User who can access Special Access Folders To remove a role assigned for Special Access folders: 1. Click the Special Access Folders option. 2. Select the appropriate folder. 3. Select the user in the list in the lower pane. 4.
Guidelines for User Management Guidelines for User Management This topic provides information and suggestions that can help you manage users and access. For more information about managing user roles, with specific examples, see “Setting Up a Folder Structure and a User Database” in Avid Interplay Best Practices.
Guidelines for User Management 3. If there are no inherited permissions, the server checks the global user rights. In this case, the server determines what role the user has from the CCS settings. 4. In case of a conflict where the evaluation sees a user with multiple roles, for example: - the user has the read role through one group - the user has the read/write role through another group then the highest ranking role wins. In this case, the user gets the read/write role.
5 Site Settings Site settings include configuration options for various Interplay components.
Defining Property Layouts These properties are sometimes referred to as system metadata. However, it is only part of the metadata included in an Avid Interplay database. For a description of available properties, see “System Metadata Properties” on page 279. For Interplay Access, administrators select which properties are displayed by default in the Content tab and Object Inspector Property tabs. Users can then add other available properties to these tabs.
Defining Property Layouts 2. Select the database for which you want to set properties. 3. Click the System Properties tab. 4. From the Active Layout options, select one of the following layouts: - Broadcast - Post - Film This option determines which set of properties is displayed in the client applications. 5.
Setting the Resolutions Available for Display n t (Option) To include a property in the Interplay Access Content tab, select the property in the Content Default Column. To remove a property from the Content tab, deselect it. t (Option) To include a property in the Interplay Access Object Inspector’s Properties tab, select properties in the Inspector Default column. To remove a property from the Object Inspector’s Properties tab, deselect it.
Setting the Resolutions Available for Display In some circumstances you might want to make additional resolutions available for display. For example, if you are using Interplay Access to view the status of assets on remote workgroups, and the database for the local workgroup does not include resolutions used on the remote workgroup, you can select those resolutions for display in the local version of Interplay Access. By default, the option “Enable used resolutions automatically” is selected.
Creating Custom Properties Resolution in local database: grayed-out check box, name in bold face Resolution not in local database: grayed-out check box, name not n bold face 5. To remove a resolution, deselect its check box in the Available column. If you want to remove a default resolution, deselect “Enable used resolutions automatically” and then deselect the resolution’s checkbox. Keep in mind that any new resolutions added to the database will not be automatically selected as available for display.
Creating Custom Properties By default, the user needs to type the value for a custom property. Administrators can import an XML file that creates a list of values from which the user can select a value.
Creating Custom Properties When the Available column is selected, the custom property is available for users to add into the application displays, and to use in an Extended search. If the user performs an All Custom search, only the available custom properties are used in the search. n Deselect the property in the Available column to turn off custom properties that you do not want displayed in the properties lists. You cannot delete custom properties for this release but you can turn off their display.
Creating Custom Properties 8. Click Apply to save the added custom property and new layout. 9. (Option) If you want to prevent a user or group from supplying a value for a custom property, change the role in the User Management view (see “Setting Access Control for Custom Properties” on page 145). The next time a user starts Interplay Access and logs in, the new custom property is displayed.
Creating Custom Properties To select a value, click an item in the list, then click Apply. In this example, a user associated the value Team A to the folder. Users can add a custom property as a column in Interplay Assist, Avid Instinct, and the Interplay Window. Setting Access Control for Custom Properties You can control which users can supply a value for a custom property. This setting applies to both typing a value and selecting one from a list. By default, users are allowed to supply a value.
Creating Custom Properties Users pane Edit button Additional Roles pane 2. In the Users pane, select a group or user. 3. In the Additional Roles pane, select an option for “Can modify properties in Access”: - Inherited: Allows the selected user or group to inherit the role of the parent group - Yes: Allows users to type a value or to select from a menu. - No: Prevents users from typing or selecting from a menu. Users can see the property and its text box, but cannot supply a value for it.
Creating Custom Properties Working with Lists for Custom Properties You can create a custom property that includes a list of values from which users can choose (see “Creating Custom Properties” on page 141). These lists are sometimes referred to as dictionaries or taxonomies.
Creating Custom Properties The following example shows an XML file that creates a two-level hierarchy, with “League 1 Team A” as the default value. PAGE 149
Creating Custom Properties n A custom property with a list of values is blank until you select a value. After you select a value, you cannot return the field to a blank state. If appropriate for your custom property, you can include a value in the list called “No Value” or something similar. To clear a value and completely remove a list, see “Removing a List for a Custom Property” on page 149. To create an XML file of values for a custom property: 1.
Creating Custom Properties To remove a list of values for a custom property: 1. Use a text editor or XML editor to create a file that matches the following format. Use quotation marks as shown: 2. Save the file. 3. In the Custom Meta Data tab, select the custom property and import the file, as described in “Adding a Custom Property” on page 142.
Configuring Remote Workgroups Configuring Remote Workgroups A large site can include more than one workgroup. When a workflow requires searching across remote workgroups or performing workgroup-to-workgroup transfers through Interplay Access, you must set up the local workgroup so that a user can access a remote workgroup. You set up this access in the Configure Remote Workgroups view. You can add an Interplay Archive Engine as a remote workgroup.
Configuring Remote Workgroups 4. Select a database from the Available Databases list. 5. In the New server pane, add information about the remote workgroup you want to access. a. b. Select the Host Type: - Interplay Server/Remote Search—to add access to a remote Interplay workgroup - TransferManager—to add access to a Workgroup 4 TransferManager - MediaManager—to add access to a Workgroup 4 workgroup or Nearchive™ system - Interplay Server / 3d Party Search—to add access for a third-party plug-in.
Configuring Categories c. Click Add. The Server name and other information about the remote workgroup appears in the list of accessible remote servers. To remove a remote workgroup from the accessible list: 1. Click the name of the remote workgroup in the list. 2. Click Remove. Configuring Categories Categories provide a grouping mechanism for the data that is stored in the database. Categories are displayed in Interplay Access, Interplay Assist, and Avid Instinct.
Configuring Categories 2. Select a database from the Available Databases list. 3. In the New Categories text box, type one name for a category, or type a comma-separated list (commas and spaces are automatically removed). 4. Click Add, and then click Apply. After refreshing Interplay Access, the categories you specified are visible in the Categories pane. When performing a search, you can use a Category name to locate items that belong to that category.
Setting Server Hostnames and the Workgroup Name Removing Categories Removing a category only removes it from the Configured Categories list in the Interplay Administrator. Objects in the database that have this category keep it, even if it is not listed anymore. If an item was assigned to a category but you removed that category in the Interplay Administrator, users are informed that the category is not valid anymore in the Interplay Access Categories tab. To remove a category: 1.
Setting Server Hostnames and the Workgroup Name • c The name of the Interplay workgroup. You must enter the name of the workgroup so that Interplay Access, Interplay Assist, and Avid Instinct can locate the Media Indexer, which is used to monitor shared storage. For more information, see the Avid Service Framework User’s Guide. The Workgroup Name field is case sensitive and the name must exactly match the workgroup name used by the Avid Service Framework.
Setting Server Hostnames and the Workgroup Name To register the Interplay Media Services Engine: 1. In the Site Settings section of the Interplay Administrator window, click the Server Hostname Settings icon. The Server Hostname Settings view opens. 2. In the Interplay Media Services Settings area, type the name of the Interplay Media Services Engine server in the text box. 3. Click Apply Changes. To set the Interplay Delivery Receiver host and port: 1.
Setting Server Hostnames and the Workgroup Name To set the workgroup name and check Media Indexer: 1. In the Workgroup and Media Indexer Settings area, type the workgroup name. c The Workgroup Name field is case sensitive and the name must exactly match the workgroup name used by the Avid Service Framework. 2. Click Apply Changes. 3. Click Check Media Indexer to check whether the Media Indexer that monitors shared storage is running.
Setting Server Hostnames and the Workgroup Name n In Interplay v2.4, the Interplay Streaming Server was re-engineered to directly play MPEG-4/H.263 and H.264 video media and MPEG1 layer 2 audio media. There is no longer any need to use the Publishing service or Workflow Engine to create QuickTime reference movies for streaming play. Double-click a clip that is associated with supported proxy media, and the clip plays in the Interplay Access Monitor. For Interplay v2.
Interplay Media Services View To rename an Interplay Streaming Server: 1. In the Stream Server Settings area, click the Rename button. The Rename Stream Server and Share dialog box opens. 2. Type the computer name of the system that is now running the Interplay Streaming Server. You do not have to type \\ before the name of the server. 3. Click OK. The computer name is displayed in the Server Hostname Settings view. To delete an Interplay Streaming Server: 1.
Interplay Transfer Status View Interplay Transfer Status View The Interplay Transfer Status view is used for monitoring the progress of transactions being handled by one or more Interplay Transfer Engines in the workgroup. It allows administrators to quickly view all the relevant details for each transaction. You can choose to have the status window open at all times in their control center.
Specifying Remote Servers for Asset Tracking Specifying Remote Servers for Asset Tracking If your facility includes more than one workgroup, you can use Interplay Access to display information for assets that are shared by different workgroups. For example, you can determine if assets stored in one workgroup are correctly archived in an archive workgroup. In the Interplay Administrator, you need to specify the name of the Interplay Engine server for the remote workgroup.
Specifying Archive Settings 3. If you want to track assets on an archive server, in the Archive Server name text box, type the computer name of the Interplay Archive Engine. 4. Click Apply Changes. Specifying Archive Settings The Asset Tracking/Archive Settings view lets you select options for how the Interplay Engine operates with the Interplay Archive Engine and the Archive Provider. The view displays different settings, depending on where you are logged in.
Specifying Archive Settings The Interplay Archive Engine avoids duplication by default. If you prefer to have the Archive Engine archive duplicate media files, you can use the Interplay Administrator to change the setting. This setting appears only when you log in to an Archive Engine database. To change whether archive operations create duplicate media: 1. Open the Interplay Administrator and log into the system running the Archive Engine. 2.
Specifying Archive Settings - Yes — The Archive Provider archives the associated media each time you archive an asset. If you delete an asset that references the duplicated media, the system asks if you want to delete the associated media files. If you choose the delete the media, the system deletes all copies of the media. 5. Click Apply Changes. Adding AAF Metadata to an Archive The Asset Tracking/Archive Settings view on the Interplay Archive Engine includes an option labeled “Allow Metadata Archive.
Setting the Ownership for New Database Folders 4. In the Archive Settings area, do the following: n t In the Archive server name text box, type the name of the computer running the Avid Interplay Archive Engine. t In the Archive Segment size (frames) text box, type the segment size used for partial restore operations, in frames. The default and minimum value is 1800 frames. If you later change the Archive Segment size, the new size applies only to new archives.
Setting the Ownership for New Database Folders 4. Editor 2 duplicates Final_Sequence, moves it into folder Final_2 and renames it Final_Sequence_2. Referenced assets are selected to be displayed in folder Final_2 (Tools > Options > Filter Settings), so the master clips that make up the sequence are displayed in the folder. 5. Editor 2 deletes Final_Sequence_2, its master clips, and its associated media.
Setting Options for Deletion - “Set creator as owner” is the default. - “Set same owner as parent folder” sets the owner of a new folder to be the owner of the folder in which the new folder was created. 4. Click Apply. The change takes effect immediately. 5. To undo your change, click Revert, then click Apply.
Setting Options for Deletion • “Logs for Deleted Media and Metadata” on page 173 • “New Properties for Deletion” on page 174 For information about deletion workflows and recommendations, see “Developing an Interplay Delete Strategy” in the Avid Interplay Best Practices Guide. Three Parts of the Deletion Process If you select to delete assets and media in the Interplay Access Delete dialog box, the deletion process consists of three major parts: 1.
Setting Options for Deletion Clip 1 (link) V1 media Clip 1 database asset Clip 1 copy (link) A1 media A2 media The last part of the process is the part that takes the longest time and places the heaviest load on the Interplay Engine. In addition, this part of the process does not provide immediate feedback, as opposed to media deletion (you can see the files deleted from shared storage) and link deletion (you can see links are deleted from the Access folder structure).
Setting Options for Deletion You can think of deletion prior to v2.4 as synchronous, because all three parts of the process occur at approximately the same time, during the interactive part of the deletion (that is, while the Delete dialog box is open). Deletion in v2.4 and later is asynchronous, because deletion of the database assets takes place after the interactive part of the deletion. c It is important to remember that in Interplay v2.4 and later the deletion process is always asynchronous.
Setting Options for Deletion Scheduled deletion works similarly on the Interplay Archive Engine. On the Interplay Archive Engine, media is flagged for deletion, but the deletion itself takes place through the third-party archive system. Changes to the Orphan Clips Folder c The function of the Orphan Clips folder and the status of its contents changed in Interplay v2.4.
Setting Options for Deletion option to delete is not selected by default, so even if you do not enable custom deletion, the Interplay Engine creates a Kept Media folder when needed. You can manually delete clips and media from this folder at a time that is appropriate for your workflow.
Setting Options for Deletion The following are examples of AvMetaDataDelete logs: • When a user deletes metadata that is moved to the Orphan Clips folder: [Thu Mar 10 12:12:17 2011] User 'Administrator' on host 'MUC-TReichgr' deleting metadata: [Thu Mar 10 12:12:17 2011] From '/Projects/Test3/' [Thu Mar 10 12:12:17 2011] moved to Orphan Clips 'LHJU MOUNTIES -Vakantiekamp' handle 1921 [Thu Mar 10 12:12:17 2011] moved to Orphan Clips • 'MOUNTIES - vakantiekamp' handle 1924 When a scheduled deletion p
Setting Options for Deletion Scheduling the Deletion of Database Assets Beginning with Interplay Engine v2.4, you can schedule custom time spans and set other options for deletion of database assets in the Interplay Administrator. This feature lets you schedule a significant part of the load generated on the Interplay Engine by deletion operations to take place during times of low activity. n Even if you do not schedule a custom deletion, deletion in v2.
Setting Options for Deletion By default, a scheduled deletion stops when an Interplay backup begins, and resumes when the backup ends or at the next scheduled deletion. Select this option to allow both processes to operate at the same time. - Permanently delete assets and associated online media from the Orphan Clips folder Select this option if you want to include assets with media in the scheduled deletion. If this option is not selected, links with media are moved to the Kept Media folder.
Setting Options for Deletion Click Add Time Span to create more than one time span. Click Remove Time Span to remove the associated time span. Overlapping time spans are not allowed. In addition to a specific time span, you can select one or more days for that time span. The following illustration shows an example of three different time spans. - The first time span specifies deletions to take place from midnight until 4:00 am every day of the week.
Setting Options for Deletion Setting Options for Deleting Only OMF Media, Only MXF Media, or Both If a clip is associated with both OMF and MXF media, you might want to delete only the OMF media or only the MXF media. You can enable an option in the Interplay Administrator so that the Delete dialog box gives users the option of which media format to delete. To set an option that allows deleting only OMF media or only MXF media: 1.
Setting Options for Deletion The next time a user logs into Interplay Access and opens the Delete dialog box, the options are active or inactive, depending on the current settings in the Delete Behavior view of the Interplay Administrator. Activating the Option to Delete Referenced Assets Starting with Interplay Access v2.
Setting Options for Deletion t If the file does not exist, open Notepad or another text editor and create a file named configuration.xml. Copy the following code into the file: true Save the file and copy the file to %APPDATA%\Avid\Workgroup.
Setting Options for Deletion Using the Delete Kept Media Tool The Delete Kept Media tool is used to automatically delete the assets and media in the Orphan Clips\Kept Media folder. The file name of the tool is delete_kept_media.exe and it is installed by default on the Interplay Engine in the following folder: C:\Program Files\Avid\Avid Interplay Engine\Server For a cluster engine, you need to execute this tool directly on the online node.
Setting Options for Deletion The maxTime option is especially useful. It allows a media manager to start the deletion process late in the evening (or generally during low-load or no-load times) and specify a window for the deletion. You can schedule the deletion before a backup starts or before use of the Interplay Engine goes up in the morning.d For example: C:\Program Files\Avid\Avid Interplay Engine\Server>delete_kept_media.
Viewing and Setting the Metadata Override Status Viewing and Setting the Metadata Override Status The Metadata Override Settings view lets you manage how the Archive Provider handles metadata when an asset is archived more than once. This view appears only when the Interplay Administrator is logged on to an Archive Engine. By default, the Archive Provider overrides the archived metadata for an Avid asset if you archive the asset again.
Viewing and Setting the Metadata Override Status 2. (Option) Select a folder in the folder tree to limit the folders displayed in the Locations window to subfolders. To enable metadata override: t Select a folder in the folder tree or one or more folders in the Locations window and click Enable Override. To disable metadata override: t Select a folder in the folder tree or one or more folders in the Locations window and click Disable Override.
6 Application Settings In the Application settings, you can configure application-specific permissions and options, as described in the following topics: • Application Database Settings View • Setting Instinct/Assist User Options • Pro Tools Plug-Ins Settings Application Database Settings View The Application Database Settings view lets you specify on a database or folder level the settings that are relevant when using an Interplay application.
Application Database Settings View Setting Options in the Editing Settings Tab The Editing Settings tab in the Application Database Settings view includes settings that apply to several different applications. Some settings apply to Interplay Instinct and Interplay Assist, some apply to Interplay Instinct only, and one setting (“Check in bins when closing”) applies only to Avid editing systems such as Media Composer®.
Application Database Settings View If the database icon has a red X, you are not connected. Click the database icon to connect. The database icon shows a green check mark when you are connected. For more information, see “Viewing General Role Assignments” on page 125. 4. Do one of the following: t Select an option from a drop-down list or by clicking an option button. t Type a setting in the text box. If a setting is grayed out, click the Edit button to enable editing. Edit button 5. Click Apply.
Application Database Settings View These settings are described in “Application Database Settings: Editing Settings Tab” on page 188. For more information about using these settings, see the Avid Instinct User’s Guide. Application Database Settings: Editing Settings Tab You can set options for the Editing Settings tab in the Application Database Settings view as described in the following table. The Applications column lists which applications are affected by each option.
Application Database Settings View Application Database Settings: Editing Settings Tab (Continued) Option Setting Description Applications Natural Sound trackAvid Instinct Interplay Central 2 If two channels are selected for NAT, Avid Instinct specifies which track of the source clip Interplay Central is mapped to NAT track 2. The default is A4. Sound on Tape track Specifies which track of the source clip Avid Instinct 1 is mapped to SOT track 1. The default Interplay Central is A2.
Application Database Settings View Application Database Settings: Editing Settings Tab (Continued) Option Setting Audio – general settings Media Creation workspace Description Applications Sets the workspace location used for Avid Instinct media clips created by users, such as Interplay Assist voice-over recordings and clips created Interplay Central during send-to-playback operations.
Application Database Settings View Application Database Settings: Editing Settings Tab (Continued) Option Setting Dynamic Relink Description Applications Enables or disables the Dynamic Avid Instinct Relink feature (for MultiRez editing). Interplay Assist If Dynamic Relink is “true,” all relink settings in the Send to Playback option are enabled; if Dynamic Relink is “false,” these settings are disabled, with the exception Audio Mixdown Mode. The default for Dynamic Relink is “not set.
Application Database Settings View Application Database Settings: Editing Settings Tab (Continued) Option Setting Description Applications Target resolution, secondary Sets a resolution to use for a second playback device. Avid Instinct Secondary target field Leave the field blank to send a sequence to playback on the primary device. Enter a value to send the sequence to the secondary playback device. Avid Instinct n Story fields are set in Avid Instinct.
Application Database Settings View Application Database Settings: Editing Settings Tab (Continued) Option Setting Description Applications Audio Mixdown Mode Sets the mixdown mode used for send-to-playback operations: Avid Instinct Interplay Assist • Mono — Maps to a center pan, which creates a mono mixdown of all audio tracks and outputs the resulting track to two channels when sent to playback. This results in two identical channels of audio, each containing the original audio tracks.
Application Database Settings View Application Database Settings: Editing Settings Tab (Continued) Option Setting Description Applications Audio Target Resolution Sets an audio resolution for output to a Avid Instinct playback device. Currently, the only Interplay Assist option is PCM. Sample Rate and Bit Depth: sets the resolution of the source audio for audio mixdowns. n If dynamic relink is enabled, you must set the audio target resolution to PCM and select a Sample Rate and Bit Depth.
Application Database Settings View Application Database Settings: Editing Settings Tab (Continued) Option Setting Description Applications Auto Reservation Duration [h] Allows you to set a default duration (in Avid Instinct hours) for auto reservations. If you do Interplay Assist not want auto reservation on a folder, set the duration to zero. The default duration is 24 hours.
Application Database Settings View Setting Audio Mixing Defaults for Access and Assist The Audio Mixing Defaults in the Application Defaults tab apply to Interplay Access and Interplay Assist. • For Interplay Access, the settings apply to the Audio Mixer controls, which let you enable and mute tracks and adjust volume. Adjustments that you make with these controls apply only when you play Avid assets and file assets in Interplay Access. For more information, see the Avid Interplay Access User’s Guide.
Application Database Settings View To set audio mixing defaults for Interplay Access and Interplay Assist: 1. In the Application Settings section of the Interplay Administrator window, click the Application Database Settings icon. 2. Click the Application Defaults tab. 3. Select the Enable Audio Mixing Defaults option so that a green check mark is displayed. 4. For each track that you want to enable, click the corresponding button, so that the button has a green icon. 5.
Application Database Settings View 6. Click Apply. Sending a Source to Playback in Interplay Assist The target settings for Send to Playback depend on the folder in which a loaded shotlist exists. The following sections describe how Interplay Assist uses target settings when sending a source to playback. Settings in the Interplay Administrator You set the target audio and video resolution for a folder in the Interplay Administrator.
Application Database Settings View If a shotlist is not open, the send to playback operation uses the target resolution that is set at the database root. If this resolution is not what you want to use for the source, you need to create or open a shotlist in a folder that has the desired settings.
Application Database Settings View 3. Click the Application Defaults tab. 4. Select the database (AvidWG). 5. For the Shotlist Start Timecode option, enter the timecode in the format HH:MM:SS. You cannot enter a default starting frame. 6. For Interplay Assist, specify the Default NTSC Shotlist Format as Drop Frame or Non-Drop Frame. 7. Click Apply.
Application Database Settings View Configuring the Frame Locators Display The Frame Locators tab in the Object Inspector displays information about locators associated with an Avid asset. Administrators and users can configure which attributes (as columns) are displayed in the Frame Locators tab. Administrators can select a default set of columns in the Interplay Administrator, and users can change the default settings in Interplay Access.
Setting Instinct/Assist User Options 3. Click the View Settings tab. 4. In the Frame Locators View section, select “Use local column configuration.” 5. Select the columns you want to display, or deselect the columns you do not want to display, then click OK. 6. Refresh Interplay Access (select View > Refresh or perform an action).
Setting Instinct/Assist User Options To change the Instinct/Assist User settings: 1. In the Application Settings section of the Interplay Administrator window, click the Instinct/Assist User Settings icon. 2. In the Users tree on the left, select a group of users or an individual user. The settings for the selected user or user group area are displayed in the pane on the right. 3. Do one of the following: t Select an option from the drop-down list or by clicking an option button.
Setting Instinct/Assist User Options Edit button 4. Select among the following options for each setting: Option Description Inherited The user inherits this setting from the group it is a part of. Yes Grants the user this setting. No Denies the user this setting. If you select Inherited, and then click Apply, the option changes to the inherited setting and the options are grayed out. 5. Click Apply. A notification box tells you whether or not the changes have been successfully applied.
Setting Instinct/Assist User Options Instinct/Assist User Settings The following table describes options for the Instinct/Assist User Settings. The table includes columns that specify which applications the setting applies to. Setting Instinct Assist Can send to playback x x Can modify column properties x x Access Avid editing applications Description If yes, allows the selected user or group to send material to a playback device.
Setting Instinct/Assist User Options Setting Instinct Assist Can use higher resolutions x Access x Avid editing applications Description If yes, allows the selected user or group to work with a higher quality than the working resolution for video and audio clips if the working resolution is not available. If this option is set to No and the only available resolution is higher than the working resolution, the user sees Media Offline in the Video monitor.
Setting Instinct/Assist User Options Setting Can create locators Instinct Assist x Access Avid editing applications Description x x If yes, allows the selected user or group to create locators. If no, a user of an Avid editing application can still create locators for an asset, but can check in only the asset, not the locator metadata (an error message is displayed). In most cases, if you want a user to create locators, select "yes" for both "Can create locators" and "Can modify locators.
Setting Instinct/Assist User Options Setting Instinct Assist Can create restrictions Access x Avid editing applications Description If yes, allows the selected user or group to mark a section of a clip with a restriction locator. In most cases, if you want a user to create restrictions, select “yes” for both “Can create restrictions” and “Can modify restrictions.” Adding text is considered modifying a restriction. Administrators and owners have this right set by default.
Pro Tools Plug-Ins Settings Pro Tools Plug-Ins Settings You can use Interplay Pro Tools Plug-ins to pass audio files back and forth between Avid video editing systems and Pro Tools audio editing and mixing systems. The following topics include information for installing and configuring the plug-ins. For details on using these plug-ins, see the Avid Interplay Best Practices guide.
Pro Tools Plug-Ins Settings If the database icon has a red X, you are not connected. Click the database icon to connect. The database icon shows a green check mark when you are connected. For more information, see “Viewing General Role Assignments” on page 125. The following illustration shows the Pro Tools Import Settings view. In this example, the settings are configured for the entire database AvidWG. You can also select an individual folder and set specific values for that folder and its subfolders.
Pro Tools Plug-Ins Settings Configuring the Pro Tools Export Plug-In The settings that you configure in the Pro Tools Export plug-in are used by an Avid editing application when an editor performs an audio export. You can select export settings for the entire database or for particular folders. All files and subfolders in the parent folder inherit the settings of the parent folder.
Pro Tools Plug-Ins Settings 3. Select options as described in the following table. Category Option Description Video Details Transcode Video Resolution The Avid editing application uses this value to perform a video mixdown when you select the Video Mixdown option for a “Check In to Interplay for Pro Tools” operation. The application might also use the value when you perform a “link to existing media” export. For more information, see the Avid Interplay Best Practices.
7 Avid Interplay Services The Avid Interplay Services settings include the Workgroup Properties and Service Configuration views, which are identical to parts of the Avid Service Framework. For example, the following illustration shows the Service Configuration view examining the Avid Interplay Media Indexer settings for a computer in the Interplay workgroup.
n Avid Workgroup Properties and Avid Service Configuration are also available from the Interplay Access View menu.
8 Troubleshooting The following topics provide information for troubleshooting problems with the Avid Interplay Engine server: • Troubleshooting Login Problems • Troubleshooting Client Connection Problems • Optimizing Avid Interplay Performance • Troubleshooting Firewalls and Avid Interplay • Troubleshooting the Server Execution User Account • Shutting Down or Locking the Server Process Troubleshooting Login Problems If you are not able to log in to the Interplay Administrator even when you are
Troubleshooting Client Connection Problems 5. In the Registry Editor, double-click CMS, type a valid entry, and click OK. 6. Unlock the server. Troubleshooting Client Connection Problems This topic provides suggestions for settings to check if a client system is not connecting properly. Network Configuration • Check the TCP/IP connection by typing ping in the Command Prompt on the client. Server Settings • Check if there is a user account for the user.
Troubleshooting Firewalls and Avid Interplay Most installations should run the Avid Interplay Engine on a dedicated machine. If you are relying on the server machine to perform other duties as well, you might have performance issues. For example, some virus scanners can lock files on a server, and the Avid Interplay Engine waits until the file is unlocked before it can be moved, renamed, deleted, and so on. • Check the speed of the LAN between the Avid Interplay Engine and the shared storage server.
Troubleshooting the Server Execution User Account Solution Usually these personal firewalls can be configured to allow all network traffic for specific applications. This should be done for Avid Interplay locally or for Internet access depending on which servers Avid Interplay should connect to. For information about ports used by Avid Interplay, see “Required TCP/IP Ports” on page 254 and “Interplay Port Usage” in the Avid Interplay Software Installation and Configuration Guide.
Troubleshooting the Server Execution User Account You have the following options for creating the Server Execution User: • If your Interplay system is joined to a Windows domain, you can create a domain user (for example, “IPEngine”). The Interplay Engine installer will associate the appropriate permissions with the account.
Troubleshooting the Server Execution User Account For security reasons, do not use the Interplay Engine server operating system Administrator account. Create a unique account that you use only as the Server Execution User. For example, you can create an administrative account called “IPEngine.” Avoiding the word Administrator can help indicate that this account is not used for normal administrative tasks. n The Server Execution User account is different from the Interplay Administrator account.
Troubleshooting the Server Execution User Account See the Avid Interplay ReadMe for more information about upgrading and troubleshooting a cluster system. Re-creating the Server Execution User If you need to re-create the Server Execution User, use the NXNServerUser.exe tool. To re-create the Server Execution User account: 1. Run the tool NxNServerUser.exe on the Avid Interplay Engine server. The tool is located in the following directory on the Avid Interplay Server: Installers\AssetMgr\Tools\NxNServerU
Shutting Down or Locking the Server Process - (64-bit OS) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Avid Technology\Workgroup\Avid Workgroup Server\ExecutionSettings - (Cluster Only) Avid Interplay Engine Monitor: The Avid Interplay Engine Monitor Service runs under the specified account. You can verify that the new user has been set in the service control panel. - (Cluster Only): Cluster Service: The Windows Cluster Service runs under the specified account.
9 Configuring Interplay for a Split Database An Interplay database includes a metadata database and a file repository (for file assets). If you do not have adequate local storage for your Interplay database, you can configure (or “split”) the Interplay database so that the metadata database remains on the Interplay Engine server and the file repository resides on an Avid shared storage workspace.
Understanding a Split Database If the Interplay Engine server does not have adequate local storage for your Interplay database, you can configure the Interplay Engine to store only the metadata database on the Interplay Engine. All other database files and folders can be stored on an Avid shared-storage workspace. This configuration is called a split database.
Supported Configurations You can configure your system to store the file repository on shared storage. However, for performance and reliability reasons, Avid requires that the metadata database be stored on the server running the Interplay Engine. If the metadata database is stored on an external file server, network problems or unavailability of the shared storage server causes the Interplay Engine to lock the databases because it cannot write changes persistently.
Preparing for a Split Database Supported Configurations for the Interplay Engine (Continued) Metadata Location File Repository Location Supported Comments Dedicated file server Interplay Engine server No Not supported. Metadata database must be on Interplay Engine server. Preparing for a Split Database To split the database, you need to prepare the Avid ISIS or Avid Unity MediaNetwork workspace.
Splitting a Database for New Interplay Installations Splitting a Database for New Interplay Installations To split the database for new Interplay installations: 1. Prepare the shared storage workspace, as described in “Preparing for a Split Database” on page 226. 2. Install the Interplay Engine. During the installation process, accept the default share on the Interplay Server as the database location. 3. Edit the workgroup.
Splitting a Database for New Interplay Installations If an error message tells you that the server is not configured to accept the UNC path, make sure the workgroup.xml file is correctly edited to include the shared storage workspace (see “Configuring the workgroup.xml File” on page 233). 8. Click the Menu button. 9. In the Database section of the Interplay Administrator window, click the Create Database icon. The Create Database view opens.
Splitting a Database for Existing Interplay Installations By default, the _Backup folder is now located on the shared storage workspace. To avoid filling up the workspace with backups, select Custom and specify the UNC path for a different external file server. Make sure the Server Execution User has read/write access to this external file server. Splitting a Database for Existing Interplay Installations In some situations, you might need to split the database after you have created it.
Splitting a Database for Existing Interplay Installations 3. On the Interplay Engine server, edit the workgroup.xml file to include the path for the new folder on the shared storage workspace (see “Configuring the workgroup.xml File” on page 233). 4. Lock the database to make sure that no user can access it: a. In the Database section of the Interplay Administrator window, click Lock/Unlock Databases. b. Select the database in the Unlocked Databases list. c. Click Lock Database.
Splitting a Database for Existing Interplay Installations 10. Navigate to the folder \\SharedStorageServer\WorkspaceName\AvidWG and open the FolderLocations.xml file. 11. Make sure the file includes the correct path for the _Database directory. It should include the line \\IEServer\WG_Database$\AvidWG\_Database For IEServer, substitute the network name for the Interplay Engine server. This path points to the metadata database on the Avid Interplay Engine. If the FolderLocations.
Splitting a Database for Existing Interplay Installations Add the file location information as follows: \\IEServer\WG_Database$\AvidWG\_Database For IEServer, substitute the network name for the Interplay Engine server. Be sure to use a UNC path. The Interplay Engine effectively maps it to a local path if possible. c Make sure to type this information accurately. Errors in the file can prevent you from activating the database.
Splitting a Database for Existing Interplay Installations By default, the _Backup folder is now located on the shared storage workspace. To avoid filling up the workspace with backups, select Custom and specify the UNC path for a different external file server. Make sure the Server Execution User has read/write access to this external file server. 15.
Splitting a Database for Existing Interplay Installations If you move the file repository to a different location, this location must be published in this file as well. For example: PAGE 235Reuniting a Split Database Database root folder Reuniting a Split Database An Interplay configuration might include a split database (see “Understanding a Split Database” on page 223). This topic provides information about reuniting a split database.
Reuniting a Split Database The following illustration shows all database files located in the same AvidWG folder on the Interplay Engine server.
Reuniting a Split Database c In a correctly split database, the AvidWG folder on the Interplay Engine should contain only the _Database folder. If the AvidWG folder on shared storage includes a _Database folder, do not copy this folder to the Interplay Engine. Rename this folder _Database_UNUSED or something similar before copying the other content to the Interplay Engine.
Reuniting a Split Database Follow one of these procedures to reunite a split database: • If the _InternalData folder is already located on the Interplay Engine, see “Reuniting a Split Database (AvidWG Only)” on page 238. • If the _InternalData folder is located on a shared storage workspace, or split between the Interplay Engine and shared storage, see “Reuniting a Split Database (AvidWG and _InternalData)” on page 241.
Reuniting a Split Database The database name no longer appears in the Databases list. 4. If you do not have a complete Interplay database backup available, manually create an archive backup of the database from both database locations: - \\SharedStorageServer\WorkspaceName\AvidWG - \\IEServer\WG_Database$\AvidWG By default, this folder is D:\Workgroup_Databases\AvidWG (non-cluster system) S:\Workgroup_Databases\AvidWG (cluster system) 5. Copy the necessary files and folders from \\SharedStorageServer\W
Reuniting a Split Database The following table lists the files and folders that you need to copy. These files and folders are illustrated in “Reuniting a Split Database” on page 235. Copy from \\SharedStorageServer\WorkspaceName\AvidWG to \\IEServer\WG_Database$\AvidWG _Backup folder _Buckets folder _CheckIn folder _Handover folder _Import folder _Master folder _PropertyHandover folder _PropertyStore folder _AvidWG.nif Aliasconfig.xml AvidWG.pro FolderLocations.
Reuniting a Split Database 8. Activate the database: a. In the Interplay Administrator, click Manage Databases. b. In the “Database (.pro) file to activate” text box, type the full UNC path to the .pro file, which now resides on the Interplay Engine server. For example: \\IEServer\WG_Database$\AvidWG\AvidWG.pro. c. Make sure “Load Database on Activation” is selected, and click Activate. If the database is activated, its name is displayed in the Databases list. The database is automatically unlocked.
Reuniting a Split Database 3. Deactivate the database: a. In the Database section of the Interplay Administrator window, click Manage Databases. b. Select the database name in the Databases list. c. Click Deactivate. The database name no longer appears in the Databases list. 4. In the Server Settings view of the Interplay Administrator, edith the path for the “Root folder for data” to match the path for the “Root folder for database.” This location is used if you create a new database. 5.
Reuniting a Split Database Copy from \\SharedStorageServer\WorkspaceName\AvidWG to \\IEServer\WG_Database$\AvidWG _Backup folder _Buckets folder _CheckIn folder _Handover folder _Import folder _Master folder _PropertyHandover folder _PropertyStore folder _AvidWG.nif Aliasconfig.xml AvidWG.pro FolderLocations.xml c In a correctly split database, the AvidWG folder on the Interplay Engine should contain only the _Database folder.
Reuniting a Split Database Copy from \\SharedStorageServer\WorkspaceName\_InternalData to \\IEServer\WG_Database$\_InternalData _Backup folder _Buckets folder _CheckIn folder _Handover folder _Import folder _Master folder _PropertyHandover folder _PropertyStore folder _AvidWG.nif Aliasconfig.xml AvidWG.pro FolderLocations.xml c If the _InternalData folder on shared storage includes a _Database folder, do not copy this folder to the Interplay Engine.
Reuniting a Split Database Check the UNC paths for RecentProject1 and RecentProject2. Both paths should show the Interplay Engine server, as shown in the following illustration. 13. Start the Interplay Engine services: - On a cluster system, bring the Avid Workgroup Engine Monitor resource (not the resource group) online. - On a non-cluster system, start the services Avid Workgroup TCP COM Bridge and the service Avid Workgroup Server Browser. 14. Activate the database: a.
Reuniting a Split Database c. Lock and unlock the database. d. After reconnecting to the database with Interplay Access, check if the file is still in the database. 17. If the test is successful, delete or rename the folder \\SharedStorageServer\WorkspaceName\AvidWG.
A Installed Components and Services The following topics provide information about components and services that are installed as part of the Interplay Administrator: • Avid Interplay Engine Directory: Folders and Files • Required TCP/IP Ports • Avid Interplay Engine Servers and Services Avid Interplay Engine Directory: Folders and Files The following components are installed in the Avid Interplay Engine directory. By default, this directory is created during installation as C:\Program Files\Avid\Avid
Avid Interplay Engine Directory: Folders and Files File Path (C:\Program Files\Avid\Avid Interplay Engine) Description Apache\logs\error.log The central Apache web server log file that contains important messages from the Apache process, especially warnings and errors. Apache\logs\access.log The central Apache web server access log file. Only created if you enable this in Apache's configuration (httpd.conf). Apache\bin\Machines\[MACHINENAM Contains preview server and generator E]\Apache.log errors.
Avid Interplay Engine Directory: Folders and Files • The request method (GET or POST), the request URI and any request parameters; • The HTTP status codes returned to the client. The returned status codes are the standard HTTP codes as described in RFC 2616 available under http://www.ietf.org/rfc/rfc2616.txt. Some of the important values are: n • 200 OK: The request has succeeded. • 403 Forbidden: The server refuses to perform the request.
Avid Interplay Engine Directory: Folders and Files File Path (C:\Program Files\Avid\Avid Interplay Engine) Data\Apache\conf\workgroup.xml Description This file contains settings for the Avid Interplay Apache modules. The settings in this file are used, for example, by the filetransfer and the preview server modules. The file transfer section contains items such as a list of UNC paths to which the Avid Interplay HTTP server can browse.
Avid Interplay Engine Directory: Folders and Files In Interplay version 1.6 and later, the Interplay Engine compresses and archives log files older than 7 days. The log compression process runs during project backup. For more information see “Restoring Archived Log Files” on page 58. AvDeletes.log The AvDeletes.
Avid Interplay Engine Directory: Folders and Files AvMetaDataDelete.log The AvMetaDataDelete.
Avid Interplay Engine Directory: Folders and Files • Mime type (master clip, sequence, and so on), display name, object handle, and source and target path of the moved objects • If the objects are sequences or subclips, the deleted and created proxies and references The following example shows these items. AvMoveEx.log q w e r t Fri May 29 11:02:45 2009] User 'airspeed' on host 'muc-ifsputnik' moving masterclip 'Flash 1.
Required TCP/IP Ports File Path (C:\Program Files\Avid\Avid Interplay Engine) Description Server\Machines\[COMPUTER NAME]\MachineConfig.ini This file is generated by the Avid Interplay Engine Server. It contains information about the versions of the dll's loaded by the server. Server\Config\Config.xml This file contains the current configuration settings for the Avid Interplay Engine events, such as whenever the server runs out of disk space, emails can be sent to the administrator.
Avid Interplay Engine Servers and Services Two servers are installed on the Interplay Engine: • The Avid Interplay Engine Server is the central process where all assets and asset meta-information are managed. See “Avid Interplay Engine Server” on page 255. • The Avid Workgroup HTTP Server is a module for the Apache server that allows clients to connect to the Avid Interplay Engine Server using a HTTP protocol.
Avid Interplay Engine Servers and Services Processes The process running is usually listed as NxNServer.exe or NXNSer~3.exe. This process is automatically launched at startup (machine boot) from the Avid Workgroup Server Browser Service. If, however, it is not running at any time and clients try to access it, it is automatically launched. The Interplay Engine always runs under the user specified in the DCOMConfig Settings.
Avid Interplay Engine Servers and Services n The Avid Interplay HTTP Server uses the Apache modules NxNworkgroupFileTransferService.nsm and NxNworkgroupInternetBridge.nsm. Windows Services See “Avid Workgroup Preview Server Service” on page 257. Requirements See “Avid Workgroup Preview Server Service” on page 257.
Avid Interplay Engine Servers and Services On both the Preview Server and on the local machine, cache directories keep the generated previews. • On the Preview Server: in the directory you specified during installation, by default \\IEServer\\WG_Database$\PreviewServer\Cache. • On the local machine: C:\Documents and Settings\User\Local Settings\Application Data\Avid\Workgroup\Cache\Preview. The server is implemented as a module for Apache.
Avid Interplay Engine Servers and Services c - (64-bit OS) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Avid Technology\Workgroup\Avid Workgroup Server\ExecutionUser - (64-bit OS) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Avid Technology\Workgroup\Avid Workgroup Server\ExecutionSettings Change the impersonation settings for the Avid Interplay Preview Server with the NXNServerUser.exe tool only. See “Troubleshooting the Server Execution User Account” on page 218.
Avid Interplay Engine Servers and Services Description of Preview Generation Settings in workgroup.xml • CacheRoot: Path where previews and thumbnails generated by the preview server are stored. This location is used by the preview server to create a cache of converted images. The preview server can reuse those images for subsequent requests from any client.
Avid Interplay Engine Servers and Services Connectivity The Avid Workgroup TCP/COM Bridge listens to port 8318. Processes The process running is usually NXNTCP~1.exe from NXNTCPCOMBridge.exe. Windows Services The service “Avid Workgroup TCP COM Bridge” is automatically started at system startup and should be running all the time. Requirements • The Avid Workgroup Server Browser must run on the same machine as the Avid Interplay Engine Server.
Avid Interplay Engine Servers and Services Windows Services The Avid Workgroup VSS service is automatically started at system startup and should be running all the time. This service always runs under the local system account. The Avid Workgroup VSS service requires that the Windows Volume Shadow Copy service is also running. The Windows Volume Shadow Copy service is installed by default and started automatically.
Avid Interplay Engine Servers and Services Example 2: COM Failure Avid Workgroup Engine Monitor Event ID 42: Failed to connect Workgroup Engine with DCOM 'Error 800706bb happened 8 times within the last 14981 msec' Avid Workgroup Engine Monitor Event ID 31: Thorough check failed: Result code: 0x800706be Avid Workgroup Engine Monitor Event ID 33: Monitoring thread terminated Processes The process running is usually listed as IEMonitorService.exe or IEMONI~1.EXE.
B Interplay Engine Configuration Files The following topics provide information for configuration that you might need to do only under certain circumstances, such as troubleshooting: • Configuring the Server Event Manager • Configuring Client Access • Setting the Filetransfer Server If you are moving the file repository to a shared-storage workspace, you need to edit the workgroup.xml file. See “Configuring the workgroup.xml File” on page 233.
Configuring the Server Event Manager The configuration file is an XML file that has the following format: Value of Parameter ... Value of Parameter ... Value of Parameter ...
Configuring the Server Event Manager The blocks are used to specify the behavior of an action. It is also possible to identify a parameter by its “Name” attribute. Parameters are identified by their “Name” attributes. Whenever the server performs an action, it searches the parameters from the inside out, which means it searches the parameter block inside the block first and then inside the block. This allows you to specify a parameter for all events.
Configuring the Server Event Manager SendMail The SendMail action is configured with the following XML block: SERVERMACHINE administrator@mydomain.com, info@mydomain.com ServerExecutionUser@mydomain.com 123.123.123.
Configuring the Server Event Manager Supported Events in Config.xml The following sections describe the events that are currently supported in Avid Interplay and that can be configured in Config.xml as events to which the Avid Interplay Engine should react.
Configuring the Server Event Manager The LogEvent is configured in the Config.xml with the following XML block: To send an e-mail when a “LogEvent” event is triggered, use the “SendMail” action. See also “LogWatch.xml” on page 271. ClusterResourceFailure Event The “ClusterResourceFailure” event is triggered only in a failover cluster setup. It is sent whenever a problem inside the cluster is detected.
Configuring the Server Event Manager Server Event Configuration Example The following is an example of the configuration of a server to send e-mails whenever the backup fails, or the free space on a server disk reaches one of the limits set, in this case 30, 100, or 500 MB: 30 100 500
Configuring the Server Event Manager 123.123.123.123 Here is an example of an e-mail sent by the Event Manager: 11/23/1999 12:09:14 [WGServer] INFO: This is a message sent by the Event Manager. LogWatch.xml Log event notifications are configured in LogWatch.xml, located in the Avid Interplay Engine installation directory: C:\Program Files\Avid\Avid Interplay Engine\Data\Server\Config. Edit this file to assign actions for different log events.
Configuring the Server Event Manager ID Severity -100 [WARN] (warnings like “loading took more than 3 sec”) 0 [ERROR] (normal errors, like “file couldn't be imported because it exists already”) 100 [FATAL] (Recoverable critical Errors, like “couldn't save database - disk full”) 200 Critical (non-recoverable errors, such as crashes) Sending E-mail Notifications from LogWatch.xml To send e-mail notification on any error with a specific severity level: t Add a mapping entry to LogWatch.
Configuring Client Access The message ID is the last number in brackets before the actual message string in the log file. The message ID of the entry below is 0x00004678. Note that the log file displays hexadecimal ids. You need to convert the numbers to decimal format before adding to the message mapping. [Thu Sep 16 17:27:43 2004] [FATAL] [.\NxNDbServer.
Configuring Client Access The “name” attribute specifies the name of the database. This name must be the same as the name of the database configured in the Active Database List through the Avid Interplay Administrator. If a database is not in the Active Database List, it cannot be made visible by specifying its name in token either. You can also use the “*” as a wildcard character representing all databases in the Active Database List.
Configuring Client Access Example 2: PAGE 276Configuring Client Access Example 4: PAGE 277Setting the Filetransfer Server Setting the Filetransfer Server Additional configuration might be required when the Interplay Server is running inside of a network configured using NAT. In this case, the IP returned by the Avid Interplay Engine is the internal address and not the external address needed by the client. The following change in the workgroup.xml configuration file tells the client to connect to the file transfer server via its name instead of address.
C Valid and Invalid Characters in Avid Interplay The following table lists the valid and invalid characters (also known as special characters) for Avid Interplay. Allowed Avid asset names File asset names Not Allowed Characters: / \ | All characters allowed Characters: * ? : / \ " < > | for files in Windows Names ending with a dot Names used as DOS devices (LPT1, com1, .., .,, for example) Property names (metadata field names) Characters: / \ | Video ID metadata field Spaces, or characters / \ : * ?
D System Metadata Properties Metadata is textual data you can use to identify and describe the creation, contents, and disposition of the clip or shotlist you are logging. Avid Interplay comes with an extensive list of system metadata. The administrator determines some of the metadata properties that can be viewed in Interplay Access as headings in the Content View and Object Inspector, and also used in Interplay searches. Some metadata properties are always available and cannot be disabled.
Search Values and Hints on Searching in Interplay Heading Description All Custom All custom properties defined in the Property Layout of the Interplay Administrator. Access Rights The access level or user role assigned to a particular folder or asset. The column displays an icon that represents the type of access. AFD Value for Active Format Description (AFD) in an ancillary data track. Media Composer v6.1 and later allows the creation of AFD values, which are supported in Interplay v2.7 and later.
Heading Description Search Values and Hints on Searching in Interplay AuxInkDur Length of the clip, expressed in the auxiliary ink number. Type numbers only in the four colon-separated entry fields displayed. AuxInkEdge Type of edgecode used in the auxiliary ink number. AuxInkEnd Ending auxiliary ink number for the clip. Type numbers only in the four colon-separated entry fields displayed. AuxInkFilm Film gauge for the auxiliary ink number.
Heading Search Values and Hints on Searching in Interplay Description Current Video Resolution Last resolution checked in with the asset. Current/Last User Last user that checked the asset in or out. Data Format Data format AAF or OMF. Database The Interplay database that contains the asset. Date Deleted (Orphan Clips folder only) Displays the date and time the last links was deleted. Deleted By (Orphan Clips folder only) displays the user name of the person who deleted the last link.
Search Values and Hints on Searching in Interplay Heading Description DRM Digital Rights Management property. Has Depending on the search flags, this search the special operators Has DRM and Does can retrieve links to the assets, assets or not have DRM. links and assets which have at least one DRM protected media somewhere in the structure. Searches for DRM should return all of the sequences, subclips, rendered effects, and so on that use a restricted master clip.
Search Values and Hints on Searching in Interplay Heading Description Initial Checkin Date Date that the asset was first checked in. Select a time range and a particular date (for example, 12/4/04 or 12/4/2004) or a time period from the pop-up menu. Click the calendar to get clickable calendar. InkDur Length of the clip, expressed in ink number. Used for 24p projects, 25p projects, and matchback projects only. You cannot modify this number.
Search Values and Hints on Searching in Interplay Heading Description KNStart Starting key number for the clip. Used for Select an operator and then type numbers 24p projects, 25p projects, and matchback only in the four colon-separated entry projects only. fields displayed. Labroll Labroll containing the clip. Last Checkin Date Date when the asset was last checked in. LUT File name of the color look-up table used for the series of clips or frames.
Search Values and Hints on Searching in Interplay Heading Description Modified Date When the asset was last modified (from the bin). Select a time range and a particular date (for example, 12/4/04 or 12/4/2004) or a time period from the pop-up menu. Click the calendar to get clickable calendar. Name The name of the asset. Type text (not case sensitive; spaces permitted). Original Bin Name of the bin where the media for this asset was originally captured.
Search Values and Hints on Searching in Interplay Heading Description Playable in Access (Interplay Stream Server v2.3 and earlier) A green triangle in this column indicates that a clip is can be played in the Interplay Access Monitor. Also applies to subclips or shotlists created from playable clips. Pullin Telecine pulldown of the first frame of the clip (pulldown phase). Pullin can have the values A, B, X (matchback only), C, or D. Used for NTSC 24p projects and matchback projects only.
Search Values and Hints on Searching in Interplay Heading Description S3D Channel Displays which channel this master clip will deliver into the stereoscopic clip. (Left eye, right eye and monoscopic are full frame channels, while Side by Side and Over/Under are frame compatible channels.) Criterion for Extended Search in Access Left Eye: Indicates that the contents of this clip are to be used as the Left eye. Right Eye: Indicates that the contents of this clip are to be used as the Right eye.
Search Values and Hints on Searching in Interplay Heading Description S3D Eye Ordering Only available if the media is in a frame Criterion for Extended Search in Access compatible format with the S3D Channel set to either Over/Under or Side by Side. Specifies which half of the image the eye is displayed. Left-Right: • For Side by Side format, the Left eye is on the left, the Right eye is on the right. • For Over/Under format, the Left eye is in the top half of the image, Right eye is in the bottom.
Search Values and Hints on Searching in Interplay Heading Description S3D Inversion Displays if and how the contents of this Criterion for Extended Search in Access clip should be inverted before being used. This is useful when beam-splitter rigs are used during filming, and a mirror is used to create the image for one of the eyes. In this case, one of the eyes will be inverted so it needs to be corrected None: Leaves the image as is. Horizontal: Inverts the image horizontally.
Heading Description Search Values and Hints on Searching in Interplay Scene Scene number of the clip. Type text. ShootDate Date the footage was shot. Slip Number and direction of perfs for subclips (audio clips only). SoundTC Timecode for audio. Soundroll Sound roll this clip came from. Used for 24p projects, 25p projects, and matchback projects only. Start Timecode of the clip’s head frame. Streamable Masterclips (Search only) Finds master clips that were are published, are not published.
Search Values and Hints on Searching in Interplay Heading Description TC30NP 30-fps timecode with no pulldown (frames 00 through 29). Select an operator and then type numbers only in the four colon-separated entry fields displayed. TC60 60-fps timecode. Used for HD projects. Select an operator and then type numbers only in the four colon-separated entry fields displayed. Text Search only Combination of Name, Tape, User Attributes, Comments, and Annotations attributes.
Search Values and Hints on Searching in Interplay Heading Description VFX Frame-counting field for visual effects. The format is the following: a descriptor of up to 32 alphanumeric characters, followed by a hyphen (-), followed by a six-digit frame count, for example, FXChildDocu-023657. VFX Reel Source reel identification for the FX shot. Video ID Lists the identification number created to track a clip in a broadcast environment. This ID is equivalent to the Tape ID in Avid editors.
E Server Error Codes The following table lists the error codes and the textual expressions that the Interplay Engine can return. 0x52e Logon failure: unknown user name or bad password. 0x525 The specified user does not exist. 0x8000ffff Failed to open the database (catastrophic failure). Contact your administrator. May require Avid support. 8007000e out of memory 80070005 Failed to open project: Access denied. The project is deactivated.
89990031 invalid name 89990032 invalid handle 89990033 invalid destination 89990034 invalid property 89990035 invalid parameter 89990036 invalid filename 89990037 invalid object 89990038 invalid hostname 89990039 invalid macro string or tool installation file 89990040 object not found 89990041 parent not found 89990042 the template for the object could not be found 89990043 titerator is invalid for this iteration-capable command 89990050 property not found 89990051 property not
89990072 root object has no parent 89990073 invalid operation for root object 89990080 cannot open file 89990081 cannot write to file 89990082 cannot read from file 89990083 the file does not exist 89990084 file system operation failed 89990085 access to file denied 89990086 sharing violation 89990087 corrupt file 89990090 cannot set mount point 89990091 object not mounted into file system 89990092 cannot create directory 89990093 cannot move directory or file 89990094 cannot co
89990111 workspace already initialized 89990120 already connected to a server 89990121 not connected to a server 89990122 cannot connect to server 89990123 cannot disconnect from server 89990124 The database share on the server is not accessible. Please contact your administrator.
89990162 the dongle is not available on the server 89990163 the registration key is invalid 89990164 the server and client versions are not compatible 89990165 the server could not be instantiated (is the server installed on this machine?) 89990166 the server is locked by the Administrator 89990167 the server is low on virtual memory 89990168 the server is low on disk space 89990169 the server is out of disk space 89990170 the specified search expression is invalid 89990171 the database i
89990201 object not found 89990202 object already exists 89990220 CopyFile command failed 89990221 file already exists 89990222 file does not exist 89990224 cookie file does not exist 89990225 can not create cookie file 89990226 can not read cookie file 89990227 cookie file is corrupt 89990228 found cookie does not match wanted cookie 89990230 object must support INxNPersistDatabase 89990231 object must support INxNPersistDatabaseObj 89990232 object must support INxNVersionControlPr
89990261 version control is disabled for this object 89990262 Connect to version control server failed 89990280 Copying file from server location to local destination failed 89990290 archive is corrupted 89990291 file is not of correct type 89990292 Disabling version creation for abstract assets is not supported 89990300 the user 'UserManagement' is not allowed 89990301 user rights do not allow this operation 89990302 user/user group exists already 89990303 command exists already 8999030
89990321 The operation cannot be performed on a system defined role 89990322 The operation cannot be performed on a system defined action 89990323 The action is not assigned to the role 89990324 The system id's for roles or actions are out - impossible to create new system actions or roles 89990326 The operation is not permitted on the user administrator 89990327 The initialization of the authorization subsystem failed - read message for more information 89990340 The initialization of the user
89990369 could not connect to the LDAP server 8999036a The operation failed because the object is protected by a reservation 8999036b CCS Connection failed 8999036c CCS is corrupt (for example, GUID missing) 8999036d The authorization config file is missing 8999036e The CCS does not have the same version as the server of the database 89990370 An LDAP search enum failed 89990371 Structural changes are not allowed on that object 89990372 No Children can be added to this folder or moved out of
89990615 use proxy 89990620 bad request 89990621 unauthorized 89990622 payment required 89990623 forbidden 89990624 not found 89990625 method not allowed 89990626 not acceptable 89990627 proxy authentication required 89990628 request timeout 89990629 conflict 8999062a gone 8999062b length required 8999062c precondition failed 8999062d request entity too large 8999062e request URI too long 8999062f unsupported media type 89990630 internal server error 89990631 not impleme
89990704 failed to apply database journal transaction 89990705 failed to apply database journal operation 89990706 error opening database journal 89990707 error reading from database journal 89990708 error writing to database journal 89990709 database journal file error 89990800 SQL error 89990801 SQL error, more info available 89990802 invalid SQL configuration 89990900 the sender of the message does not exist 89990901 the recipient of the message does not exist 89990902 The sender m
89990a07 An image could not be loaded or saved because the license for the LZW algorithm is not available. 89990a08 The image could not be read or stored because the file or image has an invalid format.
89990b0e A search request sent to the LDAP server could not dereference an alias because of missing access rights, LDAP error: LDAP_ALIAS_DEREF_PROBLEM(0x24) 89990b0f An incorrect authentication method was used when sending a request to the LDAP server, LDAP v: LDAP_INAPPROPRIATE_AUTH(0x30) 89990b10 The credentials sent to the LDAP server are invalid, LDAP error: LDAP_INVALID_CREDENTIALS(0x31) 89990b11 The request sent to the LDAP server was not completed because of missing access rights, LDAP error:
89990b1f The LDAP operation needs to be performed by multiple LDAP servers, where this operation is not permitted, LDAP error: LDAP_AFFECTS_MULTIPLE_DSAS(0x47) 89990b20 The LDAP server cannot perform the operation because of a virtual list view error, LDAP error: LDAP_VIRTUAL_LIST_VIEW_ERROR(0x4C) 89990b21 The LDAP server encountered an unknown error, LDAP error: LDAP_OTHER(0x50) 89990b22 The LDAP server could not be contacted, LDAP error: LDAP_SERVER_DOWN(0x51) 89990b23 The LDAP client detected an
89990b31 A loop was detected in an LDAP alias or referral, LDAP error: LDAP_CLIENT_LOOP(0x60) 89990b32 An LDAP operation failed because a referral required too many referral hops, LDAP error: LDAP_REFERRAL_LIMIT_EXCEEDED(0x61) 89990b50 The operation failed because the user authentication provider is not enabled 89990b51 The authentication failed because empty passwords are not allowed 89990b52 The CCS was unable to retrieve the users from a user authentication provider 89990b53 The specified user
F Consistency Check Codes The following tables explain the codes reported when you run a Consistency Check: c • Consistency Check Critical Errors • Consistency Check Errors • Consistency Check Warnings The Consistency Check is for support purposes. You should perform this check only if requested by Avid Technical Support.
Consistency Check Errors Code Meaning 7142 repository data corruption 7143 repository data corruption 7144 repository data corruption 11064 user management failed to initialize Consistency Check Errors n If any of the following errors are reported, some problems were found related to the particular object. It is still possible to use your database, but you should contact Avid using the protocol outlined in the “If You Need Help” topic in the front of this manual to resolve the problem.
Consistency Check Errors Code Meaning 7111 unknown property handle 7112 streamed property flag is not set 7113 unknown streamed property name 7114 invalid streamed property 7153 internal object state is invalid 7171 link is invalid 7172 link is invalid 7173 link is invalid 7174 link is invalid 7175 link is invalid 7176 link is invalid 11058 master user is not valid 11059 master user is not valid 11060 master user does not exist 11061 master user is not valid 11062 master us
Consistency Check Warnings Consistency Check Warnings If any of the following warnings are reported, some problems were found, but no action is urgently needed. Code Meaning 7062 file size mismatch 7072 invalid dependency source 7073 invalid dependency source 7074 invalid dependency target 7075 invalid dependency target 7076 incorrect dependency type 7091 pending change problem fixed 23022 invalid entry in the authorization role table.
ABCDEFGHIJKLMNOPQRSTUVWXYZ Index Symbols _Backup directory described 30 _Buckets directory described 30 _Database directory backing up and restoring 33, 33 described 30 _Master directory described 30 _PropertyStore directory backing up and restoring 33, 33 described 30 Numerics 7-Zip for Interplay backups 44 A AAF metadata adding to tape archive 165 Access control for custom properties 145 Accumulated inherited role described 120 Activating database 65 Administrator role described 120 Administrators gro
ABCDEFGHIJKLMNOPQRSTUVWXYZ Avid online support 14 training services 16 Avid assets described 18 Avid Instinct Application Database options 188 setting Application Database options 185, 186 setting user options 202 user options 205 Avid Interplay client-server application 21 optimizing performance 216 Avid Interplay Administrator See Interplay Administrator Avid Interplay Assist Application Database options 188 setting Application Database options 185, 186 setting user options 202 user options 205 Avid Inter
ABCDEFGHIJKLMNOPQRSTUVWXYZ Complete backup described 33, 33 Config.
ABCDEFGHIJKLMNOPQRSTUVWXYZ Event Manager settings 264 Everyone group 117 Exclusive Access for maintenance tools 80 setting and releasing 87 Exiting Interplay Administrator 27 Exporting license 95 Extended search custom properties 150 Index Hardware ID 92 Help opening 26 I Imported Users group 117 Importing LDAP users 107 license 93 users 102 Windows domain users 105 Incremental backup described 33 Inherited rights 120 IN-OUT attribute 283 Installing Pro Tools Import plug-in 209 Instinct/Assist User Setti
ABCDEFGHIJKLMNOPQRSTUVWXYZ configuration files 264 described 17 folders and files 247 optimizing performance 216 ports used 254 servers and services 254 Interplay Media Services Engine registering 155 Interplay Media Services view 160 Interplay Portal viewing 14 Interplay Transfer configuring for remote workgroups 151 Interplay Transfer Settings view 161 Interplay Transfer Status view 161 Interplay Window automatic reservation 195 Interplay workgroup described 17 multiple workgroups 19 InterplayRestore tool
ABCDEFGHIJKLMNOPQRSTUVWXYZ N plug-ins for Interplay 209 User Settings plug-in 212 Property Layout view 136 No Access role described 120 NxNServerLock.exe locking server process 222 moving database with 78 NxNServerShutdown.exe moving database with 78 shutting down server process 222 NxNServerUnlock.exe moving database with 78 NXNServerUser.
ABCDEFGHIJKLMNOPQRSTUVWXYZ S Schedule Backups view 39 Scheduled deletion 175 Searches custom properties 150 Searching remote workgroups 151 Send mail action 266 Server error codes 294 information about 85 locking 87 restarting 91 shutting down 87 unlocking 87 Server Event configuration example 270 Server Event Manager configuring 264 Server Execution User creating 218 described 21 recreating 221 troubleshooting 218 Server folder 253 Server Hostname Settings view 155 Server Information view 85 Server Settin
ABCDEFGHIJKLMNOPQRSTUVWXYZ X User Management view 115 Users adding from Avid Unity 104 adding manually 118 adding to a CCS 102 default 117 deleting 124 disconnecting all 91 importing 102 importing from LDAP 107 importing from Windows domain 105 list of connected 85 management guidelines 134 managing 115 removing from group 124 roles 120 setting attributes for 119 setting passwords for 119 XML files for custom properties 147 V Validate User Tree tool 80 Verify Link Consistency tool 80 VITC (Vertical Inte
Avid Technical Support (USA) Product Information 75 Network Drive Burlington, MA 01803-2756 USA Visit the Online Support Center at www.avid.com/support For company and product information, visit us on the web at www.avid.