Outlook Cannot Logon Error - Exchange 2013

Hi all,
I simply cannot create an Outlook (2007 or 2010) account to connect to my new installation of Exchange 2013 in Windows Server Essentials environment:
1) Using autodiscover:
I get green ticks for "Establishing network connection and "Search for [email protected] server
settings". At "Log on to Server" I get the error message "The action cannot be completed. The connection to
Microsoft Exchange
is unavailable. Outlook must be online or connected to complete this action"
2) Using manual configuration:
Outlook Anywhere (RPC over HTTP) Exchange Proxy settings configured using the internal FQDN for the Exchange
server and negotiate for authentication. Clicking "check name" button to resolve servername (internal FQDN) and
username (user email address) gives error, "Outlook cannot logon. Verify you are connected to the network and are
using the proper server and mailbox name. The connection to Microsoft Exchange is unavailable. Outlook must be
online or available to complete this action.
3) I can ping Exchange server using hostname and FQDN
4) PC is member of the domain
4) I have verified Exchange certiicate is installed on the client PC (although in the "Other People" certificates folder. Makes no difference when moved to the Trusted Root Certification Authority folder.
5) I can successfully connect to the user mailboxes via OWA
I've been working to resolve this issue for several days now and am at a complete loss as to what to do next to get this up and running.
Any assistance will be greatly appreciated.
RS
RS

Hi RS,
Did you try to run Office Configuration Analyzer Tool (OffCAT) only for Outlook and check the results? If not, proceed and run the Tool and post the results.
Additional info how to run the tool and check the results, you can find here: http://blogs.technet.com/b/catastrophic_failure_joannav/archive/2013/10/30/how-to-view-offcat-report-that-was-created-on-another-computer.aspx
If no
Regards, Catastrophic Failure "JV"

Similar Messages

Users cannot access calenders from outlook after migration to exchange 2013

I have a strange situation after upgrading to exchange 2013 some users are reporting that they cannot open or create calender appointments for calenders they used to be able to manage. we currently are using outlook 2010. also when the users access the calenders
with the webmail they are reporting that they can access the calenders and are able to do all the things they need to do.
i have tried reinstalling office and adding their exchange accounts but this does not help.
another stange thing is that to be sure i had setup the correct access policy i have reset all the security entries on all the calendars with the help of powershell. this seemed to have helped but after a couple of hours some users started reporting that they
could not access calendar items again!

Hi,
Is there any error description when the problematic users cannot open or create calendar items? Since the issue only happens to some users instead of all users and all calendars can work well in OWA, I think the calendar in the mailbox
should be configured properly.
Please configure the problematic user’s Outlook account in a clean computer with new installed Outlook to check whether the issue persists.
Thanks,
Winnie Liang
TechNet Community Support

Authorization Error Exchange 2013 and Mobile MS Outlook

With some logins
problem when connected via an MS Outlook for android client
writes that not correct login, password, domain.
And on the other
logins all right, authorization and connection
checked through https: //testconnectivity.microsoft.som
all right.

Hi,
The ability for users to use Search folders isn’t currently available in Exchange 2013. When you use Outlook in Exchange Cached Mode, the local copy of your mailbox maintains a Finder folder. So, with cached mode enabled we can make search folders still
there when we re-open Outlook.
For Outlook Online mode(cached mode off) and OWA 2013, Outlook is directly connected to Exchange mailbox without local cached. The search folder can’t be automatically synced to mailbox. Therefore, Search folders are not supported in OWA 2013 and Outlook
Online mode. We can refer to the Outlook We App and Outlook part in the following article:
What's Discontinued in Exchange 2013
http://technet.microsoft.com/en-us/library/jj619283(v=exchg.150).aspx
Regards,
Winnie Liang
TechNet Community Support

Outlook 2010 disconnects from Exchange 2013

One of the users running Outlook 2010 (14.0.7108.5000) randomly gets disconnected from her mailbox on Exchange 2013. The disconnect lasts about 5 min and then connection reestablishes. While outlook gets disconnected, computer does not have any problems
accessing any other network resources. Event 25 gets logged on the client when outlook disconnects and states the following. "Network problems are preventing connection to Microsoft Exchange."
Other users in the same mailbox database don't experience or notice the same issue.
The error message states that the mailbox database is offline, but it's probably misleading as the database remains online and mounted while the disconnect happens. The problems seems to follow the user no matter what mailbox database she is in.
The following information gets logged in exchange RCP Client Access log Listed in chronological order.
RopHandler: OpenFolder: [StoragePermanentException] There was an error parsing the entry ID. -> [MapiExceptionInvalidParameter] Unable to obtain the FID and MID from the entry id. (hr=0x80070057, ec=0)
ClientRPCCount=42;AvgClientLatency=00:00:00.0022142;ServerRPCCount=8;AvgCasRPCProcessingTime=00:00:00.0057500;AvgMbxProcessingTime=00:00:00;MaxCasRPCProcessingTime=00:00:00.0460000;20%ClientPercentile=10;40%ClientPercentile=10;60%ClientPercentile=10;80%ClientPercentile=10;90%ClientPercentile=10;95%ClientPercentile=20;99%ClientPercentile=20;100%ClientPercentile=50;20%CasPercentile=10;40%CasPercentile=10;60%CasPercentile=10;80%CasPercentile=10;90%CasPercentile=10;95%CasPercentile=10;99%CasPercentile=10;100%CasPercentile=50;20%MbxPercentile=10;40%MbxPercentile=10;60%MbxPercentile=10;80%MbxPercentile=10;90%MbxPercentile=10;95%MbxPercentile=10;99%MbxPercentile=10;100%MbxPercentile=10;ClientRpcFailureData:
RpcEndPoint: [ServerUnavailableException] Connection must be re-established -> [SessionDeadException] Connection is severed (ConnectionFailedTransientException). Client needs to reconnect. -> [ConnectionFailedTransientException] Cannot get row count.
-> [MapiExceptionNetworkError] Unable to get table row count. (hr=0x80040115, ec=0)
RopHandler: Logon: [RopExecutionException] Mailbox is temporarily unavailable. Error code = MdbOffline (0x00000476) -> [MailboxOfflineException] Cannot open mailbox /o=CORP/ou=Office/cn=Recipients/cn=Banger. -> [MapiExceptionMdbOffline] Unable to make
connection to the server. (hr=0x80004005, ec=1142)
RpcEndPoint: [ServerUnavailableException] Connection must be re-established -> [SessionDeadException] The primary owner logon has failed. Dropping a connection. -> [RopExecutionException] Mailbox is temporarily unavailable. Error code = MdbOffline
(0x00000476) -> [MailboxOfflineException] Cannot open mailbox /o=CORP/ou=Office/cn=Recipients/cn=Banger. -> [MapiExceptionMdbOffline] Unable to make connection to the server. (hr=0x80004005, ec=1142)
Any help would be greatly appreciated

After reviewing the entire RCP Client log on the server, I am ruling out the client PC at this moment.
The disconnect seems to be getting triggered by a Healthmailbox check that starts right before users gets disconnected.
Here is a similar problem with exchange 2010 with no answer.
http://serverfault.com/questions/474123/one-email-user-keeps-disconnecting-from-our-exchange-server
Healthmailbox associated with user's mailbox database preforms the following operations at 19:00:05.899Z
Connect
OwnerLogon
OwnerLogoff
Disconnect
a minute later, at 19:01:43.526Z Healthmailbox associated with initial mailbox database preforms the following operations
Connect
ArchiveLogon
ArchiveLogoff
Disconnect
and then at 19:01:46.479Z server logs RopHandler: OpenFolder: [StoragePermanentException] There was an error parsing the entry ID. -> [MapiExceptionInvalidParameter] Unable to obtain the FID and MID from the entry id. (hr=0x80070057, ec=0) for the
client connection and client notices the disconnect.

Outlook 2010 connecting to Exchange 2013 and 2007 ... delivery fails

Hello,
we are having a problem with a few Outlook 2010 Clients that have two Exchange accounts setup in one profile. One account is connecting to the company's Exchange 2013 Server, the second account is connecting to an external provider's Exchange 2007 infrastructure
using Outlook Anywhere.
The companies Exchange 2013 was recently migrated from Exchange 2010 and this is the point where the problem started.
Some users are no longer able to send using the external Exchange 2007 account. When they try they are receiving an NDR with the following error message:
#554 5.6.0 STOREDRV.Deliver; Corrupt message content## from the external provider's servers.
When I setup a profile containing only the external provider's mailbox everything works fine until I am adding the company's Exchange 2013 back in at which point the same error appears.
We have no problems using the company's Exchange 2013 servers.
Does anyone have an idea what causes this and how to resolve it? The external provider is uncooperative in troubleshooting so we are left with the problem.
Thank you
Sascha

Hi,
The problem should be related to the External Exchange 2007.
Please refer to this kb below:
http://support.microsoft.com/kb/2203381/en-us
This problem occurs when the email message is a multipart/mixed MIME message which contains a text/plain body and an application/applefile body. If the corresponding body is not a real application/applefile body, the Exchange Server 2007 server considers
that the email message is invalid. Therefore, it generates the NDR. However, Exchange Server 2010 can deliver this kind of email message successfully.
To resolve this problem, you should let the External Provider install the following update rollup:
2279665 Description of Update Rollup 1 for Exchange Server 2007 Service Pack 3
Hope this helps.
Thanks,
Melon Chen
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Outlook 2010 connected to Exchange 2013 prior to coexistence

I installed Exchange 2013 into the environment (Exchange 2010 SP3) and left it at that (ie no additional config). I noticed Outlook 2010 client connected to Exchange 2013 somehow (it got a cert warning). Why would Outlook connect to the new
Exchange 2013 server like that? Although I enabled Outlook Anywhere, it is not trying RPC/HTTP first, but rather RPC/TCP.

Hi,
By design, if the user mailbox located in Exchange 2010 server, the Outlook client will connect to Exchange 2010 server automatically.
According to your description, I found that we have nothing additional configuration on Exchange 2013. So, only server name and internal services' URLs are configured automatically during the Exchange 2013 server installation.
If it has no mailbox located in Exchange 2013, it is odd that Outlook client connect Exchange 2013 first.
I suggest running "Test E-mail AutoConfiguration" in Outlook to verify which Exchange server the Outlook connected.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Outlook anywhere not workinhg , exchange 2013

i have exchange 2013 environment everything is working fine except outlook anywhere iam using TMG 2010 for publishing rule (OWA , Active sync and OA ) all are working fine except OA
when i try to configure outlook user his computer not in domain it keep asking for username and password during configuration and after 2 times asking the password it shows the attached screen with no success
can you advice why this happening ?

this happen to all users , no one can use OA but others services like OWA and active sync working fine with all , they all configured in same TMG sever with same listener
get-outlookanywhee | fl output as below
RunspaceId                         : 8153f39f-76d2-4b02-8b4b-fdd8fa9f4977
ServerName                         : severname
SSLOffloading                      : True
ExternalHostname                   : webmail.xxxx.com
InternalHostname                   : webmail.xxxx.com
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
MetabasePath                       : IIS://servename.xxxxx.local/W3SVC/1
                                     T/Rpc
Path                               : C:\Program Files\Microsoft\Exchange
                                     Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 15.0 (Build 847.32)
Server                             : servername
AdminDisplayName                   :
ExchangeVersion                    : 0.20 (15.0.0.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web Site),CN=HTTP,CN=P
                                     cols,CN=servername,CN=Servers,CN=Exchan
                                     Administrative Group
                                     (FYDIBOHF23SPDLT),CN=Administrative
                                     Groups,CN=xxxxxx
                                     Co,CN=Microsoft Exchange,CN=Services,C
                                     nfiguration,DC=xxxxx,DC=local
Identity                           : servername\Rpc (Default Web Site)
Guid                               : b667bc75-2280-4b1b-99cd-9991b2300f6e
ObjectCategory                     : xxxxxx.local/Configuration/Schema/ms
                                     h-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory,
                                     msExchRpcHttpVirtualDirectory}
WhenChanged                        : 12/18/2014 6:07:17 PM
WhenCreated                        : 11/4/2014 9:07:48 AM
WhenChangedUTC                     : 12/18/2014 2:07:17 PM
WhenCreatedUTC                     : 11/4/2014 5:07:48 AM
OrganizationId                     :
OriginatingServer                  : DC.xxxxx.local
IsValid                            : True
ObjectState                        : Changed
note
my domian xxxxxxx.local and my extrenal url webmail.xxxxxx.com

Cannot install Windows Exchange 2013 SP1 64x non-checked build

Hello every one.
I have a problem to setup a lab asigment for school.
I have 2 Windows 2012 standard server
1e AD, DNS, IIS
2e Exchange 2013 SP1 64x
i prepared AD and installed al the features needed for AD and the Exchange server.
But when i run the readines check before i install Exchange 2013 i get to following warning
Warning:
A checked build of the operating system is installed. This can cause system instability issues including crashes, hangs, and other performance problems. It's highly recommended
that the operating system be reinstalled with a non-checked build.
For more information, visit: http:// technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.OSCheckedBuild.aspx
I cant find out what to do, thear is no Boot.ini file in Windows server 2012, any one any idea's to solve this problem
Thanks for the help,
Greatings,

Hi,
Agree with Ed. A checked build Windows is used for debug. Before installing Exchange 2013, please make sure that you use a free build. I'm afraid that you need to reinstall the OS.
What's more, you can refer the following screenshot to determine which Windows build is running. Generally, it should be Free build.
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

Migrate Exchange 2010 to Exchange 2013, Need to defined win 7 users logon to Exchange 2010 & Win 8.1 users logon to Exchange 2013

Hi,
My organization have few win 7 and windows 8.1 clients. Now I want to migrate exchange server 2010 to 2013. And I don't want to remove exchange 2010 from the organization. Because I want to connect win 7 client through exchange 2010 and windows 8.1 user
connect to exchange 2013. Is there any way to define the win 7 users to connect to exchange 2010 and Windows 8.1 users to connect to exchange 2013?
Md. Ramin Hossain

The client connections are proxied to the mailbox servers that hold the mailbox.
You would need to have 2010 MBX servers with the mailboxes for the XP users, and 2013 MBX servers holding the mailboxes for the 7 users. And of course, the appropriate CAS servers.
Realistically, you need to migrate away from Windows XP. It is no longer supported.

CRM 2013 Client for outlook cannot connect to CRM 2013 instance

Hoping this is the right forum couldnt see any specifically related to CRM
Ok we have recently setup an On-premise installation of Dynamics CRM 2013 and running the client on Outlook 2013 with Exchange 2010.
The CRM installation has had update rollup 1 applied to the server and outlook client
We have and IFD and ADFS deployment setup (*we require ADFS for a sister company as they will be utilising CRM also)
When we try to connect the outlook client we just keep getting prompted for credentials and it never connects.
In the log the following entries appear
12:17:08| Error| Error connecting to URL: https://internal.crm.timg.com/XRMServices/2011/Discovery.svc Exception: Microsoft.Crm.CrmException: Authentication failed
   at Microsoft.Crm.Outlook.ClientAuth.ClaimsBasedAuthProvider`1.AuthenticateClaims()
   at Microsoft.Crm.Outlook.ClientAuth.ClaimsBasedAuthProvider`1.SignIn()
   at Microsoft.Crm.Outlook.ClientAuth.ClientAuthProvidersFactory`1.SignIn(Uri endPoint, Credential credentials, AuthUIMode uiMode, IClientOrganizationContext context, Form parentWindow, Boolean retryOnError)
   at Microsoft.Crm.Application.Outlook.Config.DeploymentsInfo.DeploymentInfo.LoadOrganizations(AuthUIMode uiMode, Form parentWindow, Credential credentials)
   at Microsoft.Crm.Application.Outlook.Config.DeploymentsInfo.InternalLoadOrganizations(OrganizationDetailCollection orgs, AuthUIMode uiMode, Form parentWindow)
This occurs when setting up the configuration with either outlook opened or closed.
I was assuming somewhere along the lines it is getting hung up with the claims process for ADFS on authentication.
Any information on this would be appreciated. CRM logins work fine for users logging into the main CRM site, just the outlook client wont authenticate.

Did you ever have luck fixing this? I'm having a similar issue with the login box prompting but if the users put in
[email protected] & normal password they can login without issues. But it should just be using their normal Windows credentials without a need to separately authenticate. We happen to be on Windows 2012 R2, ADFS
3.0 with our CRM 2013 install.

Mac outlook 2011 users with Exchange 2013 cu5

Hi all, I had a strange issue that came up after I reconfigured our receive connector in exch2013.
I have Exch2013 with Cu5 and a 2010 sp3. In order to fight spam I needed to reconfigure a new connector that's a bit locked down compared to the default frontend that's open to all remote networks, so in the new connector under
the scope settings I put our internal network ip and disabled the default frontend connector that was created during install. Since our exch2010 box is the main server that sends in and out, and has better antispam features, this is where all emails went
through and got routed to the 2013 box.
After restarting services, all was working including iphones and androids, except for Macs with outlook 2011, they were suddenly not able to connect to the exch2013 box after the changes. I looked at the transport logs but I couldn't see
anything showing why these users were not connecting, event viewer as well. It did block a lot of spam from getting through, but I had to revert back to the default front end connector just to get the Mac outlook users working again, has anyone seen
this before, or any other settings I might have missed. If anyone can get me some ideas or pointers, I'd greatly appreciate.
Thanks in advanced.
Carlo

Hi,
I suggest try to re-create MAC 2011 user profile for testing.
Find a related KB for Exchange Online (even if it isn't for Exchange on-premises, please try it.) for your reference:
http://support.microsoft.com/kb/2847916/en-us
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

First timeout, push retry and then succesfull connect?! Starting Outlook 2010 connect to Exchange 2013

Hi!
Some info:
2x AD/DC Windows 2003 Native.
Previous Exchange 2003 installed, but now cleanly as it gets uninstalled.
Exchange 2013CU2v2 Aka Version 15.0 (Build 712.24)
Office 2010 with Outlook 2010 (Latest SP, and WU)
Outlook-prf configured for Outlook Anywhere. (i've also tried to configure manually, no difference)
Exchange: SAN Cert. GUI requested from ECP. This one covers all possible host names the server can use. autodiscover, owa, mail, "netbios"-name. Self issued from the internal CA. CA distributed to clients with GPO. I get NO certificate warnings
surfing to OWA, ECP.
Exchange: ECP/Server/Outlook Anywhere; Auth set to NTLM (not Negotiate)
Ping inside host names resolves to the Exchange server.
Starting Outlook.exe with /rpcdiag show two connections for a while. One of the type catalog and one of the type redirect.
Problem:
When starting Outlook you see "Loading profile" for about 30-40 seconds. /rpcdiag show two connections CID "9","11"; SERVERNAME "---","[GUID]@thedomain", AUTH and ENCRYPT is empty.
The the a dialog comes up that says that the server isn't available?!
Clicking "Retry" makes Outlook connect as it should. Everything from there works like a charm! /rpcdiag windows show that it has connection as it should.
Tried to click "Reconnect" in /rpcdiag. It also takes about 30 sec before it regains the conneciton. The part hanging there is the Type: Redirect.
So, does anyone have a clue for why it doesn't work and then does?
Can it be something wrong with the autodiscover?

Hello,
Do you mean the issue occurs when you select manually configure outlook exchange account or automatically configure outlook exchange account? If so, please make sure whether all users have the issue.
I recommend you check if there exists redirection on your rpc virtual directory.
I recommend you use "test e-mail autoconfiguration" tool to check if your autodiscover is correct.
Besides, I recommend you to enable global and advanced logging for outlook to check RPC trace events.
How to enable global and advanced logging for Outlook 2010 and Outlook 2013
http://support.microsoft.com/kb/2260527
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Outlook 2010 SP2 - Error when editing shared calendar: Post Exchange 2013 CU2 Migration

Hi there,
I have a strange comportment with Outlook 2010 SP2 and Exchange 2013 CU2 and i really need your help.
Frequently, when an user (who has the good permissions for) want to edit a shared calendar (edit a meeting or add one), he has this error message:
" Cannot display the folder. Your server administrator has limited the number of items you can open simultaneously. Try closing message you have opened or removing attachments and images from unsent messages you are composing "
I see anything in the Exchange server event log but i have each time, an error message in the client event log:
" Microsoft Office14 Alerts ID 300"
Everything work very well with Outlook 2013.
Many thanks in advance for your assistance, and I am looking forward to reading from you.

Hi,
According to your description, the issue is related to your Office 2010 client.
And the issue can be resolved by installing the Microsoft Office 2010 Deployment Kit.
Here are the steps you can refer to :
1. Open a command prompt with administrative permissions.
2. Browse to the directory that contains the Offvirt.msi.
3. At the command prompt, run the following command:
msiexec /i OffVirt.msi [licensing flags]
You must enter a correct licensing flag in the following list to correctly configure the Deployment Kit. Otherwise, functionality may be incorrect.
For more information, you can refer to the following article:
http://blogs.technet.com/b/virtualworld/archive/2010/07/07/microsoft-has-encountered-an-error-with-licensing-and-will-need-to-close.aspx
If you have any question, please feel free to let me know.
Thanks,
Angela
Angela Shi
TechNet Community Support

Exchange 2013 - outlook cannot connect server

Hi,
I have installed exchange server 2013 to testing it in my home lab. DC - domain.local and exchange - sub.domain.com. Internet connection is with dynamic IP from ISP - router (PPPoE). My ISP provide DDNS and I got sub.domain.com for dynamic
IP. Also ISP is blocking port 25. I've asked ISP to unblock port 25 and i don't know if they unblock it. For exchange server i use smart host for relay.
Problem: If i use port forwarding (25) mail flow is normal intern - extern. This was tested with OWA, but outlook cannot connect to exchange server: logging on mail server failed.
If i don't use port forwarding (25) outlook connect to exchange server, but i cannot receive email from external.
Please give me a hand on this.
Thank you.

Hi Radu,
how do you connect Outlook with Exchange? Usually you're using MAPI/RPC/HTTPS so there is no dependency with SMTP. How did you configure your Outlook? How did you configure your CAS Settings?
Please verify your CAS is configured correctly and you are using Outlook AnyWhere, see
http://technet.microsoft.com/en-us/library/hh529912(v=exchg.150).aspx
Regards,
Martin

Outlook 2007 SP3 can't connect to Exchange 2013

Outlok 2007 with latest hotfixes
Freshly migrated mailboxes
Gives the error
Can't open outlook-The set of folders cannot be opened
Cert has internal FQDN name. Encryption is disabled
Any pointers?

Does the certificate have the server name?
That was apparently the solution here:
http://social.technet.microsoft.com/Forums/exchange/en-US/1ae67f48-d1ba-44b5-a3c7-4e9a5e955f3e/outlook-2007-cannot-connect-to-exchange-2013?forum=exchangesvrclients
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Outlook Cannot Logon Error - Exchange 2013

Similar Messages

Maybe you are looking for