I am adding a few more notes and log file entries so others can find this string. We had a similar problem last night where we could not log in (cannot log in). We had to bring down our servers to plug them into a new UPS and when we attempted to bring up Epicor again, Progress / Open Edge was not starting properly. The Windows "AdminService for OpenEdge 10.2A" service was running, but we could not log into the system.
I tried starting open edge explorer ( Start / All Programs / Openedge Explorer / Start OpenEdge Management ) and was getting a message that port 20931 was not started (I cannot remember the exact message).
I found the following series of messages in \epicor\oe102a_wrk\admserv.log
Invalid PID number found in the adminserver lock file:
Unable to read the PID number from the adminserver lock file: Shutting down adminserver, lock file found. (11356)
After renaming the admsvr.lock file referenced, everything started cleanly upon doing a server reboot.
Also, if you are running two servers (database and application) make certain the database is up and running. We have had a few cases where the database server came up after the app in which case you cannot log in. In this situation, it is a simple reboot of the app server (or stop / start windows service) and things go clean.
I tried starting open edge explorer ( Start / All Programs / Openedge Explorer / Start OpenEdge Management ) and was getting a message that port 20931 was not started (I cannot remember the exact message).
I found the following series of messages in \epicor\oe102a_wrk\admserv.log
Invalid PID number found in the adminserver lock file:
Unable to read the PID number from the adminserver lock file: Shutting down adminserver, lock file found. (11356)
After renaming the admsvr.lock file referenced, everything started cleanly upon doing a server reboot.
Also, if you are running two servers (database and application) make certain the database is up and running. We have had a few cases where the database server came up after the app in which case you cannot log in. In this situation, it is a simple reboot of the app server (or stop / start windows service) and things go clean.
--- In vantage@yahoogroups.com, "Alex Fiedler" <alex@...> wrote:
>
> Also had to solve this yesterday. Found that the applicable Progress KB entry is this:
>
> http://progresscustomersupport-survey.force.com/OpenEdgeKB/articles/Article/P109066?retURL=%2Fapex%2FKnowledgeSearch&popup=false
>
> The PSC position seems to be that all customers should write a small script to run at system startup and delete the lock file if one is found. I'm not exactly thrilled with that. What annoys me is that the Windows service reports itself as having started!
>
> An alternate solution is to uninstall OEM and revert back to the 32-bit PET tool. It just seems unacceptable that an uncontrolled restart of a machine should prevent the OpenEdge system from restarting cleanly. Anyone have any thoughts and opinions on this?
>
>
> --- In vantage@yahoogroups.com, "Doyle, Jason" <jdoyle@> wrote:
> >
> > David,
> >
> >
> >
> > We actually had a similar issue, and for those that may want to know:
> >
> >
> >
> > There is a lock file that is created by the windows service, it's
> > located at PROGRESS/OEManage/config/admsvr.lock.
> >
> >
> >
> > If for some reason this file exists (the service did not remove it on
> > exit), the Windows service will start and immediately stop.
> >
> > 2 hours+ with Epicor Support to discover that.
> >
> >
> >
> > FYI.
>