Cisco Cisco Unified Queue Manager, Руководство по обслуживанию и устранению неисправностей

Страница: 95 / 148

8-31
Cisco Customer Response Solutions Servicing and Troubleshooting Guide, Release 5.0(1)
Chapter 8 Troubleshooting Tips
CRS Engine Problems
Attempting to start the Cisco CRS Node Manager service causes an error 1067
Symptom You attempt to start the Cisco CRS Node Manager service in the Windows Services window
and the following message appears.
Error Message Could not start the Cisco CRS Node Manager service on local computer. Error 1067: The
process terminated unexpectedly.
Possible Cause There is an internal error in the Cisco CRS Node Manager.
Recommended Action Refer to Cisco Customer Response Solutions Administration Guide or the
Administration online help for information about properly setting up the CRS Node Manager service.
Attempting to start the Cisco CRS Node Manager service causes an error 1069
Symptom
You attempt to start the Cisco CRS Node Manager service in the Windows Services window
and the following message appears.
Error Message
Could not start the Cisco CRS Node Manager service on local computer.
Error 1069: The service did not start due to a logon failure.
Possible Cause
When you install Cisco Unified Communications Manager or Cisco CRS, the Windows
2003 administrator password that you enter overwrites the existing Windows 2003 administrator
password. Also, if you enter a password that includes spaces, it may not be recorded properly.
Perform the following steps to change the password for the CRS Node Manager service:
Step 1 On the CRS Server, choose Start > Settings > Control Panel > Administrative Tools > Services .
Step 2
Double-click Cisco CRS Node Manager .
Step 3 Choose the Log On tab.
Step 4
Enter and confirm the Windows 2003 administrator password and click Apply . Do not include spaces in
the password.
Application subsystem is in partial service
Symptom The Engine Status area in the Engine web page shows that the Application subsystem is in
partial service.
Error Message
None.
Possible Cause
Some applications are invalid.
Performs these actions:
Step 1 Refer to the CRS trace files to identify the invalid application.
Step 2
Validate the corresponding script using the CRS Editor.