none
Shared calendars not working after mailbox move RRS feed

  • Question

  • Hi

    Upgrading/migrating from EX2003 to EX2010 - all Outlook 2003 clients at present. Finding more and more issues during the process.

    Latest one is that shared calendars no longer work after we've moved a mailbox from EX2003 to EX2010. Even if the user whose mailbox was moved re-adds a person in to the permissions list again, that person still can't open the calendar. Error is:

    "Unable to display the folder. The information store could not be opened"

    Is there anything else we need to do (at the server side maybe) which needs to be done for this to work. We've only moved a few users so far and it's a bit worrying how many niggly problems we're finding. We've got about 3000 users to move in total.

    Thanks

     

    Thursday, July 8, 2010 7:56 AM

Answers

All replies

  • Shared mailboxes can be a pain. The usual problem is that if you move a user who has shared mailboxes open in Outlook and the shared mailbox is also not moved, then Outlook cannot find it again. You have to remove it and open it again so that Outlook finds the new location.

    However, I notice that you are using Outlook 2003. I have been hearing things about a bug with Outlook 2003, Exchange 2010 and shared calendars giving the error that you have posted. No resolution as yet, other than a change to Outlook 2007/2010. Whether Microsoft support have a private fix, only contacting them would allow you to find out.

    Simon.


    Simon Butler, Exchange MVP. http://blog.sembee.co.uk , http://exbpa.com/
    Thursday, July 8, 2010 9:01 AM
  • Quote: “Even if the user whose mailbox was moved re-adds a person in to the permissions list again, that person still can't open the calendar”

    So, exchange 2010 mailbox users (Migrated) can’t open the share calendars that belong to the mailboxes of the exchange 2003 server, right?

    RPC encryption has been enabled on the outlook 2003, right? (KB 2006508)

    Resources:

    An error occurs when an Exchange server 2003 user tries to open more than one delegate mailbox of Exchange Server 2010 in Outlook 2003


    James Luo
    TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx)
    If you have any feedback on our support, please contact tngfb@microsoft.com
    Friday, July 9, 2010 2:04 AM
    Moderator
  • Hi

    It's the other way round. The calendars of the people who have migrated to 2010 can't be opened by those still on 2003, even if they re-add the user in the permissions list.

    Encryption is enabled on the OL2003 clients

    Thanks

     

    Friday, July 9, 2010 6:17 PM
  • Have you tried this hotfix as James suggested http://support.microsoft.com/kb/979690/en-gb 

    Have you also tried re-creating the client mail profile?

    Saturday, July 10, 2010 1:49 AM
  • Thanks James-Lou!

    I hope I can help someone with my comment (also Dutch part):

    My Outlook 2003 users on the exchange 2003 server couldn't get the free bussy information from a mailbox located on the Exchange 2010 server.

    Every link I found was related to public folder sync, but this thread gave me the right answer. Encrypting the connection from outlook 2003 to exchange 2010 fixt it for me.

    I also had a message “Unable to open your default e-mail folders” when I tried to open a mailbox on Exchange 2010 with Outlook 2003. You can use the same solution to solve this problem.  Usefull link: http://www.howexchangeworks.com/2009/09/cant-connect-outlook-2003-to-exchange.html

     

    Voor de Nederlanders onder ons:

    Aanmeldingen met Outlook is niet mogelijk. Controleer of u een verbinding hebt met het netwerk en of u de juiste server en postvaknaam gebruikt. De verbinding met de Microsoft Exchange-server is niet beschikbaar. Outlook moet on line zijn of er moet een verbinding zijn om deze actie te voltooien.

    Oplossing

    Bij de connectie instellingen van Outlook 2003 -> tabblad Beveiliging
    Vinkje: Gegevens coderen tussen Microsoft Office Outlook en Microsoft Exchange Server.

    Friday, July 23, 2010 12:26 PM