® Interplay | Engine and Interplay | Archive Engine Administration Guide Version 3.
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. This product may be protected by one or more U.S. and non-U.S patents. Details are available at www.avid.com/patents. This document is protected under copyright law.
Copyright 1996 Daniel Dardailler. Permission to use, copy, modify, distribute, and sell this software for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Daniel Dardailler not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/). © DevelopMentor This product may include the JCifs library, for which the following notice applies: JCifs © Copyright 2004, The JCIFS Project, is licensed under LGPL (http://jcifs.samba.org/). See the LGPL.txt file in the Third Party Software directory on the installation CD. Avid Interplay contains components licensed from LavanTech.
Contents Using This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Symbols and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 If You Need Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Viewing Help and Documentation on the Interplay Production Portal. . . . . . . . . . . . . . . 13 Interplay Documentation . . . . . . . . .
Performing a Consistency Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Viewing Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Database Information Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Locking and Unlocking Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Users to a Central Configuration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Setting User Authentication Providers and Importing Users . . . . . . . . . . . . . . . . . . . . . 109 Setting Avid ISIS Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Setting Windows Domain Authentication and Importing Users . . . . . . . . . . . . . . . 113 Setting LDAP Authentication and Importing Users. . . . . . . . . . . . . . . . . . . . . .
Configuring the Interplay Streaming Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Interplay Media Services View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Interplay Transfer Status View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Interplay Transfer Settings View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Workgroup Transfer Presets View . . . . . .
Pro Tools Plug-Ins Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Chapter 7 Interplay Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Chapter 8 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Troubleshooting Login Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Appendix B Interplay Engine Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 Configuring the Server Event Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 Config.xml File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 Supported Actions in Config.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 Supported Events in Config.xml . . . . . . . . . .
Symbols and Conventions Using This Guide Congratulations on your purchase of Interplay® | Production, a powerful system for managing media in a shared storage environment. This guide describes how to use Interplay | Administrator, an Interplay client application that provides tools to configure the Interplay | Engine and to manage the database on the server.
If You Need Help Symbol or Convention Meaning or Action > This symbol indicates menu commands (and subcommands) in the order you select them. For example, File > Import means to open the File menu and then select the Import command. This symbol indicates a single-step procedure. Multiple arrows in a list indicate that you perform one of the actions listed.
Viewing Help and Documentation on the Interplay Production Portal Viewing Help and Documentation on the Interplay Production Portal You can quickly access the Interplay Production Help, links to the PDF versions of the Interplay Production guides, and other useful links by viewing the Interplay Production User Information Center on the Interplay Production Portal. The Interplay Production Portal is a Web site that runs on the Interplay Production Engine.
Interplay Documentation Interplay Documentation The following documents describe how to use Interplay Production: • Interplay | Production Best Practices — provides an overview of the major Interplay components, shows sample configuration diagrams, and describes several of the key features, such as setting up a user database and using the Interplay Archive Engine.
Avid Training Services Avid Training Services Avid makes lifelong learning, career advancement, and personal development easy and convenient. Avid understands that the knowledge you need to differentiate yourself is always changing, and Avid continually updates course content and offers new training delivery methods that accommodate your pressured and competitive work environment. For information on courses/schedules, training centers, certifications, courseware, and books, please visit www.avid.
1 Getting Started with the Interplay | Administrator The Interplay Administrator provides database administrators and maintenance engineers with the tools required to configure the 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. c Previous versions of this guide described how to set up a split database. A split database refers to a configuration in which only the metadata database is stored on the Interplay Engine.
Understanding the Interplay Engine and Interplay Workgroups Interplay online database Interplay Archive Engine database For more information about the Interplay Archive Engine, see Interplay Best Practices. 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).
Using the Interplay Administrator Server Execution User The Server Execution User is a Windows operating system user that runs the Interplay Engine processes. You specify the user name and password for the Server Execution User when you install the Interplay Engine on the server. The Server Execution User needs local administrator rights on the operating system for the Interplay Engine server and read/write access to the Avid shared-storage file system.
Starting the Interplay Administrator • Configuring client applications and the workgroup. See “Site Settings” on page 144. • Configuring the Interplay Archive Engine. See “Specifying Archive Settings” on page 172. For more information on archiving, see Interplay Best Practices and the Interplay Media Services Setup and User’s Guide.. • Configuring Application Settings and Interplay Services. See “Application Settings” on page 194 and “Interplay Services” on page 223.
Using the Interplay | Administrator Window 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. The first part of the list shows recent servers, the second part of the list shows servers that were added manually (not on a local area network), and the third part shows servers available on your local area network. t Click the arrow for the server list and select Add Server.
Using the Interplay | Administrator Window Each group contains views for managing components of the 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 Interplay Administrator t Select Documentation Website on Server. The Interplay Production 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 Production Portal” on page 13 Exiting the Interplay Administrator When you are finished using the Interplay Administrator, you should log out or close the application.
2 Database Settings The Database settings allow you to create, configure, and manage the Interplay database.
Interplay Databases, Folders, and Files n To identify the actual folder, open a Command Prompt window and type net share. 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.
Interplay Databases, Folders, and Files This folder contains either the AvidWG or the AvidAM folder. If the server is functioning as the Central Configuration server, the folder also includes the _InternalData folder. The following table describes these folders: Database Description _Internal Data User database: Contains Central Configuration Server information such as users and roles.
Creating and Restoring Database Backups Database Directories and Files (Continued) Directory or File Directory or File Description _PropertyStore The database directory that contains files holding the contents of streamed properties. Streamed properties include metadata about Avid assets, such as head frames and AAF information.
Creating and Restoring Database Backups The following topics provide information about creating and restoring database backups: • “Types of Interplay Administrator Backups” on page 30 • “Recommendations for Backup Configuration” on page 31 • “Scheduling Automatic Database Backups” on page 35 • “Setting the Number of Database Backups to Keep” on page 34 • “Starting a Backup Manually” on page 39 • “Using an Archiving Tool for Backup” on page 39 • “Restoring an Earlier Version of a Database” on p
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. For information on how to restore a database, see “Restoring a Complete Backup or a Fast Backup” on page 43.
Creating and Restoring Database Backups It is extremely important to use the automatic backup process available through the Interplay Administrator instead of just a tape backup for backing up the _Database and _PropertyStore folders. Tape backups can be: • Inconsistent: A tape backup of the _Database folder while the server is running can lead to inconsistent backup files because the server might not have applied all the transactions to the database yet.
Creating and Restoring Database Backups n Prior to Interplay Engine v1.2.4, storing backups on shared storage was not recommended because of the large number of small files included in the backup. However, the backup mechanism included with Interplay Engine v1.2.4 or later significantly reduces the number of files created in the _PropertyStore folder, which reduces the amount of storage required. Alternatively, you can store the backups on an external file server.
Creating and Restoring Database Backups c • Perform a backup of the complete database to offline media. Avid recommends a complete backup to offline media using a professional backup tool. Archive tools such as Robocopy or 7-Zip are useful before doing a major system upgrade. They can be used in place of a professional backup tool. However, performance and stability might suffer. • If you schedule a regular restart of the engine, set it after the regular backup is created.
Creating and Restoring Database Backups In the same example, the Interplay Engine does not check the number of backups again until it performs a Complete backup on Sunday the 15th. On that day, it deletes the 7 oldest backups, leaving 8. The following illustration shows the 7 oldest backups deleted.
Creating and Restoring Database Backups The Backup History section displays incremental and differential backups up to the last successful complete backup. Administrators can use this as a troubleshooting tool to see if the last backup was successful and if not, which backups have failed. It also can be used to view which incremental and differential backups are required for the most recent full restore. This display does not necessarily match the backups stored in the _Backup folder.
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. 3. (Option) In the Backup Information area, change your preferences if necessary.
Creating and Restoring Database Backups “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 Interplay Engine always keeps the last Complete backup and later Fast backups. For more information, see “Recommendations for Backup Configuration” on page 31. 4. (Option) In the Backup Location preference, select Custom to change the default backup location. The custom location must be specified as a UNC path.
Creating and Restoring Database Backups t Select Custom and specify custom backup times. Use the up and down arrows to select the time, and then click Add. Repeat to add more times to perform the backup. Select a time and click Remove to cancel a backup. 11. Click the Apply Changes button. Starting a Backup Manually You can start an Interplay Administrator backup manually, rather than waiting for a scheduled automatic backup or changing the existing backup schedules. To start a backup manually: 1.
Creating and Restoring Database Backups To make a backup copy of the database on a non-cluster system: 1. Open the Interplay Administration tool. 2. Use the following steps to lock the database: a. Click Lock/Unlock Databases. b. Select the database in the Unlocked Databases list. c. Click Lock Database. 3. Click Menu and click Manage Databases. 4. Select the AvidWG database and click Deactivate. Select AvidAM for an Archive Engine. 5. Click Menu and click the Restart Server view. 6.
Creating and Restoring Database Backups 9. Select the Avid Workgroup Engine Monitor resource and take it offline. 10. If you performed the previous step correctly, drive S: should still be accessible within the Windows environment. If it is not available, use the Cluster Administration tool to put drive S: online by clicking on the disk resource within the “Avid Workgroup Server Group” and selecting online. 11. Use a backup tool to make a copy of the following folders and record their location.
Creating and Restoring Database Backups 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.4, the Interplay backup mechanism consolidates the streamed properties files (all files in the _PropertyStore folder) into large “archive” files. These files are written into the _PropertyStore folder of the corresponding backup folder.
Creating and Restoring Database Backups 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. (see “Types of Interplay Administrator Backups” on page 30 for a description of each type of backup). • A Complete backup contains a _Database folder and a _PropertyStore folder. A Complete backup is needed if the complete database needs to be restored, for example, if a hard disk crashes.
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 If you are working with a split database, this location is probably on the shared storage server. For example: \\SharedStorageServer\WorkspaceName\AvidWG\_Backup 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.
Creating and Restoring Database Backups n Split databases are no longer recommended. See “Reuniting a Split Database” on page 233. 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
Creating and Restoring Database Backups n Split databases are no longer recommended. See “Reuniting a Split Database” on page 233. 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.exe /?" for help Enter the Interplay database root or metadata directory: D:\Workgroup_Databases\AvidWG Is this a
Creating and Restoring Database Backups It leaves the database locked and gives you the following message: Database AvidWG is still locked because you need to restore _Master manually, or through your existing tape backup mechanism. When you are done restoring _Master, use the Lock/Unlock Database view in Interplay Administrator to unlock the AvidWG database. This will complete your restore operation.
Creating and Restoring Database Backups 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. Because the current backup mechanism uses archive files, you need this tool to view and work with files in the _PropertyStore backup folder.
Creating and Restoring Database Backups To unpack all streamed properties files: t Type the following and press Enter: backuparchive /U Do not use the file extension when typing the name of the archive file. For example, the following command unpacks all property store files into a temporary folder on the Interplay Engine: backuparchive /U \\docisis\workspace3\AvidWG\_Backup\AvidWG_2008-05-04_01-00\_PropertySt ore\streamed_prop D:\Workgroup_Databases\TempPropertyStore Mak
Creating and Restoring Database Backups n See the Interplay Engine and Interplay Archive Engine Administration Guide for complete information about backing up and restoring. When to Perform a Partial Restore One example of an effective use of a partial restore is if a facility is replacing its Interplay Engine with a new server. This is often a gradual process that takes several days.
Creating and Restoring Database Backups In the example, starting with file 1 and selecting two entries mean that the partial restore will be run from the following files: 1. Test_2013-02-05_16-00 incremental 2. Test_2013-02-06_16-00 incremental Results of a Partial Restore If you perform a full backup, the Interplay Engine renames the original _Database and _PropertyStore folders before the restore procedure, and creates new folders for restored files during the restore procedure.
Creating and Restoring Database Backups In either case, you are asked to choose a backup starting point. Choose a backup to restore from: [1] [2] [3] [4] 04 04 04 24 February February February February 2013 2013 2013 2013 16:39:00 16:42:00 16:44:00 01:00:00 full incremental incremental full Choose an entry ( 1 - 4 ): 3 Backup restore chain 0. Test_2013-02-04_16-39 full 1. Test_2013-02-04_16-42 incremental 2.
Creating and Restoring Database Backups Restoring to F:\Workgroup_Databases\Test\ Beginning restore from F:\Workgroup_Databases\Test\_Backup\Test_2013-02-04_16-42\ This is a incremental backup Copying streamed properties... Opening archive file F:\Workgroup_Databases\Test\_Backup\Test_2013-02-04_16-42\_PropertyStore\s treamed_prop1.bar Extracting file F:\Workgroup_Databases\Test\_PropertyStore\2013-35\1373_StreamedProperty_A AFBinary1073743196-1.prp Verifying that we have all streamed property BAR files...
Creating and Restoring Database Backups To create a metadata-only backup file: 1. In the Database section of the Interplay Administrator window, click the Backups icon. The Backups view opens. 2. In the list on the left side of the view, select the database for which you want to create the backup. The database is named either AvidWG (Interplay Engine) or AvidAM (Interplay Archive Engine). 3. At the bottom of the view, click the “Start Backup Now...” button. 4.
Performing a Consistency Check Performing a Consistency Check The database Consistency Check compares the version of the database or databases on the master directory with the current database file. The Perform Consistency Check view provides a useful tool for checking if all references are correct, seeing if all necessary files are on the disk, and checking other aspects of the database. c The Consistency Check is for support purposes.
Viewing Database Information 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 26. - Root folder for data (Assets): See “Creating an Interplay Database” on page 26. 2.
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. Database Statistics Statistics in this tab provide information about the number of pages in the database, cache usage, and how they relate to each other. These statistics are useful in determining database scalability.
Viewing Database Information • - Successfully deleted media files: The number of media files deleted from shared-storage. Only media files deleted by a scheduled deletion from Orphan Clips are counted, not media files deleted by the interactive part of a deletion. - Size of successfully deleted media files. The cumulative size of the successful deletions in KB, based on information in the Interplay Engine database. This information is not necessarily the most recent information from the Media Indexer.
Locking and Unlocking Databases Object Statistics Statistics on this tab show totals for objects in the database. This information is not updated until you open the view again. • 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.
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 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 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 Do not use a database that requires migration; always migrate a database to a CCS. You cannot administer an unmigrated database. If a database needs migration, the database icon shows a red box with an X and a yellow arrow. The database icon appears in several views in the Interplay Administrator, including the Manage Database Roles view. (Red box with X and yellow arrow) Database needs migration.
Moving a Database to Another Server (Non-Clustered Systems) 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.” The database now has the CCS users and administration properties of the new CCS you have set.
Moving a Database to Another Server (Non-Clustered Systems) c 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 67). If you move a database to another server and also move the CCS, however, this information is preserved.
Moving a Database and Users to Another Server (Non-Clustered Systems) 9. On the target server, rename the existing database folder, for example, rename AvidWG to AvidWG_old. 10. Copy the zipped file to the target server and unzip the file to the Workgroup_Databases folder. Make sure the path on the target server matches the path on the source server. 11. Activate the database by using the Manage Databases view (see “Activating a Deactivated Database” on page 65). 12.
Moving a Database and Users to Another Server (Non-Clustered Systems) 3. Deactivate the database by using the Manage Databases view (see “Deactivating a Database” on page 64). 4. Make sure the database is unloaded from the server by opening the Restart Server view and clicking Restart. 5. Lock the server using the Lock Server view (see “Locking and Unlocking the Server” on page 88). 6. Locate the database folder on the source server. The default path is \\server_name\WG_Database$\AvidWG (or AvidAM for an A
Moving a Database to Another Server (Clustered Systems) 16. Unlock the server using the Lock Server view. 17. Verify that all users are on the system by opening the User Management view and viewing the lists of user groups. 18. Activate the database by using the Manage Databases view (see “Activating a Deactivated Database” on page 65). 19. On an Interplay Access client, log in to the new server and verify that all data is available. If all data is available, the new database is ready for use.
Moving a Database to Another Server (Clustered Systems) All clients are disconnected from the source server. 3. Deactivate the database using the Manage Databases view (see “Deactivating a Database” on page 64). 4. 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.
Moving a Database and Users to Another Server (Clustered Systems) 10. Copy the zipped file to the target server and unzip the file to the Workgroup_Databases folder. Make sure the path on the target server matches the path on the source server. 11. Activate the database by using the Manage Databases view (see “Activating a Deactivated Database” on page 65). 12. On an Interplay Access client, log in to the new server and verify that all data is available.
Moving a Database and Users to Another Server (Clustered Systems) All clients are disconnected from the source server. 3. Deactivate the database using the Manage Databases view (see “Deactivating a Database” on page 64). 4. Lock the server using the Lock Server view (see “Locking and Unlocking the Server” on page 88). 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.
Moving a Database Under Low Disk Space Conditions 10. On the target server, rename the existing database folder, for example, rename AvidWG to AvidWG_old. 11. Open the Interplay Administrator, log on to the target server, and deactivate the database (AvidWG or AvidAM) using the Manage Databases View. 12. Lock the server using the Lock Server view (see “Locking and Unlocking the Server” on page 88). 13. Rename the existing _InternalData folder to _InternalData_old. 14.
Renaming a Database Server (Non-Clustered Systems)” on page 71). In the Server installation directory (by default, C:\Program Files\Avid\Avid Interplay Engine\Server), there are tools provided to solve such problems: c • NxNServerLock.exe • NxNServerUnlock.exe • NxNServerShutdown.exe Before beginning this procedure, be sure to make a backup of the database. See “Creating and Restoring Database Backups” on page 29 for information on running a backup.
Running Database Maintenance Tools To rename a database: 1. In the Database section of the Interplay Administrator window, click the Manage Databases icon. The Manage Databases view opens. 2. Select the database and click the Deactivate Database button to ensure that the database is not in use. 3. On the server or at the database location, use the Windows desktop to rename the database folder, .pro file, and .
Running Database Maintenance Tools Dependency inconsistencies are not visible. They are obsolete or invalid entries in internal database tables. A high number might cause slowdowns for certain operations. • Remove Duplicated Locators: Use this tool to detect and remove duplicated locators. Duplicated locators are locators that have the same comment, timestamp, and color as another locator on the same asset. A high number might cause slowdowns for certain operations.
Running Database Maintenance Tools When to run these tools: You can run any of these tools as part of a troubleshooting procedure, as recommended by an Avid representative. You can also run them for maintenance during regular maintenance windows. However, they are not designed to be run on a daily basis, because they require Exclusive Access to the database (see below). One approach to using the tools for maintenance is to run them in the first convenient maintenance window.
Running Database Maintenance Tools If a tool requires Exclusive Access, a dialog box is displayed that asks if you want to set Exclusive Access. Exclusive Access can be acquired and released in the Lock Server view, independently of the Maintenance tools (see “Locking and Unlocking the Server” on page 88). In an emergency, such as the Exclusive Access host crashed and there is no Interplay Administrator installed on the Engine, you can run a command-line program to release Exclusive Access.
Running Database Maintenance Tools Tool Options Recover Lost Master Mobs • Recover into ‘Orphan Clips’ folder. Select this option to create links for lost master mobs in to the Orphan Clips folder for deletion. If you do not select this option, the tool reports problems but does not take action to fix them. • Verbose Output. Select this option to display the names of the lost master mobs. • Delete File Mobs. Select this option to delete lost media information objects. • Delete Media.
Running Database Maintenance Tools Tool Options Clean Up Parentless Objects • Clean up parentless objects and move them to the “Lost&Found” folder. Use this option to both check for and fix parentless objects. The Interplay Engine either deletes the parentless object (in case it is not valid or functional anymore) or restores the object to a new parent folder named “Lost&Found.” This folder is created on the database's root folder.
Identifying the Root Folder of the Interplay Server Database - Save Log: Saves a version of the displayed information with additional specific date and time information, like the first option. It uses the following format: tool_name-dd-mm-yyyy-hh-mm-ss.log 7. Click Close. Identifying the Root Folder of the Interplay Server Database WG_Database$ is a hidden administrative share name and not an actual folder. It represents the root folder of the database.
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 • Configuring Third-Party Storage Changing the Database and Data Locations The Server Settings view lets you change the default locations for a new database.
Viewing Server Information 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. For the root folder of the data (file assets), keep the folder that was set during the installation of the server, unless you need to change the default configuration. The default is the same as the root folder of the database. 4. Click Apply Changes to change the setting for new databases.
Locking and Unlocking the Server Information view are KEY-EE for the editor, KEY-E for Access, and KEY-A for the Interplay Administrator, However, only one license type, KEY-XE, is listed as used in the Licenses view. You should use the Licenses view to manage license use. For more information, see “License Types and Usage” on page 97. To view information about the Interplay Engine server: t In the Server section of the Interplay Administrator window, click the Server Information icon.
Locking and Unlocking the Server The Lock Server view provides two different means of locking the Interplay Engine server: Lock Server and Exclusive Access. • If Lock Server is activated, the Interplay Engine server is locked and all the clients that are connected to it are disconnected. • If Exclusive Access is activated, the server process continues to run and the database can be used.
Locking and Unlocking the Server To lock the server and prevent any user access: 1. In the Server section of the Interplay Administrator window, click the Lock Server icon. The Lock Server view opens. 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.
Locking and Unlocking the Server - Lock until: Allows you to stipulate when to restart the server (longer time frame). Specify the time period by clicking the Up and Down arrows. 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.
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 Interplay needs valid licenses in order to function. Licenses are delivered to the customer in a license file, which the administrator imports through the Licenses view.
Managing Licenses Installing Permanent Licenses If you are installing the Interplay Engine on a new system, temporary licenses are activated automatically so that you can administer and install the system. There is no time limit for these licenses. If you are performing an upgrade, the currently installed licenses are used. Starting with Interplay Production v3.3, new licenses for Interplay components are managed through software activation IDs.
Managing Licenses If the USB flash drive does not automatically display: a. Double-click the computer icon on the desktop. b. Double-click the USB flash drive icon to open it. 4. Copy the license file (*.nxn) into the new folder you created. 5. In the Server section of the Interplay Administrator window, click the Licenses icon. 6. Click the Import license button. 7. Browse for the *.nxn file. 8. Select the file and click Open. You see information about the permanent license in the License Types area.
Managing Licenses - Use the Refresh Engine button to update changes to licenses you have made using the Avid License Control tool. Clicking this button gives you the same result as restarting the Interplay Engine. The following illustration shows the dongle-managed view. For the dongle-managed view, the Licenses view has four sections: - The License Types section displays information about the following: - Your current license types (see “License Types and Usage” on page 97).
Managing Licenses - n The Server Information section displays information about the following: - Customer ID. The customer name or ID number. - Hardware ID, which matches the physical application key (dongle). The Hardware ID is required to obtain technical support. The items Number of Databases, License Mode, and Lock Timeout are not applicable to current licensing. - Import License File section: For information about importing a license file, see “Installing Permanent Licenses” on page 94.
Managing Licenses Customers can also buy the following licenses: • Interplay Production Engine • Interplay Archive Engine • Third-Party AMA Storage Supported License Types The following table describes the license types used for Interplay Production v2.7.0.2 and later, how they are displayed in the Interplay Administrator Licenses view, and which applications they license.
Managing Licenses How Licenses Are Shared A client workstation, through its IP address, can use a single license to run more than one Avid client application concurrently. For example, a user can run both Media Composer and Interplay Access while using a single MediaCentral license (Base or Advance). The Interplay Engine manages access through the hostname of the workstation. The license is not released from the client workstation until all applications that require a license are closed.
Managing Licenses License Types Previously Used for Interplay Production Applications Prior to Interplay version 2.7, customers purchased licenses for individual products. The following table lists how these legacy licenses relate to current license types, how they are displayed in the Interplay Administrator Licenses view, and which applications they license.
Managing Licenses Legacy license types Current license types Current license types and legacy license types 101
Managing Licenses If a facility is using a mix of legacy licenses and current licenses, the Interplay Engine first looks for an appropriate legacy license. If none are available, it looks for an appropriate current license. For example: 1. An Assist client logs on. The Interplay Engine looks for an Assist license (KEY-XL) 2. If it does not find one available, it looks for a Base license (KEY-J). 3.
Configuring Third-Party Storage 3. Locate the registry key for the original dongle, found here: HKEY_LOCAL_MACHINE\SOFTWARE\Avid Technology\Workgroup\Avid Workgroup Server\FeatureKeys\Permanent 4. Delete the Permanent folder. 5. Close the Registry Editor window. 6. Reload the new registration file as described in “Installing Permanent Licenses” on page 94.
4 User Management An administrator controls access to 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: c • 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 Interplay.
Understanding the Central Configuration Server The following procedure is based on these assumptions: c • Server A is the CCS. • You want to keep the CCS settings and user information that exist on server A, but move them to server B. • You do not want to keep the original CCS information that exists server B. Server B should be created by a clean installation and should serve as its own CCS.
Understanding the Central Configuration Server Viewing and Changing the CCS for a Server c Before beginning the following procedure, be sure to make a backup of the database. See “Creating and Restoring Database Backups” on page 29 for information on running a backup. You can use the Start Backup Now feature to start a backup immediately. You can use the Start CCS (_InternalData) Backup Now feature to back up the CCS database. The following procedure is based on these assumptions: • Server A is the CCS.
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 105), 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 ISIS Authentication” on page 112. • 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 “_”.
Setting User Authentication Providers and Importing Users to the same converted name (for example, dann/o and dann\o become dann_o), only one converted user name is imported. These users currently cannot be authorized through LDAP or Windows Domain; they can only be imported. 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.
Setting User Authentication Providers and Importing Users Setting Avid ISIS Authentication If you select the Avid ISIS Authentication option, a user can log in to the Interplay database using a valid Avid ISIS password. The authentication mechanism always checks this User Authentication Provider first. 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.
Setting User Authentication Providers and Importing Users 4. In a multiple ISIS workgroup, click the Add Avid ISIS button and type the name of the System Director for the additional Avid ISIS systems. 5. Click Apply. The first time an Avid ISIS user logs into Interplay, the user is added to the CCS as part of the UNITY user group under Imported Users, with Read rights by default.
Setting User Authentication Providers and Importing Users “Universal Group”) and can be authenticated across the entire forest. Interplay domain authentication does not support this structure. If you select a domain for authentication, users from other forest domains will be stripped from the group during the import process. If necessary, you can combine Windows domain authentication of one domain with LDAP authentication of another domain.
Setting User Authentication Providers and Importing Users n New users added to the Windows domain are not continually imported to the CCS. You need to add them manually. See “Adding Users Manually” on page 126. Setting LDAP Authentication and Importing Users If you select the LDAP Authentication option, a user can log in to Interplay databases with an LDAP user name and password. Interplay supports LDAP Version 2 and LDAP Version 3.
Setting User Authentication Providers and Importing Users 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 120. To import LDAP users and enable LDAP authentication: 1.
Setting User Authentication Providers and Importing Users LDAP Server Configuration Settings The following table describes the LDAP server settings that are needed for authentication and import. Setting Description LDAP Server IP address of the LDAP server. LDAP Port Port for the LDAP service. For Standard LDAP, accept the default port 389. For Active Directory Global Catalog LDAP, specify port 3268.
Setting User Authentication Providers and Importing Users Setting Description User Name Attribute The attribute that becomes the imported user name in Interplay. This name is displayed in the user tree and is used for logging in to Interplay. The standard LDAP attribute is “cn” but an administrator can use other attributes, such as “displayName” or “mailNickname” for a shortened user name. The user import process automatically imports the attribute used in this field as well as the “cn” attribute.
Setting User Authentication Providers and Importing Users The following illustration shows an example of settings for an Active Directory LDAP implementation. The following illustration shows an example of settings for an OpenLDAP implementation.
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 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. 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.
Setting User Authentication Providers and Importing Users Combined LDAP Authentication and Windows Domain Authentication If you want to import and authenticate users from two domains, you can combine LDAP authentication as described in the previous sections (either for a single domain or for a single OU) with Windows Domain authentication for a second domain. For information on Windows Domain authentication, see “Setting Windows Domain Authentication and Importing Users” on page 113.
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 104).
Managing Users, User Groups, and User Rights 124
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 127. 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 133.
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 123). 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 67. 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 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 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 Interplay database. For a description of available properties, see “System Metadata Properties” on page 278. 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 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 153). The next time a user starts Interplay Access and logs in, the new custom property is displayed.
Creating Custom Properties 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. To set access control for custom properties: 1.
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 149). 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.
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 157. 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 150.
Configuring Remote Workgroups Disabling Search for Custom Properties In facilities with a large number of custom properties, the search process can be slowed down by searching for text in custom properties. The Interplay Administrator now includes a column named “Text Search” in the Custom Metadata tab of the Property Layout view, which lets you enable or disable individual custom properties for text search. A green check mark indicates the property is enabled for searching.
Configuring Remote Workgroups For complete information on transferring Avid assets, see the Interplay Transfer Setup and User’s Guide or the Interplay Transfer Help. n You can configure a maximum of 10 hostnames. For example, you can configure for searching five remote workgroups and five Nearchive servers for a total of 10. To set up access to a remote workgroup: 1. For transfers, make sure the Transfer Engines for both workgroups are correctly configured. 2.
Configuring Categories 5. In the New server pane, add information about the remote workgroup you want to access. a. b. c. 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 By default, no categories are configured in the Interplay Administrator. c There is no option to rename a category. The database items identify the categories they belong to by the category name, so this name cannot be changed once it is used. Adding Categories To make categories available in Interplay Access: 1. In the Site Settings section of the Interplay Administrator window, click the Configure Categories icon. The Configure Categories view opens. 2.
Configuring Categories When performing a search, you can use a Category name to locate items that belong to that category. 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.
Setting Server Hostnames and the Workgroup Name Setting Server Hostnames and the Workgroup Name The Server Hostname Settings view lets you set the information described in the following table. Group Setting Description Interplay Media Services Settings Interplay Media Services Engine Enter the name of the Interplay Media Services Engine so that you can run the Interplay Media Services view (see “Interplay Media Services View” on page 169) or use any Interplay Media Services.
Setting Server Hostnames and the Workgroup Name Group Setting Description Media Indexer AMA Shared-Storage Location Enter the name of the shared-storage location in which Media Indexer looks for AMA .spaaf files. Enter the name as a full UNC path. This must be the same location that you identified for the .spaaf files in the Media Indexer web interface. For more information, see “Using AMA Material in Interplay” in the Interplay Best Practices Guide.
Setting Server Hostnames and the Workgroup Name Group Setting Description Server MI Connection URL Click the Add button to add one or more Media Indexer servers. The following applications use this setting to locate the Media Indexer servers: • Avid editing applications • Media Services Transcode provider • STP Encode • Interplay Transfer engine • Interplay Access • Avid Instinct n Interplay Access uses the Workgroup Name option.
Setting Server Hostnames and the Workgroup Name 2. Supply the information described in the above table. 3. Where appropriate, click Apply Changes. Configuring the Interplay Streaming Server After you install the Interplay Streaming Server software, you need to enter the name of the computer on which you installed the software. n Beginning with Interplay v3.1, the Interplay Streaming Server installer is no longer included on the Interplay Server Installer.
Setting Server Hostnames and the Workgroup Name c After installation, exclude the folder C:\Program Files (x86)\Avid\Avid Interplay Streaming Server from scanning by any virus protection software. Scanning for virus protection could cause severe disruptions to the Interplay Stream Server and could cause it to shut down. You can add one or more additional Interplay Streaming Servers to a workgroup. See Interplay Software Installation and Configuration. n In 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 Before you can use the Interplay Media Services view, the Interplay Media Services Engine for the workgroup must be configured in the Server Hostname Settings view. For details, see “Setting Server Hostnames and the Workgroup Name” on page 164. Also, the Interplay Media Services Engine must be running. If the Interplay Media Services connection to the Interplay Media Services Engine fails, the login panel is displayed to let you manually attempt to login again.
Specifying Remote Servers for Asset Tracking n Users with Administration rights can change the configuration to another destination in the Send to Workgroup dialog box in Interplay Access. For procedures that explain the Workgroup Transfer Presets view, see the Interplay Transfer Setup and User's Guide. 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.
Specifying Archive Settings 2. If you want to track assets in a non-archive server, in the Online server name text box, type the computer name of the Interplay Engine server and click Add. The server name is added to the list of configured hosts. 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 If you are logged into an Interplay Archive Engine, the settings include: • Allow duplicate media files ) - • This option lets you choose whether the Archive Provider archives duplicate versions of the media. Allow Metadata Archive - This option lets you choose whether the AAF metadata for Avid assets is sent to the tape archive along with the media.
Specifying Archive Settings The Asset Tracking/Archive Settings view opens. 3. Select the Archive database AvidAM from the database list. The system displays the Asset Tracking/Archive Settings window for the Interplay Archive Engine. 4. Select one of the following settings for “Allow duplicated media files” option: - No — When you archive an Avid asset the first time, the Archive Provider archives all associated media.
Specifying Archive Settings Adding AAF Metadata to an Archive The Asset Tracking/Archive Settings view on the Interplay Archive Engine includes an option labeled “Allow Metadata Archive.” If you select Yes, AAF metadata for Avid assets is sent to the tape archive along with the media. This option requires special implementation by the tape archive vendor. If you select No, only media is sent to tape (the default). This option is supported for the SGL FlashNet™ solution.
Setting the Ownership for New Database Folders t c Use best effort restore - if you select this option, a restore process restores as many files as it can without returning errors. This option requires special implementation by supported third-party vendors to ignore any missing files that are no longer in the archive storage. If you do not select this option, then the restore process fails when there are any missing files (the default).
Setting the Ownership for New Database Folders To prevent this situation, you can set an option so that a new folder is owned by the same owner as the parent folder. If this option is set, in the previous example, Editor 2 inherits read/write permissions on the new folder but does not have delete permission and thus cannot delete the sequence or master clips. n An administrator can change the owner and permissions for a folder after it is created.
Enabling Interplay Synced Projects Enabling Interplay Synced Projects Interplay Synced Projects provide you with a way to link your bins and projects in Media Composer or NewsCutter with the folder structure for assets stored in your Interplay database. Before you can use synced projects, you need to enable the Synced Projects setting in Interplay. Folders for Interplay Synced Projects are indicated by a synced project icon.
Setting Options for Deletion 2. Select Enable, and then click Apply. The application enables synced projects for the selected workgroup.
Setting Options for Deletion This distinction between links and database assets is important in understanding how the deletion process works and the how it is affected by a deletion schedule. The following topics describe the deletion process: • “Three Parts of the Deletion Process” on page 180 • “Changes in Interplay v2.
Setting Options for Deletion Clip 1 (link) V1 media Clip 1 database asset Clip 1 copy (link) A1 media A2 media 3. After the last link for an asset is deleted, database assets are deleted unless they reference online media. The following illustration shows the completed 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.
Setting Options for Deletion Clip 1 (link) V1 media Clip 1 database asset Clip 1 copy (link) A1 media A2 media Orphan Clips folder Clip 1 (link) 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.
Setting Options for Deletion Custom deletion schedule: To take advantage of the improved process and lessen the load on the Interplay Engine, you need to set a custom schedule with one or more time spans. Scheduling a deletion time span results in a faster initial deletion operation and less impact on other Interplay Engine operations. You set a custom time span in the Interplay Administrator. Additional options are also available. See “Scheduling the Deletion of Database Assets” on page 186.
Setting Options for Deletion Starting in Interplay v2.4, the Orphan Clips folder includes the following subfolders: • Kept Media folder: You can select an option to include deletion of online media in the scheduled deletion (“Permanently delete assets and associated online media from the Orphan Clips folder”). If you do not select this option, the scheduled deletion moves any links with online media to a subfolder in the Orphan Clips folder named “Kept Media.
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 By default, you cannot delete referenced assets (including rendered effects) without deleting the sequence that references them (see “Restricted Deletion of Referenced Assets” in the Interplay Access User’s Guide).
Setting Options for Deletion The syntax of the tool is described in the following in-line help: *********************************************************************** delete_kept_media - Deletes assets in Kept Media folder. delete_kept_media [user:] [psw:] [proj:] [maxAssets:] [maxTime:] This tool automates the deletion of assets (including media) that were moved to the Kept Media folder by scheduled deletion.
Viewing and Setting the Metadata Override Status To run the Delete Kept Media tool: 1. On the Interplay Engine system (or for a cluster system, on the online node), open a Windows Command Prompt. 2. Navigate to the location of the tool. For example, type cd C:\Program Files\Avid\Avid Interplay Engine\Server 3.
Production Engine Bus Connector Folders with metadata override disabled are listed in the Locations window. Red icon = metadata override is disabled Blue icon = metadata override is enabled Gray icons = inherited setting 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.
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 • Media Composer | Cloud Settings • 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 133. 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 197. 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 Audio – Source audio patching Setting Description Applications Sound on Tape label Allows you to specify a name for the SOT track in source clips. The default is SOT. Avid Instinct MediaCentral Voice Over label Allows you to specify a name for the voice-over track in source clips. The default is VOICE.
Application Database Settings View Application Database Settings: Editing Settings Tab (Continued) Option Setting Description Applications Sound on Tape track If two channels are selected for SOT, 2 specifies which track of the output sequence is mapped to SOT track 2. The default is A5. Avid Instinct MediaCentral Voice Over track Avid Instinct MediaCentral Audio – general settings Media Creation workspace Specifies which track of the output sequence is mapped to voice-over sound.
Application Database Settings View Application Database Settings: Editing Settings Tab (Continued) Option Setting Description Sample bit depth Sets the sample bit depth for audio Avid Instinct clips created in the application, such as Interplay Assist voice-over recordings and audio MediaCentral mixdowns. The more bits used to sample the audio, the more accurately the amplitude is represented by the clip.
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, MediaCentral UX set the duration to zero. The default duration is 24 hours.
Application Database Settings View Application Database Settings: Editing Settings Tab (Continued) Option Setting Checkin and Checkout Use background (Disabled by default). Enabling this checkin from editors feature lets a Media Composer user check in clips and sequences to Interplay Production by using a background process. This allows you to continue working on your project while the application checks in your work to Interplay.
Application Database Settings View Setting Audio Mixing Defaults for Access, Assist, and MediaCentral | UX The Audio Mixing Defaults in the Application Defaults tab apply to Interplay Access, Interplay Assist, and Avid MediaCentral UX v2.1 and later. • 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.
Application Database Settings View To set audio mixing defaults for Interplay Access, Interplay Assist, and MediaCentral (basic sequences): 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.
Application Database Settings View 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). Configuring the Restrictions Display The Restrictions tab in the Object Inspector displays information about restrictions associated with an Avid asset.
Application Database Settings View n A user can view restrictions in Interplay Access, Interplay Assist, Media Composer, and MediaCentral UX, but can create, delete, or modify restrictions only in Interplay Assist and MediaCentral UX. An administrator sets permission to create and modify restrictions. See “Instinct/Assist User Settings” on page 218. To configure the default display in the Interplay Administrator: 1.
Media Composer | Cloud Settings Media Composer | Cloud Settings This view is used to configure upload settings for Media Composer Cloud users. For more information, see the Media Composer | Cloud Installation and Configuration Guide. You can set options for the Media Composer Cloud Settings view as described in the following table. These settings affect how remote upload functions when you use Media Composer Cloud.
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 Media Instinct Assist Access Composer MediaCentral Description Can send to playback x x Can modify column properties x x If yes, allows the selected user or group to send material to a playback device.
Setting Instinct/Assist User Options Setting Can use higher resolutions Media Instinct Assist Access Composer MediaCentral Description x x 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 Media Instinct Assist Access Composer MediaCentral Description x x 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 Media Instinct Assist Access Composer MediaCentral Description Can create restrictions x x 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. As of Interplay v3.0, Pro Tools Interplay Integration Plug-Ins for Interplay are no longer available on the Interplay Client Installer. For more information about using Pro Tools with Interplay, go to the Knowledge Base page titled “Avid Interplay Requirements With Pro Tools.
7 Interplay Services The 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 Interplay Media Indexer settings for a computer in the Interplay workgroup. You can use the Service Configuration view to configure services such as the Interplay Media Indexers for all the clients in your workgroup from one computer.
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 Interplay Engine server: • Troubleshooting Login Problems • Troubleshooting Client Connection Problems • Optimizing Interplay Performance • Troubleshooting Firewalls and Interplay • Troubleshooting the Server Execution User Account • Shutting Down or Locking the Server Process Also see “Creating a Metadata-Only Backup for Customer Support” on page 56.
Troubleshooting Client Connection Problems 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. See “Managing Users, User Groups, and User Rights” on page 123. • Check if the password is expired.
Troubleshooting Firewalls and Interplay • Check the speed of the LAN between the Interplay Engine and the shared storage server. Make sure that the Interplay Engine and the Avid shared-storage server are connected appropriately; for example, the Interplay Engine needs to read the files to create thumbnails. If the connection is slow, performance can drop. • Check the speed of file operations of the Interplay Engine on the shared storage server.
Troubleshooting the Server Execution User Account Troubleshooting the Server Execution User Account The Server Execution User is a Windows operating system user account that is used only to run the Interplay Engine processes. You specify the user name and password for the Server Execution User when you install the Interplay Engine on the server. The following topics provide more information about the Server Execution User account and information about how to recreate the account.
Troubleshooting the Server Execution User Account • You have the option of allowing the Interplay Engine installer to create the account. Select a name before the installation and specify the name and a password during the installation. The installer will create a local user in the Administrators group with the appropriate permissions. • You can also create a local Administrator account manually and specify that account during the installation.
Troubleshooting the Server Execution User Account To determine the Server Execution User name: 1. Right-click My Computer and select Manage. 2. Expand the Services and Applications branch, then click Services. 3. Right-click Avid Workgroup TCP COM Bridge and select Properties. 4. Click the Log On tab. The Log On tab contains the name of the Server Execution User.
Troubleshooting the Server Execution User Account 3. Type the name, such as MYDOMAIN\IPEngine, and the password of the account. Make sure that this name exactly matches the user name and password of an account in the Avid shared-storage Administration tool that has read/write access to the appropriate workspaces (see “Creating the Server Execution User Account” on page 228). n Make sure that you use the correct password for the specified user because the tool cannot verify the password.
Shutting Down or Locking the Server Process Shutting Down or Locking the Server Process You might need to shut down or lock the Avid Interplay Engine Server process in certain circumstances, such as low disk space conditions (see “Moving a Database Under Low Disk Space Conditions” on page 77). For more information about the process, see “Avid Interplay Engine Server” on page 254. To shut down or lock the Avid Interplay Engine Server process, do one of the following: t Lock the server using NxNServerLock.
9 Reuniting a Split Database A split database refers to a configuration in which only the metadata database is stored on the Interplay Engine. All other database files and folders are stored on an Avid shared-storage workspace. Previous versions of this guide described how to create and manage a split database to allow for a large number of file assets. This configuration is no longer recommended.
Preparing to Reunite a Split Database The following illustration shows all database files located in the same AvidWG folder on the Interplay Engine server.
Preparing to Reunite 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 (AvidWG Only) 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 236. • 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 239.
Reuniting a Split Database (AvidWG Only) 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 \\SharedS
Reuniting a Split Database (AvidWG Only) Copy from \\SharedStorageServer\WorkspaceName\AvidWG to \\IEServer\WG_Database$\AvidWG AvidWG.pro FolderLocations.xml 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 (AvidWG and _InternalData) c. Lock and unlock the database. d. After reconnecting to the database with Interplay Access, check if the file is still in the database. 12. If the test is successful, delete or rename the folder \\SharedStorageServer\WorkspaceName\AvidWG. Reuniting a Split Database (AvidWG and _InternalData) To reunite a split database (AvidWG and _InternalData): 1.
Reuniting a Split Database (AvidWG and _InternalData) For more information on Interplay Engine services, see “Avid Interplay Engine Servers and Services” on page 253. 6. If you do not have a complete Interplay database backup available, manually create an archive backup 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) 7.
Reuniting a Split Database (AvidWG and _InternalData) Copy from \\SharedStorageServer\WorkspaceName\AvidWG to \\IEServer\WG_Database$\AvidWG 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. If the AvidWG folder on shared storage includes a _Database folder, do not copy this folder to the Interplay Engine.
Reuniting a Split Database (AvidWG and _InternalData) Copy from \\SharedStorageServer\WorkspaceName\_InternalData to \\IEServer\WG_Database$\_InternalData 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. Rename this folder _Database_UNUSED or something similar before copying the other content to the Interplay Engine. 9. Delete or rename \\IEServer\WG_Database$\AvidWG\FolderLocation
Configuring the workgroup.xml File 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. In the Interplay Administrator, click Manage Databases. b. In the “Database (.pro) file to activate” text box, type the full UNC path to the .
Configuring the workgroup.xml File n On a cluster system, the following file might be installed on both nodes: C:\Program Files\Avid\Avid Interplay Engine\Data\Apache\conf\workgroup.xml. These files are not currently used and do not need to be edited. The default database location that you specified during the Interplay Engine installation is published through this file as a default. The following example shows the section of workgroup.
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 Apache Folder The Apache web server handles every incoming request and forwards them to the database server. The Apache folder includes important logs from the Apache process. 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.
Avid Interplay Engine Directory: Folders and Files The items in such a log entry are: • The IP address of the machine where the request was coming from; • The date and time when the request was received; • 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.
Avid Interplay Engine Directory: Folders and Files Data Folder The Data folder contains server-relevant configuration and data files, including the following Apache modules and configuration files used by the Avid Interplay Preview Server and Avid Interplay HTTP Server. File Path (C:\Program Files\Avid\Avid Interplay Engine) Description Data\Apache\conf\httpd.conf The configuration file for the Apache web server. Data\Apache\conf\workgroup.
Avid Interplay Engine Directory: Folders and Files File Path (C:\Program Files\Avid\Avid Interplay Engine) Description Logs\Machines\[COMPUTER NAME]\NxNServer.log The central Avid Interplay Engine Server log file containing information messages, warning and error messages generated by the Avid Interplay Engine Server. Logs\Machines\[COMPUTERNAME]\ NxNTCPCOMBridge.log The log file for the Avid Interplay TCP/COM Bridge. Is not created until the first message occurs. Logs\Machines\[COMPUTERNAME]\ NxNBack
Avid Interplay Engine Directory: Folders and Files AvDeletes.log q w e r [Mon May 25 14:02:29 2009] User 'airspeed' on host 'muc-ifsputnik' deleting media for: [Mon May 25 14:02:29 2009] /Projects/ETPB1/INCOMING1/VIEWCUT_7151_MEDEA_020809_JT [Mon May 25 14:02:29 2009] Media locations: [Mon May 25 14:02:29 2009] Successfully deleted file //caetavdisis/feeds_a/avid mediafiles/mxf/tm_caetavdetpb-1/etpb_1v01d015d6.
Avid Interplay Engine Directory: Folders and Files q w e r t [Mon May data: [Mon May [Mon May [Mon May [Mon May 25 14:02:30 2009] User 'airspeed' on host 'muc-ifsputnik' deleting meta25 25 25 25 14:02:39 14:02:39 14:02:39 14:02:39 2009] 2009] 2009] 2009] From '/Projects/ETPB-1/INCOMING1/' 'ET_VCT_7143_US_MICHELLE_5A_CY' handle 163841 'VIEWCUT_7151_MEDEA_020809_JT.
Avid Interplay Engine Directory: Folders and Files 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 Server Folder The Server folder contains the Avid Interplay Engine Server installation. 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.
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 254. • 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 256. Requirements See “Avid Workgroup Preview Server Service” on page 256.
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 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 228. Configuring the Preview Service The Preview Service is responsible for the generation of thumbnails and preview images on the server, as well as delivering them to the Interplay application. All settings can be edited in the workgroup.xml file in the section.
Avid Interplay Engine Servers and Services best performance, this path should reside on a disk that has enough free space available to hold a reasonable working set of cached images. While the default is inside of the database directory of the Avid Interplay Engine, it is a good idea to place it on a different disk. • IconRoot: Path to a directory where a set of icons is stored, usually pointing into the Avid Interplay Engine installation directory.
Avid Interplay Engine Servers and Services 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. • The Avid Workgroup TCP/COM bridge needs to run under the same user account 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 Configuring the Server Event Manager The Server Event Manager is a service that automatically informs administrators whenever an important event occurs on the server, for example, when the hard drive is almost full.
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 Interplay and that can be configured in Config.xml as events to which the 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 270. 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 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 275Configuring Client Access Example 4: PAGE 276Setting 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 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 Interplay The following table lists the valid and invalid characters (also known as special characters) for Interplay. Allowed Avid asset names Not Allowed Characters: / \ | File asset names and All characters allowed Characters: * ? : / \ " < > | Interplay database for files in Windows Names ending with a dot folder names Names used as DOS devices (LPT1, com1, .., .,, for example) Property names (metadata field names) Characters: / \ | Video ID metadata field Spaces
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. 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.
Search Values and Hints on Searching in Interplay Heading Description Auxiliary Ink Auxiliary ink format settings allow you to display an additional type of ink number. This lets you track additional types of film information for different film gauges. Used for 24p projects, 25p projects, and matchback projects only. Auxiliary Ink is the starting frame for the clip.
Search Values and Hints on Searching in Interplay Heading Description Color The text display color for metadata of the Returns items of selected color found. selected item in all Interplay Access The search does not find items colored displays. only by inheritance (only the parent is returned). Comments Displays any comments added as metadata to the media file when it was originally ingested or captured. You can edit this field in Interplay Access.
Search Values and Hints on Searching in Interplay Heading Description Disk Label Displays the XDCAM disk label created when you import XDCAM media. (This value is not currently displayed in Interplay Access.) DPX Frame-counting field for Digital Picture Exchange, a SMPTE standard describing frames scanned from film. 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, DPXChildDocu-023657.
Search Values and Hints on Searching in Interplay Heading Description Frame Chase Expected Duration Expected length of a clip captured by the Type numbers only in the four Frame Chase Editing method. colon-separated entry fields displayed. Frame Chase Known Duration Current length of a clip being captured by Type numbers only in the four the Frame Chase Editing method. colon-separated entry fields displayed. Has Closed Captions An asset that has closed captions created or edited in MediaCentral UX.
Search Values and Hints on Searching in Interplay Heading Description KN Film Key number film gauge. KN IN-OUT Mark IN and Mark OUT key number for the clip. Used for 24p projects, 25p projects, and matchback projects only. KN Mark IN Key number for the IN point, if you set one for the clip. Used for 24p projects, 25p projects, and matchback projects only. KN Mark OUT Key number for the OUT point, if you set Select an operator and then type numbers one for the clip.
Heading Description Search Values and Hints on Searching in Interplay Master End Ending key number for the final master sequence. You cannot modify this number. Select an operator and then type numbers only in the four colon-separated entry fields displayed. Master Film Gauge of the final master sequence. Master Start Starting key number of the final master sequence. Used for 24p projects, 25p projects, and matchback projects only.
Search Values and Hints on Searching in Interplay Heading Description Path Path to assets in the Interplay database. Meant to be used in conjuction with other search conditions to narrow the area where the results are coming from: for example, combine a search for all masterclips that have been updated in the last 10 minutes and that are in path "/Projects/MyName/MyBin2.” Select is or is not, then click the Select button and choose a path from the tree.
Search Values and Hints on Searching in Interplay Heading Description Reserved (Search only) Indicated item is reserved Select a user and then select a time frame. for specified timeframe by specified user. S3D Alignment Displays whether or not the media has already been aligned by a third-party application. Presently, this is just an indicator for the editor. There are no software functions associated with this field.
Search Values and Hints on Searching in Interplay Heading Description S3D Contributors (master clip only) Lists the S3D Channels (master clips) that Criterion for Extended Search in Access feed into the stereoscopic clip. 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.
Search Values and Hints on Searching in Interplay Heading Description S3D Group name A common name used to identify all Criterion for Extended Search in Access master clips originating from the same stereoscopic footage. The group name is used by the application to create a single stereoscopic clip that references these master clips. Therefore, this name must be exactly the same for all clips that need to be grouped into a stereoscopic clip.
Search Values and Hints on Searching in Interplay Heading Description S3D InversionR 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. Displays how the part of the image that provides the right eye should be inverted before being used. None: Leaves the image as is. Horizontal: Inverts the right eye image horizontally. Vertical: Inverts the right eye image vertically.
Search Values and Hints on Searching in Interplay Heading Description Start Timecode of the clip’s head frame. Streamable Masterclips (Search only) Finds master clips that were are published, are not published. For published for streaming (Interplay V2.3 Interplay v2.4 and later, add criteria and earlier). Can also be used to search “Media Status is online” for clips with directly playable proxy media.
Search Values and Hints on Searching in Interplay Heading Description Text Search only Track Formats Multichannel audio tracks for master clips and audio clips. Tracking Displays colored icons that indicate the status of shared assets across workgroups. For more information, see “Viewing the Status Assets Across Workgroups (Asset Tracking).” Tracks All tracks used by the asset (from the bin) Select Video, Audio, or Both.
Search Values and Hints on Searching in Interplay Heading Description 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. You can edit this field in Interplay Access. VITC Vertical interval timecode. Workspace Name of an Avid shared-storage workspace 293 Type the name of the workspace.
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 iterator is invalid for this iteration-capable command 89990050 property not found 89990051 property not s
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
899901a1 Object is reserved and cannot be deleted.
89990251 incorrect user name 89990252 incorrect password 89990253 version control database not found 89990260 lookup for vital creation properties failed 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 'User
89990317 Unable to complete the operation because the action exists with another type 89990318 The given role name already used by another role 89990319 The given role id is already used by another role 89990320 Unable to complete the operation because the role exists with another type 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
89990365 the group cannot be destroyed because it contains children 89990366 not a serigraph 8999036 the group must not contain other groups 89990368 the database is from a different CCS and needs a migration 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
89990611 permanently moved 89990612 moved temporarily 89990613 see other 89990614 not modified 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
89990700 database journal error 89990701 database journal initialization failed 89990702 database journal recovery failed 89990703 invalid entry in database journal found 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 inf
89990a03 Could not write an image file. The file was created but writing to the file failed. This could for example happen if disk has insufficient disk space. 89990a04 The image could not be read because it does not have a known format. 89990a05 The image could not be read because the bitmap in it is invalid. 89990a06 An unknown error occurred in the image lib. 89990a07 An image could not be loaded or saved because the license for the LZW algorithm is not available.
89990b0b The LDAP server detected an error when trying to dereference an alias, LDAP error: LDAP_ALIAS_PROBLEM(0x21) 89990b0c The syntax of a DN sent to the LDAP server is incorrect, LDAP v: LDAP_INVALID_DN_SYNTAX(0x22) 89990b0d The LDAP server cannot perform the operation on a leaf entry, LDAP error: LDAP_IS_LEAF(0x23) 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 a
89990b1d The LDAP server cannot perform the operation because it would change the structure rules of the object class, LDAP error: LDAP_NO_OBJECT_CLASS_MODS(0x45) 89990b1e The results of a request to the LDAP server are too large to return them, LDAP error: LDAP_RESULTS_TOO_LARGE(0x46) 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 beca
89990b2d An LDAP operation failed because it is not supported by the LDAP server, LDAP error: LDAP_NOT_SUPPORTED(0x5c) 89990b2e The LDAP server refused to return results, LDAP error: LDAP_NO_RESULTS_RETURNED(0x5e) 89990b2f An LDAP operation failed because a required control was not found, LDAP error: LDAP_CONTROL_NOT_FOUND(0x5d) 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 referra
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 27 _Buckets directory described 27 _Database directory backing up and restoring 29, 30 described 27 _Master directory described 27 _PropertyStore directory backing up and restoring 29, 30 described 27 Numerics 7-Zip for Interplay backups 39 A AAF metadata adding to tape archive 175 Access control for custom properties 153 Accumulated inherited role described 128 Activating database 65 Administrator role described 128 Administrators gro
Index ABCDEFGHIJKLMNOPQRSTUVWXYZ online support 12 training services 15 Avid assets described 17 Avid Instinct Application Database options 197 Media Composer Cloud options 215 setting Application Database options 194, 195 setting user options 215 user options 218 Avid Interplay client-server application 20 optimizing performance 226 Avid Interplay Administrator See Interplay Administrator Avid Interplay Assist Application Database options 197 Media Composer Cloud options 215 setting Application Database
ABCDEFGHIJKLMNOPQRSTUVWXYZ Config.
Index ABCDEFGHIJKLMNOPQRSTUVWXYZ setting and releasing 88 Exiting Interplay Administrator 25 Exporting license 102 Extended search custom properties 158 F Failed to Delete folder 179 Fast backup described 30 File assets described 17 Filetransfer server 276 Firewalls troubleshooting 227 Folderlocations.
ABCDEFGHIJKLMNOPQRSTUVWXYZ Interplay Portal viewing 13 Interplay Transfer configuring for remote workgroups 159 Interplay Transfer Settings view 170 Interplay Transfer Status view 170 Interplay Window automatic reservation 205 Interplay workgroup described 16 multiple workgroups 18 InterplayRestore tool described 41 example 48 J Journal files described 27 K Kept Media folder 179 L LDAP authentication 115 LDAP server settings 117 LicenseKeyInfo.
Index ABCDEFGHIJKLMNOPQRSTUVWXYZ locking server process 232 moving database with 77 NxNServerShutdown.exe moving database with 77 shutting down server process 232 NxNServerUnlock.exe moving database with 77 NXNServerUser.exe recreating Server Execution User 230 O Object Inspector configuring Frame Locators 212 configuring Restrictions 213 OMF files option for deleting 189 Online support 12 Orphan Clips folder changes for v2.
ABCDEFGHIJKLMNOPQRSTUVWXYZ S Schedule Backups view 35 Scheduled deletion 186 Searches custom properties 158 Searching remote workgroups 159 Send mail action 265 Server error codes 294 information about 87 locking 88 restarting 92 shutting down 88 unlocking 88 Server Event configuration example 269 Server Event Manager configuring 263 Server Execution User creating 228 described 20 recreating 230 troubleshooting 228 Server folder 253 Server Hostname Settings view 164 Server Information view 87 Server Settin
Index ABCDEFGHIJKLMNOPQRSTUVWXYZ User management guidelines 142 User Management view 123 Users adding from Avid Unity 112 adding manually 126 adding to a CCS 109 default 125 deleting 132 disconnecting all 92 importing 109 importing from LDAP 115 importing from Windows domain 113 list of connected 87 management guidelines 142 managing 123 removing from group 132 roles 128 setting attributes for 127 setting passwords for 127 X XML files for custom properties 155 V Validate User Tree tool 79 Verify Link Co
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.
