Outlook Error Could Not Read The Calendar
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Sun, 23 Oct 2016 17:59:01 GMT by s_nt6 (squid/3.5.20)
van GoogleInloggenVerborgen veldenZoeken naar groepen of berichten
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get https://www.experts-exchange.com/questions/27393981/Could-Not-Read-Calendar.html Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers http://www.markwilson.co.uk/blog/2012/10/could-not-read-the-calendar-outlook-cannot-open-this-item-the-item-may-be-damaged.htm Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > "Could Not Read Calendar" Want to Advertise Here? Solved "Could Not Read Calendar" Posted on 2011-10-12 Outlook 1 Verified Solution 16 Comments 1,681 Views Last Modified: 2014-08-18 I have a user on our network (SBS 2008 using exchange mailboxes) that cannot read shared calendars. could not We are using Outlook 2010 and each one in the office has shared their calendars with one another using the "Share Calendar" function and choosing the email list from Global Address. Everyone else is fine and can view calendars, but this one particular user cannot, most of the time. Sometimes if he closes all other calendars, opens a shared calendar by itself, then opens other calendars it might work. It's very could not read inconsistent and I can not find a rhyme or reason to it. I have ran a scanpst, I have created a new user in Outlook, I've re-created the .ost file and I've restored "View" settings to no avail. Anyone have any answers? Windows 7 64 bit Office 2010 32 bit 0 Question by:Randy Cole Facebook Twitter LinkedIn Google Best Solution byRandy Cole Seemed to be an issue with this particular mailbox. We have deleted the mailbox and started fresh and the issue doesn't seem to be there any longer. Go to Solution 16 Comments LVL 47 Overall: Level 47 Outlook 45 Message Expert Comment by:apache092011-10-12 UNless you have a type'o there 64 bit OS, requires 64 bit Office 2010 0 LVL 11 Overall: Level 11 Outlook 9 Message Expert Comment by:DavidT5432011-10-13 Correction to apache09 - Microsoft recommend running 32bit Office - even on 64bit OS http://technet.microsoft.com/en-us/library/ee681792.aspx 0 LVL 11 Overall: Level 11 Outlook 9 Message Expert Comment by:DavidT5432011-10-13 How are they choosing the calendar to view - and what error do they get? 0 Message Author Comment by:Randy Cole2011-10-13 Yes DavidT543, you are correct. I did my research before installing Office and Microsoft DOES recommend 32 bit, no matter the OS. Each calendar is shared by
dump my corporate laptop* and this week has been no exception with abysmally slow performance, new software installs that require reboots and then, after working well (so nothing to do with the Cisco unified communications integration components that I installed yesterday), Outlook decided that it didn't like my calendar any more. Other people's calendars were fine; other folders (Inbox, etc.) were fine; and the calendar data was fine, as long as I didn't want a day/week/month view. Could not read the calendar. Outlook cannot open this item. The item may be damaged. OK, but which item? I could take a guess that this was something to do with a corrupted offline folders (.OST) file but a bit of Googling turned up a fix. In a TechNet Forum post Exchange MVP Rich Matheisen suggests deleting the OST file (the location of this can be found from Outlook's Account Settings), then running outlook /cleanfreebusy to create a new .OST and pull down the free/busy calendar information. One slight snag was that I couldn't rename/delete the existing Outlook.OST file because it was in use. This time, Windows was a little more helpful with its error reporting, telling me that the Microsoft Windows Search Protocol Host had the file open. The answer was to open services.msc, stop the Windows Search service, then work on the Outlook.OST file, before restarting the Windows Search service. Outlook is now happy again, but I'm not convinced it would have been any quicker to go via the official support channels (probably would have necessitated a visit to the office for the deskside support guys to take a look) than to self-support… which makes me wonder if corporate IT budgets would be better spent on providing cross-platform technology services, rather than maintaining and supporting standard PC builds? * I make no secret that I'm not a fan of standard operating environments ("gold brick" PC builds) with layers and layers of "security" software. Even though I spent many years implementing such solutions (and reaping the rewards in terms of reduced support costs, etc.), it's an outdated model that has no place in an age of consumerisation (for many knowledge workers at least - of course, there are exceptions, e.g. in heavily regulated environments). There are many who will say, "so what do you suggest instead?", to which my response is: