Troubleshooting

Common Issues

The following troubleshooting tips list common problems and suggestions on how to correct them. Because underlying problems are often difficult to identify, you should perform regular maintenance to diagnose and repair problems or prevent them entirely.

What problem are you having?

Replication is not taking place between Organizations.

Check the Ex00yymmdd.log and Ex01yymmdd.log log files for errors.
These error logs are created when you add a session to the configuration file. You specify at that time where the log files are saved. The log files can be viewed with any text editor, such as Microsoft Word.
Use the application Event Viewer to make sure there are no errors.
Configure the Event Viewer to 2 MB, and configure it to wrap as needed. For more information, see the Windows 2000 documentation for Event Viewer.
Verify that you have granted the appropriate permissions to root folders and the ExchsyncSecurity Folder.
These permissions are set when you prepare the publisher server and prepare the subscriber server. If they do not have the appropriate permissions, you will receive the following error message:

Event ID 116
Source Exchsync
Type Error
Category None
Mailbox user (username) does not have enough security to replicate to server [servername] on session 'Session Name'.
WARNING: Create subfolder access is not available to '[SERVERNAME]\Foldername, skipping.
WARNING: Write access is not available to '[SERVERNAME]\ Foldername, skipping.
WARNING: Write access is not available to '[SERVERNAME]\ Foldername \ Foldername,skipping.
WARNING: Read access is not available to '[SERVERNAME]\ Foldername, skipping.
WARNING: Read access is not available to '[SERVERNAME]\ Foldername \ Foldername, skipping.

Verify that each mailbox you are replicating free and busy information to on the publisher server has a corresponding custom recipient on the subscriber server.
If none exist, create them. The Simple Mail Transfer Protocol (SMTP) address of the mailbox matches the mailbox to its corresponding custom recipient. If a corresponding custom recipient does not exist, free and busy information is not published.
If free and busy information is not displayed after you verify that the custom recipients exist, quit, and then restart your client.
This causes your free and busy information to be written to the server. The next replication cycle will then publish your free and busy information.

I am unable to successfully publish a form in the Organizational Forms Library due to a MAPI error.

Cause
The form cannot be installed because you do not have owner permission.
Solution
By default, Exchange 2000 grants all users read-only rights on the EForm folder. The EForm folder is a system folder used to maintain the Organizational Forms Library. To grant a user the ability to publish a form to the Organizational Forms Library, grant the user All Folder rights and All Message rights.
See also
Maintain the Organizational Forms Library