Kbase P184819: Why am I seeing an admsrv.lock file after a CTRL_SHUTDOWN_EVENT, when I didn't see it before?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
28/03/2011 |
|
Status: Unverified
GOAL:
Why am I seeing an admsrv.lock file after a CTRL_SHUTDOWN_EVENT, when I didn't see it before?
GOAL:
I always reboot my machine and now all of a sudden I am seeing error messages regarding an admsrv.lock file when I try to start the OpenEdge Explorer. Why am I getting these messages now?
GOAL:
Why do I now receive error messages regarding an admsrv.lock file when attempting to start OpenEdge Management Console?
GOAL:
Why do I now receive error messages regarding an admsrv.lock file when attempting to start OpenEdge Explorer?
GOAL:
Where is the admsrv.lock file coming from?
GOAL:
Why is there an admsrv.lock file remaining behind when a machine is rebooted?
FACT(s) (Environment):
OpenEdge 10.2B
Windows
Fathom Management 3.x
Fathom Management 2.1A
OpenEdge Explorer
All Supported Operating Systems
FIX:
OpenEdge Management and OpenEdge Explorer are a plugin to the OpenEdge AdminServer. These processes work in unison with the AdminServer when OpenEdge Management or OpenEdge Explorer are being used with an AdminServer. The admsrv.lock file exists in the config subdirectory of the OpenEdge Management installation. This is a lock file which, if present when starting, will not allow the OpenEdge/Fathom Management AdminServer or OpenEdge Explorer process to restart.
This lock file is removed when the AdminServer is shut down properly. If the AdminServer is killed or the system is restarted without stopping the OpenEdge AdminServer first, then this file will remain behind.
This lock file would not have been created or in use if you were making use of the Progress Explorer. This file only exists if OpenEdge Management or OpenEdge Explorer are being used to monitor or manage an AdminServer.