® 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Setting Windows Domain Authentication and Importing Users . . . . . . . . . . . . . . . 113 Setting LDAP Authentication and Importing Users. . . . . . . . . . . . . . . . . . . . . .
Setting Server Hostnames and the Workgroup Name . . . . . . . . . . . . . . . . . . . . . . . . . 165 Configuring the Interplay Streaming Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Interplay Media Services View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Interplay Transfer Status View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Interplay Transfer Settings View . . . . . . . . . . . . . . .
Setting Instinct/Assist User Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Instinct/Assist User Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Pro Tools Plug-Ins Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Chapter 7 Interplay Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Avid Workgroup VSS Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262 Avid Workgroup Engine Monitor Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 Appendix B Interplay Engine Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 Configuring the Server Event Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 Config.xml File . . . . . . . . . . . . . . . . . . . . . . . . . .
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 145. • Configuring the Interplay Archive Engine. See “Specifying Archive Settings” on page 174. 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 197 and “Interplay Services” on page 224.
Using the Interplay | Administrator Window 2. Select the server you want to work with by doing one of the following: t Accept the server that is displayed. t Type the name of the server that you want to log in to. You can also use an IP address. t Click the arrow for the Server list and select the server name from the list.
Using the 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 Interpla y 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 40 • “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.
Creating and Restoring Database Backups 3. (Option) In the Backup Information area, change your preferences if necessary. “Backup only if modified” is selected by default to save space and avoid duplicate identical copies. The default number of versions to keep is 10. The 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, change the path if desired. a.
Creating and Restoring Database Backups 10. (Option) Change the Backup time by selecting one of the following: t Select Once at and change the hour and minutes (within 10 minute intervals) on which it occurs using the up and down arrows. t Select Every and set the backup to occur at regular intervals starting at midnight. Use the down arrow to select the interval. t Select Custom and specify custom backup times. Use the up and down arrows to select the time, and then click Add.
Creating and Restoring Database Backups The backup is created in the location you specified. If you navigate to the location, and the backup is still being created, the folder name includes the words “backup in progress.” Using an Archiving Tool for Backup In some circumstances, such as performing a system upgrade, you might want to use an archive tool to create a backup copy of the complete database folder (AvidWG or AvidAM) and the user database folder (_InternalData).
Creating and Restoring Database Backups To make a backup copy of the database on a 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. Close the Interplay Administration tool. 6.
Creating and Restoring Database Backups Restoring an Earlier Version of a Database Restoring a backup version of the _Database and _PropertyStore folders returns a database to the state it was in when the backup was created. Before restoring a database, make sure that it is really necessary, because changes since the backup will be lost. To restore a backup, you need to run the InterplayRestore tool in a Command Prompt window. The InterplayRestore tool is installed in the following folder: C:\Program Files
Creating and Restoring Database Backups How the Restore Tool Renames Folders When the tool begins the restore, it locks the database and then renames the existing folder _Database to _Database.1. If you are performing a restore from a Complete backup, the tool also renames _PropertyStore to _PropertyStore.1. If a folder _Database.1 already exists, the tool creates _Database.2, and so on up to _Database.9.
Creating and Restoring Database Backups For example, if a sequence of backups looks like this: c(complete)1 -> i(incremental)1 -> i2 -> d(differential)1 -> i3 -> i4 -> d2 -> i5 -> i6, to restore i6 the backups you need in the same folder are c1, d2, i5, and i6. You need these files because i6 contains the changes since i5, which contains the changes since d2, which contains the changes since c1. • A Fast Metadata Only backup contains only a _Database folder, and can only be run manually.
Creating and Restoring Database Backups Fast Metadata Only backup folder Complete, Fast Incremental, or Fast Differential backup folder To distinguish between Complete, Fast Incremental, and Fast Differential backups, open the backup folder and then open the inventory.xml file in Notepad or another text editor. The type of backup is listed, along with other information.
Creating and Restoring Database Backups 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. Use the InterplayRestore tool to restore the latest Fast Differential backup (from Thursday). 2.
Creating and Restoring Database Backups 4. InterplayRestore prompts you for the database root directory. Type the path and press Enter. You can use a local path or a UNC path. For example: D:\Workgroup_Databases\AvidWG \\IEServer\WG_Database$\AvidWG You can use the administrative share name WG_Database$ only in a UNC path. 5. The next prompt asks if you are restoring a split database configuration.
Creating and Restoring Database Backups To restore an earlier version of a database from a backup by passing parameters to the tool, do one of the following: t For a non-split database, navigate to the folder that holds InterplayRestore, type the following, and press Enter: InterplayRestore /m /backupdir For example: InterplayRestore /m d:\Workgroup_Databases\AvidWG /backupdir d:\Workgroup_Databases\AvidWG\_Backup InterplayRestore prompts you to choose
Creating and Restoring Database Backups For example: InterplayRestore /m d:\Workgroup_Databases\AvidWG /backupdir d:\Workgroup_Databases\AvidWG\_Backup /backuptorestore d:\Workgroup_Databases\AvidWG\_Backup\AvidWG_2007-08-20_01-00 InterplayRestore restores the earlier version. Continue with steps 8 through 11 above. Database Restore Session Example The following is an example of an interactive session, which begins with the command for starting the InterplayRestore tool.
Creating and Restoring Database Backups Assume you choose 1. The tool locks the project so that no one can access the database and then copies the files: Beginning restore from \\isis\workspace1\avidwg\_Backup\AvidWG_2010-06-10_03-05\ This is a Full backup Restoring split database. Metadata restored to d:\Workgroup_Databases\avidwg\. PropertyStore Assets restored to \\isis\workspace1\avidwg Locked project AvidWG Copying files into d:\Workgroup_Databases\avidwg\_Database Copying file AvidWG.dor ...
Creating and Restoring Database Backups The following illustration shows the corresponding files as they appear in the archive file \AvidWG\_Backup\AvidWG_2008-05-04_01-00\_PropertyStore\streamed_prop1.bar: The .bar file is a file that you can only open by using the BackupArchive tool. n In previous versions of Interplay, you could use Windows Explorer to view and work with the streamed properties files in the _PropertyStore backup folder.
Creating and Restoring Database Backups For example, type the following and press Enter: cd C:\Program Files\Avid\Avid Interplay Engine\Server 3. Type the following and press Enter: backuparchive /L Do not use the file extension when typing the name of the archive file. For example, backuparchive /L \\docisis\workspace3\AvidWG\_Backup\AvidWG_2008-05-04_01-00\_PropertySt ore\streamed_prop Make sure to type the command on a single line.
Creating and Restoring Database Backups Restoring Archived Log Files In Interplay version 1.6 and later, the Interplay Engine compresses and archives log files older than 7 days. The log compression process runs during project backup. (This process runs at most once per day, even if multiple backups are scheduled on the same day.) Archive files (with the extensions .bar and .bin) are stored in the same directory as the log files for 30 days and then are automatically deleted.
Creating and Restoring Database Backups [4] 07 February 2013 16:00:00 incremental Choose an entry ( 1 - 4 ): 3 Backup restore chain 0. Test_2013-02-04_16-00 full 1. Test_2013-02-05_16-00 incremental 2. Test_2013-02-06_16-00 incremental 3. Test_2013-02-07_16-00 incremental The InterplayRestore tool gives you an option of selecting a partial restore. If you type “y,” you are asked to select which file in the restore chain from which to start the restore.
Creating and Restoring Database Backups Displaying a Restore Chain You have the option of displaying the restore chain for a selected backup without performing the restore. To display the restore chain, use the /printchain option in a interactive or non-interactive command line, as shown in the following examples: Non-interactive mode: InterplayRestore /metadata F:\Workgroup_Databases\Test /backupdir F:\Workgroup_Databases\Test\_Backup /printchain Interactive mode: InterplayRestore /printchain In either
Creating and Restoring Database Backups Choose a backup to restore from: [1] 04 February 2013 16:39:00 full [2] 04 February 2013 16:42:00 incremental [3] 04 February 2013 16:44:00 incremental [4] 24 February 2013 01:00:00 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 F:\Workgroup_Databases\Test\_PropertyStore\2013-35\1436_StreamedProperty_A AFBinary1073743260-0.prp Verifying that we have all streamed property BAR files... Copying Copying ... Restore Project files into F:\Workgroup_Databases\Test\_Database file Test.jdf operation successful Test is still locked for your restore of _Master. The database is still locked because you need to restore the _Master directory manually, or through your existing tape backup mechanism.
Performing a Consistency Check The backup file is created in specified backup location, for example: AvidWG\_Backup\AvidWG_2013-02-12_01-00 To distinguish between a metadata-only backup and the other types of backups, open the backup folder and check if a _PropertyStore folder exists. A metadata-only backup does not contain a _PropertyStore folder. 5. Use an archive program like 7-Zip to create a compressed file to send to customer support.
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 2. Do one of the following: t In the “Database (.pro) file to activate” text box, type the full UNC path to the .pro file. For example: \\IEServer\WG_Database$\AvidWG\AvidWG.pro t Click the Browse button, log in if prompted, navigate to the .pro file using a network, select the file, and click Open. The following illustration shows the path to AvidWG.pro, using the Microsoft Windows smb network and the administrative share WG_Database$.
Managing Databases: Deactivating, Activating, and Migrating 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 89). 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 89). 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 and Users to Another Server (Clustered Systems) 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 89). 13. Rename the existing _InternalData folder to _InternalData_old. 14.
Moving a Database Under Low Disk Space Conditions Moving a Database Under Low Disk Space Conditions If disk space on the server is critically low, the Interplay Engine refuses client connections and displays an error message.
Renaming a Database Renaming a Database Under some circumstances you might need to rename a database For example, if you need to create a new database with the same name, you can rename the original database. You can keep the original database as an archive for searching. c 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 Running Database Maintenance Tools The Maintenance view in the Database section of the Interplay Administrator provides the following tools that you can use to fix database problems. You can use these tools with Interplay Engine databases v2.4.0.1 or later, except for Validate User Tree, which you can use only with Interplay Engine v2.6. The tools are not displayed when connected to earlier versions of the Interplay Engine.
Running Database Maintenance Tools • Validate AssignedRoles Table: Use this tool to check or fix (by removing) invalid entries in the AssignedRoles table. This table keeps information about user roles that are assigned to database objects. The tool verifies this table for integrity and fixes entries if needed. • Validate Property Objects: (Interplay Engine v2.7.6 or later, Interplay Engine v3.0.6 or later.
Running Database Maintenance Tools 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 89). 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. The file name of the tool is NxNServerExclusiveAccessRelease.
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 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. For example, the default root folder (which is set during installation) is named D:\Workgroup_Databases (S:\Workgroup_Databases on a cluster system). To identify the root folder of the database: 1.
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 To change the root folders for a new database: 1. In the Server section of the Interplay Administrator window, click the Server Settings icon. The Server Settings view opens. 2. For the root folder of the database (metadata), keep the folder that was set during the installation of the server (the default is \\IEServer\WG_Database$\). 3.
Viewing Server Information The license class is different from the license type. The license class is an internal key that is used by the Interplay Engine. The license type is the key displayed in the Licenses view.
Locking and Unlocking the Server Locking and Unlocking the Server The Lock Server view allows the administrator to lock the Interplay Engine server for a specific period of time. Locking the server is useful when carrying out tasks such as: n • Server maintenance or upgrading the server software. • Maintaining or rebooting the Avid shared-storage server. Whenever a database or data location is unavailable, you should lock the database or the server.
Locking and Unlocking the Server The following table summarizes the differences between a server lock, a database lock, and Exclusive Access: Feature Description Server lock (Lock Server view) Saves and unloads all databases (including _InternalData). Also prevents access by the Interplay Administrator. Should be used for maintenance operations that require access to all database files (in the share WG_Database$). Usually shutting down the Interplay Engine is a better approach than a server lock.
Locking and Unlocking the Server 2. In the Lock Server section, select one of the following for the locking duration: - Indefinitely: An indefinite shutdown. This is a good choice when shutting down the server to carry out any vital maintenance, for example replacing hard drives, or making the first backup of a new database. The server needs to be manually unlocked after maintenance work. - Minutes: Allows you to stipulate when to restart the server (short time frame).
Locking and Unlocking the Server 3. In the “Lock comment” text box, type a comment as to why you are locking the server. This comment is displayed when an Interplay Administrator tries to log into the Interplay Engine. 4. Click Lock Server. The Lock Server view changes to display lock information. You cannot return to the Interplay Administrator window by clicking the Menu button. You can log out of the Interplay Administrator tool and then log in again.
Restarting the Server You can return to the Interplay Administrator window by clicking the Menu button, log out of the Interplay Administrator tool and then log in again, and perform other database tasks. To manually unlock the server after activating Exclusive Access, do one of the following: t t Log in to the Interplay Administrator from the host where you acquired Exclusive Access or on the Engine host itself, click the Lock Server icon, then click Release Exclusive Access.
Managing Licenses Managing Licenses 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. A set of permanent licenses is provided by Avid in the form of a file (with the extension .nxn) on a USB flash drive or another delivery mechanism.
Managing Licenses Displaying the Licenses View To view information about your licenses: t In the Server section of the Interplay Administrator window, click the Licenses icon. The Licenses view opens. 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). - Number of license types available. - Number of license types used.
Managing Licenses - - n Days Remaining: The number of days until expiration of a time-limited license. Interplay licenses are usually not time limited, so in most cases the value for a license type is “0.” Only one value for the days remaining is stored for each license type. 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).
Managing Licenses Customers can also buy two types of server licenses: n • Interplay Archive Engine • Interplay Streaming Server There is no license required for the Interplay Engine. Current 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 The following illustration compares a set of legacy license types, a set of current license types, and a mix of the two. In all cases the number of client licenses available is 140.
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 95.
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. The following procedure is based on these assumptions: • Server A is the CCS. • You want server B to be the CCS for server A.
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 111. • Importing users from a Windows domain or LDAP directory.
Setting User Authentication Providers and Importing Users n All special characters are allowed in user names except for \ (backslash), / (forward slash), | (vertical bar), and quotes (" and '). When LDAP and Windows Domain users are imported, these characters are replaced with “_”. If two users have different user names that are mapped to the same converted name (for example, dann/o and dann\o become dann_o), only one converted user name is imported.
Setting User Authentication Providers and Importing Users The users are added to the Imported Users folder in the User Management page, under the respective subfolder for LDAP, Microsoft, or Avid Unity. Users are also added to the Everyone folder. The following illustration shows these subfolders with the LDAP folder selected.
Setting User Authentication Providers and Importing Users This method of authorization is implicit. In other words, there is no active import of users at the time the Avid ISIS Authentication is enabled. Instead, the first time that an Avid ISIS user logs in to Interplay, the user is added to the UNITY user group subfolder. By default, this user group has Read rights. If your workgroup includes multiple ISIS systems, you need to specify each additional ISIS server name.
Setting User Authentication Providers and Importing Users Setting Windows Domain Authentication and Importing Users If you activate Windows Domain authentication, a user is able to log in to an Interplay database with a Windows domain user name and password. Any time a user tries to access an Interplay database, the CCS (Central Configuration Server) can use the Windows login information to authenticate the user and in turn to check which databases the user can access.
Setting User Authentication Providers and Importing Users To enable Windows domain authentication: 1. In the User Management section of the Interplay Administrator window, click the User Authentication Providers icon. The User Authentication Providers view opens. 2. Select the Windows Domain Authentication option. 3. Click Import Windows Domain Users. The Import User Groups dialog box opens. 4. Do one of the following: t Select the user groups you want to import into the Interplay system.
Setting User Authentication Providers and Importing Users To properly configure LDAP authentication, you must know the schema of the LDAP database. Two common schemas are • Microsoft Active Directory LDAP implementation • A freely available LDAP service such as OpenLDAP The configuration you specify depends on the LDAP schema against which you are authenticating. The following illustration shows some differences between Active Directory and OpenLDAP.
Setting User Authentication Providers and Importing Users To import LDAP users and enable LDAP authentication: 1. In the User Management section of the Interplay Administrator window, click the User Authentication Providers icon. The User Authentication Providers view opens. 2. Select the LDAP Authentication option. 3. Type information in the edit fields to specify the LDAP settings you want to use for import and authentication.
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 Attribute that stores the user name to use for LDAP-authenticated logins. The content of this attribute becomes the imported user name in Interplay and defines the user name for LDAP-authenticated login attempts. This attribute might vary according to the LDAP schema, and there might be multiple attributes storing different varieties of the user name.
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 Adding User Groups Interplay creates default user groups during the server installation. You can create additional groups so that you can more easily manage access to the database. For example, you might have a group of editors that should always have Read/Write/Delete privileges on all files. You might also have a group of assistants that should have Read/Write privileges.
Managing Users, User Groups, and User Rights 3. Do one of the following: t Press Ctrl+U for a new user. t Click the Create User button. 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.
Managing Users, User Groups, and User Rights n The password should only include characters from the ASCII the character set. Multibyte passwords might cause login problems, and the administrator then has to reset the password. 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.
Managing Users, User Groups, and User Rights You can assign rights for specific users on specific folders in the Manage Database Roles view (see “Managing Database Roles” on page 133). 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.
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 Removing Users from User Groups You can remove any user except Administrator from any user group except the Everyone group. Removing a user does not delete the user from other groups. 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 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 The following illustration shows the Projects folder, the Editors group, and All roles selected. All roles are listed in the lower panel.
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 The formula in the middle of the view shows your selection. For example, in the following illustration, you are going to give Editors the Read role (read-only access) for the Antarctica folder. 6. Click Set Role. The role appears in the lower panel.
Managing Database Roles 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. The role for the users on that item is inherited from the parent user group again.
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 280. 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.
Setting the Resolutions Available for Display 5. Select and deselect properties as follows: n t (Option) To make a property available for users to add into displays on their own, and to use in an Extended Search in Interplay Access, select the property in the Available column. To make a property unavailable, deselect it. 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.
Setting the Resolutions Available for Display In some circumstances you might want to make additional resolutions available for display. For example, if you are using Interplay Access to view the status of assets on remote workgroups, and the database for the local workgroup does not include resolutions used on the remote workgroup, you can select those resolutions for display in the local version of Interplay Access. By default, the option “Enable used resolutions automatically” is selected.
Creating Custom Properties Resolution in local database: grayed-out check box, name in bold face Resolution not in local database: grayed-out check box, name not n bold face 5. To remove a resolution, deselect its check box in the Available column. If you want to remove a default resolution, deselect “Enable used resolutions automatically” and then deselect the resolution’s checkbox. Keep in mind that any new resolutions added to the database will not be automatically selected as available for display.
Creating Custom Properties By default, the user needs to type the value for a custom property. Administrators can import an XML file that creates a list of values from which the user can select a value.
Creating Custom Properties When the Available column is selected, the custom property is available for users to add into the application displays, and to use in an Extended search. If the user performs an All Custom search, only the available custom properties are used in the search. n Deselect the property in the Available column to turn off custom properties that you do not want displayed in the properties lists. You cannot delete custom properties for this release but you can turn off their display.
Creating Custom Properties 8. Click Apply to save the added custom property and new layout. 9. (Option) If you want to prevent a user or group from supplying a value for a custom property, change the role in the User Management view (see “Setting Access Control for Custom Properties” on page 154). The next time a user starts Interplay Access and logs in, the new custom property is displayed.
Creating Custom Properties To select a value, click an item in the list, then click Apply. In this example, a user associated the value Team A to the folder. Users can add a custom property as a column in Interplay Assist, Avid Instinct, and the Interplay Window. Setting Access Control for Custom Properties You can control which users can supply a value for a custom property. This setting applies to both typing a value and selecting one from a list. By default, users are allowed to supply a value.
Creating Custom Properties Users pane Edit button Additional Roles pane 2. In the Users pane, select a group or user. 3. In the Additional Roles pane, select an option for “Can modify properties in Access”: - Inherited: Allows the selected user or group to inherit the role of the parent group - Yes: Allows users to type a value or to select from a menu. - No: Prevents users from typing or selecting from a menu. Users can see the property and its text box, but cannot supply a value for it.
Creating Custom Properties Working with Lists for Custom Properties You can create a custom property that includes a list of values from which users can choose (see “Creating Custom Properties” on page 150). 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 158. 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 151.
Configuring Remote Workgroups Configuring Remote Workgroups A large site can include more than one workgroup. When a workflow requires searching across remote workgroups or performing workgroup-to-workgroup transfers through Interplay Access, you must set up the local workgroup so that a user can access a remote workgroup. You set up this access in the Configure Remote Workgroups view. You can add an Interplay Archive Engine as a remote workgroup.
Configuring Remote Workgroups 4. Select a database from the Available Databases list. 5. In the New server pane, add information about the remote workgroup you want to access. a. b. Select the Host Type: - Interplay Server/Remote Search—to add access to a remote Interplay workgroup - TransferManager—to add access to a Workgroup 4 TransferManager - MediaManager—to add access to a Workgroup 4 workgroup or Nearchive™ system - Interplay Server / 3d Party Search—to add access for a third-party plug-in.
Configuring Categories c. Click Add. The Server name and other information about the remote workgroup appears in the list of accessible remote servers. To remove a remote workgroup from the accessible list: 1. Click the name of the remote workgroup in the list. 2. Click Remove. Configuring Categories Categories provide a grouping mechanism for the data that is stored in the database. Categories are displayed in Interplay Access, Interplay Assist, and Avid Instinct.
Configuring Categories 2. Select a database from the Available Databases list. 3. In the New Categories text box, type one name for a category, or type a comma-separated list (commas and spaces are automatically removed). 4. Click Add, and then click Apply. After refreshing Interplay Access, the categories you specified are visible in the Categories pane. When performing a search, you can use a Category name to locate items that belong to that category.
Configuring Categories Removing Categories Removing a category only removes it from the Configured Categories list in the Interplay Administrator. Objects in the database that have this category keep it, even if it is not listed anymore. If an item was assigned to a category but you removed that category in the Interplay Administrator, users are informed that the category is not valid anymore in the Interplay Access Categories tab. To remove a category: 1.
Setting Server Hostnames and the Workgroup Name 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 170) 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. For installation information, see Interplay Software Installation and Configuration. c After installation, exclude the folder C:\Program Files (x86)\Avid\Avid Interplay Streaming
Setting Server Hostnames and the Workgroup Name You can add one or more additional Interplay Streaming Servers to a workgroup. See Interplay Software Installation and Configuration. n In Interplay v2.4, the Interplay Streaming Server was re-engineered to directly play MPEG-4/H.263 and H.264 video media and MPEG1 layer 2 audio media. There is no longer any need to use the Publishing service or Workflow Engine to create QuickTime reference movies for streaming play.
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 165. 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.
Workgroup Transfer Presets View Workgroup Transfer Presets View When performing workgroup transfers, you can use presets to select a predefined destination for the transferring files. Transfer presets provide the name of the remote workgroup, a destination workspace, and a destination folder for the metadata. You can also choose whether to display the preset in the Send to Workgroup dialog box.
Specifying Remote Servers for Asset Tracking 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 Specifying Archive Settings The Asset Tracking/Archive Settings view lets you select options for how the Interplay Engine operates with the Interplay Archive Engine and the Archive Provider. The view displays different settings, depending on where you are logged in. 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.
Specifying Archive Settings To change whether archive operations create duplicate media: 1. Open the Interplay Administrator and log into the system running the Archive Engine. 2. In the Site Settings section of the Interplay Administrator window, click the Asset Tracking/Archive Settings icon. 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.
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 181 • “Changes in Interplay v2.
Setting Options for Deletion 2. Links for assets that are not reserved or referenced by other assets are deleted from the database. 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.
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 187.
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 3. Select the options that you want: - Allow scheduled deletions during database backups 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.
Setting Options for Deletion - One time span from 23:00 to 23:59 - One time span from 00:00 to 01:00 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.
Setting Options for Deletion Setting Options for Deleting Only OMF Media, Only MXF Media, or Both If a clip is associated with both OMF and MXF media, you might want to delete only the OMF media or only the MXF media. You can enable an option in the Interplay Administrator so that the Delete dialog box gives users the option of which media format to delete. To set an option that allows deleting only OMF media or only MXF media: 1.
Setting Options for Deletion The next time a user logs into Interplay Access and opens the Delete dialog box, the options are active or inactive, depending on the current settings in the Delete Behavior view of the Interplay Administrator. Activating the Option to Delete Referenced Assets Starting with Interplay Access v2.
Setting Options for Deletion t If the file does not exist, open Notepad or another text editor and create a file named configuration.xml. Copy the following code into the file: true Save the file and copy the file to %APPDATA%\Avid\Workgroup.
Setting Options for Deletion Using the Delete Kept Media Tool The Delete Kept Media tool is used to automatically delete the assets and media in the Orphan Clips\Kept Media folder. The file name of the tool is delete_kept_media.exe and it is installed by default on the Interplay Engine in the following folder: C:\Program Files\Avid\Avid Interplay Engine\Server For a cluster engine, you need to execute this tool directly on the online node.
Setting Options for Deletion The maxTime option is especially useful. It allows a media manager to start the deletion process late in the evening (or generally during low-load or no-load times) and specify a window for the deletion. You can schedule the deletion before a backup starts or before use of the Interplay Engine goes up in the morning.d For example: C:\Program Files\Avid\Avid Interplay Engine\Server>delete_kept_media.
Viewing and Setting the Metadata Override Status Viewing and Setting the Metadata Override Status The Metadata Override Settings view lets you manage how the Archive Provider handles metadata when an asset is archived more than once. This view appears only when the Interplay Administrator is logged on to an Archive Engine. By default, the Archive Provider overrides the archived metadata for an Avid asset if you archive the asset again.
Production Engine Bus Connector 2. (Option) Select a folder in the folder tree to limit the folders displayed in the Locations window to subfolders. To enable metadata override: t Select a folder in the folder tree or one or more folders in the Locations window and click Enable Override. To disable metadata override: t Select a folder in the folder tree or one or more folders in the Locations window and click Disable Override.
6 Application Settings In the Application settings, you can configure application-specific permissions and options, as described in the following topics: • Application Database Settings View • 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 200. 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 Dynamic Relink Setting Description Applications Ducking [-dB] Allows you to specify the amount of audio ducking (automatic lowering of audio gain in background audio). The default is 12 dB. Avid Instinct MediaCentral Audio file format Sets the audio file format to PCM. Not Avid Instinct changeable.
Application Database Settings View Application Database Settings: Editing Settings Tab (Continued) Option Setting Description Applications Send to playback Target resolution, primary Sets a resolution for output to a playback device. Avid Instinct Interplay Assist n n If dynamic relink is enabled, this field is enabled and you must select an option. The resolutions that are available depend on the resolutions available in the Resolutions tab in the Property Layout view.
Application Database Settings View Application Database Settings: Editing Settings Tab (Continued) Option Setting Description Applications Audio Mixdown Mode Sets the mixdown mode used for send-to-playback operations: Avid Instinct Interplay Assist • Mono — Maps to a center pan, which creates a mono mixdown of all audio tracks and outputs the resulting track to two channels when sent to playback. This results in two identical channels of audio, each containing the original audio tracks.
Application Database Settings View Application Database Settings: Editing Settings Tab (Continued) Option Setting Description Applications Audio Target Resolution Sets an audio resolution for output to a Avid Instinct playback device. Currently, the only Interplay Assist option is PCM. Sample Rate and Bit Depth: sets the resolution of the source audio for audio mixdowns. n If dynamic relink is enabled, you must set the audio target resolution to PCM and select a Sample Rate and Bit Depth.
Application Database Settings View Application Database Settings: Editing Settings Tab (Continued) Option Setting Description Applications Auto Reservation Duration [h] Allows you to set a default duration (in Avid Instinct hours) for auto reservations. If you do Interplay Assist not want auto reservation on a folder, set the duration to zero. The default duration is 24 hours.
Application Database Settings View Setting Audio Mixing Defaults for Access, 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 To configure the default display in the Interplay Administrator: 1. Open the Interplay Administrator and log in to the database for which you want to set the default display. 2. In the Application Settings section, click Application Database Settings. 3. Click the Application Defaults tab. 4. In the Access Restrictions View section, select the columns that you want to display in the Restrictions tab. The Start Time, End Time, and Comment columns are always displayed. 5.
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 If a setting is grayed out (inherited), click the Edit button to enable editing 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.
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 Avid editing MediaCe Instinct Assist Access applications ntral Can send to playback x x Can modify column properties x x Description 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 Avid editing MediaCe Instinct Assist Access applications ntral x x Description If yes, allows the selected user or group to work with a higher quality than the working resolution for video and audio clips if the working resolution is not available. If this option is set to No and the only available resolution is higher than the working resolution, the user sees Media Offline in the Video monitor.
Setting Instinct/Assist User Options Setting Can create locators Avid editing MediaCe Instinct Assist Access applications ntral x x x x Description 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).
Setting Instinct/Assist User Options Setting Avid editing MediaCe Instinct Assist Access applications ntral Can create restrictions x x Description If yes, allows the selected user or group to mark a section of a clip with a restriction locator. In most cases, if you want a user to create restrictions, select “yes” for both “Can create restrictions” and “Can modify restrictions.” Adding text is considered modifying a restriction. Administrators and owners have this right set by default.
Pro Tools Plug-Ins Settings Pro Tools Plug-Ins Settings You can use Interplay Pro Tools Plug-ins to pass audio files back and forth between Avid video editing systems and Pro Tools audio editing and mixing systems. 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 57.
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 Determining the Server Execution User Name If necessary, you can check the user name of 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 Re-creating the Server Execution User If you need to re-create the Server Execution User, use the NXNServerUser.exe tool. To re-create the Server Execution User account: 1. Run the tool NxNServerUser.exe on the Interplay Engine server. The tool is located in the following directory on the Interplay Server: Installers\AssetMgr\Tools\NxNServerUser 2. Select Custom User. 3. Type the name, such as MYDOMAIN\IPEngine, and the password of the account.
Shutting Down or Locking the Server Process The Avid Interplay Engine processes have all necessary access rights. 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 78). For more information about the process, see “Avid Interplay Engine Server” on page 256.
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 Preparing to Reunite a Split Database The following illustrations show a correctly split database: • The _Database folder is located in the AvidWG folder on the Interplay Engine server • The remaining folders and files are located in the AvidWG folder on a shared storage workspace 235
Preparing to Reunite a Split Database The following illustration shows all database files located in the same AvidWG folder on the Interplay Engine server. 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 237. • If the _InternalData folder is located on a shared storage workspace, or split between the Interplay Engine and shared storage, see “Reuniting a Split Database (AvidWG and _InternalData)” on page 241.
Reuniting a Split Database (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) The following table lists the files and folders that you need to copy. These files and folders are illustrated in “Reuniting a Split Database” on page 234. Copy from \\SharedStorageServer\WorkspaceName\AvidWG to \\IEServer\WG_Database$\AvidWG _Backup folder _Buckets folder _CheckIn folder _Handover folder _Import folder _Master folder _PropertyHandover folder _PropertyStore folder _AvidWG.nif Aliasconfig.xml AvidWG.pro FolderLocations.
Reuniting a Split Database (AvidWG Only) 8. Activate the database: a. In the Interplay Administrator, click Manage Databases. b. In the “Database (.pro) file to activate” text box, type the full UNC path to the .pro file, which now resides on the Interplay Engine server. For example: \\IEServer\WG_Database$\AvidWG\AvidWG.pro. c. Make sure “Load Database on Activation” is selected, and click Activate. If the database is activated, its name is displayed in the Databases list.
Reuniting a Split Database (AvidWG and _InternalData) Reuniting a Split Database (AvidWG and _InternalData) To reunite a split database (AvidWG and _InternalData): 1. If you are working on a cluster system, make sure that cluster services that provide the local S drive are running. 2. Lock the database to make sure that no user can access it: a. In the Database section of the Interplay Administrator window, click Lock/Unlock Database. b. Select the database in the Unlocked Databases list. c.
Reuniting a Split Database (AvidWG and _InternalData) 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. Copy the necessary files and folders from \\SharedStorageServer\WorkspaceName\AvidWG to \\IEServer\WG_Database$\A
Reuniting a Split Database (AvidWG and _InternalData) The following table lists the files and folders that you need to copy. These files and folders are illustrated in “Reuniting a Split Database” on page 234. Copy from \\SharedStorageServer\WorkspaceName\AvidWG to \\IEServer\WG_Database$\AvidWG _Backup folder _Buckets folder _CheckIn folder _Handover folder _Import folder _Master folder _PropertyHandover folder _PropertyStore folder _AvidWG.nif Aliasconfig.xml AvidWG.pro FolderLocations.
Reuniting a Split Database (AvidWG and _InternalData) Copy from \\SharedStorageServer\WorkspaceName\_InternalData to \\IEServer\WG_Database$\_InternalData _Backup folder _Buckets folder _CheckIn folder _Handover folder _Import folder _Master folder _PropertyHandover folder _PropertyStore folder _AvidWG.nif Aliasconfig.xml AvidWG.pro FolderLocations.xml c If the _InternalData folder on shared storage includes a _Database folder, do not copy this folder to the Interplay Engine.
Reuniting a Split Database (AvidWG and _InternalData) 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 16. Test the setup by doing the following: a. Open one Interplay Access client. b. Connect to the database and import a new file asset. c. Lock and unlock the database. d. After reconnecting to the database with Interplay Access, check if the file is still in the database. 17. If the test is successful, delete or rename the folder \\SharedStorageServer\WorkspaceName\AvidWG. Configuring the workgroup.
Configuring the workgroup.xml File If the file repository was moved to a different location, such as a shared-storage workspace, this location was published in this file as well. For example: PAGE 248A 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 File Path (C:\Program Files\Avid\Avid Interplay Engine) Data\Apache\conf\workgroup.xml Description This file contains settings for the Avid Interplay Apache modules. The settings in this file are used, for example, by the filetransfer and the preview server modules. The file transfer section contains items such as a list of UNC paths to which the Interplay HTTP server can browse.
Avid Interplay Engine Directory: Folders and Files In Interplay version 1.6 and later, the Interplay Engine compresses and archives log files older than 7 days. The log compression process runs during project backup. For more information see “Restoring Archived Log Files” on page 53. AvDeletes.log The AvDeletes.
Avid Interplay Engine Directory: Folders and Files AvMetaDataDelete.log The AvMetaDataDelete.
Avid Interplay Engine Directory: Folders and Files AvMoveEx.log The AvMoveEx.
Required TCP/IP Ports Preview Server Folder The Preview Server folder contains a script to clear the Preview Cache. 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 256. • 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 258. Requirements See “Avid Workgroup Preview Server Service” on page 258.
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 229. 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 Description of Preview Generation Settings in workgroup.xml • CacheRoot: Path where previews and thumbnails generated by the preview server are stored. This location is used by the preview server to create a cache of converted images. The preview server can reuse those images for subsequent requests from any client.
Avid Interplay Engine Servers and Services Avid Workgroup TCP/COM Bridge Service The Avid Workgroup TCP/COM Bridge service acts as bridge to the Avid Interplay Engine Server. The Avid Workgroup HTTP Server needs the Avid Interplay TCP/COM Bridge to connect to the Avid Interplay Engine Server. Connectivity The Avid Workgroup TCP/COM Bridge listens to port 8318. Processes The process running is usually NXNTCP~1.exe from NXNTCPCOMBridge.exe.
Avid Interplay Engine Servers and Services Connectivity The VSS Service communicates with the Avid Interplay Engine using standard Operating System pipes. Processes The process running is usually IEVSSS~1.EXE or IEVSSService.exe. 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.
Avid Interplay Engine Servers and Services Example 1: Startup: Avid Workgroup Engine Monitor Event ID 22: Service has been started successfully Avid Workgroup Engine Monitor Event ID 28: Workgroup Engine process started Avid Workgroup Engine Monitor Event ID 30: Monitoring thread started: thorough ping 90 sec, heart beat max idle 90 sec, monitoring interval 15 sec Example 2: COM Failure Avid Workgroup Engine Monitor Event ID 42: Failed to connect Workgroup Engine with DCOM 'Error 800706bb happened 8 times
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 272. 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 277Configuring Client Access Example 4: PAGE 278Setting 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 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. Created by Displays the name of the user who created the shotlist. Creation Date When the asset was created. The format of the date and time depends on the local language and regional options of the operating system and the Java software. Type text.
Search Values and Hints on Searching in Interplay Heading Description 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. DRM Digital Rights Management property.
Search Values and Hints on Searching in Interplay Heading Description In Use (Search only) If Is in use, asset is referenced by a sequence also in the database. Select Is in use or Is not in use. IN-OUT The length of the marked segment of a clip, if any. Select an operator and then type numbers only in the four colon-separated entry fields displayed. Initial Checkin Date Date that the asset was first checked in.
Search Values and Hints on Searching in Interplay Heading Description KNMarkIN Key number for the IN point, if you set one for the clip. Used for 24p projects, 25p projects, and matchback projects only. KNMarkOUT Key number for the OUT point, if you set Select an operator and then type numbers one for the clip. Used for 24p projects, only in the four colon-separated entry 25p projects, and matchback projects fields displayed. only. KNStart Starting key number for the clip.
Heading Description Search Values and Hints on Searching in Interplay Master Start Starting key number of the final master sequence. Used for 24p projects, 25p projects, and matchback projects only. Select an operator and then type numbers only in the four colon-separated entry fields displayed. Media File Format Clip media format. MXF or OMF. Media Size Media file size. Specify KB, MB, GB and type a number. Note that this specification cannot be saved in a Saved Search.
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. Take Take number of the scene. Type a number. Tape Source tape name (from the bin).
Search Values and Hints on Searching in Interplay Heading Description 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. Transfer Frame-counting field for sources that have been prepped for transfer.
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.
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 40 A AAF metadata adding to tape archive 176 Access control for custom properties 154 Accumulated inherited role described 128 Activating database 65 Administrator role described 128 Administrators group 125 Apache web server act
Index Avid online support 12 training services 15 Avid assets described 17 Avid Instinct Application Database options 200 Media Composer Cloud options 216 setting Application Database options 197, 198 setting user options 216 user options 219 Avid Interplay client-server application 20 optimizing performance 227 Avid Interplay Administrator See Interplay Administrator Avid Interplay Assist Application Database options 200 Media Composer Cloud options 216 setting Application Database options 197, 198 settin
Index Complete backup described 29, 30 Config.
Index Exclusive Access for maintenance tools 80 setting and releasing 89 Exiting Interplay Administrator 25 Exporting license 102 Extended search custom properties 159 F Failed to Delete folder 180 Fast backup described 30 File assets described 17 Filetransfer server 278 Firewalls troubleshooting 228 Folderlocations.
Index Interplay Media Services Engine registering 165 Interplay Media Services view 170 Interplay Portal viewing 13 Interplay Transfer configuring for remote workgroups 160 Interplay Transfer Settings view 171 Interplay Transfer Status view 171 Interplay Window automatic reservation 207 Interplay workgroup described 16 multiple workgroups 18 InterplayRestore tool described 42 example 49 J Journal files described 27 K Kept Media folder 180 L LDAP authentication 114 LDAP server settings 117 LicenseKeyInfo
Index N No Access role described 128 NxNServerLock.exe locking server process 233 moving database with 78 NxNServerShutdown.exe moving database with 78 shutting down server process 233 NxNServerUnlock.exe moving database with 78 NXNServerUser.exe recreating Server Execution User 232 O Object Inspector configuring Frame Locators 213 configuring Restrictions 214 OMF files option for deleting 190 Online support 12 Orphan Clips folder changes for v2.
Index Root folders setting 86 S Schedule Backups view 35 Scheduled deletion 187 Searches custom properties 159 Searching remote workgroups 160 Send mail action 267 Server error codes 295 information about 87 locking 89 restarting 93 shutting down 89 unlocking 89 Server Event configuration example 271 Server Event Manager configuring 265 Server Execution User creating 229 described 20 recreating 232 troubleshooting 229 Server folder 255 Server Hostname Settings view 165 Server Information view 87 Server Se
Index removing users from 133 roles 128 setting attributes for 127 setting passwords for 127 User management guidelines 143 User Management view 123 Users adding from Avid Unity 111 adding manually 126 adding to a CCS 109 default 125 deleting 132 disconnecting all 93 importing 109 importing from LDAP 114 importing from Windows domain 113 list of connected 87 management guidelines 143 managing 123 removing from group 133 roles 128 setting attributes for 127 setting passwords for 127 Workgroups described 16
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.
