My Exchange Calendar shows an "Exclamation Error" but there is no detail when I click it.

Question

OSX 10.8.2
Added an Exchange Account through the wizard, Calendar worked for a number of months but stopped some time recently. 
Perhaps when I did a password change. 
Perhaps when I upgraded to Outlook 2013 on my work PC
Updated my password, Mail works, Contacts work, but Calendar does not sync.  Small Exclamation Mark does not show error when clicked so I can't tell what the real problem it.  Tried to remove and re-add the account, same issue. 
Checked out the Console logs and it throws these three errors below.  There is something with the "LegacyFreeBusyStatus" that is causing the sync to fail.  Outlook 2013 has a new status of "working somewhere else".  I had used it for a few items.  I also found an item that had a Null status (like what it is pointing to in the error).  Removed that item and changed all the others to a valid stauts for previous versions of outlook.  ie. Free, Busy, etc. 
2/12/13 3:29:32.871 PM CalendarAgent[19447]: [com.apple.calendar.store.log.exchange.queue] [-[CalOperationQueue executeOperations] :: [<EWSCalendarItemType 0x7f9dfac9e9b0> setNilValueForKey]: could not set nil as the value for the key LegacyFreeBusyStatus.]
2/12/13 3:29:32.872 PM CalendarAgent[19447]: [com.apple.calendar.store.log.exchange.queue] [error = Error Domain=CalExchangeErrorDomain Code=-1 "Calendar can’t refresh the account “Exchange”." UserInfo=0x999dfaaa0000 {NSLocalizedFailureReason=The account "Exchange" currently can’t be refreshed., CalFailedOperationKey=<CalExchangeSyncFolderItemsOperation: 0x7f9df521de50>, NSLocalizedDescription=Calendar can’t refresh the account “Exchange”.}]
2/12/13 3:29:33.623 PM CalendarAgent[19447]: Unexpected type EWSMessageType for calendar Calendar in account Exchange

Answer 1

Whaoo,
   Looks like all I needed to do was ask the question and I would answer it. 
It is definitely the outlook 2013 calendar item that had the new status.  Even though I changed the item to a valid status, I needed to completely remove the item and add it back in with a valid legacy status from the start. 
-The Steve