This project has moved and is read-only. For the latest updates, please go here.

Outlook 2010 Import produces CalCheck detected errors

Apr 2, 2013 at 9:02 PM
Edited Apr 2, 2013 at 9:05 PM
Hi, when we import a csv file of Flex day calendar bookings it results in CalCheck detecting an error for each imported item. Is this an Outlook 2010 issue or do we have some other problem? Any tips would be welcomed. Our environment is Outlook 2010 on Exchange 2007.

CalCheck run immediately before the import detects no errors. Run immediately after the import results in all imported items being marked as the same error.

The CalCheck error is
04/02/2013 11:48:35AM   Error: The dispidGlobalObjectID and the dispidCleanGlobalObjectID properties are not populated on this item.

04/02/2013 11:48:35AM          Many mobile devices that sync through Exchange Active Sync will not sync items that are missing these properties,

04/02/2013 11:48:35AM          so this item may not show on a device if it is in use with this mailbox.

04/02/2013 11:48:35AM          Please see the following article for additional information: 

04/02/2013 11:48:35AM   Properties to help investigate this reported item:

04/02/2013 11:48:35AM   This item occurred in the past and ended: 01/19/2013 08:00:00AM

04/02/2013 11:48:35AM   Subject:  Flex Day B
                        Start Time:  01/18/2013 08:00:00AM
                        End Time:  01/19/2013 08:00:00AM
                        Last Modifier:
                        Last Modified Time: 04/02/2013 06:47:28PM
                        Is a recurring appointment:  false
                        Sender Name:  
                        Sender Address:  
                        Organizer Name:  
                        Organizer Address: 
A fragment of the csv file is below:
Subject,Start Date,Start Time,End Date,End Time,All day event,Reminder on/off,Reminder Date,Reminder Time,Meeting Organizer,Required Attendees,Optional Attendees,Meeting Resources,Billing Information,Categories,Description,Location,Mileage,Priority,Private,Sensitivity,Show time as
Flex Day B,1/18/2013,8:30:00 AM,1/18/2013,5:00:00 PM,TRUE,FALSE,1/18/2013,8:30:00 AM,,,,,,,Flex Day B,,,Normal,FALSE,Normal,4
Flex Day B,2/1/2013,8:30:00 AM,2/1/2013,5:00:00 PM,TRUE,FALSE,2/1/2013,8:30:00 AM,,,,,,,Flex Day B,,,Normal,FALSE,Normal,4
Apr 3, 2013 at 1:44 PM

Yes - since you are not specifically populating the global object id properties - you are getting this.
The issue at hand here is that many mobile devices that sync with Exchange use these values for tracking what has/hasn't been sync'd to the device, etc. So if they are missing - then they might not sync to the device.

If that is not an issue for you - you can edit the CalCheck.cfg file and set the "NoGlobalObjectIDs" test to "false" and CalCheck will ignore these.

Apr 3, 2013 at 8:02 PM
Thanks for responding so quickly on this. Yes, I gues I could turn the test off, but at the same time I want to know that all my meetings are configured correctly as we were having some users lose meetings.

This may be a stupid question, so please help me ask the correct one when you answer. But - since I'm using Outlook's import function and I don't think that there is any place I can define dispidGlobalObjectID and dispidCleanGlobalObjectID using the csv import - shouldn't Outlook 2010 build correct items?

Apr 3, 2013 at 10:05 PM
Right - so Outlook and Exchange do not necessarily need these props to be present for them to function. They are really used more for recurring meetings - so that Outlook/Exchange can match up exceptions to the series with the series. So NOT having them on single instance items is / can be fine.

The problem is more with how third party devices interact with these properties - and that is why they get flagged.