Problems starting the c-treeACE Service
If the c-treeACE service fails to start, it returns a service-specific error, and logs a message to the Windows application event log. This information can be used to determine the reason why the c-treeACE Server Service failed to start up. Below is the output of a failed startup when starting the c-treeACE service using FairCom’s SCP. The service-specific error is displayed as the “Service Exit” code.
c:\faircom\bin.svc> ctntinst -start
Starting the c-tree Server service...
c-treeServer start unsuccessful:
Current State: STOPPED
Win32 Exit: 1066
Service Exit: 6
Checkpoint: 0x0
WaitHint: 0x0
The table below shows possible service-specific errors returned by the c-treeACE Server Service, the corresponding message, and possible causes for each of these errors.
Error Code
|
Error Message
|
Possible Causes
|
2
|
(Varies)
|
An operating system function call failed. See the event log for a detailed error message.
|
4
|
The c-treeACE settings file is missing. It is required to operate this server.
|
c-treeACE service requires a settings file, but it was not found.
|
5
|
The current settings file is invalid.
|
c-treeACE requires a settings file, and the settings file that was found was not valid. Contact your application developer for assistance.
|
6
|
c-treeACE must be activated with a FairCom activation key to operate. See the c-treeACE Activation Key Card within your package for more information.
|
c-treeACE has not yet been activated.
|
Use the Windows Event Viewer to list events reported by the c-treeACE service. Start the Event Viewer and select the Application log option from the Log menu. Events logged by the c-treeACE service have the “Source” field set to the service name (“c-treeACE Database Engine” by default). Double-clicking an event displays the event detail (see the following Figure; Using the Event Viewer to display events logged by the c-treeACE service).
|
