7.0

Table Of Contents
Table 24. Connection Broker Events (Continued)
Event Type Severity ModuleAndEventText
BROKER_MACHINE_PROTOCOL_NOT_SUPPORT
ED
AUDIT_FAIL Unable to launch from Pool ${DesktopId} for user $
{UserDisplayName}: Machine ${MachineName} does not
support protocol ${ProtocolId}
BROKER_MACHINE_PROTOCOL_UNAVAILABLE AUDIT_FAIL Unable to launch from Pool ${DesktopId} for user $
{UserDisplayName}: Machine ${MachineName} did not
report protocol ${ProtocolId} as ready
BROKER_MACHINE_REJECTED_SESSION WARNING Unable to launch from Pool ${DesktopId} for user $
{UserDisplayName}: Machine ${MachineName} rejected the
start session request
BROKER_MACHINE_SESSION_TIMEDOUT WARNING Session for user ${UserDisplayName} timed out
BROKER_MULTIPLE_DESKTOPS_FOR_KIOSK_USE
R
WARNING User ${UserDisplayName} is entitled to multiple desktop
pools
BROKER_POOL_CANNOT_ASSIGN AUDIT_FAIL Unable to launch from Pool ${DesktopId} for user $
{UserDisplayName}: There are no machines available to
assign the user to
BROKER_POOL_COMANAGER_REQUIRED AUDIT_FAIL Unable to launch from Pool ${DesktopId} for user $
{UserDisplayName}: No co-management availability for
protocol ${ProtocolId}
BROKER_POOL_EMPTY AUDIT_FAIL Unable to launch from Pool ${DesktopId} for user $
{UserDisplayName}: The Desktop Pool is empty
BROKER_POOL_NO_MACHINE_ASSIGNED AUDIT_FAIL Unable to launch from Pool ${DesktopId} for user $
{UserDisplayName}: No machine assigned to this user
BROKER_POOL_NO_RESPONSES AUDIT_FAIL Unable to launch from Pool ${DesktopId} for user $
{UserDisplayName}: No machines in the Desktop Pool are
responsive
BROKER_POOL_OVERLOADED AUDIT_FAIL Unable to launch from Pool ${DesktopId} for user $
{UserDisplayName}: All responding machines are currently
in use
BROKER_POOL_POLICY_VIOLATION AUDIT_FAIL Unable to launch from Pool ${DesktopId} for user $
{UserDisplayName}: This Desktop Pool does not allow online
sessions
BROKER_POOL_PROTOCOL_NOT_SUPPORTED AUDIT_FAIL Unable to launch from Pool ${DesktopId} for user $
{UserDisplayName}: There were no machines available that
support protocol ${ProtocolId}
BROKER_POOL_PROTOCOL_UNAVAILABLE AUDIT_FAIL Unable to launch from Pool ${DesktopId} for user $
{UserDisplayName}: There were no machines available that
reported protocol ${ProtocolId} as ready
BROKER_POOL_TUNNEL_NOT_SUPPORTED AUDIT_FAIL Unable to launch from Pool ${DesktopId} for user $
{UserDisplayName}: Tunnelling is not supported for protocol
${ProtocolId}
BROKER_PROVISIONING_ERROR_CONFIG_CLEA
RED
INFO The previously reported configuration problem is no longer
present on Pool ${DesktopId}
BROKER_PROVISIONING_ERROR_CONFIG_SET ERROR Provisioning error occurred on Pool ${DesktopId} because of
a configuration problem
BROKER_PROVISIONING_ERROR_DISK_CLEARE
D
INFO The previously reported disk problem is no longer present on
Pool ${DesktopId}
BROKER_PROVISIONING_ERROR_DISK_LC_RESE
RVATION_CLEARED
INFO The previously reported error due to available free disk space
reserved for linked clones is no longer present on Pool $
{DesktopId}
BROKER_PROVISIONING_ERROR_DISK_LC_RESE
RVATION_SET
ERROR Provisioning error occurred on Pool ${DesktopId} because
available free disk space is reserved for linked clones
Chapter 2 Integrating View with the Event Database
VMware, Inc. 13