Monitoring Microsoft Speech Server 2004 Using SNMP Traps

Monitoring Microsoft Speech Server ...

Published: September 12, 2005

Introduction

One way to monitor Microsoft Speech Server 2004 (MSS) is to use a Simple Network Management Protocol (SNMP) management console to monitor Windows Event Log events. Using two utilities available when the SNMP service is installed—the Event-to-Trap Translator (ETT) and evntcmd.exe—any Event Log event can be configured to generate SNMP Type 6 traps, Enterprise Specific. These traps are sent to the Windows SNMP service, which then delivers the traps to an SNMP management console application such as HP Openview, Novell NMS, IBM NetView, or Sun Net Manager.

This paper explains how to set up the SNMP service to monitor MSS events. To set up the service, you must:

Install the SNMP service on each server you want to monitor.
Translate MSS events to SNMP traps.
Configure SNMP trap destinations.

Note This paper does not provide information on how to use the SNMP management console to monitor SNMP traps. Please consult the documentation for the console application for more information.

About SNMP

SNMP is the Internet standard protocol for exchanging management information between management console applications and managed entities. The managed entities can include hosts, routers, bridges, and hubs.

SNMP uses a distributed architecture consisting of agents and managers. An agent is an SNMP application that responds to queries from SNMP manager applications. The SNMP agent is responsible for retrieving and updating local management information based on the requests of the SNMP manager. The agent also notifies registered managers when significant events or traps occur. A manager is an SNMP application that generates queries to SNMP agent applications and receives traps from SNMP agent applications.

On computers running Microsoft Windows NT, Windows 2000, Windows XP, or Windows Server 2003, the SNMP agent is implemented by the SNMP service (SNMP.EXE). The SNMP manager is typically a third-party SNMP management console application. The management console application does not need to run on the same host as the SNMP agent. To use the information the Microsoft SNMP service provides, you need at least one SNMP management console application.

Note The Windows SNMP service includes libraries that support SNMP management console applications. It does not include an SNMP management console application.

Using SNMP Traps to Monitor MSS Events

There are seven types of traps defined in the SNMP standard. Using the ETT or evntcmd.exe utility, you can configure the SNMP service to generate Type 6, Enterprise Specific, traps for specific MSS events. When the event occurs, a trap is generated and sent to an SNMP management console application. In this way, any MSS event that you specify can generate an SNMP trap and multiple servers can be monitored at the same time using a single SNMP management console (see Figure 1).

Figure 1 - MSS events configured to generate SNMP traps monitored by a common SNMP management console

Top of page

Setting Up SNMP for Monitoring MSS

To set up the SNMP service to monitor servers running MSS, follow these steps:

Install the SNMP service on each server you want to monitor.
Configure SNMP to generate traps for MSS events. There are two ways to do this:
- Using Events to Traps Translator (ETT)
- Using evntcmd.exe
Configure SNMP trap destinations. There are two ways to do this:
- Using evntcmd.exe
- Using the SNMP service properties

Install the SNMP Service

To monitor a server with SNMP traps, install the Windows SNMP service on that server.

Note You must install the SNMP service on each server you want to monitor.

To install the SNMP service

Click Start, click Control Panel, and then click Add or Remove Programs.
Click Add/Remove Windows Components.
In Components, click Management and Monitoring Tools (but do not select or clear its check box), and then click Details.
Select the Simple Network Management Protocol check box, and click OK.
Click Next.

Configure SNMP to Generate Traps for MSS Events

To configure the SNMP service to generate traps for MSS events, you can use either the ETT tool or the evntcmd.exe command. ETT is an easy-to-use graphical tool for selecting events for the SNMP service to monitor. The evntcmd.exe command is run from the command line and can be used to easily configure the SNMP service on multiple servers. The evntcmd.exe command requires a configuration file (.cnf file) identifying which events to monitor for SNMP traps. For an example of this file, see Appendix B: Sample .cnf File. You can create this file manually or use ETT to export it based on the selections you make in the tool.

Tip Use ETT to select the events you want to monitor on the local computer. Then export the .cnf file to use with the evntcmd.exe command to quickly configure other computers you want to monitor in the same way.

Using ETT to Configure SNMP to Generate Traps for MSS Events

ETT is a graphical tool you can use to configure the translation of events to traps on the local computer and is installed when you install the Windows SNMP service. You can also use ETT to export a configuration file (.cnf file) that can be used with evntcmd.exe to configure SNMP from the command line.

Important ETT is an easy-to-use tool for associating events with SNMP traps, but has a problem displaying the lists of some MSS events properly. Even though the events are not listed correctly in the tool, you can still use the tool effectively to select events to translate to traps.

To start ETT:

Click Start, and then click Run.
Type evntwin, and then click OK. Figure 2 shows the ETT startup window.

Figure 2 – The ETT startup window

To translate events to SNMP traps using ETT

In Configuration type, click Custom, and then click Edit. An area at the bottom of the window is displayed that allows you to browse registered events that can be configured to generate traps (see Figure 3).

Figure 3 – The ETT using Custom Configuration type, with event navigation controls visible.
In Event sources, expand the Applications folder, and then select the MSS event source for the events you want to monitor (see Figure 4).

Figure 4 - MSS event sources among others shown in the ETT

MSS logs events from several event sources, but it is recommended that you configure trap generation from the following sources:
- Speech Engine Services
- Telephony Application Services
- Telephony Application Services Host
When you select an event source in the tree, the list to the right displays the registered events for that event source.

Important ETT has a problem correctly displaying the list of events for the Speech Engine Services and Telephony Application Services event sources (Events for the Telephony Application Services Host event source display correctly in ETT.). When you select either the Speech Engine Services or Telephony Application Services event sources, the list of events appears similar to the events shown in Figure 5.

Figure 5 - MSS events displayed incorrectly for Telephony Application Services.

Although the Speech Engine Services and Telephony Application Services MSS events are not displayed correctly in ETT, you can still use ETT to select any MSS event to configure it to generate an SNMP trap. To do so, you must know the event ID for the event you want to configure without the assistance of ETT displaying the details of the event. For event sources that have this problem, use Appendix C: MSS Events to find the event ID of the event you want to configure.
In Events, select an event that you want to monitor with an SNMP trap, and then click Add. If you are selecting events for the Speech Engine Services of Telephony Application Services event sources, use Appendix C: MSS Events to find the event ID of the event you want to configure.
In Properties, specify when to generate the trap for the event, if necessary. You can specify whether to generate a trap every time the event is logged or to generate a trap only after the same event is logged a specified number of times during a specified time interval.
Click OK. The selected event appears in Events to be translated to traps (see Figure 6).

Figure 6 - Event ID 1538 correctly configured to generate a trap in ETT.
Continue adding events that you want to monitor by repeating Steps 3-4.
Click Apply to save the trap configuration for the events.

To export a .cnf file:

In Events to be translated to traps, select the events you want to export to a configuration file.
Click Export.
Save the file to a location on the local computer. You can use this file to configure SNMP traps on other computers using the evntcmd.exe command.

Using evntcmd.exe To Translate Events to Traps

The evntcmd.exe command is a command-line tool you can use to configure SNMP to generate traps for events specified in the .cnf file. For an example of a .cnf file, see Appendix B: Sample .cnf File. You can also export this file from the ETT tool. The eventcmd.exe command is installed when you install the Windows SNMP service.

One of the advantages to using this command over using ETT is that you can configure multiple computers to be monitored in the same way, using the same .cnf file. ETT only allows you to configure the local computer.

For more information on the eventcmd.exe command, see Appendix A: How to Use evntcmd.exe

To translate events to traps using eventcmd.exe

Click Start, and then click Run.
Type cmd, and then click OK.
In the command window, browse to the directory containing the events.cnf file and type evntcmd.exe /s ComputerName events.cnf where ComputerName is the name or IP address of the computer on which you want to configure the SNMP traps. Press ENTER. If you do not specify a computer, the configuration occurs on the local computer.

Configuring SNMP Trap Destinations

SNMP traps must be configured to be sent to one or more specified destination computers where the traps are received by an SNMP management console application. To configure SNMP trap destinations, you can use either the Services MMC snap-in to modify the properties of the SNMP service or use the evntcmd.exe command, which uses the .cnf file to specify the trap destinations.

You must know the SNMP community name and either the host name or IP address of the destination computer to configure SNMP trap destinations.

Using the SNMP Service Properties to Configure SNMP Trap Destinations

To direct where the SNMP service sends traps, modify the Properties of the SNMP service in the Services MMC snap-in

To configure trap destinations by modifying the SNMP Service Properties

Open the Services MMC snap-in.
In the Details pane, click SNMP Service.
On the Action menu, click Properties.
On the Traps tab, under Community name, type the case-sensitive community name to which this computer will send trap messages, and then click Add to list.
In Trap destinations, click Add.
In Host name, IP or IPX address, type information for the host, and click Add.
Repeat steps 4 through 6 until you have added all the communities and trap destinations you want.

Using evntcmd.exe to Configure SNMP Trap Destinations

To configure SNMP trap destinations using the eventcmd.exe command, modify the .cnf file to include lines that use the ADD_TRAP_DEST parameter.

The syntax for using the ADD_TRAP_DEST parameter is:

#pragma ADD_TRAP_DEST CommunityName HostID

where CommunityName specifies, by name, the community in which traps are sent and HostID specifies, by name or IP address, the host to which the traps are sent.

Add one or more ADD_TRAP_DEST entries to the .cnf file and then run eventcmd.exe from the command line to configure the trap destinations.

For more information on the eventcmd.exe command, see Appendix A: How to Use evntcmd.exe

Top of page

Monitoring MSS with SNMP

After you have used ETT or evntcmd.exe, your MSS server will generate SNMP traps for the selected events and these traps can be monitored with the SNMP management console of your choice via the Windows SNMP service.

The snmputil.exe command line tool, available in the Windows 2000 Resource Kit, can assist you in monitoring traps. At a command prompt, type,

snmputil trap

and snmputil.exe remains running in the command prompt window, waiting for traps. If a trap is generated, the values of the trap are displayed.

Figure 7 - snmputil.exe shown monitoring a trap generated by an MSS event

Top of page

Appendix A: How to Use evntcmd.exe

The usage of evntcmd.exe is as follows:

Syntax

evntcmd [/s ComputerName] [/v VerbosityLevel] [/n] FileName

Parameters

/s ComputerName

Specifies, by name, the computer on which you want to configure the translation of events to traps, trap destinations, or both. If you do not specify a computer, the configuration occurs on the local computer.

/v VerbosityLevel

Specifies which types of status messages appear as traps and trap destinations are configured. This parameter must be an integer between 0 and 10. If you specify 10, all types of messages appear, including tracing messages and warnings about whether trap configuration was successful. If you specify 0, no messages appear.

/n

Specifies that the SNMP service should not be restarted if this computer receives trap configuration changes.

FileName

Specifies, by name, the configuration file that contains information about the translation of events to traps and trap destinations you want to configure.

/?

Displays help at the command prompt.

Remarks

If you want to configure traps but not trap destinations, you can create a valid configuration file by using the ETT (see description earlier in this document). You can use the ETT to easily create a configuration file and then use the configuration file with evntcmd.exe at the command prompt to quickly configure traps on multiple computers.
The syntax for configuring a trap is as follows:
```
#pragma ADD EventLogFile EventSource EventID [Count [Period]]
```
- The text #pragma must appear at the beginning of every entry in the file.
- The parameter ADD specifies that you want to add an event to trap configuration.
- The parameters EventLogFile, EventSource, and EventID are required. The parameter EventLogFile specifies the file in which the event is recorded (e.g., Application, Security, System). The parameter EventSource specifies the application that generates the event. The EventID parameter specifies the unique number that identifies each event. To find out what values correspond to particular events, use ETT or for the MSS events that exhibit the incompatibility problem described earlier, use the table of MSS events in the Appendix.
- The Count parameter is optional, and it specifies how many times the event must occur before a trap message is sent. If you do not use the Count parameter, the trap message is sent after the event occurs once.
- The Period parameter is optional, but it requires you to use the Count parameter. The Period parameter specifies a duration of time (in seconds) during which the event must occur the number of times specified by the Count parameter before a trap message is sent. If you do not use the Period parameter, a trap message is sent after the event occurs the number of times specified by the Count parameter, no matter how much time elapses between occurrences.
The syntax for removing a trap is as follows:
```
#pragma DELETE EventLogFile EventSource EventID
```
- The text #pragma must appear at the beginning of every entry in the file.
- The parameter DELETE specifies that you want to remove an event to trap configuration.
The syntax for configuring a trap destination is as follows:
```
#pragma ADD_TRAP_DEST CommunityName HostID
```
- The text #pragma must appear at the beginning of every entry in the file.
- The parameter ADD_TRAP_DEST specifies that you want trap messages to be sent to a specified host within a community.
- The parameter CommunityName specifies, by name, the community in which trap messages are sent.
- The parameter HostID specifies, by name or IP address, the host to which you want trap messages to be sent.
The syntax for removing a trap destination is as follows:
```
#pragma DELETE_TRAP_DEST CommunityName HostID
```
- The text #pragma must appear at the beginning of every entry in the file.
- The parameter DELETE_TRAP_DEST specifies that you do not want trap messages to be sent to a specified host within a community.

Examples

The following examples illustrate entries in the configuration file for the evntcmd command. They are not designed to be typed at a command prompt.

To send a trap message when the Speech Engine Services service is stopped or started, type:

#pragma ADD “Application” "Speech Engine Services" 0

To send a trap message if the Speech Engine Services service is stopped or started twice in three minutes, type:

#pragma ADD “Application” "Speech Engine Services" 0 2 180

To stop sending a trap message whenever the Speech Engine Services service is stopped or started, type:

#pragma DELETE “Application” "Speech Engine Services" 0

To send trap messages within the community named Public to the host with the IP address 192.168.100.100, type:

#pragma ADD_TRAP_DEST public 192.168.100.100

To send trap messages within the community named Private to the host named Host1, type:

#pragma ADD_TRAP_DEST private Host1

To stop sending trap messages within the community named Private to the same computer on which you are configuring trap destinations, type:

#pragma DELETE_TRAP_DEST private localhost

Top of page

Appendix B: Sample .cnf File

Use a .cnf file with the evntcmd.exe command to configure the SNMP service to generate traps for MSS events. The following is the contents of a sample .cnf file that contains events that Microsoft recommends for monitoring:

#pragma add "Application" "Speech Engine Services" 334 1 0
#pragma add "Application" "Speech Engine Services" 335 1 0
#pragma add "Application" "Speech Engine Services" 640 1 0
#pragma add "Application" "Speech Engine Services" 1366 1 0
#pragma add "Application" "Speech Engine Services" 1537 1 0
#pragma add "Application" "Speech Engine Services" 1546 1 0
#pragma add "Application" "Speech Engine Services" 1603 1 0
#pragma add "Application" "Speech Engine Services" 1604 1 0
#pragma add "Application" "Speech Engine Services" 1667 1 0
#pragma add "Application" "Speech Engine Services" 1670 1 0
#pragma add "Application" "Speech Engine Services" 1671 1 0
#pragma add "Application" "Speech Engine Services" 1806 1 0
#pragma add "Application" "Telephony Application Services" 8 1 0
#pragma add "Application" "Telephony Application Services" 9 1 0
#pragma add "Application" "Telephony Application Services" 21 1 0
#pragma add "Application" "Telephony Application Services" 39 1 0
#pragma add "Application" "Telephony Application Services" 352 1 0
#pragma add "Application" "Telephony Application Services" 353 1 0
#pragma add "Application" "Telephony Application Services" 354 1 0
#pragma add "Application" "Telephony Application Services" 355 1 0
#pragma add "Application" "Telephony Application Services" 356 1 0
#pragma add "Application" "Telephony Application Services" 357 1 0
#pragma add "Application" "Telephony Application Services" 358 1 0
#pragma add "Application" "Telephony Application Services" 359 1 0
#pragma add "Application" "Telephony Application Services" 360 1 0
#pragma add "Application" "Telephony Application Services" 361 1 0
#pragma add "Application" "Telephony Application Services" 1808 1 0
#pragma add "Application" "Telephony Application Services" 2070 1 0
#pragma add "Application" "Telephony Application Services" 2075 1 0
#pragma add "Application" "Telephony Application Services" 2076 1 0
#pragma add "Application" "Telephony Application Services" 2078 1 0
#pragma add "Application" "Telephony Application Services" 2079 1 0
#pragma add "Application" "Telephony Application Services" 2080 1 0
#pragma add "Application" "Telephony Application Services" 2081 1 0
#pragma add "Application" "Telephony Application Services" 2082 1 0
#pragma add "Application" "Telephony Application Services" 2083 1 0
#pragma add "Application" "Telephony Application Services" 8196 1 0
#pragma add "Application" "Telephony Application Services" 8213 1 0
#pragma add "Application" "Telephony Application Services" 8217 1 0
#pragma add "Application" "Telephony Application Services" 8218 1 0
#pragma add "Application" "Telephony Application Services" 8219 1 0
#pragma add "Application" "Telephony Application Services" 8222 1 0
#pragma add "Application" "Telephony Application Services Host" 3221229571 1 0
#pragma add "Application" "Telephony Application Services Host" 3221229575 1 0
#pragma add "Application" "Telephony Application Services Host" 3221229576 1 0
#pragma add "Application" "Telephony Application Services Host" 3221229577 1 0
#pragma add "Application" "Telephony Application Services Host" 3221229586 1 0
#pragma add "Application" "Telephony Application Services Host" 3221233665 1 0
#pragma add "Application" "Telephony Application Services Host" 3221233666 1 0
#pragma add "Application" "Telephony Application Services Host" 3221233667 1 0
#pragma add "Application" "Telephony Application Services Host" 3221233669 1 0
#pragma add "Application" "Telephony Application Services Host" 3221233670 1 0

Top of page

Appendix C: MSS Events

The Rec. trap column suggests which events are recommended to be configured for trap generation.

Event Source	Event ID	Severity	Message Description	Rec. trap
Telephony Application Services Host	0	Error	TAS detected an invalid Operating System and could not continue. Microsoft Speech Server is supported only on Microsoft Windows Server 2003 or above.
Telephony Application Services Host	1	Error	TAS was unable to initialize the worker process for the following reason: %1. Try restarting TAS, rebooting the computer, or reinstalling Microsoft Speech Server.
Telephony Application Services Host	4096	Error	TAS was unable to connect to the Service Control Manager. Try restarting TAS, rebooting the computer, or reinstalling Microsoft Speech Server.
Telephony Application Services Host	4097	Error	The host process TAS.exe cannot be run as an application. Use the Microsoft Management Console (MMC) snap-in for MSS to run "Telephony Application Services".
Telephony Application Services Host	4098	Error	TAS was unable to initialize the worker process for an undetermined reason. Try restarting TAS, rebooting the computer, or reinstalling Microsoft Speech Server.
Telephony Application Services Host	4099	Error	TAS was unable to create a worker process. Try restarting TAS, rebooting the computer, or reinstalling Microsoft Speech Server.	X
Telephony Application Services Host	4100	Warning	The TAS worker process did not close within the allotted time, and had to be shut down.
Telephony Application Services Host	4101	Warning	This evaluation version of Microsoft Speech Server will expire on %2/%3/%1. Please obtain a full version to continue using this product.
Telephony Application Services Host	4102	Error	This evaluation version of Microsoft Speech Server expired on %2/%3/%1. Please obtain a full version to continue using this product.
Telephony Application Services Host	4103	Error	One or more configuration settings for TAS is inaccessible, invalid or missing. Please check that the service is correctly installed and configured.	X
Telephony Application Services Host	4104	Error	The configuration could not be updated because one or more configuration settings for TAS is inaccessible, invalid or missing. Please check that the server service is correctly installed and configured.	X
Telephony Application Services Host	4105	Error	TAS can no longer detect configuration changes. Stop and restart TAS.	X
Telephony Application Services Host	4113	Informational	A scheduled worker process recycle has occurred.
Telephony Application Services Host	4114	Error	A worker process unexpectedly stopped running and will be replaced.	X
Telephony Application Services Host	4115	Informational	A worker process recycle was requested via the Service Control Manager.
Telephony Application Services Host	4116	Informational	An Application Domain recycle was requested via the Service Control Manager.
Telephony Application Services Host	4117	Informational	A Managed Heap garbage collection was requested via the Service Control Manager.
Telephony Application Services Host	4118	Warning	A worker process did not start within the allotted time and has been stopped. Another attempt will be made to start a worker process. If the process continues to fail, TAS may stop running.
Telephony Application Services Host	4120	Informational	A request to refresh the start page of all inactive SALT interpreters was received via the Service Control Manager.
Telephony Application Services Host	4121	Informational	A worker process recycle has occurred due to a change in the recording directory configuration setting.
Telephony Application Services Host	4128	Warning	TAS received an unsupported Service Control Manager command: %1. The command was ignored.
Telephony Application Services Host	4129	Informational	TAS is resuming after a pause.
Telephony Application Services Host	4130	Informational	TAS is preparing to pause.
Telephony Application Services Host	4131	Success	TAS paused successfully.
Telephony Application Services Host	4132	Success	TAS started successfully.
Telephony Application Services Host	4133	Informational	TAS is preparing to start.
Telephony Application Services Host	4134	Informational	TAS is preparing to stop.
Telephony Application Services Host	4135	Success	TAS stopped successfully.
Telephony Application Services Host	4136	Success	TAS has resumed after being paused.
Telephony Application Services Host	4137	Error	Microsoft Speech Server could not detect a valid product ID, and is shutting down. Please obtain a licensed version of the product and reinstall. Further information for support personnel follows: %1.
Telephony Application Services Host	4138	Error	Failed to create directory "%1" for temporarily storing recorded audio files. The following error may provide more information: %2
Telephony Application Services Host	4139	Warning	Failed to remove directory "%1" for temporarily storing recorded audio files. This directory may need to be manually removed.
Telephony Application Services Host	4140	Warning	Path "%1" for temporarily storing recorded audio files already exists as a file.
Telephony Application Services Host	4141	Error	Directory "%1" for temporarily storing recorded audio files doesn't exist or couldn't be accessed. The following error may provide more information: %2
Telephony Application Services Host	4142	Error	The absolute length for the temporary recorded audio location is more than the allowed maximum of 190 characters.
Telephony Application Services Host	8193	Error	TAS was unable to initialize the worker process because of low memory. Try restarting TAS, rebooting the computer, or reinstalling Microsoft Speech Server.	X
Telephony Application Services Host	8194	Error	TAS was unable to create one or more SALT interpreter instances for the following reason: %1. Try restarting TAS, rebooting the computer, or reinstalling Microsoft Speech Server.	X
Telephony Application Services Host	8195	Error	TAS was unable to close one or more SALT interpreter instances for the following reason: %1. Try restarting TAS, rebooting the computer, or reinstalling Microsoft Speech Server.	X
Telephony Application Services Host	8197	Error	TAS was unable to connect to the Common Language Runtime environment: the error returned was %1. Try restarting TAS, rebooting the computer, or reinstalling Microsoft Speech Server. If this fails to address the problem, reinstall the operating system.	X
Telephony Application Services Host	8198	Error	The host process TAS.exe stopped running unexpectedly.	X
Telephony Application Services Host	8199	Error	The TASWorker.exe file cannot be run as an application.
Telephony Application Services Host	8200	Warning	TAS has successfully modified the maximum number of worker threads to %1 threads.
Telephony Application Services Host	8201	Warning	Setting the maximum number of threads failed. The system should continue to function correctly, however system performance may be affected. If a change in performance is detected, contact Product Support.
Telephony Application Services	4	Informational	The SALT interpreter has downloaded and successfully compiled the scripts for this page.
Telephony Application Services	5	Warning	The SALT interpreter could not use the passed value %4 for attribute %3 of SALT element %1 for the following reason: %5 The interpreter will use the default value '%2' instead.
Telephony Application Services	8	Error	The SALT interpreter is stopping the current application from running as a result of the following exception: %1.	X
Telephony Application Services	9	Error	The SALT interpreter was unable to load the application Start page and will try again every %1 seconds. Until the page is successfully loaded, calls may be rejected. The exception returned was: %2.	X
Telephony Application Services	21	Error	The SALT interpreter was unable to load the start page '%1' as specified in the notification message queue. The exception returned was: %2.	X
Telephony Application Services	10	Informational	The SALT interpreter has loaded the application Start page %1.
Telephony Application Services	11	Error	The SALT interpreter was unable to load the application Start page for the following reason: %1.
Telephony Application Services	12	Warning	No inbound startpage is configured, and TAS is unable to answer calls. Set the StartPageIn property or use the Speech Server MMC snap-in to configure a Start Page for TAS.
Telephony Application Services	16	Warning	There was no end element for %1 beginning at line %2, position %3. The SALT interpreter has assumed the element to be implicitly closed.
Telephony Application Services	17	Warning	The SALT interpreter ignored end element %1 at line %2, position %3.
Telephony Application Services	18	Warning	The value of attribute '%1' should be enclosed in quotes at line %2, position %3.
Telephony Application Services	19	Error	The SALT interpreter stopped responding after %2 seconds during the following operation: %1. As a result, the application has stopped running and the call has been disconnected.
Telephony Application Services	25	Warning	The value for the attribute %3 of element %1 is not within the allowed range. The SALT interpreter is using %2 instead.
Telephony Application Services	32	Warning	The value for the attribute %3 of element %1 is not within the allowed range. The SALT interpreter is using %2 instead.
Telephony Application Services	2074	Warning	The SALT interpreter encountered an invalid boolean value for attribute %2 in element %1, and will use the default value %3 instead.
Telephony Application Services	33	Warning	The resource at %1 could not be found. The SALT interpreter will ignore the error and continue to download the page
Telephony Application Services	34	Warning	The SALT interpreter could not delete all the contents of the recording directory %1. The files may be in use by another process, or the account may not have sufficient privileges to perform this operation. Manually delete any files left in the directory to ensure no confidential information remains.
Telephony Application Services	35	Error	The SALT interpreter could not create a recording directory with the path %1. The value assigned to the RecordingDirectory configuration setting may not be valid, or may point to a directory that TAS cannot access.
Telephony Application Services	36	Warning	Event name %2 is not valid for element %1 and could not be attached or detached.
Telephony Application Services	37	Warning	The referenced function is not valid for event %2 of element %1 and could not be attached or detached.
Telephony Application Services	38	Warning	Event name %2 is not defined for element %1 and could not be detached.
Telephony Application Services	39	Error	The SALT interpreter could not find a recording directory with the path %1. The value assigned to the RecordingDirectory configuration setting may not be valid, or may point to a directory that TAS cannot access.	X
Telephony Application Services	40	Error	The SALT interpreter is navigating to the error page as a result of the following exception: %1.
Telephony Application Services	41	Warning	The application error page '%1' could not be loaded for the following reason: '%2'. TAS will continue to run the application without an error page.
Telephony Application Services	42	Warning	A caller disconnected during download of '%1' which took longer than %2 seconds to complete. Further information may be available in the log entries for the web server.
Telephony Application Services	43	Warning	A caller disconnected after %2 seconds while TAS was connecting to SES at '%1'. Further information may be available in the event trace logs for TAS or SES.
Telephony Application Services	262	Warning	The application attempted to call %1 on %2, but was unsuccessful because %2 is not active.
Telephony Application Services	263	Warning	The application attempted to call Start() on %1, but was unsuccessful because another %2 is still active.
Telephony Application Services	264	Warning	The application attempted to call Start() on %1, but was unsuccessful because a call has not yet been connected.
Telephony Application Services	312	Warning	The application requested language %2, but the current page is configured to use %1. Ensure that the xml:lang attribute of the SALT elements matches the HTML xml:lang attribute of the page.
Telephony Application Services	349	Error	TAS did not have sufficient privileges to delete file %1 for the following reason: '%2'.
Telephony Application Services	351	Warning	TAS was unable to record to folder %1 because the folder is invalid. TAS will use the default recording folder %2 instead.
Telephony Application Services	352	Error	A call failed because the value for the TAS EngineAttributes property is not valid. The following error was returned: %1: "%2"	X
Telephony Application Services	353	Error	A call failed because SES could not find a recognition engine with the required attributes. The following error was returned: %1: "%2" Please ensure that TAS and SES are configured correctly.	X
Telephony Application Services	354	Error	A call failed because SES URL '%1' could not be found. Please ensure that the TAS SpeechServer property is correct. The following error was returned: %2: "%3"	X
Telephony Application Services	355	Error	TAS was unable to answer a call. The following error was returned from SES URL '%1': %2: "%3"	X
Telephony Application Services	356	Error	A call failed because SES URL %1 is invalid. Please ensure that the TAS SpeechServer property is correct. The following error was returned: %2.	X
Telephony Application Services	357	Error	The Telephony Interface Manager was unable to record audio to file %1. This could be caused by loss of the directory or lack of access permissions. Ensure that the folder specified by the Temporary Audio File Location is valid, and has the appropriate permissions.	X
Telephony Application Services	358	Error	A call failed because TAS had insufficient privileges to access %1. The following error was returned: %2: "%3". Further information may be available in the log entries for SES.	X
Telephony Application Services	359	Error	A call was terminated unexpectedly because of the following error: %1: "%2"	X
Telephony Application Services	360	Error	A call failed because of a SES error. The following error was returned: %1: "%2". Further information may be available in the log entries for SES.	X
Telephony Application Services	361	Error	A call failed because SES could not find a speech output engine with the required engine attributes. The following error was returned: %1: "%2" Please ensure that TAS and SES are configured correctly.	X
Telephony Application Services	522	Warning	The SALT interpreter encountered %1 compiler warnings: %2.
Telephony Application Services	523	Informational	The application script at %1 has been compiled and cached to %2
Telephony Application Services	524	Warning	The application script at %1 was marked as cacheCompiled, but compilation failed. TAS will attempt to recompile the script without caching.
Telephony Application Services	525	Informational	The application script has been cached.
Telephony Application Services	526	Informational	The SALT interpreter has recompiled the application script because the script changed since the last download. If the script is dynamically generated, performance will be adversely affected.
Telephony Application Services	533	Warning	The SALT interpreter encountered unsupported MIME type %1 in line %2 of the application page. The interpreter cannot use this script; the application will continue to run but may have unexpected results.
Telephony Application Services	534	Warning	The SALT interpreter detected dynamic script content for the following url: %1. To identify the dynamic content, review the versions of the script (%2) that were saved to: %3. These files will be deleted during the next Application Domain recycle. Dynamic script may negatively impact performance. Refer to the MSS help files for tips on avoiding dynamic script content.
Telephony Application Services	770	Warning	Invalid MIME type '%1' in page '%3' on line %2 /nl The SALT interpreter encountered unsupported MIME type %1 in line %2 of the application page %3. The interpreter cannot use this script; the application will continue to run but may have unexpected results
Telephony Application Services	771	Warning	The namespace %1 specified in element %2 is invalid. The interpreter will ignore any elements that are bound to this namespace.
Telephony Application Services	774	Warning	The specified character set %2 is invalid, because of this reason: %1.
Telephony Application Services	777	Warning	The element %1 is not a supported SALT element.
Telephony Application Services	784	Warning	The SALT interpreter encountered invalid MIME type %1 in the "enctype" attribute of Form element %2, and substituted the default MIME type %3. As a result, the uploaded audio file may be rejected by the server. Valid MIME types are: %4, %5.
Telephony Application Services	785	Warning	The element '%1' on line %2 of this page is a SALT element but is not bound to the SALT namespace. The SALT interpreter will ignore the element. /n One possible reason for this error is that the prefix is missing from an element in an inline prompt or grammar created using the Microsoft Speech Application SDK. If this element is intended to be used as a SALT element, try adding the predefined prefix "salt:" or binding to the namespace "%3".
Telephony Application Services	786	Warning	The element '%1' on line %2 of the text passed to a SALT prompt element is a SALT element but is not bound to the SALT namespace. The SALT interpreter will ignore the element.One possible reason for this error is that the prefix is missing from an element returned by a prompt function created using the Microsoft Speech Application SDK. If this element is intended to be used as a SALT element, try adding the predefined prefix "salt:" or binding to the namespace "%3".
Telephony Application Services	787	Warning	The element '%1' on line %2 of an external prompt resource file (%4) is a SALT element but is not bound to the SALT namespace. The SALT interpreter will ignore the element. If this element is intended to be used as a SALT element, try binding to the namespace "%3".
Telephony Application Services	788	Warning	An attempt to navigate to a previously visited page was unsuccessful for the following reason: The history.go() argument, %1, is invalid.
Telephony Application Services	789	Warning	An attempt to navigate to a previously visited page was unsuccessful for the following reason: The history.go() argument, %1, was not in the history list. Ensure that the URL matches the target exactly.
Telephony Application Services	1046	Error	The SALT interpreter was unable to load grammars for Listen element %1 for the following reason: "%2"
Telephony Application Services	1049	Error	The SALT interpreter was unable to process a recognition result for Listen element %1 for the following reason: "%2"
Telephony Application Services	1059	Error	The SALT interpreter was unable to activate or deactivate the specified rule for Listen element %1, because the referenced grammar %2 could not be found.
Telephony Application Services	1060	Error	The SALT interpreter was unable to activate or deactivate the specified rule for Listen element %1, because no grammar name was specified.
Telephony Application Services	1062	Error	The SALT interpreter was unable to apply the binding specified in element %2 to element %1 for the following reason: %3
Telephony Application Services	1066	Error	The SALT interpreter encountered invalid MIME type %2 in Listen element %1, and was unable to begin recording. Valid MIME types are: %3.
Telephony Application Services	1067	Error	The contents of the param element 'nbest' in Listen element %1 are invalid. The SALT interpreter will use the default value of %2 instead.
Telephony Application Services	1068	Error	Grammar element %3 requested language %2, but the current page is configured to use %1. Ensure that the xml:lang attribute of the SALT elements matches the HTML xml:lang attribute of the page.
Telephony Application Services	1290	Error	The SALT interpreter was unable to parse the prompt string in Prompt element %1 for the following reason: "%2"
Telephony Application Services	1292	Error	The SALT interpreter was unable to process either the name or the content of the param element in Prompt element %1 for the following reason: "%2"
Telephony Application Services	1293	Warning	The SALT interpreter encountered an invalid bargeintype in Prompt element %1, and will use the default value %2 instead.
Telephony Application Services	1295	Error	The SALT interpreter encountered an invalid parameter (%2) for method %3 in Prompt element %1.
Telephony Application Services	1296	Error	A method (%2) was called on Prompt element %1 in the application error page. Error page prompts must be played from a local file.
Telephony Application Services	1298	Warning	Element '%1': The target element %2 referenced by value element cannot be found and was ignored.
Telephony Application Services	1305	Error	Prompt string given is not a valid XML fragment. Please ensure that XML reserved characters (such as '&' and '<') are escaped where appropriate (for example, with & and < respectively). The reason given is: %2 The prompt string is: %1
Telephony Application Services	1306	Warning	Element '%1': Attribute '%3' on element '%2' referenced by value element does not exist, and was ignored.
Telephony Application Services	1307	Warning	The SALT interpreter encountered the following error with the content element in Prompt element %1: %2. The optional inline prompt was used instead.
Telephony Application Services	1308	Warning	The SALT interpreter was unable to download any audio files for the application error page.
Telephony Application Services	1309	Warning	Element '%1': Content tags on the error page should reference external audio files. Speech synthesis (TTS) will not be available on the error page.*** The Prompt element %1 on the application error page contained one or more content elements without a specified audio file. Speech synthesis will not be available for the error page.
Telephony Application Services	1310	Warning	TAS encountered the following error in the prompt queue: %1
Telephony Application Services	1808	Error	The xml message sent to smex element %1 was not well-formed and could not be accepted. This may indicate an issue with the Telephony Interface Manager. The body of the message was: "%2"	X
Telephony Application Services	1809	Error	The SALT interpreter was unable to apply the binding specified in element %2 to element %1 for the following reason: %3
Telephony Application Services	1810	Error	The SALT interpreter found more than one %1 param element on the smex element %2. Only one param element of this type is allowed.
Telephony Application Services	1811	Error	The SALT interpreter encountered a smex element (%1) with no assembly information specified.
Telephony Application Services	1812	Error	The SALT interpreter encountered a smex element (%1) with no class information specified.
Telephony Application Services	1813	Error	TAS could not find the assembly '%1'. Please ensure that it is present in the global assembly cache and the fully qualified assembly name is being used on the page.
Telephony Application Services	1814	Error	TAS could not find the class '%1' in the assembly '%2'. Please ensure that the class and assembly information is specified correctly.
Telephony Application Services	1815	Error	The smex element '%1' is referencing the same underlying object as the smex element '%2'.
Telephony Application Services	2070	Error	TAS was unable to download the audio file at %1, for the following reason: "%2"	X
Telephony Application Services	2071	Error	TAS was unable to access file %1 while processing input element %2 for the following reason: "%3"
Telephony Application Services	2075	Error	An exception was thrown while trying to write to the Telephony Server performance counters. The values of the performance counters may not now be accurate. The error reported was: "%1"	X
Telephony Application Services	2076	Error	TAS is performing an unscheduled worker process recycle because it encountered a fatal error while trying to access the TIM. Please ensure that the TIM is working correctly. The error reported was: %1, %2. Further trace information for support personnel follows:	X
Telephony Application Services	2077	Informational	The SALT application attempted to open a modal dialog box with the following message: %1
Telephony Application Services	2078	Error	TAS is performing an unscheduled worker process recycle. Further trace information for product support follows:	X
Telephony Application Services	2079	Error	TAS is performing an unscheduled worker process recycle because the pagefile usage %1 exceeds the limit %2. This could indicate that the process memory limit is too low. Adjust the value of the ProcessMemoryLimit property or use the Speech Server MMC snap-in to ensure that the process memory limit is correct.	X
Telephony Application Services	2080	Error	TAS is performing an unscheduled worker process recycle because a second forced app domain recycle was requested within %1 minutes. This could indicate that the memory limit is too low. Adjust the value of the LoadMemoryLimit property or use the Speech Server MMC snap-in to ensure that the Memory Limit is correct.	X
Telephony Application Services	2081	Error	TAS is performing an unscheduled worker process recycle because the following directory "%1" couldn't be created. Further trace information for product support follows:	X
Telephony Application Services	2082	Error	TAS is performing an unscheduled worker process recycle, and may have aborted some calls, because it has run out of memory. This could indicate that the RecycleCallLimit or LoadMemoryLimit properties are too high. Use the Speech Server MMC snap-in to ensure that their values are correct.	X
Telephony Application Services	2083	Error	TAS is performing an unscheduled worker process recycle because the available virtual bytes %1 dropped below the minimum limit %2. This could indicate that the RecycleCallLimit or LoadMemoryLimit properties are too high. Use the Speech Server MMC snap-in to ensure that their values are correct.	X
Telephony Application Services	2084	Warning	TAS is throttling the number of interpreters because the current memory usage %1 exceeds the LoadMemoryLimit %2. This could indicate that the application is consuming too much memory or that the LoadMemoryLimit property is too low. Use the Speech Server MMC snap-in to ensure that the value is correct.
Telephony Application Services	2085	Warning	TAS is performing an unscheduled application domain recycle because the current memory usage exceeds the LoadMemoryLimit and the number of interpreters cannot be reduced any further. This could indicate that the application is consuming too much memory or that the LoadMemoryLimit property is too low. Use the Speech Server MMC snap-in to ensure that the value is correct.
Telephony Application Services	4102	Error	The SALT interpreter encountered an error in element %1 when invoking method %2 on %3., for the following reason: %4. ***
Telephony Application Services	4103	Error	The targetelement attribute is missing in bind element %1 at line %2.
Telephony Application Services	4104	Error	The node %2 specified by the bind element %1 at line %3 does not exist. The bind has failed.
Telephony Application Services	4105	Error	The target element %2 specified by the bind element %1 at line %3 does not exist. The bind has failed.
Telephony Application Services	4106	Warning	The method %3 of element %4 at line %5 could not be invoked because targetattribute='%2' has also been specified.
Telephony Application Services	4352	Error	The method %2 called on element %3 by element %1 does not exist. The method was referenced at line %4.
Telephony Application Services	4353	Error	The method %2 called on element %3 by element %1 could not be invoked: methods used for binding may not take any parameters. The method was referenced at line %4.
Telephony Application Services	4354	Warning	The value %2 of the targetattribute attribute in element %1 contains invalid characters in line %3.
Telephony Application Services	8194	Warning	Some applications did not close during a recycle or shutdown of an application domain. Some callers may have been disconnected if the call duration exceeded the configured shutdown timeout period.
Telephony Application Services	8196	Error	TAS encountered a fatal error while trying to initialize the TIM. The error reported was: %1; %2. Please ensure that the TIM is installed and working correctly. Further trace information for support personnel follows:	X
Telephony Application Services	8197	Error	TAS encountered a fatal error during initialization: "%1". Please check that the service is correctly installed and configured. Further trace information for product support follows:
Telephony Application Services	8198	Error	TAS encountered a fatal error when attempting to pause: "%1". The service will shut down immediately, and some callers may be disconnected. Please check that the service is correctly installed and configured. Further trace information for product support follows:
Telephony Application Services	8199	Error	TAS encountered a fatal error when attempting to stop: "%1". The service will shut down immediately, and some callers may be disconnected. Please check that the service is correctly installed and configured. Further trace information for product support follows:
Telephony Application Services	8202	Warning	The application error page URL %1 could not be resolved, for the following reason: '%2'. TAS will continue to run the application without an error page.
Telephony Application Services	8203	Warning	An attempt was made to navigate to %1 from the application error page. This is not supported. TAS will continue to run the application.
Telephony Application Services	8204	Warning	The application error page contained a reference to error page %1. This is not supported. TAS will continue to run the application.
Telephony Application Services	8205	Warning	The application contained references to multiple error pages. This is not supported. TAS will ignore the error page specified at %1, and continue running the application.
Telephony Application Services	8206	Warning	TAS was unable to play the application error page audio file %1, for the following reason: "%2"
Telephony Application Services	8207	Warning	TAS did not play any audio files for element %1 on the application error page.
Telephony Application Services	8208	Warning	TAS has determined that just-in-time (JIT) debugging is enabled on this machine, which leaves the system vulnerable to denial-of-service attacks. To disable JIT debugging, change the registry setting HKEY_LOCAL_MACHINE\\%1\\%2 to the value %3.
Telephony Application Services	8209	Warning	An invalid configuration setting was detected: %1 Note that configuring Microsoft Speech Server by direct editing of the registry is unsupported.
Telephony Application Services	8210	Error	Microsoft Speech Server could not detect a valid product ID, and is shutting down. Please obtain a licensed version of the product and reinstall. Further information for support personnel follows: %1.
Telephony Application Services	8211	Error	The TIM configuration for outbound channels exceeds the number allowed for this version of Microsoft Speech Server and TAS will not start. Please reconfigure this TIM setting to a value less than or equal to %1.
Telephony Application Services	8212	Error	The TIM configuration for inbound channels exceeds the number allowed for this version of Microsoft Speech Server and TAS will not start. Please reconfigure this TIM setting to a value less than or equal to %1.
Telephony Application Services	8213	Error	TAS was unable to connect to the notification message queue "%1" for the following reason: "%2" Until the problem is corrected, no notifications will be processed.	X
Telephony Application Services	8215	Informational	TAS has connected to the notification message queue "%1" successfully.
Telephony Application Services	8216	Warning	No notification message queue is configured. If an application requires TAS to handle notifications, set the NotificationMessageQueue property or use the Speech Server MMC snap-in to configure a notification message queue for TAS.
Telephony Application Services	8217	Error	TAS was unable to connect to the notification message queue "%1" for the following reason: "%2" Until the queue is correctly configured, no notifications will be processed.	X
Telephony Application Services	8218	Error	TAS was unable to connect to the notification message queue "%1" because it does not exist, or access was denied. TAS will try again every %2 seconds. Until the queue is created, or correctly configured, no notifications will be processed.	X
Telephony Application Services	8219	Error	TAS is unable to process any notification messages because calls are failing to connect. TAS will try again every %1 seconds. One possible reason for this error is that all outbound channels are being used by inbound applications.	X
Telephony Application Services	8220	Informational	TAS has processed a notification message successfully.
Telephony Application Services	8221	Error	TAS cannot process notification message (id "%1") because of an error in the message format. The application must supply notifications which are URLs formatted with the XmlMessageFormatter.
Telephony Application Services	8222	Error	TAS is shutting down as a result of the following fatal error: "%1" Please check that the service is correctly installed and configured. Further trace information for product support follows:	X
Speech Engine Services	1	Warning	SES memory usage is approaching the recommended upper limit. Try reducing the number of SR or TTS engine instances. Reducing the total size of grammars required by your application may also help.
Speech Engine Services	132	Warning	The request to load a resource %1 was denied because the host is not in the Trusted Sites list. To make this resource available to users, add %2 to the Trusted Sites list.
Speech Engine Services	133	Warning	The request to preload a resource from the application manifest %1 was denied because the host is not in the Trusted Sites list. To make the manifest available, add %2 to the Trusted Sites list.
Speech Engine Services	134	Warning	The resource '%1' took more than %2 ms to be prepared for use; end users may experience this as a delay in the application. To decrease the time it takes to download this resource, add it to the application manifest.
Speech Engine Services	135	Warning	The resource '%1' was specified by the application manifest to be preloaded at service startup. This resource is not cacheable and should not be preloaded.
Speech Engine Services	136	Warning	The subgrammar '%1' of grammar '%2' was specified by the application manifest to be preloaded at service startup. This resource is not cacheable and should not be preloaded.
Speech Engine Services	137	Warning	SES has removed the prompt database file '%1' from the disk cache, or was unable to save it, due to insufficient space. Until the file is successfully cached, calls may be lost. Use the Speech Server MMC snap-in to increase the value for "Cache maximum size" in the Speech Services Settings tab.
Speech Engine Services	138	Warning	The SES disk cache for prompt databases is approaching full capacity. If additional prompt databases are downloaded, the cache may become full, and calls may be lost. Use the Speech Server MMC snap-in to increase the value for "Cache maximum size" in the Speech Services Settings tab.
Speech Engine Services	256	Warning	An SR engine instance could not recover from an error and will be shut down. Server capacity may be reduced temporarily while a new instance is created.
Speech Engine Services	334	Error	%1 does not match the name of any installed engine on this server. Update the EngineName property for the %2 engine configuration with a valid, installed SAPI engine name.	X
Speech Engine Services	335	Warning	SES was unable to load the grammar %2 for the following reason: '%1' Until this problem is corrected, any application logic that uses the grammar will fail.	X
Speech Engine Services	512	Warning	A TTS engine instance could not recover from an error and will be shut down. Server capacity may be reduced temporarily while a new instance is created.
Speech Engine Services	640	Warning	SES was unable to load the prompt database %2 for the following reason: '%1' Until this problem is corrected, any prompt request that requires this database will be rendered using TTS	X
Speech Engine Services	1360	Warning	An unexpected exception occurred in %1, with the following message: '%2'.
Speech Engine Services	1361	Warning	Access to SES by account %1 was denied because of insufficient privileges. To grant access to this account, add it to the ACL on Access.txt.
Speech Engine Services	1362	Warning	Access to inline grammars by account %1 was denied because of insufficient privileges. To grant access to this account, add it to the ACL on TrustedAccess.txt.
Speech Engine Services	1363	Warning	Parameters passed by the SALT application for a %1 request caused the operation to fail for the following reason: '%2'.
Speech Engine Services	1364	Warning	SES was unable to process the grammars for the %1 request for the following reason: '%2'.
Speech Engine Services	1365	Warning	SES was unable to connect to the audio stream for a %1 request for the following reason: '%2'. Ensure that the TIM is functioning correctly and is accessible over the network.
Speech Engine Services	1366	Warning	SES was unable to process a speech output request for the following reason: '%1'.	X
Speech Engine Services	1367	Warning	SES was unable to process the %1 request; the SR engine returned an error code of %2. The grammar may not be compatible with the engine being used to service this request.
Speech Engine Services	1368	Warning	SES was unable to process the %1 request for the following reason: '%2'.
Speech Engine Services	1369	Error	No engine instance was available to process the %1 request. To address this problem, increase the number of engine instances for this configuration.
Speech Engine Services	1370	Warning	Administrative access to SES by account %1 was denied because of insufficient privileges. To grant access to this account, add it to the Administrators group for this machine.
Speech Engine Services	1371	Warning	SES prevented the attempted operation due to the following reason: %1.
Speech Engine Services	1372	Warning	SES rejected the incoming audio connection for the following reason: %1.
Speech Engine Services	1536	Informational	SES has terminated the SESWorker process (PID %1).
Speech Engine Services	1537	Error	SES failed to create new SESWorker process due to the following reason: %1.	X
Speech Engine Services	1538	Informational	SES created a new SESWorker process (PID %1).
Speech Engine Services	1539	Warning	SES created a new SESWorker process (PID %1). This worker was already started %2 time(s).
Speech Engine Services	1540	Informational	Active SESWorker process (PID %1) has successfully started and is ready to accept new sessions.
Speech Engine Services	1541	Informational	Idle SESWorker process (PID %1) has successfully started.
Speech Engine Services	1542	Informational	SES detected that SESWorker process (PID %1) has successfully stopped.
Speech Engine Services	1543	Error	SES detected that SESWorker process(PID %1) has terminated unexpectedly. Any sessions that were in progress have been aborted.
Speech Engine Services	1544	Warning	SESWorker process (PID %1) exceeded maximum start timeout and will be terminated.
Speech Engine Services	1545	Warning	SESWorker process (PID %1) exceeded maximum shutdown timeout and will be terminated.
Speech Engine Services	1546	Error	SESWorker process has exceeded maximum number of restarts (%1). SES is unable to recover and will shutdown.	X
Speech Engine Services	1547	Informational	SES WebService has successfully established connection to SES.
Speech Engine Services	1548	Error	SES has no active SESWorker processes available. The new incoming sessions will be rejected.
Speech Engine Services	1549	Warning	SES was unable to activate SESWorker process (PID %1). This process will be recycled.
Speech Engine Services	1585	Warning	The active SESWorker process (PID %1) may have reached the UpperMemoryThreshold, or has detected an error, and will be recycled. If EnableFailoverWorkerProcess=False, this may result in lost calls. (Any lost calls will be logged separately.) If this problem occurs frequently, modify application resources to use less memory.
Speech Engine Services	1601	Warning	SES was unable to process the Service Control request %1 for the following reason: '%2'.
Speech Engine Services	1602	Warning	SES has detected internal problem : '%1'. SES service will exit.
Speech Engine Services	1603	Error	SES was unable to start for the following reason: '%1'.	X
Speech Engine Services	1604	Error	Failed to start an SESWorker instance, because of this reason: %1.	X
Speech Engine Services	1605	Warning	This evaluation version of Microsoft Speech Server will expire on %1. Please obtain a full version to continue using this product.
Speech Engine Services	1606	Warning	SES was unable to shut down for the following reason: '%1'.
Speech Engine Services	1607	Warning	SES was unable to create an instance of configuration %1 because the LowPressureMemoryThreshold limit was exceeded. To address this problem, reduce the number of engine instances or the size of preloaded resources.
Speech Engine Services	1608	Warning	SES was unable to create an instance of the SR engine %1 for the following reason: '%2'.
Speech Engine Services	1609	Warning	SES was unable to create an instance of the TTS engine %1 for the following reason: '%2'.
Speech Engine Services	1610	Warning	SES was unable to create an instance of the DTMF engine %1 for the following reason: '%2'.
Speech Engine Services	1611	Warning	SES was unable to download the application manifest %1 because of the following reason: '%2'. As a result, no grammar or prompt resources were preloaded.
Speech Engine Services	1612	Informational	Preloading of application resources started.
Speech Engine Services	1613	Informational	Preloading of application resources completed.
Speech Engine Services	1614	Warning	The engine configurations '%1' and '%2' load resources from the same application '%3' into different engines ('%4' and '%5'). To resolve this conflict, use the MMC snap-in to change either the Resourceset to Preload or the application name for one of these configurations. You must also update the application manifest file to reflect the change.
Speech Engine Services	1665	Error	This evaluation version of Microsoft Speech Server has expired. Please obtain a full version to continue using this product.
Speech Engine Services	1667	Error	SES was unable to start because of the following configuration error: '%1'. Ensure that SES is correctly installed and configured, and that the WMI services are running.	X
Speech Engine Services	1668	Informational	Configuration successfully updated.
Speech Engine Services	1669	Warning	Configuration update failed for the following reason: '%1'.
Speech Engine Services	1670	Warning	SES was unable to preload some grammar or prompt resources while processing the application manifest, for the following reason '%1'.	X
Speech Engine Services	1671	Error	SES was unable to recycle an engine instance for the following reason: '%1'. To restore the specified number of instances, restart SES.	X
Speech Engine Services	1672	Warning	SES was unable to process the application manifest %1 for the following reason: '%2'. As a result, no grammar or prompt resources were preloaded.
Speech Engine Services	1673	Warning	SES could not find an engine configuration of type %1 which supports application %2 or the Default application. As a result, no grammar or prompt resources for this application were preloaded.
Speech Engine Services	1674	Warning	This server is configured with multiple IP Addresses. SES binds to one specific IP Address, which must be dedicated to this host (not a virtual IP) and reachable by clients. SES is using %1 by default. If this is not appropriate, set the AudioConnectionIP setting to the correct IP address.
Speech Engine Services	1675	Warning	SES was unable to resolve the IP address of this server for the following reason: '%1'. SES is using 127.0.0.1 by default. No other hosts will be able to use SES. If this is not appropriate, change the AudioConnectionIP setting to the correct address.
Speech Engine Services	1676	Informational	SES could not find an engine configuration of type %1 which supports application %2. The resources required by this application have been loaded into the Default engine configuration instead.
Speech Engine Services	1677	Warning	An attempt was made to set the LowerMemoryThreshold limit to a value higher than the UpperMemoryThreshold limit. This is not supported. SES has adjusted the LowerMemoryThreshold value to equal the UpperMemoryThreshold value.
Speech Engine Services	1806	Warning	SES was unable to create a new session for the following reason: '%1'.	X
Speech Engine Services	1807	Informational	SES is starting.
Speech Engine Services	1808	Warning	SES was unable to update setting %1. The SES service needs to be restarted for changes to this setting to take effect.
Speech Engine Services	1809	Warning	SES web service aborted an opened session.
Speech Engine Services	1810	Error	The SESWorker process was unable to create performance counters for the following reason: %1. The process will now exit. SES may need to be reinstalled or repaired.
Speech Engine Services	1811	Error	SES was unable to update performance counters for the following reason: %1. The numbers reported by the counters may be unreliable until the service is restarted.