T.R | Title | User | Personal Name | Date | Lines |
---|
2907.1 | You need OAFC$SYSMAN identifier when in MS | IOSG::STANDAGE | | Thu Jun 24 1993 09:53 | 17 |
|
Mike,
So what you're saying is, the server is running OK and functioning
normally, but there's an error from the Manage Servers subsystem ??
If this is the case, I suggest you look at the account from which
you're using the Manage Servers subsystem. It must be privileged, and
with the OAFC$SYSMAN identifier. The ALL-IN-1 managers account has the
OAFC$SYSMAN granted to it at installation time - so try the same thing
from that account.
Kevin.
|
2907.2 | server master file | CHRLIE::HUSTON | | Thu Jun 24 1993 14:25 | 7 |
|
In addition to what Kevin says to check:
Was the server master file updated when the node name was changed?
--Bob
|
2907.3 | Already checked it. | TRCOA::TROTTI | VAX..more than just a vacuum cleaner | Thu Jun 24 1993 17:55 | 13 |
| RE .1
I am using the ALLIN1 account.
RE .2
I did change the server master file right after the I changed the node
name and I seemed to recall that it was running OK. But something
weird has happen since then.
Thanks
Mike
|
2907.4 | Stop, delete, create, and start again ?? | IOSG::STANDAGE | | Thu Jun 24 1993 18:09 | 11 |
|
Mike,
I suggest you stop the FCS, delete the old config files and create
new ones. Then start the server(s) up and see what happens. I'm
not sure how you've got into this state, but hopefully that might do
the trick...
Kevin.
|