Error messages are sent to the Windows Event Log when the DirectConnect server is started as a Windows service and encounters an error.
Message  | 
Description  | 
|---|---|
2 The DirectConnect server service could not be registered with the Windows service manager.  | 
Indicates an operating system error or a problem with the Windows Registry.  | 
3 DirectConnect server failure while reporting status to Windows service manager.  | 
Indicates an operating system error or a problem with the Windows Registry.  | 
4 DirectConnect server failure creating event for process thread.  | 
Indicates an operating system error or a system resource problem. Check whether excessive processes are presently running.  | 
5 DirectConnect server failure launching process thread.  | 
Indicates an operating system error or a system resource problem. Check whether excessive processes are presently running.  | 
6 DirectConnect server failure constructing system information.  | 
Either the system environment variables are not working properly, or the system is low on memory or other resources. Check the system path syntax and the SYBASEDSLISTEN and environment variables.  | 
7 DirectConnect server could not load the server configuration: <filespec>. The file may be missing.  | 
One or more configuration properties contains an invalid value. If the server was started from a command line, the offending line number is indicated. If the server was started on a Windows system as a Windows service, run the product from the command line and add the -t switch to perform a start-up test. Doing this displays the full error information.  | 
9 DirectConnect server failure constructing the log manager.  | 
The log manager process could not be started. Make sure that the executable exists in the \DC-15_0\bin directory.  | 
10 DirectConnect server
“{server_name}” started.
 | 
This informational message logs when the server starts.  | 
11 DirectConnect server
“{server_name}” stopped.
 | 
This informational message logs when the server stops.  |