Thursday, 26 December 2013

Most Common Lotus Notes Error Messages and Their Solutions

Lotus Notes email application offers business teamwork functionality which includes sending/receiving emails, instant messaging, contact management, team-rooms, user directories, calendars, file sharing, blogs, micro-blogging, to do lists, and discussion forums. Lotus Notes also provide access and integration with other IBM Domino databases and applications.

Database files of Lotus Notes are prone to corruption due to a number of logical and  physical errors. Error messages are not only frustrations to Lotus Notes administrators and users but they are also call to action to fix the issues. We have assembled some of the most common Lotus Notes/Domino error messages and accompanying solutions and suggestion in this post. If you are also getting error messages when using Lotus Notes database files, migrating to Lotus Notes 8 or errors due to network connectivity, you will find the answers and solutions to fix it here. Check out most common Lotus Notes/Domino error messages along with their solutions below:  

Error 1. 'Your current ID does not specify an Internet certificate for signing'

This error message has caused confusion to end-user for many years, and usually it is generated when a user puts the default setting to sign emails.

In Lotus Notes, this is completed by means of the Public Key Infrastructure of your current Lotus Notes ID. Your client signs the messages to other Lotus Notes recipients with your public key.

To send the mail through Internet, Lotus Notes keys will not work. You need to have X.509 certificate incorporated into your Lotus Notes ID. Though, this is not common because those people who are not in a need, don’t get an access to these keys usually.

When the Lotus Notes client goes to sign the Internet message, it cannot discover a legitimate certificate to make use of, and causes the error. To hold back this, you need to alter the default setting of signing messages. If that is not achievable, then you can accept the dialog box when it comes out.

Error 2. 'Network operation did not complete in a reasonable amount of time'

Tip 1: It is recommended to open the "Replicator" page in your Lotus Notes client and manually trigger/reproduce the line, "Sending outgoing mail" (or a similarly named line).

Tip 2: In your Lotus Notes client, you need to open your existing "Location" and check the "Mail" tab. If the "Mail file location" is "Local," then adjust it to "On Server" to test it. Then, check the "Send outgoing mail" field. If it shows, "directly to Internet," then change it to "through Domino server" and you are done.

Error 3. Lotus Notes error: 'You are not authorized to the database for user's local mail file'

The Lotus Notes StdR7Mail template and 6.5.6 client don't fit in mutually, so you should not make use of R6 client with R7 design template as it is not supported. You should remove the local copy, and then update the server mail file with the help of  R6 mail template from R6 Notes client installation wizard. When you are done with that , replicate this back to the user's system. Many truly unusual problems have been observed from this kind of version incompatibility but It might not essentially be the actual reason, but you should get rid of this prospect prior to trying some other way.

Error 4. 'The object store that is used by this note was not found’. Run the object store COLLECT task on this database.

This error points to Lotus Notes Shared Mail, which is usually not used nowadays, as disk space has turned out to be economical and the exertion required in cleanup of such problems can be expensive and challenging.

Normally this error occurs when a Lotus Notes document that is trying to be read is not available in the Domino object store which leads to the generation of the error. Running “Collect” would clean up the reference, which can resolve the error.

Error 5. Domino server error message:' Entry Not Found in Index'

Earlier, this issue resulted from a locally edited policy. You are advised to try to edit or re-save all described policies straightforwardly on server copy of names.nsf. This will definitely resolve the issue.

Error 6. Database error: 'Database Corrupt -- Cannot Allocate Space'

The most probable reason of this database error is a problem with your Notes client's Desktop.dsk file. Running Nfixup or Compact on the Desktop.dsk file may lessen the problem. In some circumstances, generating a new copy of the corrupted or damaged database will resolve this problem. The copy should be created either at the OS-level or through the Database File in Notes.

If running Nfixup at the server console is not a choice, as in this situation, then you need to remove cache.ndk and rename it as bookmark.nsf.

Error 7. Lotus Notes 8 migration error: 'Database has not been opened yet'

Usually, LotusScript code produces this error when it generates a null database object handle and then attempts to function with this null database object handle. This could happen if the file or server path is incorrect or if the existing machine cannot connect to the end server. Most probably, however, the user does not have a right to access the end database.

If you are still unable to get rid of the above errors, then this problem might corrupt or damage your NSF files. If your Lotus Notes file gets corrupt due to the above physical or logical errors, then in that case, you need to make use of any recovery software which can repair corrupt or damaged files.  These tools have superior features and advanced algorithms that can aid you to repair and recover from serious corruption circumstances and one such reliable tool is "Stellar Phoenix Lotus Notes Recovery Software" which is a great tool to recover and repair your important data.