My colleague and I are at a loss with this. We've had a company look at the problem and they are at a loss too.

We had exchange 2007, upgraded to 2013 in the summer of 2013 and migrated all the mailboxes, public folders and shared calendars across. Everything was fine until the people who should be able to edit the shared calendars couldn't. New appointment button was greyed out. They all have permission to do this, however it's not working.

It's really intermittent too. You would close Outlook (2010) open it and then it works, and then close it again and it stops working. Sometimes even stops working when your working on it.

Exchange is virtualized and Hyper-V being the hyper-visor. The server it's on is a 2013 Server too.

It's been driving us nuts, and the company said that they've had to let Microsoft know of the issue, but it might not even get addressed.

All I'm looking for is a step for a hint or maybe even an alternative to it all?

  • What kind of shared calendar? Public folder calendar or resource mailbox or user mailbox? – TheCleaner Oct 28 '13 at 17:37
  • I bet you're not actually running Windows 2013 Server. – mfinni Oct 28 '13 at 18:13
  • Sorry, yeah its 2010. It's a user mailbox calendar that we set up as a 'favour' for folk and has now turned into a necessity. For instance we have a car that people book out. We set up a mailbox called Car. We then gave certain folk permission to view it and others permission to edit. Now since the switch to 2013 (exchange) we get this intermittent allowing and denying of access to create a new entry. – Paulst30 Oct 29 '13 at 19:11
  • Have you reviewed the RPC client access logs on your Exchange server? Turn up the logging, and see if you can get a success and a failure at known times and see what the logs say. – mfinni Nov 1 '13 at 21:14
  • This sounds like a user mailbox issue. After upgrading to the new Exchange server, did you upgrade all of your user mailboxes? By default after a migration, the 2007 mailboxes will remain 2007 until you manually update them to 2010/2013. This can cause unexpected behavior, such as permissions wonkiness. – Thomas Jan 4 '17 at 17:38

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.