VMware View Manager 4.5 Integration Manual page 13

Table 2-4. Connection Broker Events (Continued)
EventType
BROKER_MACHINE_REJECTED_SESSION
BROKER_MACHINE_SESSION_TIMEDOUT
BROKER_POOL_CANNOT_ASSIGN
BROKER_POOL_EMPTY
BROKER_POOL_NO_MACHINE_ASSIGNED
BROKER_POOL_NO_RESPONSES
BROKER_POOL_OVERLOADED
BROKER_POOL_POLICY_VIOLATION
BROKER_POOL_PROTOCOL_NOT_
SUPPORTED
BROKER_POOL_PROTOCOL_UNAVAILABLE
BROKER_POOL_TUNNEL_NOT_SUPPORTED
BROKER_PROVISIONING_ERROR_CONFIG_
CLEARED
BROKER_PROVISIONING_ERROR_CONFIG_
SET
BROKER_PROVISIONING_ERROR_DISK_
CLEARED
BROKER_PROVISIONING_ERROR_DISK_LC_
RESERVATION_CLEARED
BROKER_PROVISIONING_ERROR_DISK_LC_
RESERVATION_SET
BROKER_PROVISIONING_ERROR_DISK_SET
VMware, Inc.
Chapter 2 Integrating with the Event Database
Severity ModuleAndEventText
WARNING Unable to launch from Pool ${DesktopId}
for user ${UserDisplayName}: Machine
${MachineName} rejected the start session
request
WARNING Session for user ${UserDisplayName}
timed out
AUDIT_FAIL Unable to launch from Pool ${DesktopId}
for user ${UserDisplayName}: There are no
machines available to assign the user to
AUDIT_FAIL Unable to launch from Pool ${DesktopId}
for user ${UserDisplayName}: The Desktop
Pool is empty
AUDIT_FAIL Unable to launch from Pool ${DesktopId}
for user ${UserDisplayName}: No machine
assigned to this user
AUDIT_FAIL Unable to launch from Pool ${DesktopId}
for user ${UserDisplayName}: No
machines in the Desktop Pool are
responsive
AUDIT_FAIL Unable to launch from Pool ${DesktopId}
for user ${UserDisplayName}: All
responding machines are currently in use
AUDIT_FAIL Unable to launch from Pool ${DesktopId}
for user ${UserDisplayName}: This
Desktop Pool does not allow online
sessions
AUDIT_FAIL Unable to launch from Pool ${DesktopId}
for user ${UserDisplayName}: There were
no machines available that support
protocol ${ProtocolId}
AUDIT_FAIL Unable to launch from Pool ${DesktopId}
for user ${UserDisplayName}: There were
no machines available that reported
protocol ${ProtocolId} as ready
AUDIT_FAIL Unable to launch from Pool ${DesktopId}
for user ${UserDisplayName}: Tunnelling
is not supported for protocol ${ProtocolId}
INFO The previously reported configuration
problem is no longer present on Pool
${DesktopId}
ERROR Provisioning error occurred on Pool
${DesktopId} because of a configuration
problem
INFO The previously reported disk problem is no
longer present on Pool ${DesktopId}
INFO The previously reported error due to
available free disk space reserved for linked
clones is no longer present on Pool
${DesktopId}
ERROR Provisioning error occurred on Pool
${DesktopId} because available free disk
space is reserved for linked clones
WARNING Provisioning error occurred on Pool
${DesktopId} because of a disk problem
13