OpenSwitch log messages server_alloc to tdata_set

Message text	Explanation and action
`server__alloc: Memory allocation failure.`	OpenSwitch encountered a memory allocation failure. Check available memory on the OpenSwitch host and any memory usage limit on the OpenSwitch process. Increase this limit and restart OpenSwitch.
`server_get_prop: Invalid property <property>.`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`server_get_prop: Invalid server name 'NULL'.`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`server_get_prop: Invalid server value 'NULL'.`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`server_init: Unable to create server list mutex.`	This error may be due to insufficient memory. Check that you have adequate system memory. Contact Sybase Technical Support if needed.
`server_set_prop: Invalid property <property>.`	Check that the supplied property is valid. See the OpenSwitch Administration Guide for details.
`server_set_prop: Invalid server name 'NULL'.`	Check that the supplied server name is not NULL. See the OpenSwitch Administration Guide for details.
`server_set_prop: Invalid value for SERVER_P_STATUS.`	Check that Server Status has a valid value (UP, DOWN or LOCKED).
`server_set_prop: Invalid value for SERVER_P_TYPE.`	Check that Server Type has a valid value of HA.
`service__main: Error recording current service state`	Check any previous errors in the OpenSwitch error log.
`service__main: Error recording SERVICE_RUNNING status`	Check any previous errors in the OpenSwitch error log.
`service__main: Error registering control handler`	OpenSwitch was unable to register the control handler Check the application log or event log for additional information about this failure.
`service_init: Cannot find <PATH>/ConfigFile in registry: <ERROR_MSG>`	Check that the configuration file exists in the location pointed to be <PATH>, and that it is the same file used to start the OpenSwitch server. The error string contains more information.
`service_init: Cannot start service dispatcher:`	An error had occurred while connecting the main service thread to the service control manager thread. Check the application log or event log for additional information about this failure.
`service_init: Unable to spawn service management thread`	An error occurred when OpenSwitch tried to spawn a thread to talk to the service manager on Windows. Check the application log or event log for additional information about this failure.
`service_install: Cannot fetch the binary image path: <ERROR_MSG>`	Check that the OpenSwitch binary file OSwitch.exe exists in the location specified by the error (it normally resides in %OPENSWITCH%\bin). The error string contains more information.
`service_install: Cannot set ConfigFile to <PATH>: <ERROR_MSG>`	OpenSwitch was unable to set the configuration file path to the specified path for this registry key. The error string contains more information.
`service_install: Cannot set ImagePath to <PATH>: <ERROR_MSG>`	OpenSwitch was unable to set the binary image path to the specified path for this registry key. The error string contains more information.
`service_install: Failed to create service <SVC_NAME>: <ERROR_MSG>`	OpenSwitch was unable to create a service for the new server. The error string contains more information.
`service_install: Failed to look up key <KEY>`	Check previous errors in the OpenSwitch log file. Check the application log or event log for additional information about this failure.
`service_install: GetModuleFileName() failed`	OpenSwitch was unable to retrieve the fully qualified path for the specified module. Check the application log or event log for additional information about this failure.
`service_install: OpenSCManager() failed: <ERROR_MSG>`	OpenSwitch was unable to access the service control manager database. The error string contains more information.
`service_remove: <SVC_NAME> failed to stop`	OpenSwitch was unable to stop its service on the registry. Check the application log or event log for additional information about this failure.
`service_remove: failed to remove service <SVC_NAME>`	OpenSwitch was unable to remove its service from the registry. Check the application log or event log for additional information about this failure.
`service_remove: OpenSCManager() failed: <ERROR_MSG>`	OpenSwitch was unable to access the service control manager database. The error string contains more information.
`service_remove: OpenService(<SVC_NAME>) failed: <ERROR_MSG>`	OpenSwitch was unable to open the existing service. The error string contains more information.
`service_status: SetServiceStatus(): <ERROR_MSG>`	OpenSwitch was unable to set the service status for its service. The error string contains more information.
`slock_create: <LOCK>: Unable to create exclusive mutex`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`slock_create: <LOCK>: Unable to destroy shared mutex`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`slock_create: <LOCK>: Unable to unlock global lock`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`slock_create: Could not lock global mutex`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`slock_create: Unable to unlock global lock`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`slock_destroy: <MUTEX>: Unable to destroy shared mutex`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`slock_destroy: Could not lock global mutex`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`slock_destroy: Unable to unlock global lock`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`slock_destroy:<MUTEX>: Unable to destroy exclusive mutex`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`slock_exit: <LOCK>: Unable to destroy exclusive mutex`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`slock_exit: <LOCK>: Unable to destroy shared mutex`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`slock_exit: Could not lock global mutex`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`slock_exit: Unable to destroy global mutex`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`slock_init: Unable to create slock_mtx`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`slock_lock: <LOCK>: Unable to unlock exclusive lock`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`slock_lock: <LOCK>: Unable to unlock shared lock`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`slock_unlock: <LOCK>: Unable to unlock exclusive lock '<LOCK>'`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`slock_unlock: <LOCK>: Unable to unlock shared lock`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.
`SRVLIB Fatal Process Error: N<errno.>/S<severity>/T<state>: <errtext>.`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`SRVLIB O/S Error: <os_errorno.>: <os_errortext>.`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`SRVLIB: N<errno.>/S<severity>/T<state>: <errtext>.`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`tdata__alloc: Memory allocation failure`	OpenSwitch encountered a memory allocation failure. Check available memory on the OpenSwitch host and any memory usage limit on the OpenSwitch process. Increase this limit and restart OpenSwitch.
`tdata__alloc: Unable to set user data`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`tdata__free: Unable to clear user data`	This is an internal OpenSwitch error. Contact Sybase Technical Support to report the error.
`tdata_set: Memory allocation failure`	OpenSwitch encountered a memory allocation failure. Check available memory on the OpenSwitch host and any memory usage limit on the OpenSwitch process. Increase this limit and restart OpenSwitch.
`tdata_set: Unable to create new table`	This is an internal OpenSwitch error. Check previous errors in the OpenSwitch log file.