Hi Judith
 
as dce/3000 is the most unreliable implementation of dce I have EVER =
seen
and it took me 3 full weeks and help from hp-labs to get it running. I =
doubt if you'll
get it running overnight.
 
I do need to know more about what you are installing. Are you just a =
dce-client,
or are you a server or are you both? What sort of systems are there in =
your cell?
If you give me more data on what you are trying to accomplish I'm sure I =
can help,=20
for now....
 
Here are some general hints.
 
login as manager.sys and get into the posix-shell by typing sh
 
The first thing to do is to look for the file rc.dce
 
That is the script that is used to start dce.
=20
there are a couple of them on your system. Everytime you (re)configure =
dce it takes 1 original and edits it. The edited version usually ends up =
in /etc
 
take this file (/etc/rc.dce) in your favourite editor and look for the =
DEAMONRUNNING statements. If there are #'s in front of all these =
statements you have an unedited version.
Look all over the system for an edited version, it is there somewhere. =
(try find command)
 
At the end of this command you'll see a construction that starts rc.dts
in front of that statement there is a sleep statement. Increase this =
sleep time to 10 minutes. Your system is way too slow for the std =
sleep-time.
 
Next be sure there are no dce-jobs running by entering dce.clean (from =
posix shell, as manager.sys)
Doublecheck by entering callci showjob
If there are still dce jobs running abort them and reboot.
I'm sorry to tell you this but rebooting is something you get good at =
with dce/3000.
 
Now enter the full file-name including path of your rc.dce file=20
On my system this is: /etc/rc.dce
If you just enter rc.dce it often starts an unedited version which =
starts a sleep and does nothing.
 
Now the system starts 3, 4, 5 or 6 jobs depending on what you =
configured.
 
Some other pitfalls.
If you configured your system as a time-server. It's system-time should =
be within 5 minutes of the time on the others in your cell (and TZ =
identical). If it's not you don't get an errormessage, but the =
startupscript just hangs.
 
During configuring you get asked. Can this system braodcast to =
...servername....
Always answer this with yes. It just starts some caching which you will =
need on the small system you have. If you don't you don't get an =
errormsg either, the script just hangs.
 
I often ignore registry errors, but yours look bad.
 Registry: Fatal Error - Cannot register server
  at line 398 of file ../../../../../src/security/server/rs/rs_main.c - =
0x16c9a0
16 - communications failure (dce / rpc) [16c9a016]
 Registry: Error - DT received fault - 0x16c9a016 - communications =
failure (dce
/ rpc) [16c9a016]
 
This is the point where the dce_config tries to put the data about your =
node into the cell registry.
Are you sure you entered the right cell_admin password. This is ux and =
case is crucial.
If you are not sure. Try to remove the entire configuration with =
dce_config. And re-configure entirely. =20
The silly thing about it is that you have to have dce-running for a bit =
to be able to unconfigure it.=20
Ignore the errors you get.=20
 
I hope you won't have a time as hard as the one I had.=20
If you have any question don't hessitate.=20
Anyway I'm happy to hear there are more dce3000 victims.
 
 
Leon Degeling
Vrij Uit BV
Hoofddorp
The Netherlands