To troubleshoot this issue, follow these steps:
- Start Exchange System Manager, and then view the mailboxes under the default store in the First Storage Group. By default, the System Attendant mailbox is located in this mailbox store. Note the total number of items in the System Attendant mailbox and the total size of the mailbox. To do this, follow these steps:
- In Exchange System Manager, if administrative groups are enabled, expand Administrative Groups, and then expand First Administrative Group.
- Expand Servers, expand your Exchange server, expand First Storage Group, and then expand Mailboxes.
- In the right pane, note the total number of items in the System Attendant mailbox and the total size of the System Attendant mailbox.
- Start OWA, and then create a test appointment. Save the appointment.
- Return to Exchange System Manager to determine if the number of items in the System Attendant mailbox has increased. If the number of items in the System Attendant mailbox has increased, continue to step 4.
If the number of items in the System Attendant mailbox has not increased, it is likely that you are experiencing a CDO problem. CDO is controlled by the Cdoexm.dll file. In this scenario, look for other CDO errors in the application log to help you troubleshoot CDO. - Verify the client permissions that are assigned to the Schedule+ Free/Busy folder. The following client permissions should be assigned to the Free/Busy folder:
Collapse this tableExpand this table
Name | Role |
Default | Editor |
Anonymous | None |
To view these permissions, follow these steps:- In Exchange System Manager, under First Storage Group, expand Public Folder Store (SERVERNAME), and then click Public Folders.
- In the right pane, right-click Schedule+ Free Busy Information - First Administrative Group, and then click Properties.
- Click the Permissions tab, and then click Client permissions.
- Create a profile for the System Attendant service, and then open the root folder for all mailboxes. To do this, follow these steps.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756�
How to back up and restore the registry in Windows
- Click Start, click Run, type regedit in the Open box, and then click OK.
- Locate and then click the following registry subkey:
HKEY_USERS\.DEFAULT\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles
- Under the Profiles registry subkey, click ExchangeAdmin SERVERNAMEhexadecimal string.
Note There may be many of these registry subkeys listed under Profiles. Click any one of them. - On the Registry menu, click Export Registry File.
- In the File name box, type a name such as systemattendantprofile, and then click Save.
- Right-click the .reg file that you saved, and then click Edit.
- Replace all instances of HKEY_USERS\.DEFAULT in the .reg file with HKEY_CURRENT_USER, and then save the changes to the .reg file.
- Copy the modified .reg file to a computer where Microsoft Outlook is installed. If you have Outlook installed on the Exchange 2000 computer, you do not have to copy the file to another computer.
Note Microsoft does not recommend that you install Outlook on your Exchange 2000 computer. For additional information, see this article:266418�
Microsoft does not support installing Exchange Server and Outlook on the same computer
- On the computer where Outlook is installed, double-click the .reg file, click Yes when you are prompted to add the information to the registry, and then click OK when you receive a message that states that the information has been successfully imported into the registry.
- On the computer where you imported the .reg file, start Registry Editor, and then locate the following registry subkey:
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging
Subsystem\Profiles
- Verify that ExchangeAdmin SERVERNAME hexadecimal string appears together with the corresponding subfolders. If this registry key appears, you have successfully created a MAPI profile for the System Attendant.
- On the computer where you imported the .reg file, start the Exchange Information Store viewer (Mdbvu32.exe). This file is located in the Support\Util\I386 folder on the Exchange 2000 Server CD.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
316279�
XGEN: Tools that are included with the Exchange 2000 Server CD-ROM
- In the MAPILogonEx(MAPI_LOGON_UI) dialog box, click to select the following check boxes, and then click OK:
- MAPI_NEW_SESSION
- MAPI_EXPLICIT_PROFILE
- MAPI_NO_MAIL
- In the Choose Profile dialog box, click ExchangeAdmin SERVERNAME hexadecimal string in the Profile Name list, and then click OK.
- On the MDB menu, click OpenMessageStore.
- Click Mailbox - System Attendant, and then click Open.
- On the MDB menu, click Open Root Folder.
- In the Child Folders box, note the list of child folders. The free/busy messages are stored in the SpecialPrivateFolderForFreeBusy folder. Double-click this folder to determine if you can access it.
When you troubleshoot a permissions issue, move up the chain of inherited permissions if you do not detect a permissions problem with the particular mailbox or with the client permissions. By default, permissions are inherited from the parent object. If the permissions that are set on a particular object are correct, view the permissions of that object's parent object, and so on. For example, make sure that you do not have an explicit Deny permission for the
Create names properties in the Information Store permission on the public folder store. Explicit Deny permissions override Allow permissions.
After you finish troubleshooting permissions on the public folder store, restart the server.