Running Startup Command (AREV Specific)
At 07 SEP 1999 04:13:03PM Victor Engel wrote:
Occasionally we have a situation where if someone tries to log on they are stuck at a screen which states only, "Running Startup Command" on the status line. I recognize that this is a problem of a lock not being released, however, I don't know what lock is being set at this point. Can anyone help here? I'd like to use NLM_STATS to determine who has the lock, but I need to know which table to look at first.
At 07 SEP 1999 06:19PM Warren wrote:
Since you metioned NLM_STATS I assuming a Novell system:
Just go to the system console, look at the files in-use in the connection information for the workstation/network connection. The last one listed should be the culprit.
Log in to ARev, do a listmedia on the directory in question, ctl-f on the REVxxxxx number to find the application file name.
At 07 SEP 1999 08:38PM Victor Engel wrote:
That would be great if I had console access. Life was so much simpler when I had access to the console. Now it seems like it takes a requisition to get someone else to look at the console.
At 07 SEP 1999 10:14PM Richard Hunt wrote:
It is a very strong possibility that it is the "SYSTEMP" table. i believe that there is a encryption subroutine that uses the "SYSTEMP" table, and this subroutine… i think… is used at start up.
I have had times when a user gets hung at startup. And then other users seem to start getting hung when logging off then too.
At 08 SEP 1999 02:32PM Warren wrote:
Well, insist on rebuilding ALL the indexes after every one of these lockup incidents. If it is a very large system it could take hours. After a few days of down time they'll ask you why you can't solve the problem. Tell 'em you could if you get at the system console.