For us, it wasn't causing a critical issue like an entire server load of people would have, and our workaround was to recreate mailboxes. Downtime for each affected user was 3 minutes - 30 minutes depending on the size of the mailbox. If we had no workaround, you can be sure we'd have been on the phone :)
Richard -----Original Message----- From: bounce-9241830-8066...@lyris.sunbelt-software.com [mailto:bounce-9241830-8066...@lyris.sunbelt-software.com] On Behalf Of Michael B. Smith Sent: 12 January 2011 23:56 To: MS-Exchange Admin Issues Subject: RE: Exception message: The start time has not been set. No. I've just seen the complaint several times although none of my personal customers have experienced it (and let me open a PSS call). The PM I pinged at MSFT said they didn't have any issues like this "trending up" (i.e., a growing call volume) and he wasn't aware of it. So... call records are things I can use to push attention. If people don't care enough to open a call, MSFT considers the issues not particularly important. (Note: that's a generalization. But a fairly accurate one.) Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -----Original Message----- From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk] Sent: Wednesday, January 12, 2011 6:46 PM To: MS-Exchange Admin Issues Subject: RE: Exception message: The start time has not been set. We haven't; since we couldn't confirm if it was a problem caused by mobile devices or a bug in Exchange I think we decided to carry on trying to gather information and see if there was a common cause. We haven't seen any new occurrences since the New Year though, the servers got RU5 on or around the 17th December last year courtesy the wrong button being pushed in WSUS, and were rebooted at the same time. Do you know something I don't? :) ________________________________________ From: bounce-9241800-8066...@lyris.sunbelt-software.com [bounce-9241800-8066...@lyris.sunbelt-software.com] on behalf of Michael B. Smith [mich...@smithcons.com] Sent: 12 January 2011 22:56 To: MS-Exchange Admin Issues Subject: RE: Exception message: The start time has not been set. Have you opened a case on this Richard? Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -----Original Message----- From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk] Sent: Wednesday, January 12, 2011 12:16 PM To: MS-Exchange Admin Issues Subject: RE: Exception message: The start time has not been set. I do believe we have the same issue, and more: 1) Clicking on Calendar folder in OWA Premium crashes IE, but works fine in Light mode. 2) Some Calendar items have no start date, making them corrupt. 3) ActiveSync cannot sync Calendar meeting requests. However, the "Exception message" we get is different. I'll try and dig out some examples if you like. I have confirmed that moving an affected mailbox (only done this once, to a test account that was experiencing the problem) to Exchange 2010 and back again resolved at least one of those problems (1). We run Exchange 2007 SP2 RU5, all roles on separate servers. Cheers Richard -----Original Message----- From: bounce-9241387-8066...@lyris.sunbelt-software.com [mailto:bounce-9241387-8066...@lyris.sunbelt-software.com] On Behalf Of Kennedy, Jim Sent: 12 January 2011 16:29 To: MS-Exchange Admin Issues Subject: RE: Exception message: The start time has not been set. Thanks, that might be a clue. No BES, but the affected users have smartphones. I am out for training for the rest of the week, I will dig in Monday. If I get no where I will open up a PSS and certainly report the findings either way. ________________________________________ From: Michael B. Smith [mich...@smithcons.com] Sent: Wednesday, January 12, 2011 11:16 AM To: MS-Exchange Admin Issues Subject: RE: Exception message: The start time has not been set. I asked around about this - the only comment I got was to also ensure you are current with BES and BES/X if you have either in your environment... Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -----Original Message----- From: Kennedy, Jim [mailto:kennedy...@elyriaschools.org] Sent: Tuesday, January 11, 2011 9:24 AM To: MS-Exchange Admin Issues Subject: RE: Exception message: The start time has not been set. Yes, fully current. I keep up with that pretty well. Hub Server is also the CAS role. Then two mailbox servers. CAS sits behind ISA. -----Original Message----- From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, January 11, 2011 9:14 AM To: MS-Exchange Admin Issues Subject: RE: Exception message: The start time has not been set. I've seen this somewhere. Are you current on SPs and URs? Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -----Original Message----- From: Kennedy, Jim [mailto:kennedy...@elyriaschools.org] Sent: Tuesday, January 11, 2011 9:08 AM To: MS-Exchange Admin Issues Subject: Exception message: The start time has not been set. Exchange 2007. A handful of random users trying to accept meetings. This only happens on OWA, same user can accept the same appointment in Outlook with no issues. OWA version: 8.3.137.0 Mailbox server: munged Exception Exception type: Microsoft.Exchange.Data.Storage.CorruptDataException Exception message: The start time has not been set. Call stack Microsoft.Exchange.Data.Storage.CalendarItemBase.get_StartTime() Microsoft.Exchange.Data.Storage.MeetingRequest.UpdateMeetingRequest(CalendarItemBase calendarItem) Microsoft.Exchange.Data.Storage.MeetingRequest.UpdateCalendarItemInternal(CalendarItemBase& correlatedCalendarItem) Microsoft.Exchange.Data.Storage.MeetingMessage.TryUpdateCalendarItemInternal(CalendarItemBase& originalCalendarItem, Boolean shouldThrow, Boolean canUpdatePrincipalCalendar) Microsoft.Exchange.Data.Storage.MeetingMessage.UpdateCalendarItem(Boolean canUpdatePrincipalCalendar) Microsoft.Exchange.Clients.Owa.Core.MeetingUtilities.UpdateCalendarItem(MeetingRequest meetingRequest) Microsoft.Exchange.Clients.Owa.Premium.EditMeetingInviteEventHandler.NonEditResponseInternal(Boolean sendResponse) --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
