##### File > Convert to Collaborate Mode (or Collaborate) > Collaborate > Administrate

# Update Servers

Administrative users can currently change the lock mode and unlock databases from this section of the Genesys Agent Scripting Collaboration Administration application.

Clicking the Update Servers link in the catalog opens the Update Servers window.

## Server Table

The server table contains a list of project books that have been converted to collaboration mode.

### Database Name

Displays the name of a Genesys Agent Scripting Collaboration project book.

### Locked Mode

The database can be locked in one of two ways:

- Pessimistic Mode

In this mode, the database assumes that users are going to do things that conflict with each other, so the database prevents this from happening. For example, this mode will prevent a user from adding a new reference to an object that a different user is currently attempting to delete.

- Optimistic Mode

In optimistic mode, it is assumed that these situations are very rare and not worth the cycle time.

### Locked?

This specifies whether the database currently has a database-wide lock placed on it.

### Locked Exclusive?

This specifies whether the database has been locked for a user’s exclusive use. In this mode, individual records will not need to be checked out in order to make changes. However, all changes will need to be checked in prior to releasing the exclusive lock.

### User Name

Displays the name of the user who currently has a lock on the database.

## Change Lock Mode

The Change Lock Mode button allows you to change the lock mode of the currently selected database. In order to change the lock mode, all items must be checked in and the database must not be locked.

## Unlock Database

The Unlock Database button will clear a database-wide lock on the currently selected database as long as it is not an exclusive lock. Exclusive lock maintenance is handled from within the Genesys Agent Scripting client application.

### Why Unlock a Database?

When Genesys Agent Scripting is in the process of checking in or checking out Genesys Agent Scripting components, it places a database lock on the entire database so that no one else makes changes to the central database during its operation. Under normal conditions, this database lock is acquired and released automatically. However, if a user’s machine crashes or the network goes down during the course of a check in or check out, this global database lock might not be released. The administrative application provides a facility where this database lock can be manually cleared.

You should only clear a database lock manually if it is clear that the last check in or check out failed and is no longer processing.

Note: here only database-level locks are displayed. Finer granular locks, such as locks on individual scripts, pages, fields, and so on, are administrated through the Genesys Agent Scripting client application.