Specifications

Event Codes Telephony Management Service (TMS)
A
ShoreTel 14 Maintenance Guide 247
243 Warning TAPI request thread
timed out after <number
of seconds> seconds for
context <context handle
ID> performing request
type <request type ID>.
TMS is not
responding to
internal messages
in a timely fashion.
This event can
precede a
significant failure in
TMS.
Contact ShoreTel
Technical Support
and be prepared to
provide server logs
from the day of the
occurrence.
244 Warning <Connection type user
or App Server> TAPI
connection attempt for
login <user ID> from <IP
address> failed. Invalid
<LoginID>.
A TAPI connection
request was denied
due to an invalid
login or password.
Contact the user
and assist him or
her with login
information.
246 Information Telephony Management
Service logged an
informational debug
message. The debug
message contents
are:<Message>
A logic assertion
within TMS failed.
No action, unless
the event is
accompanied by
system failures.
If system failures
are occurring,
contact ShoreTel
Technical Support.
247 Information The log file <log file
name> current size is
<log file size> bytes. It
exceeded its maximum
size limit of <max log
size> bytes. Further
logging is suspended.
The log file cannot
write new events
because it reached
its maximum size.
This event typically
results from a
configuration that
creates an event
loop.
Review all
configured call
handling modes for
loops.
Example: UserA
forwards calls to
userB, who in turn
is forwarding all
calls to userA.
If no logic fault is
found, contact
ShoreTel Technical
Support.
Table 55: Event codes: TMS (Continued)
ID Severity Levels Message Cause Action