Quantcast
Channel: Office 2013 and Office 365 ProPlus - IT Pro General Discussions forum
Viewing all articles
Browse latest Browse all 14306

Outlook 2013 Calendar Corruption

$
0
0

Hello,

I ran into this last week and was able to replicate the issue and have a workaround in place.

Environment: Windows 7 Pro SP1 x64 & Windows Server 2008 R2 running Exchange 2010 fully patched/updated.

Issue:

Day 1: User logs into Win 7 machine running Office 2013 Pro Plus and launches Outlook 2013, accesses Calendar --> Multiple (4) Shared Calendars (some connected to SharePoint); No Issue.

Day 2: User logs into OWA (Outlook Web App) and accesses Calendar --> Multiple Shared Calendars; Some shared calendars do not display.

Day 3: User logs back into the Win 7 machine and opens Outlook 2013, accesses Calendar --> Multiple Share Calendars; Cannot open some shared calendars and receives an error that the calendar cannot be found/accessed.

Workaround: Remove and Create a new Outlook Profile under Control Panel - Mail 32-bit

User is able to reconnect to all Calendars.

Error:

"The operation failed. The message interfaces have returned an unknown error. If the problem persists, restart outlook.

-

System

   

- 

   

Provider

   
   

[    Name]

   
   

Microsoft     Office 15 Alerts

   
   

-

   
   

EventID

   

300

   
   

[    Qualifiers]

   
   

0

   
   

Level 

   

4

   
              

Task

   

0

   
   

Keywords

   

0x80000000000000

   
   

-

   
   

TimeCreated   

   

[    SystemTime]

   
   

2013-08-27T15:09:24.000000000Z

   
   

EventRecordID

   
   

103

   
Channel      

OAlerts

   

Computer

   

XXXXXXXX

   
Security   

 

-

EventData

Microsoft   Outlook

 

The   operation failed. The messaging interfaces have returned an unknown error. If   the problem persists, restart Outlook.

301670  

15.0.4517.1509  

acikm

0x80040201 

Thoughts?



Viewing all articles
Browse latest Browse all 14306

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>