"owsctl start admin" Doesn't Work!

When I attempt an "owsctl start admin" command from a *fresh* install of the OWAS v3.0.2.0.0 on a
SPARCstation 10 with 128MB of memory running Solaris v2.7, I get the following:

% owsctl start admin

Oracle Web Listener 3.0.2 Production (Domestic), Version 2.14FC1 Copyright 1997 Oracle Corp. All Rights Reserved.

Information: Listening on NORM port 8888 address 0.0.0.0 Cannot assign name to lock file!
Error: Companion oraweb process failed
OWS-08811: Unable to startup Oracle Web Listener `admin'.

Does anyone have a clue as to what is wrong here? I've looked all through the documentation and everywhere I've looked it seems that once installed, "owsctl start wrb" and "owsctl start admin" should start just fine, with no problems, and the truth is "owsctl start wrb" DOES work with no
problems. It's just the administrator that won't start.

What is the problem with the assigning of a name to a lock file? How can I check this. I know for
a fact that the process that is NOT starting is the "oraweb" process (and that's where the
"Cannot assign name to lock file!" error message comes from).

Any help will be greatly appreciated. This is day two of me getting kind of frustrated with the lack of
useful documentation Oracle put out for the OWAS. Email replies are preferable, but I will be paying
attention to this group for the forseeable future.

Thanks in advance,

• Cliff