If you assign a task to a user on another Exchange Server computer and select only the Send me a status report when this task is complete
option, you may not receive an update when the task is completed.
This issue can occur because the list of recipients that receive the status report is stored in the Bcc
field of the task. Therefore, when the client requests the list, the client receives an empty list and cannot locate the recipient.
To resolve this problem, obtain the latest service pack for Exchange Server 5.5. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack
: When you start this version of the information store, the information store databases are automatically upgraded to a new format. After the databases have been upgraded, you can restore an earlier version of the Store.exe file on the server, but only if it is version 5.5.2652.68 or later. If you restore a Store.exe file earlier than version 5.5.2652.68 after the database has been upgraded, you are no longer able to start the information store. For additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
XADM: Event ID 1197 and 1005 When Starting the Information Store
The following files are available for download from the Microsoft
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.
To work around this issue, only assign one task for each user at any given time. Use two separate tasks if two users both need to complete the task.
Microsoft has confirmed that this is a problem in Microsoft Exchange Server 5.5 Service Pack 3. This problem was first corrected in Exchange Server 5.5 Service Pack 4.