Unable to locate a server document, et al

Seeing three errors:

(1) WARNING: Unable to locate a server document for this server - Hub1/Servers/Test/ESS

(2) Error reading server information for name server: The Domino Directory does not contain a server document for this server

(3) Connection denied: The server you connected to has a different name foom the one requested

-=-=-

Background:

*) Servers on their own private LAN, without any other Domino servers

*) Created new Certifier [/ESS] and OU Certifier [/Servers/Test] during installation

*) Red Hat AS 2.1 on xSeries (Intel)

*) First domino server in a new three-partition ND6.5.1 install TEST environment I created this weekend

*) Ran Remote ServerSetup on first server [Hub1]; remaining two servers yet to be setup

Current situation:

*) Java console works – no issues here

*) Admin client generates error (3)

*) Server console lists errors (1) & (2) [see below]

*) Host file contains the FQDN and alias for server as private IP rather than loopback (default)

*) Server document contains correct hostname on Basics tab and hostname alias [hub1] for Net Address on Notes Network Ports sub-tab

*) Server is correctly listed as Administration Server for Domino Directory

*) Server is Manager with full rights and roles for Domino Directory

*) Name stored within server.id equates name in sole server document with Domino Directory

*) ServerName= token in Notes.ini equates correctly spelled server name stored in server.id

*) ServerKeyFileName=server.id [and file exists in the current directory]

*) Server name as appears for Show Server and log entries contains only visible characters (as opposed to a prepended space, for example) " hub1" vs. “hub1” → {subtle error to track down}

*) Cleared out all three Server Document fields as listed in KB 167007 {$SavedAddresses ; $SavedPorts ; $SavedServers}

*) Verified that IP address is static (rather than DHCP); re-booted server for sanity purposes

*) Searched Google for newsgroup entries and followed advice [some suggestions included above]

*) Setup PortMapping within Hub1’s notes.ini file

*) “trace hub1/servers/test/ess” via server console works

Notation:

Initially, the IP Address was 192.168.1.118 during the server installation and setup process; realizing that the box was set to DHCP, I reset the IP to 192.168.1.3 as static and changed the host file and verified the server document entries; then bounced server to mitigate Domino cache issues.

Question:

a) Does Domino store the server’s IP somewhere that I missed? Using only hostnames in documents;

b) What’s causing these errors?

Would welcome any and all input. Thanks. :slight_smile:

-=-=-=-

Server Console Excerpt

========================

Lotus Domino (r) Server, Release 6.5.1, January 21, 2004

Copyright (c) IBM Corporation 1987, 2004. All Rights Reserved.

06/27/2004 11:50:28 PM WARNING: Unable to locate a server document for this server - Hub1/Servers/Test/ESS

06/27/2004 11:50:28 PM Begin scan of databases to be consistency checked

06/27/2004 11:50:28 PM End scan of databases: 58 found

06/27/2004 11:50:28 PM Error reading server information for name server: The Domino Directory does not contain a server document for this server

06/27/2004 11:50:28 PM Event Monitor started

06/27/2004 11:50:29 PM The Console file is /local/notesdata/partitioned/notesdata1/IBM_TECHNICAL_SUPPORT/console.log

06/27/2004 11:50:29 PM Console Logging is DISABLED

06/27/2004 11:50:29 PM Index update process started

06/27/2004 11:50:29 PM Database Server started

Subject: Unable to locate a server document, et al.

The Admin Client Registration Tool performs line parsing for mal-characters, more robustly than the Server Setup program’s line parser. Thus, one can create and setup a server that would be unable to launch properly, see its own Server document, see the Domino Directory, or administer via the Admin Client.

Lotus is currently testing this and will provide me a bug number upon completion.

Bottom line: Start over.