The Notes driver accesses some files (dsrepcfg.ntf, dsrepcfg.nsf, ndsrep.nsf, etc) via the Domino Server, so if the Domino Server and its data files are not configured correctly (TCP/IP, proper user authentication, database signing, etc), then connection and file access errors can occur.
The ndsrep.nsf file will not be created by the ndsrep add-in process until detectable changes (to objects and attributes specified within the publisher filter) have occurred within the file. To force ndsrep.nsf to be created, you may want to use a Notes client (administrator client) to modify a Person document (or other object that has been specified within the publisher
filter of the driver). If loopback is enabled, ensure you are not making this modification as the Notes Driver user, or it will be ignored by loopback detection.
Connection and file access problems sometimes can be resolved by finding the answers to the following questions.
1. On Windows, which notes.ini is found first in the OS search path? It should be a notes.ini equivalent to that of the Domino server (which references \Lotus\domino\data), and not a notes client (which references \Lotus\notes\data).
2. Does pub-configuration database (dsrepcfg.nsf and/or its template dsrepcfg.ntf) exist in the appropriate (\lotus\domino\data on Win32, or /local/notesdata on Linux, Solaris, or AIX) location?
3. Does the Notes driver's user account (CN=Notes DirXML/O=MyOrg) user have appropriate rights to access the file?
4. Does the Notes driver's user account of the OS have appropriate rights to access, read, and write to the file?
5. If running on Windows, is the Domino server running as a service? Does the Windows OS have the NOTESNTSERVICE=1 environment variable appropriately set? (see TID 10075627).
6. Are the network settings (TCPIP) properly configured on the Domino server?
For example, it is possible to see a Notes 4043 file access problem on a system where:
a) the Domino server has improperly configured DNS names for its TCPIP connection values,
b) no DNS is available within the Domino server's sub-network, and
c) thus, the Domino server is not be able to appropriately 'communicate' to its clients.
Using Domino Administrator, go to the Configuration Tab | Server->Current Server Document | Ports Tab | Notes Network Ports Tab. Make sure a TCPIP Port is defined and ENABLED using Protocol "TCP" with a Notes Network of "TCPIP Network". Also make sure there is a valid Net Address that can be verified using other networking tools (such as ping).
7. Can the file in question be accessed from a Notes client via the server, authenticated as the IDM notes driver user (DIRXML.ID)?
This means opening the database using the server name selection box from a client; this verifies that the file server can access and open the user in your behalf. Opening the database using the 'local' option in the file open selection box, does not count! This latter method has the Notes client opening the database directly, but it is necessary to verify that the server can open the database.
8. Do any of the following TIDs offer help?
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.