IBM E027SLL-H - Tivoli Monitoring - PC, Руководство по устранению неисправностей

Страница: 104 / 310

e. After you have changed the Firewall state in all of the profiles, click OK.
2.
Configure the monitoring server to work correctly with Windows User Account
Control (UAC).
v
Using Windows Explorer, navigate to the IBM Tivoli Monitoring product
installation directory (default is
c:\IBM\ITM
).
v
Navigate to the appropriate subdirectory, right-click one of the executable
files listed below, and select Properties.
–
itm_home\CMS\cms.exe
–
itm_home\CMS\kdsmain.exe
–
itm_home\CMS\kdstsns.exe
–
itm_home\InstallITM\kinconfg.exe
v
When the Properties window appears, select the Compatibility tab.
v
In the Privilege Level section, check the box next to “ Run this program as an
administrator .
v
Click OK.
v
Repeat this procedure for each of the files listed.
After an upgrade, the Tivoli Enterprise Portal Server is in the
'stop pending' state and cannot be manually started
After the upgrade, the Tivoli Enterprise Portal Server was in the 'stop pending'
state. Attempts to manually start the Tivoli Enterprise Portal Server failed. End the
kfwservices process from the Windows task manager and then attempt the manual
start. Your Tivoli Enterprise Portal Server can then be started and stopped.
This behavior can happen if a program that locks files is running in the
background, such as Norton Antivirus.
When running the setup.exe, an unknown publisher error
message displays
If you run the
setup.exe
from a network drive on Windows, a window displays
with the following message:
File Download - Security Warning
The Publisher could not be verified.
Are you sure you want to run this software?
Selecting Cancel closes the window and the installation cannot complete. To install
the software without this problem, map the network drive and run the
setup.exe
file from a DOS prompt.
The error “Could not open DNS registry key” occurs
This message is informational an no action is required. The Windows agent reports
the fact that it could not find a registry entry for the DNS Server Event Log,
indicating that the DNS Server Event Log is not installed. You can stop all
situations and recycle the Tivoli Enterprise Monitoring Server with no situations in
ACTIVATE AT STARTUP to prevent this message being written to the trace log.
Agent not connecting to Tivoli Enterprise Monitoring Server
If you find a message similar to "Unable to find running TEMS on CT_CMSLIST"
in the Log file, the Agent is not connecting to the Tivoli Enterprise Monitoring
Server. Confirm the following to ensure connectivity:
86
IBM Tivoli Monitoring: Troubleshooting Guide