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

Similar Messages

  • 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

  • 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

  • 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

  • Cannot open Yahoo! Web Mail. HTTP Error: 404 - Not Found.

    See my Post [https://support.mozilla.com/en-US/questions/858363 Cannot open Yahoo! Web Mail]

    Strange, but finally the procedure below did solve my problem.
    # Go to Control Panel > Add or Remove Programs and look for '''Anti Phishing Domain Advisor'''.
    # If you click on ''Click here for support information'' you'll see it is a Panda program.
    # Uninstall '''Anti Phishing Domain Advisor''' program...
    # This did solve my problem
    See also [https://support.mozilla.com/en-US/questions/811399#answer-205531 Can't open mail. Get this message: 404 Not Found nginx/0.6.32]

  • The icon for firefox is not working. "There was a problem sending the command to the program" pops up. Cannot get in to firefox

    Since the upgrade, the icon does not work. Now this message comes up. I made Google my home page by following directions on this site. I deleted the old icon as it didnt work, and this new one came up on my desktop and it presented the message above.

    Hi,
    Before you open any of the applications, please go to Task Manager to see if their processes are stuck there. If so, shut them down and try again.
    You can also try starting the applications in Safe Mode to determine if the problem is 3rd-party add-ins related.
    Please refer to this article below to learn more:
    http://office.microsoft.com/en-001/support/why-cant-i-start-my-office-2013-application-HA104011864.aspx
    As for the Excel problem 'There was a problem sending the command to the program', please note when double-clicking an Excel workbook, a
    dynamic data exchange (DDE) message is sent to Excel, instructing it to open the workbook that you double-clicked. If you
    turn on the "Ignore other applications that use Dynamic Data Exchange (DDE)“ setting,
     the DDE message sent to Excel by Windows Explorer is ignored, and Excel does not open the workbook that you double-clicked.
    To automatically solve this issue , we recommend to run “Microsoft Fix it 20074” and follow the steps in the wizard:
    http://support.microsoft.com/kb/211494/en-us
    You can also try to fix it manually by the steps under 'Let me fix it myself'.
    If the steps above don't help, we can try to repair Office from Control Panel -> Programs and Features to check the result.
    Regards,
    Melon Chen
    TechNet Community Support

  • I cannot finalize a project in iMovie, notwithstanding 175g of memory.  iMovie says there is a problem with the heap zone.  Worried about a virus or other issue.  Please help.

    I cannot finalize a project in iMovie, notwithstanding 175g of memory.  Could this be a virus or other operating problem.  Have shut down iMovie several times and moved more projects to hard drive to free up space.  Help!

    Hi
    Error -108 memFullErr  Ran out of memory [not enough room in heap zone]
    Turn off - TimeMachine usually works - re-try.
    (the application down in Dock)
    But can mean many thing's - My first thought is
    • Free Space on Start-Up hard disk. How much ? (other disks do not count)
    175Gb should be enough.
    Yours Bengt W

  • Outlook 2010 Problem opening shared mailbox "the set of folders cannot be opened. Microsoft Exchange is not available"

    Hi, I have a number of mailboxes configured for sharing.
    For those users who have full access rights (given via EMC) the mailboxes automatically appear in Outlook 2010.
    However for one of those mailboxes the users recieve the following error when they try to access it:
    "The Set of Folders cannot be opened. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance."
    Meanwhile the users' primary mailboxes continue to work as normal, as do the other mailboxes that have been shared with them.
    The output of get-mailboxpermissions for the problematic mailbox is the same as the output for a full working one.
    If I add the mailbox to my account (as though I was using Outlook 2003) it allows me access, however I then have the situation of having the mailbox listed twice, one working the other not.
    How do I get this mailbox to behave as expected?
    Many thanks
    Nick

    So the problem returns. I'm not sure what we did to work around it, the users who were having the problem have left and the new batch are now encountering it.
    I have issued the following command on the Exchange Server (one site, one server, all roles, only a default throttling policy exists):
    $a = Get-ThrottlingPolicy | where-object {$_.IsDefault -eq $true}
    $a | Set-ThrottlingPolicy -RCAMaxConcurrency 40
    The result of Get-ThrottleingPolicy is:
    RunspaceId                                : 8bc47cdf-a695-47f0-b31e-e6ffba6aed66
    IsDefault                                 : True
    AnonymousMaxConcurrency                   : 1
    AnonymousPercentTimeInAD                  :
    AnonymousPercentTimeInCAS                 :
    AnonymousPercentTimeInMailboxRPC          :
    EASMaxConcurrency                         : 10
    EASPercentTimeInAD                        :
    EASPercentTimeInCAS                       :
    EASPercentTimeInMailboxRPC                :
    EASMaxDevices                             : 10
    EASMaxDeviceDeletesPerMonth               :
    EWSMaxConcurrency                         : 10
    EWSPercentTimeInAD                        : 50
    EWSPercentTimeInCAS                       : 90
    EWSPercentTimeInMailboxRPC                : 60
    EWSMaxSubscriptions                       : 5000
    EWSFastSearchTimeoutInSeconds             : 60
    EWSFindCountLimit                         : 1000
    IMAPMaxConcurrency                        :
    IMAPPercentTimeInAD                       :
    IMAPPercentTimeInCAS                      :
    IMAPPercentTimeInMailboxRPC               :
    OWAMaxConcurrency                         : 5
    OWAPercentTimeInAD                        : 30
    OWAPercentTimeInCAS                       : 150
    OWAPercentTimeInMailboxRPC                : 150
    POPMaxConcurrency                         : 20
    POPPercentTimeInAD                        :
    POPPercentTimeInCAS                       :
    POPPercentTimeInMailboxRPC                :
    PowerShellMaxConcurrency                  : 18
    PowerShellMaxTenantConcurrency            :
    PowerShellMaxCmdlets                      :
    PowerShellMaxCmdletsTimePeriod            :
    ExchangeMaxCmdlets                        :
    PowerShellMaxCmdletQueueDepth             :
    PowerShellMaxDestructiveCmdlets           :
    PowerShellMaxDestructiveCmdletsTimePeriod :
    RCAMaxConcurrency                         : 40
    RCAPercentTimeInAD                        : 5
    RCAPercentTimeInCAS                       : 205
    RCAPercentTimeInMailboxRPC                : 200
    CPAMaxConcurrency                         : 20
    CPAPercentTimeInCAS                       : 205
    CPAPercentTimeInMailboxRPC                : 200
    MessageRateLimit                          :
    RecipientRateLimit                        :
    ForwardeeLimit                            :
    CPUStartPercent                           : 75
    AdminDisplayName                          :
    ExchangeVersion                           : 0.10 (14.0.100.0)
    Name                                      : DefaultThrottlingPolicy_eccf5379-4fb6-4e97-8b47-37b1dc58a9
    DistinguishedName                         : CN=DefaultThrottlingPolicy_eccf5379-4fb6-4e97-8b47-37b1dc5
    ettings,CN=Our Org Name,CN=Microsoft Exchange
    onfiguration,DC=domain,DC=internal
    Identity                                  : DefaultThrottlingPolicy_eccf5379-4fb6-4e97-8b47-37b1dc58a9
    Guid                                      : a274d3ec-f2f8-43c3-ad26-6b960924ef0e
    ObjectCategory                            : domain.internal/Configuration/Schema/ms-Exch-Throttling-Polic
    ObjectClass                               : {top, msExchGenericPolicy, msExchThrottlingPolicy}
    WhenChanged                               : 07/06/2011 10:24:47
    WhenCreated                               : 07/06/2011 10:24:41
    WhenChangedUTC                            : 07/06/2011 09:24:47
    WhenCreatedUTC                            : 07/06/2011 09:24:41
    OrganizationId                            :
    OriginatingServer                         : OneOfTheDCs.domain.internal
    IsValid                                   : True
    But the problem remains. Do I need to adjust anything else for this value (40) to become active? The documentation implies that the above is required on a CAS, however there is mention of registry settings but no guidance on whether these are required if
    the above is used.
    When I create a second profile via Mail (in control panel) for the shared mailbox and then start outlook using this profile I am able to access the mailbox as expected. This is running in the context of the user who cannot access it from her
    default Outlook profile.
    Many thanks

  • Office 365 Outlook is now frozen. I cannot open outlook folders or mail. Can't access Options either. Works fine in IE.

    Office 365 Outlook is now frozen in Firefox.
    I cannot open Outlook folders or mail.
    Can't access Outlook Options either.
    Works fine in IE.
    Running latest Firefox, Win 7 and Office 365/Office 2010
    Cheers
    John

    LOL It worked! Thanks for your help. I will keep this handy in case I need to do it again!

  • Cannot delete item from junk mail folder in iPad?

    Some items cannot be deleted from junk mail folder on iPad 2. It will not move to trash.

    Have you tried swiping across the message in the preview pane when you open the junk folder instead of opening the email and trying to use the trash can icon?
    If that will not work either, try rebooting your iPad and then see if you can delete the junk mail.
    Reboot the iPad by holding down on the sleep and home buttons at the same time for about 10-15 seconds until the Apple Logo appears - ignore the red slider if it appears on the screen - let go of the buttons. Let the iPad start up.

  • HT1430 I cannot open my email which is a Microsoft outlook account

    I cannot open my email which is a Microsoft outlook account

    What are you using to attempt to open it? Are Using a browser? an App?
    What happens when you try?
    Have you set it up in the Mail App or are you using a different App?
    Unless you give us some details you are basically asking us to guess at what may be happening.

  • I downloaded Lion onto my Mac, and now cannot open or access any of my Microsoft word documents or Power Points. Is there a fix for this? I need my documents

    I downloaded Lion onto my Mac, and now cannot open or access any of my Microsoft word documents or Power Points. Is there a fix for this? I need my documents

    If it's because you were using Office 2004, the eight year old version of Office that was written when Intel processors were not used in Macs, then there will be no fix. Lion dropped support for PowerPC applications, as has been widely reported since Lion's release last August.
    You can upgrade Office 2004 to Office 2008 or Office 2011. You can use iWorks 2009 that can open Microsoft files. You can use a number of free applications that are also capable of working with Microsoft documents. You can go back to Snow Leopard, if you have a backup. Or, if you have an external drive or room to add a partition to your current drive, you can install Snow Leopard on it.
    Search these forums for more information. If this is your issue, it's been posted and answered several times a day since August 2011.

Maybe you are looking for