Below we are describing Notes and Domino files & folders in brief.
Names.nsf: Can be reffered as the Public Address Book or Name and Address Book. Also called Domino Directory. Automatic created by Domino server. Contains Server documents, Configuration settings, personal Documents and Internet Site Document. Administrators use Domino Directory to manage the Domino System.
Log.nsf: All Domino Server has a Log file which reports all server activity and provides detailed information about databases and users on the server. Created automatic when user starts a server for the first time.
Admin4.nsf: Also called Administration Requests Database. Created when server starts for the first time. Domino servers use replicas of this dtabase to distribute requests made on server to other servers in the domain.
Notes.ini: A text file, contains mainy settings on whichboth Lotus Notes and Domino rely to work properly. Any incorrect change may cause both to run unpredictably.
Mail.box: Special database on server, automatic created at startup. Acts as a temporary repository for all massages in transit to and from mail clients, applications and other servers. Server creates number of Mail.box database specified on Configuation Settings document.
User.id: A unique file and security features of Notes that identifies Notes user. Created when a Domino Administrator registers a user. Contains name of the user, certificate from Certificate ID, public key, private key, password and encryption keys.
.nsf: A database format, stands for Notes Storage Format. Commonly used for Lotus Notes client and Domino Server. Read More...
.ntf: Stands for Notes Template File, contains structure element viz. views, forms, folders etc. Does not contain any document.
Program Folder: A directory in which Lotus Notes and Domino Server is installed. In this folder Notes/Domino executable file are located along with Notes.ini. This folder is specified by user during installation process.
Data Folder: In this folder Notes/Domino applications and templates are located. Specified by user during installation process.
Follow these steps:
Check names.nsf is on right place or not. Location will be C:\\Program Files\IBM\Lotus\Notes\Data for single user install. For multiuser install C:\\Documents and Settings\Username\Local Settings\Application Data\Lotus\Notes\Data.
Search for notes.ini. It will show you the correct location faster than searching the registry.
Check names.nsf is there or not. If not, then restore or recreate the database.
To recreate names.nsf, reconfigure the Notes client.
To do this, open notes.ini and delete all rows below the DST line.
Now start Notes, this will be prompted to reconfigure Notes.
The local names.nsf is a Personal Address Book designed for the user to put personal contacts in it. This uses the template pernames.ntf, holds address book entries for the user and configuration settings such as connection / location documents. These documents determine how the Notes Client communicates with different servers. It also holds trusted certificates amongst other things. The names.nsf located at the server is called the Domino Directory (Template name Pubnames.ntf). The Domino Directory contains Person and Group documents. The Domino Directory determines who can create or edit a particular type of document in the Directory. The Domino Directory also contains the Server document that user access to provide another user with administrative privileges. All the Domino servers in the same domain share this one database (names.nsf) which is the most important database in Domino environment.
This step includes:
Configure a new machine with Lotus Notes client (not connected with Domino Server) and Outlook for the successfully conversion process. and copy the .ID file associated with the NSF file in a new machine.
Then open Lotus Notes, go to File -> Security -> Switch ID.
Locate the .ID file and enter password.
And then you will be able to open the NSF file on the conversion machine.
This error comes when a Lotus Notes database is locally secured. If user performs any operation on that NSF database then this error comes.
To remove this error we have provided a NSF local security eraser Securase which perform efficiently on this error and remove local NSF database security.
Conversion of NSF items in EML & MSG format.
Conversion of Lotus Notes emails in Outlook Express emails.
Convert emails from Lotus Notes NSF to MBOX format.
Convert Lotus Notes emails to Adobe PDF files.
Convert Lotus Notes emails to Word file.
User can access Notes calendar data in globally supported ICS format.
Conversion of Lotus Notes NSF file into Outlook PST file.
Migration of bulk mails from Lotus Notes/Domino server to Outlook/Excahange server.
Migration of Notes NSF emails to Exchange Archive mailbox.
Conversion of Lotus Notes Address Book to Outlook PST file.
Conversion of Lotus Notes contacts into Outlook Express file format.
Conversion of Lotus Notes contacts into Excel Spreadsheets.
User can convert entire contact list from Lotus Notes to Gmail platform in very less time.
Find NSF files from networks that are members of same domain. Also list NSF files, and copy NSF files to safe location.
Migration of bulk NSF mail accounts and document base to user's Google Apps account.
Convert both healthy as well as corrupted OST file to Lotus Notes NSF format.
Conversion of PST files into NSF file format of Lotus Notes.
Export Outlook contacts to Lotus Notes in one go.
NSF Local Security Removal. Removes local security of NSF file and allows access of data stored in NSF files.