[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?
Solved

"This meeting is not in the calendar; It may have been moved and deleted"

Posted on 2011-03-09
4
Medium Priority
?
654 Views
Last Modified: 2012-05-11
I have been running into several users who are recieving the following error message after receiving meeting invites.
"This meeting is not in the calendar; It may have been moved and deleted"

It's sporadic and I havn't been able to track down the cause. I havn't been able to find any event logging related to calendering that I can bump up. What would be the best way to proceed to troubleshoot?

Thanks
0
Comment
Question by:HappyMapi
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 8

Accepted Solution

by:
point_pleasant earned 2000 total points
ID: 35086778
Common problem of this issue is delegate receiving meeting requests of the manager and if delegate deletes the meeting request, manager will receive this error pop up that your manager is receiving.
 
Check if the below KB article helps
http://support.microsoft.com/kb/899704/en-us 
0
 

Author Comment

by:HappyMapi
ID: 35086881
Thanks Point. I am familiar with delegates causing this issue however I'm also running into this on my own account and I have  no delegates.

In the article you refrenced it mentions"
Turn on Calendar logging for executives and for other frequent users" I'm not familiar with how to do this. Is this event loggiing I can set with Exchange (running exchange 2007)? I find no refrence to calendaring event logging. Below is a copy of my  powershell query results for event log data.

Identity    : MSExchange Common\General
IsValid     : True
ObjectState : Unchanged
Name        : General
Number      : 1
EventLevel  : Lowest

Identity    : MSExchange Common\Configuration
IsValid     : True
ObjectState : Unchanged
Name        : Configuration
Number      : 2
EventLevel  : Lowest

Identity    : MSExchange Common\Logging
IsValid     : True
ObjectState : Unchanged
Name        : Logging
Number      : 3
EventLevel  : Lowest

Identity    : MSExchange Extensibility\Transport Address Bo
IsValid     : True
ObjectState : Unchanged
Name        : Transport Address Book
Number      : 1
EventLevel  : Lowest

Identity    : MSExchange Extensibility\MExRuntime
IsValid     : True
ObjectState : Unchanged
Name        : MExRuntime
Number      : 2
EventLevel  : Lowest

Identity    : MSExchange EdgeSync\Synchronization
IsValid     : True
ObjectState : Unchanged
Name        : Synchronization
Number      : 1
EventLevel  : Lowest

Identity    : MSExchange EdgeSync\Topology
IsValid     : True
ObjectState : Unchanged
Name        : Topology
Number      : 2
EventLevel  : Lowest

Identity    : MSExchange EdgeSync\SyncNow
IsValid     : True
ObjectState : Unchanged
Name        : SyncNow
Number      : 3
EventLevel  : Lowest

Identity    : MSExchange Management Application\Shell
IsValid     : True
ObjectState : Unchanged
Name        : Shell
Number      : 1
EventLevel  : Lowest

Identity    : MSExchange Management Application\Console
IsValid     : True
ObjectState : Unchanged
Name        : Console
Number      : 2
EventLevel  : Lowest

Identity    : MSExchange Process Manager\ProcessManager
IsValid     : True
ObjectState : Unchanged
Name        : ProcessManager
Number      : 1
EventLevel  : Lowest

Identity    : MSExchange System Attendant Mailbox\General
IsValid     : True
ObjectState : Unchanged
Name        : General
Number      : 1
EventLevel  : Lowest

Identity    : MSExchange Topology\Topology Discovery
IsValid     : True
ObjectState : Unchanged
Name        : Topology Discovery
Number      : 1
EventLevel  : Lowest

Identity    : MSExchange ADAccess\General
IsValid     : True
ObjectState : Unchanged
Name        : General
Number      : 1
EventLevel  : Lowest

Identity    : MSExchange ADAccess\Cache
IsValid     : True
ObjectState : Unchanged
Name        : Cache
Number      : 2
EventLevel  : Lowest

Identity    : MSExchange ADAccess\Topology
IsValid     : True
ObjectState : Unchanged
Name        : Topology
Number      : 3
EventLevel  : Low

Identity    : MSExchange ADAccess\Configuration
IsValid     : True
ObjectState : Unchanged
Name        : Configuration
Number      : 4
EventLevel  : Lowest

Identity    : MSExchange ADAccess\LDAP
IsValid     : True
ObjectState : Unchanged
Name        : LDAP
Number      : 5
EventLevel  : Lowest

Identity    : MSExchange ADAccess\Validation
IsValid     : True
ObjectState : Unchanged
Name        : Validation
Number      : 6
EventLevel  : Low

Identity    : MSExchange ADAccess\Recipient Update Service
IsValid     : True
ObjectState : Unchanged
Name        : Recipient Update Service
Number      : 7
EventLevel  : Lowest

Identity    : MSExchange ADAccess\Site Update
IsValid     : True
ObjectState : Unchanged
Name        : Site Update
Number      : 8
EventLevel  : Lowest


Thanks
0
 
LVL 8

Expert Comment

by:point_pleasant
ID: 35087323
have you tried
1)Close your outlook and search your computer for FRMCACHE.DAT file.
Make sure to select hidden and system files.

Delete it.
Restart Outlook.

Outlook should rebuild FRMCACHE.DAT file.

2) Other option is to to run outlook.exe /cleanreminders command line switch
0
 

Author Comment

by:HappyMapi
ID: 35109869
I can try that but I would like to look at logging to see what is happening. I know I can bump up logging on the Outlook side but what event type logging should I increase on the server?
Thanks
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

By default Outlook 2016 displays only one time zone in the Calendar. The following article explains how to display two time zones in one calendar view.
With so many activities to perform, Exchange administrators are always busy in organizations. If everything, including Exchange Servers, Outlook clients, and Office 365 accounts work without any issues, they can sit and relax. But unfortunately, it…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses

649 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question