You open your mail file in a Lotus Notes® client and see that it is listed under "Mail Archive" instead of as a regular mail file.

When a Lotus Notes database mail file shows "Archive" contrary to "Mail," you can run this code to change the ArchiveDatabase field value to 0. Simply close the Lotus Notes database and open again. Then, run the script with the user ID.

Dim s As New NotesSession

Dim db As NotesDatabase

Dim doc As NotesDocument

Set db = s.currentdatabase

Set doc=db.GetProfileDocument("archive database profile")

doc.ArchiveDatabase = "0"

Call Doc.Save(True,True)

New mail does not show up in $Inbox but shows up in 'All Documents' view

If email is intermittently not appearing in the Inbox, then the problem is most likely occurring because of a corrupt view index. If this is the case, then running updall -r on the mail file will resolve the issue.
This problem has also been known to happen if more than one ($Inbox) exists in the mail file. One way this is known to occur is described in the following document: " Double Inbox is Created When the Design Task Runs on New Databases That Are Not Yet Initialized" (#1089921).
Additionally it may be possible that the different replicas were inheriting the design and one of the design templates was modified.

1. Go to Domino Designer and open the mail database.
2. Check if there is more than one $Inbox folder.

In-place with file size reduction -B Uses in-place compacting, recovers unused space and reduces file size,

unless there's a pending structural change in which case copy-style compacting occurs. If you use transaction logging, do full database backups after compacting completes.
In another case, this problem occurred in a mail file that had only one ($Inbox); however, the ($Inbox) view was corrupted. In that case, the issue was resolved by doing the following:
1. Created new folder called TEMPINBOX.
2. Selected all the current INBOX items and moved them to TEMPINBOX.
3. Using the Designer client, deleted the $INBOX design element.
4. Replaced the Design on the user mail file.
5. Sent new test message and mail now arrives in the new INBOX view.
6. Copied mail to new INBOX from TEMPINBOX folder
Caution: Beware that when the $Inbox folder is deleted (as is recommended in the next step), users will lose documents that are in the $Inbox. To avoid this, they should move the documents in the $Inbox folder to another folder (for example, Testfolder), and then delete the $Inbox, and replace design as specified to have only one $Inbox. Then, move the documents in Testfolder back to $Inbox.
3. If there are multiple $Inbox folders, delete them all.
4. Replace the design with the server template (by selecting File -> Database -> Replace Design, and specifying the template on the server).

In one case, a customer was able to resolve this issue by running compact -B on all affected mail files.

server Error : this database cannot be read due to an invalid on disk structure

Resolving the problem

This issue can occur if the user has "Always keep a copy" selected for the "Save mail that you sent" option under File > Preferences > User Preferences > Mail. If changing this setting to not keep a copy allows the user to successfully send the message, this would indicate a problem with the Sent folder being corrupt. Running fixup, compact and updall on the mail database should resolve the problem in this case. In one case, running these utilities did not resolve the issue and resulted in additional errors such as "Database is corrupt -- cannot allocate space." Further, when this database was opened in a browser, the error "HTTP Web Server: Lotus Notes Exception - Special database object cannot be located" displayed. Finally, an attempt to recompile all of the LotusScript code in the database resulted in 'Invalid syntax' errors.

How to add and delete member groups starting with special characters

To add such groups, follow these instructions:

In the text box under Customise -> People, prefix \\ (double backslash) to the group name and then such a group name can be added.

To delete such a group once added, you should have the following fix installed PM22013 .

Notes calendar free time displays wrong information

What can an administrator do when free time displays incorrectly?

Should the administrator rebuild the busytime.nsf database periodically?

Answer

Recreation of the free time database should be conducted during off hours. In some environments, this process can take several hours to complete and during the process, free time lookups will not work for anyone.

---

How to recreate busytime.nsf:
Busytime.nsf is the free time database on a non-clustered server. To rename the busytime.nsf file, do the following:

1. If possible, map a drive or FTP to the Domino server's Data directory.
2. In Domino Administrator, open the live console and issue the following commands:

tell sched q tell calconn q tell RnRMgr q (Domino 7 and later) dbcache flush NOTE: Several "dbcache flush" commands may be required depending on the operating system and server load.

3. In the Domino server's Data directory, locate busytime.nsf and rename it to something else, such as busytime.old. Then move it out of any data or any reference to a database or directory link. DO NOT leave the renamed copy in the Data directory hierarchy or you may encounter unexpected results..

4. Issue the following commands (not case sensitive):

load sched load calconn load RnRMgr (Domino 7 and later)

---

How to recreate clubusy.nsf:
Clubusy.nsf is the free time database on a clustered server. To recreate or restore it, do the following:

NOTE: This process must be done to all servers in the cluster to avoid replication. Please see the following link for instructions on sending a command to multiple servers at one time.
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Tip__Send_the_same_server_command_to_multiple_servers_at_once

1. If possible, map a drive or FTP to the Domino server's Data directory.
2. In Domino Administrator, open the live console.
3. Shut down the Sched and Calconn tasks on all clusters and flush the database cache with the following commands:

tell sched q tell calconn q tell RnRMgr q (Domino 7 and later) dbcache flush

NOTE: Several "dbcache flush" commands may be required depending on the operating system and server load.

4. On the Domino server's Data directory, find clubusy.nsf and rename it to something else, such as clubusy.old. Then move it out of any data or any reference to a database or directory link.

NOTES:
• DO NOT leave the renamed copy in the Domino server's Data directory hierarchy or you may encounter unexpected results.
• Steps 3 and 4 must be done on ALL clustermates before Step 5 is performed on any server. Otherwise, old data may be added back into the clubusy database and invalidate what you are trying to do. If you do not do this correctly, you must restart the process for clubusy.nsf over again.

5. Issue the following commands on all clustermates (not case sensitive):

load sched load CalConn load RnRMgr (Domino 7 and later)

---