| Hans,
If you're in Europe you might not be aware of the fact that last weekend
was a long weekend in the United States (Memorial Day).
The "invalid access" errors in the server log file might be caused by a
program that the customer is trying to run during DECwindows startup. e.g.
they could have redefined the DECW$MAINAPP global symbol in
sys$manager:decw$private_apps_setup.com. Some people do this because they
want DECwindows to come up with the user already logged in instead of
making the user enter a username and password at the login box.
Is the DECW$LOGINOUT process or a _WSAn: process getting started briefly
and then exiting? Try to obtain a login log file. To do this, have them
edit sys$manager:decw$private_apps_setup.com (if it doesn't exist copy it
from sys$manager:decw$private_apps_setup.template) and add the following
global symbol definition, or remove the "!" comment character from the
definition which is already there:
$ decw$loginlog == "sys$manager:decw$login.log"
When they restart DECwindows again, if the DECW$LOGINOUT process is
starting and then exiting it should create the decw$login.log file, which
might contain some useful error messages.
-- Bob
|
| Bob,
> If you're in Europe you might not be aware of the fact that last weekend
> was a long weekend in the United States (Memorial Day).
sorry for being so insistent. Yes, I'm in Europe, but nevertheless I should have
thought about this - there are far less US holidays to remember than European
holidays. And most of us had long weekends before and after the Memorial Day
weekend...
Anyway, meanwhile I found the problem. The customer had restarted the
JOB_CONTROL process from an account other than SYSTEM. This account was shown in
the 'invalid access messages'. After restarting the job controller from the
SYSTEM account, the problem went away.
Thanks for the tip with decw$loginlog - I'm sure I can make use of it when
troubleshooting future calls...
Thanks again,
Hans.
|