Error opening dsrepcfg.nsf on server ...  ID = 4043.  Message: Database open failed

(Last modified: 14Mar2006)

This document (10092978) is provided subject to the disclaimer at the end of this document.

fact

Nsure Identity Manager 2.0

Novell Lotus Notes Driver

Microsoft Windows 2000 Advanced Server

Microsoft Windows 2000 Server

symptom

Error opening dsrepcfg.nsf on server ...  ID = 4043.  Message: Database open failed

dsrepcfg.nsf NOT FOUND on server

Unable to run NDSREP.EXE because the DSREPCFG.NSF database is missing

The Notes driver is unable to create the DSREPCFG.NSF database

cause

The DSREPCFG.NSF is a database created on the Notes server by the driver using the DSREPCFG.NTF database template. This database contains the configuration data used by NDSREP.EXE. When the driver starts, it checks to see if the DSREPCFG.NSF database exists. If it does, it updates it with the configuration data used by NDSREP.EXE. If it can't be found, it uses the DSREPCFG.NTF database template to create a new database and then updates it with the configuration data. Although the error states that the driver is unable to open the DSREPCFG.NSF, the actual problem is that the driver is unable to find the template (NTF) that is used to create the database.

fix

Here are several suggestions that have resolved the problem in the past. However, one hasn't proved any more effective than the rest.

  • Make sure that the DSREPCFG.NTF is placed in the Lotus\Domino\Data directory
  • Put the Lotus\Domino\Data directory in the system PATH environment variable
  • Remove the Notes Client from the Notes server
  • Verify that there is only one instance of NOTES.INI
  • Start Notes server before the remote loader starts
  • Start remote loader before Notes server starts
  • Use the Notes admin account for the driver's Authentication ID
  • Run Notes server as a service
  • Sign the database template to allow the Domino Server access to the file

There are multiple ways to gain access to an option to sign a database. Here is one using the Domino Administrator tool:

1. Select the Files Tab. Adjust the "Show Me:" selector on the right if you want to see 'databases only', 'templates only', all files, etc.
2. Select the file you want to sign, and right click the mouse to get and action dialog box.
3. Select "Sign..." from the action dialog box.
4. From the Sign Database dialog, select "Active Server's ID"
5. Click OK to complete the action.

  • Modify the Access Control List on the DSREPCFG.NTF. You may need to use this DSREPCFG.NTF that doesn't have any access control specified.

To modify the access control:

1. If you're able to modify the ACL on the current NTF skip to step 4
2. Replace the current DSREPCFG.NTF with the one in the above link. You may need to stop the Domino server in order to replace it.
3. Restart the Domino server
4. Select the Files tab and select 'Templates only' in the 'Show me' drop down
5. Right click on the DSREPCFG.NTF and select 'Access Control' | 'Manage ...'
6. Click Add and browse to the user specified in the driver's Authentication ID field
7. Add the user and click Ok.
8. Verify the access control of Manager and that all check boxes are checked.
9. Click Ok.

  • Verify that TCPIP is setup correctly in Notes

1. Select the Configuration tab
2. Select Server | 'Current Server Document'
3. Select the Ports tab
4. Verify that the TCPIP ports listed can be resolved the the Notes server. (For example, 127.0.0.1 or the name of the Notes server)

In addition you should also ensure that the DNS on the server and Domino Server name have been set up correctly, otherwise the Domino server might not be found, thus the database cannot be opened and the dsrepcfg.nsf cannot be created

document

Document Title: Error opening dsrepcfg.nsf on server ...  ID = 4043.  Message: Database open failed
Document ID: 10092978
Solution ID: NOVL97071
Creation Date: 21May2004
Modified Date: 14Mar2006
Novell Product Class:DirXML

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.