Hi,
I just realized that since our upgrade to 7 we have this fatal error in the log:
“Server document in Domino Directory does not contain a network name (or one for this port)”
The server is running fine except I have few problems with Sametime (which I think could be related to this fatal error).
On which tab is the network name field? is it the Notes Network Ports? There is already an entry in this section, so I don’t understand why I get this error message.
Thanks for the help!
Genevieve
Subject: fatal server error with domino 7
ok finally I removed LAN0tcpip from the notes.ini. This fixed at least the fatal warning. But I still have other problems… One Is that everytime I shutdown the server, either with the command - quit or restart server, the shutdown is ok, but we the server restart, I always get the following lines :
09/22/2005 11:42:17 AM Event Monitor started
09/22/2005 11:42:17 AM Starting Server shutdown
09/22/2005 11:43:28 AM Event: Error opening monitoring profile document in the Domino Domain Monitoring database ddm.nsf: Domino Domain Monitoring functions cannot be executed when the Event task is not loaded.
So everytime I shutdown the server, I have to restart the whole machine…
Any ideas?
Thanks,
Genevieve
Subject: RE: fatal server error with domino 7
I did a upgrade from version 5 to version 7 on a test server. I have exactly the same problem. Is there already someone with a solution?Thanks.
Subject: RE: fatal server error with domino 7
Hi,
Did you ever get an answer to this? I have the same problem when a Windows service is called from a program document - unless you shut down the services that are called before restarting the server, I get the exact same error message as you.
Nick
Subject: RE: fatal server error with domino 7
I had the same problem when I upgraded from 7.0 to 7.0.1 after a couple of daysAll I did was cut the ddm.nsf out of the folder and restarted the server. Everything smooth back to normal.
just create a new ddm.nsf with the new ddm.nsf template
cheers
the question for IBM/Lotus is why did it happen? Do we have something wrong … might be something to check to for the next version 
Subject: HELP- Deleteting/recreating DDM.nsf did not help
I cannot schedule a backup of my server.
If I use NET STOP or NSERVER -Q, either way - the server will not restart.
Deleting the DDM.nsf did not help.
I shutdown using nserver -q, this is what happened.
05/03/2006 01:11:16 AM LDAP Server: All tasks have completed
05/03/2006 01:11:16 AM LDAP Server: Shutdown
05/03/2006 01:11:18 AM Database Replicator shutdown
05/03/2006 01:11:21 AM Database Designer shutdown
05/03/2006 01:11:32 AM Database Fixup: Shutdown
05/03/2006 01:11:37 AM Updated database MAIL\jchiesa.nsf in catalog
05/03/2006 01:11:37 AM Unable to update catalog: Program shutdown in progress
05/03/2006 01:11:38 AM Server shutdown complete
If I click to start the service, this is what I get.
05/03/2006 05:48:38 AM Event Monitor started
05/03/2006 05:48:53 AM Index update process started
05/03/2006 05:48:58 AM Index update process shutdown
05/03/2006 05:49:00 AM 0 duplicate PUIDs found while initializing Domino Domain Monitoring
05/03/2006 05:49:01 AM Event Monitor had a problem checking for DDM probes in the job scheduler: Operation stopped at your request
05/03/2006 05:49:02 AM Event Monitor shutdown
05/03/2006 05:49:03 AM Server shutdown complete
If I try to start a 2nd time, I get this:
05/03/2006 05:53:32 AM Event Monitor started
05/03/2006 05:53:33 AM Index update process started
05/03/2006 05:53:34 AM Starting Server shutdown
05/03/2006 05:53:38 AM Index update process shutdown
05/03/2006 05:53:41 AM Event: Error opening monitoring profile document in the Domino Domain Monitoring database ddm.nsf: Domino Domain Monitoring functions cannot be executed when the Event task is not loaded.
05/03/2006 05:53:45 AM Event Monitor shutdown
05/03/2006 05:53:45 AM Server shutdown complete
Subject: RE: fatal server error with domino 7
hmm I think this has to do with the fact that nservice.exe is not shutting down completely. This is causing corruption on some databases that after rebooting ar being repaired and back up again.
Always shut the server using the service tasks in windows. Do not use the “q” or “restart server” in the domino console.