hand window of the va management console gui when the service 39 s name is clicked on in the component tree as illustrated in fig2 the user has highlighted the testapplicationresourcemgr node which is the nuance resource manager for the testapplication application the properties for the service appear in the right hand part of the screen on this properties panel the process status field indicates the status of the process it can have one of the following values error the process has failed to start because of an error if the process has an error status then the code for the error will be displayed in the error code field this error code u2014 a hexadecimal number u2014 indicates the reason for the process 39 s failure a complete listing of the possible error codes and their meanings is set forth below if one or more of the processes for an application fail to start the displayed error code can be looked up to determine the reason for the failure in addition to displaying an error code a failed process may also list troubleshooting information in the large process events text box on its properties panel one of the most common causes for a component 39 s failure to start is that one of its prerequisite services is not running a va engine for example will not start if its tts server is not running a recognition server will not start if its license manager service is not already running if a particular component has failed to start make sure that all its associated services are running correctly and if they are not attempt to start them as with starting va services the administrator has several options to choose from when shutting down services on the va platform when va.