Getting error 'Cannot open your default e-mail folder' in Exchange server 2010? what are common causes?

I'm getting error
'Cannot open your default e-mail folder' when try to access my email account on exchange 2010? Why I am getting this error? Is there any particular reason? And how can I manually fix it? plz suggest!!

Hi,
Some questions:
1. Can you open your account via OWA?
2. Can you configure your account on other user's computer?
Try disabling any 3rd-party firewall or AV programs, make sure no proxy applictions or settings.
Thanks,
Simon Wu
TechNet Community Support

Similar Messages

Cannot open your default e-mail folder. Microsoft Exchange is not available. Either there are network problems or the Exchange computer is down for maintenance

Windows Server 2012 R1 with Exchange 2013 SP1
Windows XP SP3 with Outlook 2010 (14.0.4760.1000) computer is on the same network, but not a part of the domain.
When I try to configure Outlook profile for the user, I manually enter exchange server name and user name.
Check User button underlines server name and user name and profile gets created successfully.
Once I try to open outlook for the user I get
Cannot open your default e-mail folder. Microsoft Exchange is not available. Either there are network problems or the Exchange computer is down for maintenance
If I search the content of the log files under
X:\Program Files\Microsoft\Exchange Server\V15\Logging\RPC Client Access
I can’t find any records indicating a connection attempt from the client’s IP or references to the version of the outlook used, however I can see a 3 way handshake followed by a 4 RCP packets and then 4 nspi bind requests and responses when outlook opens
up and then connection is torn down.

Windows Server 2012 R1 with Exchange 2013 SP1
Windows XP SP3 with Outlook 2010 (14.0.4760.1000) computer is on the same network, but not a part of the domain.
Hi,
That version of Outlook 2010 (14.0.4760.1000) is not supported with Exchange 2013 and will not be able to connect. It need to be on at least SP1 +
Outlook 2010 November 2012 update (14.0.6126.5000)
See: Exchange 2013 System Requirements -
Client Support
Martina Miskovic

Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost)

Fresh installation of Exchange Server 2013 on Windows Server 2012.
Our first test account cannot access their email via Outlook but can access fine through OWA. The following message appears - "Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize
your folders with your Outlook data file (.ost)" is displayed.
If I turn off cached Exchange mode, setting the email account to not
cache does not resolve the issue and i get a new error message - "Cannot open your default e-mail folders. The file (path\profile name).ost is not an Outlook data file (.ost). Very odd since it creates its own .ost file when you run it for the first
time.
I cleared the appdata local Outlook folder and I tested on a new laptop that has never connected to Outlook, same error message on any system.
Microsoft Exchange RPC Client Access service is running.
No warning, error or critical messages in the eventlog, it's like the healthiest server alive.
Any help would be greatly appreciated. I haven't encountered this issue with previous versions of Exchange.

So it looks like a lot of people are having this issue and seeing how Exchange 2013 is still new (relatively to the world) there isn't much data around to answer this. I've spend ALOT of time trying to figure this out.
Here is the answer. :) - No I don't know all but I'm going to try to give you the most reasonable answer to this issue, in a most logical way.
First thing I did when I was troubleshooting this issue is that I ignored Martina Miskovic's suggestion for Step4 http://technet.microsoft.com/library/jj218640(EXCHG.150)because it didn't make sense to me because I was trying to connect
Outlook not outside the LAN but actually inside. However, Martina's suggestion does fix the issue if it's applied in the correct context.
This is where the plot thickens (it's stew). She failed to mention that things like SSL (which I configure practically useless - anyone who ever worked in a business environment where the owner pretty much trusts anyone in the company, otherwise they don't
work there - very good business practice in my eyes btw, can confirm that...) are some sort of fetish with Microsoft lately. Exchange 2013 was no exception.
In exchange 2003, exchange 2007 and exchange 2010 - you could install it and then go to outlook and set it up. And when outlook manual Microsoft Exchange profile would ask you for server name, you would give it and give the name of the person who you setting
up - as long as machine is on the domain, not much more is needed. IT JUST WORKS! :) What a concept, if the person already on premises of the business - GIVE HIM ACCESS. I guess that was too logical for Microsoft. Now if you're off premises you can use things
like OutlookAnywhere - which I might add had their place under that scenario.
In Exchange 2013, the world changed. Ofcourse Microsoft doesn't feel like telling it in a plain english to people - I'm sure there is an article somewhere but I didn't find it. Exchange 2013 does not support direct configuration of Outlook like all of it's
previous versions. Did you jaw drop? Mine did when I realized it. So now when you are asked for your server name in manual outlook set up and you give it Exchange2013.yourdomain.local - it says cannot connect to it. This happens because ALL - INTERNAL AND
EXTERNAL connection are now handled via OutlookAnywhere. You can't even disable that feature and have it function the reasonable way.
So now the question still remains - how do you configure outlook. Well under server properties there is this nice section called Outlook anywhere. You have a chance to configure it's External and Internal address. This is another thing that should be logical
but it didn't work that way for me. When I configured the external address different from the internal - it didn't work. So I strongly suggest you get it working with the same internal address first and then ponder how you want to make it work for the outside
users.
Now that you have this set up you have to go to virtual directories and configure the external and internal address there - this is actually what the Step 4 that Martina was refering to has you do.
Both external and internal address are now the same and you think you can configure your outlook manually - think again. One of the most lovely features of Outlook Anywhere, and the reason why I had never used it in the past is that it requires a TRUSTED
certificate.
See so it's not that exchange 2013 requires a trusted certificate - it's that exchange 2013 lacks the feature that was there since Windows 2000 and Exchange 5.5.
So it's time for you to install an Active Direction Certificate Authority. Refer to this wonderful article for exact steps - http://careexchange.in/how-to-install-certificate-authority-on-windows-server-2012/
Now even after you do that - it won't work because you have to add the base private key certificate, which you can download now from your internal certsrv site, to Default Domain Policy (AND yes some people claim NEVER mess with the Default Domain Policy,
always make an addition one... it's up to you - I don't see direct harm if you know what you want to accomplish) see this: http://technet.microsoft.com/en-us/library/cc738131%28v=ws.10%29.aspx if you want to know exact steps.
This is the moment of ZEN! :) Do you feel the excitement? After all it is your first time. Before we get too excited lets first request and then install the certificate to actual Exchange via the gui and assign it to all the services you can (IIS, SMTP and
there is a 3rd - I forgot, but you get the idea).
Now go to your client machine where you have the outlook open, browse to your exchange server via https://exchang2013/ in IE and if you don't get any certificate errors - it's good. If you do run on hte client and the server: gpupdate /force This will refresh
the policy. Don't try to manually install the certificate from Exchange's website on the client. If you wanna do something manually to it to the base certificate from the private key but if you added it to the domain policy you shouldn't have to do it.
Basically the idea is to make sure you have CA and that CA allows you to browse to exchange and you get no cert error and you can look at the cert and see that's from a domain CA.
NOW, you can configure your outlook. EASY grasshoppa - not the manual way. WHY? Cause the automatic way will now work. :) Let it discover that exachange and populate it all - and tell you I'm happy! :)
Open Outlook - BOOM! It works... Was it as good for you as it was for me?
You may ask, why can't I just configure it by manual - you CAN. It's just a nightmare. Go ahead and open the settings of the account that got auto configed... How do you like that server name? It should read something like [email protected]
and if you go to advanced and then connection tab - you'll see Outlook Anywhere is checked as well. Look at the settings - there is the name of the server, FQDN I might add. It's there in 2 places and one has that Mtdd-something:Exchange2013.yourdomain.local.
So what is that GUID in the server name and where does it come from. It's the identity of the user's mailbox so for every user that setting will be different but you can figure it out via the console on the Exchange server itself - if you wish.
Also a note, if your SSL certs have any trouble - it will just act like outlook can't connect to the exchange server even though it just declines the connection cause the cert/cert authority is not trusted.
So in short Outlook Anywhere is EVERYWHERE! And it has barely any gui or config and you just supposed to magically know that kind of generic error messages mean what... Server names are now GUIDs of the [email protected] - THAT MAKES PERFECT
SENSE MICROSOFT! ...and you have to manage certs... and the only place where you gonna find the name of the server is inside the d*** Outlook Anywhere settings in the config tab, un it's own config button - CAN WE PUT THE CONFIG ANY FURTHER!
Frustrating beyond reason - that should be Exchange's new slogan...
Hope this will help people in the future and won't get delete because it's bad PR for Microsoft.
PS
ALSO if you want to pick a fight with me about how SSL is more secure... I don't wanna hear it - go somewhere else...

Outlook 2010 - Cannot open your default e-mail folders. The requesting program is an incompatible version.

Outlook 2002 was installed on one of our Windows Server 2003 Terminal Servers. In the process of upgrading to Office 2010, the Outlook 2002 was replaced by Outlook 2010. Although the other Office 2010 programs seem to work, when we try to use
Outlook 2010 on this Terminal Server we get the following message.
Microsoft Outlook
Cannot open your default e-mail folders. The requesting program is an incompatible version. Contact your system administrator about upgrading your Microsoft Exchange Client.
Does anyone have any ideas on how to correct this?
Thanks,
Tom

Hi Tom,
Outlook 2010 is not supported in Windows Server 2003. For Microsoft Outlook 2010, the following operating systems supports only the 32-bit edition of Office 2010:
Windows XP with Service Pack 3 (SP3)
Windows Server 2003 Service Pack 2 (SP2), MSXML 6.0
Windows Server 2003 R2
For more information about system requirements for Office 2010, please refer to:
http://technet.microsoft.com/en-us/library/ee624351(v=office.14).aspx#section10
Personal suggestion, we can upgrade your Windows server 2003 to higher version for more features.
Regards,
Winnie Liang
TechNet Community Support

Outlook 2010: "Cannot open your default e-mail folders..."

When I open Outlook 2010 I receive the message: "Cannot open your default email folders. There is not enough memory to perform the operation.", after which the program closes. This is on a network running SBS 2003, with about 25 users, and I
am the only with this problem. System resources on the exchange server are fine, so I can only imagine a disk usage quota has been exceeded somewhere. Storage limits for my account looked fine. I've tried restarting exchange services, restarting
the server itself, restarting my desktop, etc etc, to no avail.
This specific problem just started yesterday, but I've been having memory issues for months now. Usually, the Send and Receive dialogue will tell me that there are not enough resources on the server, but mail comes and goes just fine. It's never
simply refused to let me open outlook before, like it is now.
I also tried logging in through another computer and using Outlook 2003, which actually let me open the program, but did not sync mail properly.
Also, we use cached exchange mode, so I tried creating a new ost file, but no dice.
Anyone know what the deal might be?

Hi,
I agree with Don’s guess of damaged PST file or MAPI profile. Analyzed your description(sync mail improperly on another computer and using cache mode), this problem might occur when your Outlook messaging profile includes a Microsoft Exchange account
that is configured to Use Cached Exchange Mode, and you have lots of cached public folders. Usually, this problem occurs when you exceed approximately 1,000 public folders, or a gigabyte of space is taken.
To prevent this problem, keep the number of cached public folders to fewer than 1,000. Or, reduce the number of folders until the error or errors stop occurring. If you are experiencing this problem, delete some public folder favorites by using the Outlook
client. In some cases, if you have too many favorites, you may be unable to delete the folders because the error occurs when you click the public folder favorites folder.
To delete the public folder favorites, follow these steps:
1.Download MFCMAPI from http://mfcmapi.codeplex.com.
2.Run MFCMAPI.exe.
3.On the Session menu, click Logon and Display Store Table.
4.If you are prompted for a profile, select your profile name, and then click OK.
5.In the top pane, locate the line that corresponds to your mailbox, and double-click it.
6.In the navigation pane (left-side pane), expand Root - Mailbox, and select the Shortcuts folder.
7.In the results pane (right-side pane), locate the PR_FOLDER_CHILD_COUNT properties. The value contains the number of public folder favorites.
8.In the navigation pane, right-click the Shortcuts folder, and then select Empty Items and Subfolders from Folder.
9.Keep the default options, and then click OK.
Good Luck.
Tony Chen
TechNet Community Support

Cannot open your default e-mail folders. The file C:\Users\"USERNAME"\AppData\Local\Microsoft\Outlook\***.ost Is not a outlook data file .(ost)

I am not connecting to an exchange server. I am trying to connect to hotmail and live.com only. This occurred during start up of Outlook 2010 client on windows 7. can anyone help. It is an ost file. Can I edit the file or how do I remove the references
to the ost file?

I appreciate your understanding that this is Exchange forum, for hotmail and live email related issue, we have the correspond forum:
http://www.windowslivehelp.com/forums.aspx?productid=15
Just for your reference, the issue apprears to be the .ost file corrupted. You might need to remove the old one an re-download.
Hope it is helpful.
Fiona Liao
TechNet Community Support

Getting error- Cannot open as archive for CS6 Master suite collection. How to d/l & install?

I have an account and a license key code. I purchased a new laptop that doesn't have a dvd drive. I want to download CS6 Master Suite Collection but I keep getting error "cannot open as archive"!!! I have already located the d/l files, but they will NOT install. Does anyone know how to get around this problem?

if you downloaded an exe and 7z, they should both be in the same folder and click (or double click) the exe.
do NOT manually try to extract the 7z file.
if that doesn't solve your problem, what file names and extensions did you download and what are their file sizes?

Cannot open you default e-mail folders. The information store could not be opened?

Hi
I have a freshly installed version of windows (windows 7 ultimate x64) and when I put my credentials into Microsoft office via the Hotmail outlook connector (x64) i receive the following error message
Cannot open you default e-mail folders. The information store could not be opened
is there a way around this?

What's the version of Office you are using? Is it a 64bit or 32bit edition?
Check if Outlook is in a compatibility mode:
1> Open My Computer>Local Disk C>Program Files>Microsoft Office>Office XX>Outlook.exe.
(If you are using a 64 bit machine and not using Office 64bit, go to C:\Program Files x86\Microsoft Office>Office XX>Outlook.exe)
2> Right click on Outlook.exe and click on Properties and then click onCompatibility tab. Check if you have any check mark in any of the compatibility mode options. Make sure you also click on the option "change
settings for all users" tab at the bottom of the same screen and look for similar check boxes in the window.
3> If you see any check boxes in the compatibility mode options, uncheck all the boxes and click onApply and OK.
4> Try to open outlook again.
Thanks.
Tony Chen
TechNet Community Support

Getting error "cannot open" when playing Videos purchased on itunes.

I'm trying to stream videos from my PC to my iPad 2 using the "Videos" app and i keep getting error "cannot open" on any video that I try to play that I purchased through iTunes. Other videos I added that werent purshased through itunes play fine however. Can anyone help with a solution? My iPad is on 5.0.1 if that helps.

I'm getting this error suddenly. I used to be able to stream purchased movies just fine, and now it simply says, "Cannot open." With movies I ripped from my DVDs, they will play just fine, but movies purchased from iTunes give the error every time.
I know I don't have any odd characters in my name like mikesoderstrom had and I haven't changed any account details since the last time it was working a few weeks ago. The only major change I can think of is upgrading to iTunes 11.
My iTunes account says that both my Mac and my Phone are still authorized. Maybe I should try deauthorizing all anyway, but I'd rather not deal with the hassle of re-authorizing, especially if it didn't work for someone who tried it already.
I have no problems with downloading/updating apps, just with Home Sharing purchased movies.

Getting error "Cannot open the file "*****.INDD". Adobe InDesign may not support the file format, a plug-in that supports the file format may be missing, or the file may be open in another application."

How to fix this problem
"Cannot open the file "*****.INDD". Adobe InDesign may not support the file format, a plug-in that supports the file format may be missing, or the file may be open in another application."

When I have seen this message it is either when I try to open a document with an older version of Indesign E.g. an indesign 2014 document with Indesign CC.
The other time I have seen it is to open an Indesign CC document with Indesign 2014 which does not have Mindsuite - a plugin I use. Mindsuite, as yet, has not upgrade the plugin for Indesign 2014 therefore it recognises that a the document was created withe a plugin that the 2014 version does not have installed.
I believe your problem will be something like that.

Loosing X ... 'Error: cannot open display: localhost:11.0'

Hello, I hope some may be able to help me finding a solution to this X related problem.
Before Lion everything worked as expected.
From a terminal I
ssh -X user@linuxbox
and it work as expected... all the X application come back to my Mac.
but after a while (generaly not long ... about 5 to 10 min)
I cannot launch any X application anymore.
within my Terminal I get "Error: cannot open display: localhost:11.0"
and on the linuxbox side I get " sshd[xxxx]: channel 4: open failed: administratively prohibited: open failed"
Running 10.7.1. fully updated (from my 10.6.8 Mac I do not have this problem
... and never had)
Thanks in advance for your help
PhS

'arch' is set as the alias for localhost. I never entered 'arch' anyway, that's just what the error said.
e: I tried ssh-ing into a X session on another laptop running an Ubuntu live CD. I can ssh into it normally, but when I run 'xinit -e ssh -XCT [email protected] gnome-session -- :1' it just starts a new X session on ctrl+alt+F8 using my startx file, rather than the one on the other computer.
Last edited by Yes (2008-07-11 19:17:28)

Getting error -2147221219 when trying to execute OpenMsgStore function on Exchange 2007 Server

Hello,
I am getting error -2147221219 when trying to execute OpenMsgStore API on Exchange Server 2007. I have created the Public Folder also on the same server. Also, I have installed the Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 on the server. Please do let me know if our previous MAPI / CDO applications would work for Exchange Server 2007 in this environment?
Also, while executing the Microsoft Exchange MAPI editor when I click on Session -> Logon and Display Store Table I see Err:0x8004010F=MAPI_E_NOT_FOUND in the row type column. The MAPI initialization is successful and in the Display Name I get Public Folders and Mailbox - Administrator. Please let me know how to I make work the MAPI Editor.
Thanks for your time and cooperation !!
Thanks & Regards,
Neel

Answers in social.msdn.microsoft.com/Forums/en-US/3a2e9489-6137-42fb-95d1-bebcfe2ea138 may solve your problem.
PR_PROFILE_CONNECT_FLAGS = 0 will also work.

When sending e-mail messages to a mail-enabled public folder that have been replicated from old Exchange Server 2000/2003/2007, Exchange Server 2010 environment mails are rejected with NDR.

Hi, I would like to share with you issue that I’ve solved regarding mail-enabled PF that migrated from Exchange 2000/2003/2007 to 2010, I’ve searched & contacted my MVP leader – there’s no official KB regarding this issue right
now, so I’m posting here in order to share this among others.
Note: There’s article(s) that talked about PF replication from Exch2000/2003/2007 to 2010 – this is the same issue as well.
Symptoms
E-mail messages that been sent to mail-enabled public folder in Exchange Server 2010 environment rejected with the following NDR:
“#< #5.2.0 smtp;554 5.2.0 STOREDRV.Deliver.Exception:ObjectNotFoundException; Failed to process message due to a permanent exception with message The Active Directory user wasn’t found. ObjectNotFoundException: The Active Directory
user wasn’t found.> #SMTP#”
Sometimes Exchange Server 2010 is documented as well Event ID 1020 on the Event Viewer with this information:
“Log Name: Application
Source: MSExchange Store Driver
Event ID: 1020
Level: Error
Description:
The store driver couldn’t deliver the public folder replication message "Hierarchy ([email protected])" because the following error occurred: The Active Directory user wasn't found.”
Cause
In an environment where Microsoft Exchange Server 2000 or Microsoft Exchange Server 2003 previously existed, and all those servers have been removed, there is a chance that an Administrative Group (First Administrative Group or another custom Administrative
Group) remains with a Servers container, but no servers inside it.
During replication, when the Exchange 2010 Store Driver sees the empty Servers container in Active Directory, it's expecting a System Attendant object inside the container and when it is not found the error occurs.
Resolution
To work around the issue, delete the empty Servers container. This can't be done through Exchange System Manager. Use the ADSI Edit tool to remove it using the following steps:
Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows
2003 Server, Microsoft Windows Server 2008, Microsoft Exchange 2010 Server or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes
at your own risk.
1.
Start the ADSI Edit MMC Snap-in. Click Start, then
Run, and type adsiedit.msc, and then click OK.
2.
Connect & Expand the Configuration Container [YourServer.DNSDomainName.com], and then expand
CN=Configuration,DC=DNSDomainName,DC=com.
3.
Expand CN=Services, and then CN=Microsoft Exchange, and then expand
CN=YourOrganizationName.
4.
You will see an empty Administrative Group. Expand the
CN=YourAdministrativeGroupName.
5.
Expand CN=Servers.
6.
Verify there are no server objects listed under the
CN=Servers container.
7.
Right click on the empty CN=Servers container and choose
Delete.
8.
Verify the modification, and try to send again the E-mail to the mail-enabled public folder.
Applies to
Exchange Server 2010, Standard Edition
Exchange Server 2010, Enterprise Edition
Netanel Ben-Shushan, MCSA/E, MCTS, MCITP, Windows Expert-IT Pro MVP. IT Consultant & Trainer | Website (Hebrew): http://www.ben-shushan.net | IT Services: http://www.ben-shushan.net/services | Weblog (Hebrew): http://blogs.microsoft.co.il/blogs/netanelb
| E-mail: [email protected]

Sounds like you are looking in the wrong Administrative Group container which is why you are seeing your Exchange 2010 servers in there.
When you install Exchange 2003 only you will see a container named by default as "CN=First Administrative Group" container. But this could be named anything if you changed the Organization Name on the installation when you installed the first
Exchange 2003 server into the domain/forest.
You will notice that when you install Exchange 2010 part of the AD setup is to create a new configuration container and is named by default "CN=First Administrative Group (FYDIBOHF23SPDLT)".
So it sounds like you are not looking in the right location within ADSIEdit.
You may find the following article also helpful for this issue which is the same resolution:
http://blogs.technet.com/b/sbs/archive/2012/05/17/empty-cn-servers-container-causing-issues-with-public-folders-on-small-business-server-2011.aspx
I recommend though that you ensure your Exchange 2003 servers are fully uninstalled or no longer present in your environment before you go deleting the Servers container though.. The following Microsoft article will help with this:
http://technet.microsoft.com/en-gb/library/gg576862(v=exchg.141).aspx

Receive email delay one hour using Mac Mail client (Mountain Lion) connect Exchange Server 2010

Hi all,
My boss use iPhone, iPad, MacBook Air (Mac Mail client), MacPro (Mac Mail client) connect Exchange Serve 2010 to receive emails. All clients are okay except MacBook Air, the Mac Mail client cannot receive the latest emails from Exchange Server, but it can receive (sync) the emails after one hour. The other clients can receive the latest email after Exchange Server receive new emails immediately.
In this period, the MacBook Air can receive the other IMAP, POP3 and webmail from ISP normally. I tried to set 5 mins to check emails or manual check email from Exchange Server. However, the latest email still delay one hour.......... .
I dumped a screenshot for Mac Mail setting for Exchange Server and a Log file.
could anyone help me to solve this issue?
Thanks

I am not sure what the user has the check for new messages set for but mail does arrive as short as 2 minutes. It does however arrive on his iphone immediately first.

Trying to install iCloud on Win7 get error message either no default mail client or current mail client cannot fulfill messaging request. How fix?

Trying to install iCloud on Win7 get error message either no default mail client or current mail client cannot fulfill messaging request. How fix?

Outlook 2013. Under Start Up Options, I have checked "Make Outlook the default program for E-mail, Contacts, and Calendar".

Getting error 'Cannot open your default e-mail folder' in Exchange server 2010? what are common causes?

Similar Messages

Maybe you are looking for