Calendar Items that You Copied Do Not Allow Meeting Updates

Every item in MS Outlook 2000 possesses a unique identity. Each and every item gets stored up with a unique identifier. This particular unique identifier helps in identifying the item whenever there is a need to in numerous situations.

Every unique identifier has a code that tells you in which storage area an item is being stored in. The storage area could be a Personal Storage Folders .PST, a Microsoft Exchange mailbox, or an offline address book.

Another advantage of unique identifier is its ability to distinguish between two identical items that have been copied into two different stores. Messaging Application Programming Interface (MAPI) has a requirement for unique identifiers for all items even the store ID must be in the unique identifier. This way MAPI can verify for the item’s unique identifier.

If you want to locate an original meeting for updating it, then unique identifier would be very much helpful. But, when you move an item between stores or storage areas, the item’s unique identifier changes and Outlook treats the item as a different meeting. Actually, the unique identifier that is required for a meeting synchronization is set during the initial processing of the meeting request. Therefore, if you are using the Exchange mailbox or a Personal Folders .PST file, the calendar must work properly.

Whenever there are meeting requests in an organization, Outlook has a tendency to work with one message store for the calendar at a time. At that time the copied calendar items are not updated. If you want to change this behavior, then you would be required to change the entire extensive designs. Outlook’s object model needs to be rewritten.

Problem does arise when there is copying of calendar items from one storage area to another. If you copy an Exchange mailbox to a .PST Personal Storage file, quite often you get meetings displaying a SEND button instead of a SEND UPDATE button. To tackle the situation, it is recommended that you write a Component Object Model (COM) Add-In or Exchange Client Extension for removing the original meeting. So now the newly received meeting request gets replaced with the previous one meeting.

Still you are not able to handle this issue, and then there may be the other reason behind it. The reason could be the corruption in the PST file or Exchange Server. This can be resolved using efficient email recovery software. Kernel for Outlook Repair is one such tool for dealing with Outlook disaster issues. It is supportive to all versions of MS Outlook for PST file repair.