Free Microsoft Outlook Resources & Whitepapers

Can't open shared calendars after migrating to Exchange 2010

We recently migrated users from Exchange 2003 to Exchange 2010 and users are having problems accessing other user calendars that were shared in 2003 but for some reason are no longer working after migration. I see there is a problem for users trying to access shared calendars from mailboxes on the Exch 2010 from mailboxes on Exch 2003, but this one is slightly different that both mailboxes and calendars are on exchange 2010, has any one else found this problem and is there an fix or workaround?

The error that the users get back when trying to open the shared calendar is - The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action.

When I check the connection status of the users outlook they are online or connected.

The other problem that the users who are effected have noticed is if they go into the delgates page in the Outlook 2003 option they get a message returned - The delegates page is not available. Unable to access Outlook folder. - The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action.



Post your answer or comment

comments powered by Disqus

Related Results

We have recently started migrating an exchange 2003 network to exchange 2010.
We are now in a mixed mode with about 100 users on exchange 2010 and the rest of the users, about 2500 users, still on exchange 2003.
All our clients use Outlook 2003. When the user is migrated to exchange 2010 they experience problems with opening shared calendars in their favorites. Some calendars open some calendars won't open and the user gets an error stating they do not have sufficient permission to open the calendar folder, or operation failed. They can also get this error if they have opened too many calendars or received an error on attempting anyone of them. The problem occurs for both calendars that reside on exchange 2003 and calendars that reside on exchange 2010 mailboxes Although we can’t find a common denominator for this problem, we have two work arounds. One is have them close and open outlook. They will then regain access to the calendar they were just blocked from before, though they may now be blocked from another’s they just had access to before they closed and opened Outlook. The second one is they delete the calendar which is causing the problem from the favorites and reopen the same calendar in their favorites. Sometimes the problem goes away. But we had cases where the problem persists. Or another calendar gets blocked.
End-users are complaining because there's no real solutions. And we still have to migrate about 2500 users, needless to say that with this problem we can't migrate.
Any help would be appreciated

I've got an interesting one here that is hopefully a quick fix.  After migrating to Exchange 2010 and moving the PF replicas to their new E2K10 server, users on Outlook 2003 cannot see the Free/Busy info for Resources (conf. rooms) that are into next year.  We can, however, see the Free/Busy via Webmail and Outlook 2007.  It seems very sporatic too.  On my Outlook, I can see one of the Resources Free/Busy, but not another (whereas prior I could not see either one of them beyond Dec. 2010).  Could this be RPC Encryption on the system folders?  If so, how do I remove it?  When I do a Get-RPCClientAccess, the encryption is denoted as False for the all the servers w/ PF and Mailboxes. Karl

I have an issue with a few migrated users being unable to open another users calendar. Before being migrated from Exchange 2003 to Exchange 2010 they could.

I've checked the permissions and they look ok. I've added myself and can open the calendar with no problems. We are using Outlook 2003 predominantly, but I've seen the issue occur with Outlook 2007 clients too.

Has anybody come across this?



I've noticed after migrating to Exchange 2010 from Exchange 2003, I've got an event log being generated infrequently that I can't figure out how to solve and I was wondering if anyone has experience on them.

Event 14031, Unable to find freebusy public folder: EX:/O=itc/OU=FIRST ADMINISTRATIVE GROUP on the server: EXCHANGE2010.itc.local for the user: User Name:50bc7a1b-00c3-403f-a531-ca9ddc31737e:b42e416c-5c0c-40ac-a7a9-ef230ab7f6ac:itcES2010.itc.local with legacy DN: /o=itc/ou=First Administrative Group/cn=Recipients/cn=user_id

For Event 14031 I can run the all users group and expand it in outlook's calendar and pull everyone's free/busy fine. Granted I recreated the free/busy public folder on the new exchsrv1 server and setup everything to point to the public folder/store. Note: Exchange 2003 no longer exis since 8-9 monthst!

Hi all.

A customer of mine recently migrated from exchange 2003 to Exchange 2010. They are still in the middle of transition but all mailboxes are moved to the 2010 mailbox store. Exchange 2003 servers are still in Exchange Organization.

Some of the users are experiencing some weird problems with calendar permissions after getting their mailbox moved.

Calendar permissions for user A (checking it from either the users Outlook or from ExFolders) shows permissions for direct calendar access for user B, C, D and so on.

User B, C, D cannot access user A’s calendar even though permissions looks fine. The error message from Outlook is the same as if User B, C, D didn’t have access to User A’s calendar at all.
Removing User B, C, D’s permissions from User A’s calendar and adding them again with exactly the same permission level solves the problem.

Have any of you seen this problem after migrating from Exchange 2003 to Exchange 2010 before and know why this happens?



Two domains, the root,, and a son,
I have Exchange 2003 on, with accounts only for email. Windows users belong to the child domain and have different accounts.

That is, each user has two accounts, one for windows and another one for email, so you have to enter username and password each time you open Outlook.

I'm going to migrate to Exchange 2010, but I want the users have mailboxes instead of

How do I have to do the migration?
1. Prepare domain of
2. Prepare domain of
3. Installing Exchange 2010 in
4 ?????

Thanks and regards

One of our clients wants to migrate from Exchange 2007 to Exchange 2010, his infrastructure now consist of 24 servers as below:
Client Access Server       5 servers
Edge Transport Server   2 servers
Hub Transport Server     3 servers
Mailbox Server                                 7 servers
Passive Mailbox Server                 7 servers
Number of users:            21000
1.       Anyone have idea about number of Mailbox Server after migrate to Exchange 2010, I think it will be less.
2.       Anyone have idea about capacity planner tools which help me to design the solution (I was using Microsoft capacity planner 2007 but it don’t support Exchange 2010).

After upgrading to Exchange 2010, all users seem to be having the issue of sending out calendar appointments and they will show up as plain text to everyone. Then if they create another with just a couple invitees, it shows up good. Why would this be happening and how to fix? It has to be a setting within the new server itself, correct? Please help if you can. Thanks!


I have a very bizarre problem with our new MS Exchange 2010 server.  We migrated from Exchange 2007 and have almost no problems except for a very small issue which we can't seem to resolve.  Our company uses a variety of MS Word documents, either doc or docx, and mail merge from MS Outlook using the Tools > Mail Merge drop down in Outlook.  The mail merge works fine and pulls over all information from the contact except the Notes field.  We have confirmed that the same user and mailbox works on our Exchange 2007 server and the problem doesn't seem to be dependent on the version of MS Outlook or Word we are using.  The only thing that we can figure out thats different is we changed from Exchange 2007 (where it worked with Outlook 2003 and 2007) to Exchange 2010 (where it doesn't work with either Outlook 2003 or 2007).  We tried deleting the field in the word form and recreating it with no luck.  We did notice that the Notes field doesn't seem to show up any longer in the chooser when adding a mail merge field in our Word doc.  So my question is obviously, has anyone run into this and have a fix or did MS change the name of the Notes field and we are using the wrong one.

Any help would be really appeciated.


Hello everyone, I have a question to the end of the migration process "Migrate Exchange 2003 to Exchange 2010".

I've installed a new Exchange Server 2010 in the present exchange 2003 organization. After this, I've moved all mailboxes and the public folder structure sucessfully. At the end, I've tried to uninstall the Exchange Server 2003, but I couldn't choose uninstall. An error message appears, that there are still some user mailboxes on the exchange server 2003. I've powered off the old Exchange Server 2003 for a few days whithout any errors in the exchange organization.
Si I've made a search on the AD and searched for mailboxes who lie on the old Exchange Server. The result shows, that there are email activated public folders and the distribution lists, which are stored on the old database.
So, how can I move this entries to the new Exchange 2010 Server, so it is possible to uninstall the exchange server 2003?

thanks for any comments!

Hi All,

I have an interesting project coming soon. Basically Company A has got Exchange 2007 with 2000 mailboxes in domain
The plan is to move the mailboxes to a service provider that has Exchange 2010 SP2 installed in Hosted, multitenancy mode in a new forest.

Company A wants to be able to use the same username and password once the mailboxes have been moved.
They also will use their own GAL, OAB, etc

Has anyone got ant idea how to proceed?

What are the Microsoft technologies that needs to be implemented?

The Exchange 2010 hosted environment was installed using the guide "Building and Migrating to Exchange 2010 SP1 Cloud Services"

ExtendASP is used as Control Panel in hosted environment to control user mailbox size, etc

Kindly share your ideas/views

Thank you

Hi folks,


we recently moved from Exchange 2007 to Exchange 2010 and our Users who use OL2k3 experienced a problem with the mails received after the move.

After open Outllok all mail bodies of the mails received right after the Mailbox move are empty. But new mails which arrived after Outlook has been opened are displayed properly.


Also the subject and attachments are available. Just the body text dissappeard.


The Eventlog does not indicate any problem with the Replication of the Mailbox Move. Also the Move Request Properties shows "Number of bad items: 0" 


Is this a known problem?




I want to be able to store Active Directory (i.e. Exchnage users) passwords in a separate Access database.   I use this database to upload to our intranet.  In the event a user loses their password, we allow them to login to a user specific page on our intranet and retrive the passowrd.   I used to manage a Communigate email server and we were able to pull these passwords out; however, after migration to Exchange 2010 I don't know if this is allowed.

The intranet and exchange server are not on the same domain, so I need to pull them  them into a separate database.

Any thoughts or suggestions will be greated appreciated.



Hi, I was looking for some feedback on the following.  We currently have a single Exchange 2007 server and we use LCR.  We have about 1500 mailboxes and our end-users use PSTs.  No mail is stored on the server.

We are moving to Exchange 2010 and we are going to now use server-based mailboxes and allow 1 GB mailboxes.  A Microsoft consultant recommended the following configuration:

Three servers running all roles (CAS, HUB, MB) with JBOD
Two active Databases (250 mailboxes per database), and 4 passive DB copies per server (So we would be using a DAG)
Hardware load balancer (two for redundancy)

We are looking at purchasing three (3) fairly powerful Dells each with 24 GB memory, 2TB disks,  beefy processors, etc

I understand that three servers protects us from a double-failure.  However, what else do we gain from a three-server model?  The discussion in our office is coming back to whether we could drop back to two servers with three active databases and three passive databases.

I am not sure if the three server model is overkill...It's hard for us to gauge this coming from a single server model.

Any feedback or opinions for those deploying exchange 2010 in small/medium organization?

I have a user who needs data from back in an Exchange 2007 backup, before we migrated to Exchange 2010. We use EMC Avamar, so i *should* be able to get the logs and edb files, but i'm not so sure that Exchange 2010 is going to play nicely even if i get them... Does anyone have an ideas?


CapnDoody (Chris)


Very soon company that i work for will migrate Exchange 2003 SP2 on Windows 2003 Standard SP2 to Windows SBS 2011. I would like to ask some professionals here are there any steps how to proceed.

I did full installation of Exchange Server 2010 and before I could do that I had to run setup tools like PrepareAdD PrepareDomain.

But Exchange 2010 with SP1 already comes preinstalled on SBS 2011 so I am not sure whether I still need to prepare domain with setup switches. SOme say we need to create answer file.

Are there any steps how to migrate this properly. I found steps for migrating to Exchange 2010 on Windows 2008 Enterprise edition but seems that migration to SBS 2011 is slightly different because Exchange 2010 is already installed on the server.

WIndowsw 2003 already of course setup and I would assume I dont need to prepare things with setup switches but create answer file to transfer it to new server.

But to stop guessing I would like to get opinion of the people that already did this. As I said Windows 2003 server is standard edition ( not SBS) but we will migrate to SBS 2011 from WIndows 2003 standard.

Any idea how to perform this operation

Thanks in advance

Hi All!

  I'm test migration from Exchange 2003 to Exchange 2010. Because documentation not describe this procedure i'm used this link in assumption that migration to Exchange 2010 similar to Exchange 2007
I'm successfully moved OAB, my admin mailbox, RUP to a new server, remove mailbox DB frpm old server, but when try replicate public folder structure nothing happen. When i go to Public Folder Store - Replication Status - all folder "In Sync" exept System Configuration and Public folder Hierarchy, thay are Local Modified. I'm try to wait for a few hours, reboot servers... nothing, replication not accur (replication schedule set to Always Run). What i do wrong?MCSE: M+S, SMS/SCCM, CCNA

Yesterday I installed SP1 to Exchange 2010 sucsesfully. Today start I receiving following warning. To correct this issue what I have to do? If you can give me command with syntax that would be appreciated.



Log Name:      Application
Source:        MSExchange ADAccess
Date:          19/12/2010 11:06:39 AM
Event ID:      2937
Task Category: Validation
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      itcES2010.itc.local
Process mmc.exe (PID=8780). Object [CN=David Citizen,OU=Users,OU=Stf,DC=itc,DC=local]. Property [HomeMTA] is set to value [itc.local/Configuration/Deleted Objects/Microsoft MTA
DEL:e935515e-50b7-49da-9054-c318904beb2d], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible.
Event Xml:">
    CN=David Dean,OU=Users,OU=Stf,DC=itc,DC=local
    itc.local/Configuration/Deleted Objects/Microsoft MTA

We were running POP3 email up until recently, when we (finally) upgraded to Exchange 2010 sp1. I added my Exchange account, then went into Data Files and removed my personal folder files. However, in my folder list, there is still a listing for "Personal Folders." If I try to right click it and "Close", I get an error "The operation failed. An object could not be found." There are no pst files in use. Somehow it just seems to be slight corrupted. Any suggestions on how to get rid of this pesky thing? I'm thinking I'll have to recreate my mail profile?

Thanks in advance.


We have just migrated an Exchange 2003 environment to a new server.

- moved all mailboxes, roles, public folders replicatied and so on
- stopped all exchange services on old server.

Now we have some outlook 2000 clients who try to open a shared calendar (a
calendar that already was opend in the past and now is just accessible
through a link). They get an error that the calendar is not accessible
If they go through the option "open calendar" and choose the user, it works.

Other clients, outlook 2003 doesnt have this problem.

Is there a way to fix this, or are these "links" only kept in the local ost



We have just migrated an Exchange 2003 environment to a new server.

- moved all mailboxes, roles, public folders replicatied and so on
- stopped all exchange services on old server.

Now we have some outlook 2000 clients who try to open a shared calendar (a
calendar that already was opend in the past and now is just accessible
through a link). They get an error that the calendar is not accessible
If they go through the option "open calendar" and choose the user, it works.

Other clients, outlook 2003 doesnt have this problem.

Is there a way to fix this, or are these "links" only kept in the local ost


     I migrated from Exchange 2000 on old server to Exchange 2003 on a new server.  Everything is fine except 1 small issue.  The shared calendars can not be accessed if the old mailstore is dismounted.  The error message that appears is "Unable to display the folder.  The calendar could not be found."  ALSO, when I try to log onto a mailbox, I get a seperate error message.  Here's what I do.  I log onto a server as the domain admin, change the properties of Outlook to point to a mailbox I want to backup (say for a terminated employee).  When I do this, I receive the following error: "Unable to open your default e-mail folders.  You do not have permission to log on."  I then click OK and it asks if I want it to open my default file-system folders.  I tell it no and Outlook closes down.  This happens whether the mailstore is mounted or dismounted.

Does anyone know what happened to the permissions on the server when I migrated from the old box to the new one?  How can I log in as the administrator and be able to backup the mailboxes?  Currently I have to log in as the user, backup the email, then delete the account.  Also, how do I get the security back to where it was on the old mailserver?  Any help is appreciated.

Recently moved the calendar's to exchange 2003 servers, and now some of the
calendars I cannot right click in Outlook and see the Permissions tab to
assign permissions. I also do not see other tabs like


I just see General and Summary tab. Is there anything that I should do
after the move from Exchange 2000 to Exchange Server 2003, that is not
completed which is the reason it is not showing up?

thanks in advance


I am the email administrator for a county government. Our current messaging system is Groupwise 7.0.3.

Background: In our state, there are several County Agencies each managed by an elected official (Board of commissioners, Tax Collector, Property appraiser, Sheriff, Fire Department, Supervisor of Elections, Clerk of the Court). These are known as constitutional agencies. They have 100% separately managed staff's, managed by their own Administrative staff. Each agency has a 100% separate IT staff.

When originally set up back in the day, each agency ran Netware. Each Agency had their own separate NDS Tree, managed by them. We have WAN connectivity to each agency through a dedicated PTP T1 or better.

We were the first to set up email (WPMail), and along the way, several other agencies set up their own mail system. Somewhere around 1993 or so, the decision was made to bring all the other agencies into our Groupwise system (Groupwise 4.x at the time).

For those of you that dont know, in Groupwise, you have a "Groupwise System", and what are known as email domains. Our domain was the PRIMARY domain, and each other Agency is a Secondary or External domain. Now, to be clear, each domain was still managed by its department, but being part of our Groupwise System, each domain had the ability to automatically share Address Book (AKA contacts in Exchange) and you could also do Busy Searches (AKA: free/busy in Exchange).

Over the years, several of the Agencies have migrated from Groupwise to various versions of Exchange (most are 2003). But us and one or 2 others still run Groupwise. As Agencies migrated to Exchange, we were able to maintain connectivity to them via a API Gateway on the Groupwise side, and the Groupwise connector for Exchange on the Exchange side. This has worked well.

Until this year, when one of the agencies migrated from Groupwise right to Exchange 2007. Doing this broke connectivity to us, and created a political shi*storm for both us (who didnt know anything about the migration, and after the fact could not assist them) and them (who did not ask their superiors if they cared about losing this functionality (their bad).

To get to my ultimate point. When we migrate to Exchange 2007 SP1 later this year, we will be decommissioning our Groupwise system, and the existing connectors will cease to function. Those still running Groupwise will become their own Primary Domain until they migrate.

I need to know what my options are for (if at all possible) to allow address book synchronization and free/busy searches between Exchange systems. These exchange systems are in completely different forests, with (currently) no trusts set up between them.

Also what if any options will I have for connecting to the remaining (now stand alone) Groupwise systems.

As I understand, there is no Groupwise connector for Exchange 2007.

I knew one day this setup would bite us in the ass, and I doubt there are many (if any) setups like this, but you have to remember, you are dealing with Government agencies and prima donna elected officials that only know "its always been this way" and dont (or dont) understand the concept that we HAVE to do this migration, and the technical limitations of the product. You explain that the product is NOT designed to do this, and get a blank stare and a "make it work" response.


Not finding an answer? Try a Google search.