FAQ: Crawling Lotus Notes (Office SharePoint Server 2007)
Applies To: Office SharePoint Server 2007
This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.
Topic Last Modified: 2007-07-16
This article answers frequently asked questions about crawling Lotus Notes databases, as follows:
What is the purpose of the Lotus Notes user ID file?
What metadata in a Domino database is indexed?
Where is the MissingIdLog.txt file located and what is its use?
What type of changes would require me to run NotesSetup again?
What does NotesSetup capture and store from the Lotus Notes client configuration that I should be aware of?
What is the purpose of the Lotus Notes user ID file?
The Lotus Notes user ID file is used by the Lotus Notes C++ API to connect to the Domino server and crawl the Domino database. The Lotus Notes user ID file contains the following three things:
A Domino client certificate issued by a Domino certification authority
A pair of public/private keys
A password used to encrypt the private key
What metadata in a Domino database is indexed?
Microsoft Office SharePoint Server 2007 indexes the metadata for any property that appears in quotes in the right pane of the Document properties window. For example, if you select a field in the left pane named Form and "Secure" appears in the right pane, the metadata for the property named Secure is indexed for the Form field.
Where is the MissingLogId.txt file located and what is its use?
The MissingIdLog.txt file contains a list of Lotus Notes user IDs that are not mapped to valid Windows user accounts in the mappings table. For example, if the Lotus Notes user ID LotusManager1 is mapped to the Windows user account Contoso\User1, but User1 is not a valid user in the Contoso domain, the MissingIdLog.txt file will have an entry for Contoso\User1.
The MissingIdLog.txt file is located in the root directory of the index server's drive on which you installed Lotus Notes. To ensure that all missing IDs are listed in this file before you view it, we recommend that you stop and restart the OSearch service after all crawls are complete before viewing the MissingIdLog.txt file.
The index server does not overwrite this file. Instead, new entries are appended to the MissingIdLog.txt file.
Important
Do not use the Services on Server page on the SharePoint Central Administration Web site to stop and start this service. Doing so removes the service and deletes the index and associated configuration. Instead, use the following steps.
Stop and restart the Office SharePoint Server Search service
On the index server, click Start, click Administrative Tools, and then click Services.
Scroll down the list, right-click the Office SharePoint Server Search service, and then click Properties. The properties page appears.
Click Stop. After the service is stopped, click Start.
Ensure that the Startup Type is not set to Disabled.
What type of changes would require me to run NotesSetup again?
If you want to specify a different mappings database or change the Domino server on which the mappings database is located, run the NotesSetup application again to specify the new mappings database or location.
What does NotesSetup capture and store from the Lotus Notes client configuration that I should be aware of?
NotesSetup writes entries in the registry of the index server under the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Setup\Notes Configs
The following entries are written to the registry using NotesSetup:
The name of the Domino server where the Mappings.nsf database is located
The name of mappings database
The view name of Mappings file
The location of the MissingIdLog.txt file
Names of the columns used to store the Lotus Notes user Ids and Windows domain accounts
See Also
Concepts
Configure Office SharePoint Server Search to crawl Lotus Notes (Office SharePoint Server 2007)