Kbase P131836: NameServer doesn't start and the log file is not created
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
14/01/2009 |
|
Status: Unverified
SYMPTOM(s):
NameServer doesn't start and the log file is not created
Attempt to start the AppServer produces the error 8297
Unable to start <service_name> (8297)
Error 8171 in AdminServer log file
SvcControlCmd.connectToService() failure: (8171)
Abnormal shutdown of the NameServer is observed in the AdminServer log file:
Thread[BrokerAbnormalShutdownWatcher: NameServer.<NameServer_Name1>,5,RMI Runtime] (PID xxxxx) keepWatching changed from true..
..to true
About to post abnormal shutdown event ## keepWatching = true
EAbnormalShutdownEvent for <NameServer_Name1> is posted..
FACT(s) (Environment):
AdminServer is started as a Windows Service
NameServer_Name1 configuration in ubroker.properties contains the property neighborNameServers
neighborNameServers=<NameServer_Name2>
<NameServer_Name2> configuration was not found in ubroker.properties
Windows
Progress 9.1E
OpenEdge 10.x
CHANGE:
Manually edited ubroker.properties file. The previous neighborNameServers' configuration was removed.
CAUSE:
Corrupted ubroker.properties.
FIX:
Remove the property neighborNameServers= <NameServer_Name2> or add the configuration for the <NameServer_Name2> that was deleted.