Outlook 2013 Account Addition Crash
Hello,
I'm running Windows 8 with Office 2013 and I've successfully added a few of my email accounts to my Microsoft Outlook, they all work great but recently I attempted to add my university address by using the automatic "add account" and every time
it searches for my address a pop-up box reads "Microsoft Outlook has stopped working". In my attempts to manually add the account via the control panel through the Mail (Microsoft Outlook 2013) button, once it starts searching for my address,
again, it claims the "Windows Shell Common Dll has stopped working" and forces me to close that box. In both situations which I have tried many times, after powering on and off my computer, the add account box continues to crash right when
it starts looking for my address. Any suggestions? Thank you for your help in advance.
-Justalistener
Hi,
It sounds like an Outlook profile issue. You may follow the steps in the article below to create a new Outlook profile and configure your university email account as default:
http://office.microsoft.com/en-001/outlook-help/create-a-profile-HA102749460.aspx
Best regards,
Rex Zhang
TechNet Community Support
Similar Messages
-
Acrobat XI Outlook 2013 add-on crashes Outlook
Acrobat XI Outlook 2013 add-on crashes Outlook each time I try to convert an email to PDF,
I did not see a relevant answer to this specific problem in the forums.
Of course I can print an email to acrobat PDF but I believe a fix or an update from Adobe is overdue.
I had to disable the add-on in the meantime.
Otherwise PDF maker in the right click context menu works fine.
Windows 7 64 bit, Acrobat XI Pro 11.0.5
Anybody has an idea ?Have you tried the following?
Launch Office 2013 as Administrator, i.e. right click on Office icon and select 'Run as Administrator'.
or
Try creating a new user account on Windows to see if the same issue occurs. -
Exch 2010/Outlook 2013 - Accounts limit reached
Trying to connect to mailbox in exchange 2010 with Outlook 2013, got message (translated):
Unable to add another accounts to server Microsoft exchange server.
Maximal allowed number of accounts of server Microsoft exchange server was reached.
If you want to try to configure this account with POP3 or IMAP protocols, click to NEXT button.
Googling for solution but have no luck with translated error message. Anybody have idea? Is there built-in limit to mailboxes in exch 2010 or it is limited by some internal settings? I do not know how I can recognize versions of Exch 2010 but probably
taken from Action pack.
L.Hi,
To learn more about Exchange 2010 Store Limits:
http://technet.microsoft.com/en-us/library/ff477612(v=exchg.141).aspx
To understand Client Throttling Policies:
http://technet.microsoft.com/en-us/library/dd297964(v=exchg.141).aspx
In addition, Outlook 2013 allows up to 10 Exchange accounts to be configured in a single mail profile by default.
You can modify the relevant Group Policy key for Outlook 2013 to change the number of accounts.
Key: HKEY_CURRENT_USER\Software\Policies\Microsoft\Exchange
DWORD: MaxNumExchange
Type: REG_DWORD
Values: a number between 1 and 9999
To solve your issue, I recommend you to create a profile to check it:
Close Outlook.
In Control Panel, click or double-click the Mail module.
Under Profiles, click Show Profile.
Click Add.
In the New Profile dialog box, type a name for the profile, and then click OK.
If this issue still exists, please let me know. -
Outlook 2013 Scheduling Assistant Crashing
We have a user that has an issue where Outlook 2013 will crash when using the scheduling assistant with external addresses. For some reason it doesn't crash when using my external email address but every other email address we have tried will cause it to
crash. I have tried disabling all the add-ins but it doesn't make a difference. I have also tried running the outlook diagnostic utility which disabled add-ins and other things but it still crashes after running that.
The only thing that worked was starting Outlook 2013 in safe mode.
Any ideas?
Hi,
In Outlook Safe Mode, all Add-ins are disabled, but you mentioned you have tried disabling all add-ins, so add-ins shouldn't be the cause.
Another thing that is disabled in Safe Mode is the NormalEmail.dotm template. It can cause the crash issue if it has been corrupted. Please go to the following location:
C:\Users\<username>\AppData\Roaming\Microsoft\Templates
Find the NormalEmail.dotm file, rename it to ".old". Outlook then will create a new one, check if this issue persists with the new NormalEmail.dotm file.
If the problem persists, please collect the event logs and send it to us.
Press Win + R, type "eventvwr" in the blank box, press Enter.
Browse to Windows Logs -> Application, find the errors about the issue.
To protect your private information, you can send the logs to our email address:
[email protected]
Regards,
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 2013 crashed when user sending email from Adobe Writer xi pro ver 11.0.07
I ask Adobe, but they are signaling to Outlook problem
PC-HP, Windows 8.1 Pro X64 connected to Windows 2008 R2 DC
Adobe Acrobat Pro ver 11,x
When user trying to send email from Adobe direct, Outlook 2013 Pro is crashing
The only way to send email is to save adobe ( PDF) file and attached to the email
All patches are installedLog Name: Application
Source: Application Error
Date: 7/15/2014 8:05:38 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Liz7PM-HP.armadale.local
Description:
Faulting application name: Acrobat.exe, version: 11.0.7.79, time stamp: 0x536b812b
Faulting module name: SendMail.api, version: 11.0.7.79, time stamp: 0x536b7fd0
Exception code: 0xc0000005
Fault offset: 0x0003390b
Faulting process id: 0x139c
Faulting application start time: 0x01cfa024deec4218
Faulting application path: C:\Program Files (x86)\Adobe\Acrobat 11.0\Acrobat\Acrobat.exe
Faulting module path: C:\Program Files (x86)\Adobe\Acrobat 11.0\Acrobat\plug_ins\SendMail.api
Report Id: 553a89c7-0c18-11e4-be97-80c16ee27020
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-07-15T12:05:38.000000000Z" />
<EventRecordID>66128</EventRecordID>
<Channel>Application</Channel>
<Computer>Liz7PM-HP.armadale.local</Computer>
<Security />
</System>
<EventData>
<Data>Acrobat.exe</Data>
<Data>11.0.7.79</Data>
<Data>536b812b</Data>
<Data>SendMail.api</Data>
<Data>11.0.7.79</Data>
<Data>536b7fd0</Data>
<Data>c0000005</Data>
<Data>0003390b</Data>
<Data>139c</Data>
<Data>01cfa024deec4218</Data>
<Data>C:\Program Files (x86)\Adobe\Acrobat 11.0\Acrobat\Acrobat.exe</Data>
<Data>C:\Program Files (x86)\Adobe\Acrobat 11.0\Acrobat\plug_ins\SendMail.api</Data>
<Data>553a89c7-0c18-11e4-be97-80c16ee27020</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Log Name: Application
Source: Windows Error Reporting
Date: 7/15/2014 8:05:55 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Liz7PM-HP.armadale.local
Description:
Fault bucket 73304412188, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: Acrobat.exe
P2: 11.0.7.79
P3: 536b812b
P4: SendMail.api
P5: 11.0.7.79
P6: 536b7fd0
P7: c0000005
P8: 0003390b
P9:
P10:
Attached files:
C:\Users\ewhitton\Desktop\140.pdf
C:\Users\ewhitton\AppData\Local\Temp\WER8000.tmp.WERInternalMetadata.xml
C:\Users\ewhitton\AppData\Local\Temp\WER8BB9.tmp.appcompat.txt
minidump.mdmp
These files may be available here:
C:\Users\ewhitton\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Acrobat.exe_2a26ba191a528da71b85271ed9509f7e426babf8_0d6f35c4_1735c074
Analysis symbol:
Rechecking for solution: 0
Report Id: 553a89c7-0c18-11e4-be97-80c16ee27020
Report Status: 4104
Hashed bucket: f6a7a946597169e4aea5077b3b7f0848
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-07-15T12:05:55.000000000Z" />
<EventRecordID>66131</EventRecordID>
<Channel>Application</Channel>
<Computer>Liz7PM-HP.armadale.local</Computer>
<Security />
</System>
<EventData>
<Data>73304412188</Data>
<Data>1</Data>
<Data>APPCRASH</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>Acrobat.exe</Data>
<Data>11.0.7.79</Data>
<Data>536b812b</Data>
<Data>SendMail.api</Data>
<Data>11.0.7.79</Data>
<Data>536b7fd0</Data>
<Data>c0000005</Data>
<Data>0003390b</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
C:\Users\ewhitton\Desktop\140.pdf
C:\Users\ewhitton\AppData\Local\Temp\WER8000.tmp.WERInternalMetadata.xml
C:\Users\ewhitton\AppData\Local\Temp\WER8BB9.tmp.appcompat.txt
minidump.mdmp</Data>
<Data>C:\Users\ewhitton\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Acrobat.exe_2a26ba191a528da71b85271ed9509f7e426babf8_0d6f35c4_1735c074</Data>
<Data>
</Data>
<Data>0</Data>
<Data>553a89c7-0c18-11e4-be97-80c16ee27020</Data>
<Data>4104</Data>
<Data>f6a7a946597169e4aea5077b3b7f0848</Data>
</EventData>
</Event>
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Log Name: Application
Source: Outlook
Date: 7/15/2014 8:06:05 AM
Event ID: 50
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Liz7PM-HP.armadale.local
Description:
The following providers do not implement fast shutdown APIs, but are being shut down using fast shutdown:
MDConnector.dll (MAPI Store Provider)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Outlook" />
<EventID Qualifiers="16384">50</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-07-15T12:06:05.000000000Z" />
<EventRecordID>66132</EventRecordID>
<Channel>Application</Channel>
<Computer>Liz7PM-HP.armadale.local</Computer>
<Security />
</System>
<EventData>
<Data>MDConnector.dll (MAPI Store Provider)
</Data>
</EventData>
</Event> -
Outlook 2013 says "You cannot add to the server junk email list- you are over the size allowed."
I keep getting the above message over and over. Then it asks "do you want to manage the junk mail lists". Of course I have tried that many times with no success. One particular email continues to show up with a reminder-
when I try to "snooze" the warning, it tells me that the message cannot be found.
In addition, sometimes if I try to view a subfolder other than the inbox, when I return to the inbox, I find a "shadow" group of emails that are about 4 months old. If I click on any of the messages, the program tells me the message cannot
be found on the servers.
When I close the program and re-start it, the legitimate inbox re-appears.
It's incredibly annoying, but I am hoping that I can get rid of it without deleting and re installing outlook 2013. I have not tried to re-install the profile- was hoping there would be an easier way.Hi,
Please uncheck Use Exchange Cached mode in Outlook 2013 Account Settings. Then confirm if the issue occurs in Outlook Onlinde mode. If the issue doesn't happen in Online mode, please create a new Outlook profile to have a try.
If the issue persists in Online mode, please close Outlook and check whether you would still receive the message over and over in OWA. Also restart Outlook in safe mode to verify if the issue is caused by any third-party add-ins.
Regards,
Winnie Liang
TechNet Community Support -
Help needed with buggy Outlook 2013 and Exchange 2010 trashing profiles
Hi All,
I have a customer who has eschewed MOLP and buys all their Office OEM from Dell. So as a result they are starting to have more and more office 2013 be deployed. They have a SBS 2011 server with Exchange 2010 and it is patched to the latest
rollups and service packs. (SP3, RU2) Their Outlook 2010 and earlier clients are just peachy on this. But the Outlook 2013 clients are having problems.
What is going on is that periodically I'll get a complaint from a user that their Outlook 2013 is randomly crashing. In all cases the fix is going into the Outlook Profiles, creating a new profile, then setting the new profile as the default
and going back into Outlook 2013 and letting it rebuild the cached data on the PC. This seems to happen a few times a month with random users on the network.
I told the customer it was probably people not logging out of Outlook 2013 at night and their machines being power spiked but I think that's highly unlikely since it doesen't happen to the Outlook 2010 clients.
I don't know if any Microsoft developers read this but if you do, please take it back to your bug database. Any other suggestions would be appreciated (other than scotch Outlook 2013 - while I'd appreciate that, my customer wouldn't)In all cases the fix is going into the Outlook Profiles, creating a new profile, then setting the new profile as the default and going back into Outlook 2013 and letting it rebuild the cached data on the PC.
The Outlook 2013 crash problem would be fix after you re-create a new profile and re-sync the data from Exchange, right?
When we meet the same problem in next time, I suggest we run the Outlook Product Stability Diagnostic tool to isolate known causes of crashes in Outlook. The Outlook Product Stability Diagnostic also creates a diagnostic report outlining the data it collected
and recommendations on possible steps you can take to reduce or eliminate Outlook stability issues.
Please click the following link to run the Outlook Product Stability Diagnostic tool in the Microsoft Fix it Center Pro portal:
Outlook Product Stability Diagnostic:
https://wc.ficp.support.microsoft.com/SelfHelp?knowledgebaseArticleFilter=2764035
Other troubleshoot steps for Outlook 2013, please refer to the link below.
Let me know the result.
http://support.microsoft.com/kb/2632425/en-us
Tony Chen
TechNet Community Support -
I have a exchange 2010 server and outlook clients using outlook 2013.
I've noticed that Outlook 2013 prompts many times for credentials if basic authentication is set. NTLM however does not seem to prompt so much.
I tried to set the GPO in the outlook 2013 template "Microsoft Outlook 2013-Account Settings-exchange-Authentication to exchange server to force NTLM but, it does NOT change on the client.
The GPO is user based and I filtered the GPO based upon just a few test users.
Any Ideas?You no need to configure any Outlook template on GPO.
Your Exchange is 2010 right? so this is for outlook anywhere right?
If you want your clients connect via NTML authen for outlook anywhere , you just logon to Exchange Management Console and then on OutlookAnywhere setting >> change Authentication to NTLM (by default is "basic authen")..
After that just waiting for autodiscover process and clients will change it to NTLM by automatically. -
I have a exchange 2010 server and outlook clients using outlook 2013.
I've noticed that Outlook 2013 prompts many times for credentials if basic authentication is set. NTLM however does not seem to prompt so much.
I tried to set the GPO in the outlook 2013 template "Microsoft Outlook 2013-Account Settings-exchange-Authentication to exchange server to force NTLM but, it does NOT change on the client.
The GPO is user based and I filtered the GPO based upon just a few test users.
Any Ideas?It is enabled yes.
[PS] C:\Windows\system32>Get-ClientAccessServer | fl OutlookAnywhereEnabled,AutoDiscoverServiceInternalUri
OutlookAnywhereEnabled : True
AutoDiscoverServiceInternalUri : https://owa.costandcompliance.com/Autodiscover/Autodiscover.xml
OutlookAnywhereEnabled : True
AutoDiscoverServiceInternalUri : https://owa.costandcompliance.com/Autodiscover/Autodiscover.xml
OutlookAnywhereEnabled : True
AutoDiscoverServiceInternalUri : https://owa.costandcompliance.com/Autodiscover/Autodiscover.xml
[PS] C:\Windows\system32>Get-AutodiscoverVirtualDirectory | fl InternalAuthenticationMethods,MetabasePath
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
MetabasePath : IIS://CCA-EXCHTNJ1.CCACloud.local/W3SVC/1/ROOT/Autodiscover
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
MetabasePath : IIS://CCA-EXCHTNJ3.CCACloud.local/W3SVC/1/ROOT/Autodiscover
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
MetabasePath : IIS://CCA-EXCHTNJ2.CCACloud.local/W3SVC/1/ROOT/Autodiscover -
Outlook 2013 not responding upon startup
Good day
We have a client that is running Windows Multipoint server on a Dell server, the remote users connected to the server can not open Outlook 2013, when they try open Outlook 2013 it would crash and state that Outlook can not open at this time please try again
later.
Please advise on what to do to solve this matter.
Thank you in advance.Hi,
Are you using Outlook with Cached Exchange mode enabled? If not, please enable it to check the result.
Please first try to open Outlook in safe mode to check if this issue is caused by problematic add-ins. To do this, hold Ctrl key and then double-click on the Outlook shortcut to open it. If the problem would be gone in safe mode, please go to File >
Options > Add-ins and disable suspicious add-in to resolve the problem.
If above doesn't help, please follow the steps in the KB article below to troubleshoot the issue:
http://support.microsoft.com/kb/2652320/en-gb
Regards,
Steve Fan
TechNet Community Support -
Outlook 2013 and iCloud contacts and calendar?
What does it take to get outlook 2013 to access my iCloud contacts and calendar?
I can log into ICloud and see my contacts and my calendar. My iPhone works with iCloud just fine.
However, Outlook 2013 doesn't know iCloud has a calendar or contacts and I cannot access them. I have tried to add my iCloud contact file to Outlook 2013 but i must not be doing that correctly. I have tried to add my ICloud calendar file to outlook 2013 but i must not be doing that correctly either, In Outlook 2013, when I click on either the "Calendar" or "People" at the bottom of the Outlook screen, what comes up is blank, no contacts, no calendar items. I can long into iCloud and see the calendar and contacts just fine.
Surely, someone must know how to get this to work. I must not be adding the contact file or calendar file correctly in the Outlook 2013 Account Settings. I cannot find any place where it discusses these settings. I have tried to add them as https://www.icloud.com/#contacts or #calendar. That has not worked. Can anyone explain to me what I have to do to get these two products to communicate with each other?
GaryI have to say that I have gone through this setup several times by removing the check items on the icloud control panel and rechecking them and it accomplished nothing. This time when I opened up the icloud control panel, the calendar item was unchecked. Don't know why. I checked it and it went through a process of moving a few thousand items into outlook. When I opened outlook, my contacts and calendar items were there.
Thank you for the guidance. I have contacts and calendar items available now. Great news.
Gary -
Outlook 2013 Mail Setup Add Account crashes or will not connect to Exchange in Windows 8.1
I've posted this in the answers.Microsoft.com forum, as well as the Office365 forum, and they sent me here, saying the Outlook engineers would be the best to help with this. I actually already posted this question a week ago, but nobody here replied.
Getting a bit frustrated at the lack of support, except for Richard over at the Office365 Forum.
I'm setting up a new laptop with Windows 8.1. Just installed Office Professional Plus 2013. I have an Office365 E1 subscription, but this Office 2013 is not associated with the subscription.
When I go to setup any email account using the automatic mode (primary will be Exchange Online with my 365 account, but I've tested POP email accounts with the same result), the Mail Setup crashes once the email address and password is entered and Next is
pressed. This error message is displayed:
"Windows host process (Rundll32) has stopped working
A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."
The step displayed as in process when the crash occurs is the "Searching for [email address] settings". The first step "Establishing network connection" is checked complete.
I've run an Office Repair, and there's no change. I've run a clean boot, and no change. I uninstalled/reinstalled both from the Click to Run version, as well as reinstalling from a disk install, with the same error still appearing.
If I use the manual setup mode and input the server outlook.office365.com, both the Check Name function and the Next button result in 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."
I've disabled the firewall and still get this Outlook error. I am able to start Outlook and it will run now, and I can connect POP and IMAP email using the manual setup, but still cannot connect to ExchangeOnline via the manual setup. I still
get the error "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
I deleted the Outlook data file and deleted the profile, and created a new profile, and I'm still getting the Add account setup crash Rundll32 error in the auto-setup mode.
Important to note: I tested my friend's Office365 E3 ExchangeOnline account and was able to get a successful setup test, so it doesn't appear that the problem is entirely just the Outlook2013 client, since it worked once with a 365 Exchange account.
I've been trying to get this working for 2 weeks now, and I am unable to completely switch off my old laptop using Outlook 2010 until I can get Outlook2013 setup on my new one, which is a huge hassle.
Can you offer any ideas or solutions? Please help ASAP.
Thanks,
JasonIMPORTANT: I found the solution. Another user figured it out and posted the answer on another thread.
Please spread this around to all other Outlook support techs so they know to point people in the direction of the quick (though very obscure) fix to this problem.
See this thread for how to disable graphics acceleration in Office, which iswhat causes the rundll23 error.
http://answers.microsoft.com/en-us/office/forum/office_2013_release-outlook/rundll32-outlook-mail-windows-host-process-error/bf90e1fd-3985-4b15-bc50-f9b3e937a859?tm=1424345216297
Thanks,
Jason -
I've been in touch with several Microsoft support teams about this issue, and the latest move was to shove me off onto Pro support, but since I'm using a personal Office account, I'm hoping that through the community I can find a way to resolve this issue without
escalating through our IT department. I do not think this is an Exchange issues because I have previously used this product and method without resulting in this error on a Windows 7 32-bit AMD computer and a Windows 8 and 8.1 Professional 64-bit Intel computer.
Here's my current specs:
Windows 7 Professional 64-bit, service pack 1
AMD A6-5400 3.6 GHz
8GB RAM
Microsoft Office 365 Home Premium
Office updates automatically, version 15.0.4551.1512
About Outlook shows "Microsoft Outlook 2013 (15.0.4551.1511) MSA (15.0.4551.1508) 32-bit/Part of Microsoft Office 365 Home Premium"
Here's how to reproduce the issue:
1) Open View Settings
2) Select "Other Settings..."
3) Disable "Use compact layout in widths smaller than XX characters" and enable "Always use single-line layout"
4) Select "Columns..."
5) Under "All Mail fields" add "In folder"
6) Select any email
7) Context-menu -> Find Related -> Emails in this Conversation
8) Select "more"
9) Sort by folder
10) Select all messages from Inbox.
11) Use Outlook's preset "Done" function and select a destination folder
12) Watch Outlook fail to run "Done" and reset your UI without producing an error.
The first attempt to resolve this issue was to set up a new Outlook profile. This seemed to exacerbate the problem and resulted in Outlook providing an "Unknown error" before resetting the UI.
The second attempt to resolve this issue was to run "outlook.exe /resetnavpane". However, the nav pane does not appear immediately relevant to this issue.
The following similar steps also result in a crash, this time with an error:
11) Flag all select message as Complete.
12) Move all messages from Inbox to a destination folder.
This change in procedure results in the error "Cannot move the items. Some items cannot be moved. They were either already moved or deleted, or access was denied."
Help me, Microsoft Community. You're my only hope.Import the calendar and contacts in Outlook.com. For contacts, export from Outlook as csv and import into Outlook by choosing the Other option (https://people.live.com/import/other?biciid=ImportCatalog)
You'll need to save the calendar as an ics file to import it. Select the calendar folder, the File, Save as an save as an ics.
Diane Poremsky [MVP - Outlook]
Outlook & Exchange Solutions Center
Outlook Tips
Subscribe to Exchange Messaging Outlook weekly newsletter -
Dear All,
I cannot connect to my Exchange account in Outlook 2013 using "Microsoft Exchange Server or Compatible Service".
First I would like to present my network environment, I have 4 physical servers;
The first one is holding the Domain Controller 1, IP@: 192.168.1.10
The second server is holding the additional Domain Controller which it is DC2, IP@: 192.168.1.11
The third server is holding the Exchange 2013 Mailbox, IP@: 192.168.1.15
And the last server is holding the Exchange 2013 CAS-HT, IP@: 192.168.1.16
I am doing the steps below:
1-Creating a new profile in outlook and start configuring the exchange account by entering the IP address of the Exchange-CAS Server, 192.168.1.16
2-entering the account name: [email protected]
3-Go to "More Settings" > "Connection" > "Connect to Microsoft Exchange using HTTP" > and entering the "Exchange Proxy Settings"
4-type the exchange CAS Server URL, https://192.168.1.16
5-Check the "Connect using SSL Only"
6-Authentication Settings: "NTLM Authentication", and pressing Apply
7-When I press the "Check Name" button, a message occurred> "The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action".
8-I go back to the "Exchange Proxy Settings" and I Uncheck the "Connect using SSL Only" and pressing Apply
9-i press the "Check Name" Button, a small window occurred to enter a Username and Password, so I enter the Administrator username and the administrator password and pressing "OK", but nothing is changed, I tried to enter my
username and password in the small window and I still got the same result.
I cannot verify the account name and I cannot complete the process.
I appreciate you kind assistance.Hi,
To narrow down the cause, I’d like to recommend the following troubleshooting:
1. Try to login the test account through OWA.
2. Check the Autodiscover settings: get-clientaccessserver |fl autodiscoverserviceinternaluri
3. Check the result of directly accessing the following URL:
https://autodiscover.domain.com/autodiscover/autodiscover.xml
Thanks,
Angela
Angela Shi
TechNet Community Support -
Outlook 2013 with exchange online account disconnected, tryin to connect for hours or indefinitely
I posted this in another forum (office 365) and was told to copy it here as it wasn't an office 365 issue so here is what I posted there:
===================================
Let me see if I can clarify better. This issue has been ongoing as long as I have worked for this client (I started in January but have been told the issue has been going on since before November of last year). The client has multiple construction sites
and its headquarters. There is a remote desktop server setup with a public IP address for the users "in the field" for accessing network resources at headquarters. At major construction sites (currently 3) they have high speed internet service installed
since the projects typically are 1+ years to complete. So at current times we have the following:
Main office:
Remote Desktop Server with logins for all employees
Main 2012R2 server
50MB/s internet connection via CenturyLink ISP
Site 1:
3 main users of computers. 1 constant user, 2 minimal use users. All 3 have experience the issue 3+ times a week
Comcast 50MB/S ISP
Site 2:
3 Main users of computers. 1 constant, 2 medium use users. All 3 experience the issue 3+ times a week
Comcast 50MB/s ISP
Site 3:
4+ computer users. 1 constant, 2 medium use users and the rest check email couple times a day. They also experience the disconnect issue 3+ times a week
15 MB/S DSL from CenturyLink ISP
There have been instances where (as examples) user 1a called me to tell me it was happening. Users 1b and 1c were not experiencing the issue. I was able to use a remote tool called Teamviewer to connect to her computer. Once connected I tried to open OWA
but it would not connect. I tried to ping the site and could not get a response. To verify I remoted into user 1b computer and his outlook was still connected and pinged fine. Both users being at the same site are on the same network. Had user 1a remote desktop
into the RDserver at the main office. Remoted into the server at the office her outlook on that machine connected no issues (in my mind rules out account issue?).
I don't believe it is network related due to the other computers working fine and being able to connect to her computer indicated to me that her NIC was fine. I don't think it was her account because it worked fine from the RD Server plus email service to
iPads/iPhones continue to work without issue. Once the computer is rebooted everything works fine for a while (could be hours, could be days).
Now to answer the questions for you:
1. it happens to all computers not at the main office but happens at random times to them. It also does not affect every computer at a remote location. It could be 1 or it could be multiple computers at the same time.
2. Affected users iPhones, iPads and outlook 2013 pro session on the RD Server at the main office continue to work no issues.
3. They cannot get to OWA on their machines when in that state, however can log into OWA on another machine plus the answer to #2 above.
4. It is all users at those locations, however I have experienced it myself at my house 1 time since January (I have a different exchange online plan/company than the one I am discussing in this post). The issue is random and it is uncertain if it will correct
itself if left sitting long enough (longest time it has been left is about 20 minutes or so) however even 20 minutes is a long time to wait for the service to return so users just reboot.
Please let me know If you have any solutions/ideas.
Thanks,
Brandon Smith
Cadence Communications
====================================
Hi Branon,
Thanks for your detailed information.
After going your post carefully, I am impressed by your strong technical skills. Regarding “I don't believe it is network related due to the other computers working fine and being able to connect to her computer indicated to me that her NIC was
fine. I don't think it was her account because it worked fine from the RD Server plus email service to iPads/iPhones continue to work without issue. Once the computer is rebooted everything works fine for a while (could be hours, could be days)” ,
I go along with you. Since the affected account could connect to other clients without issue , it indicates Office 365 account is no problem. And other computer were working fine and can connect to her computer, it shows the network environment does not cause
the issue. In this situation, the issue should relate to the specific Outlook Client. However this forum mainly focuses on Office 365 online services, to get more accurate responses, it’s suggested that you raise the problem in the Outlook forum. If they got
any result and you need further assistance from Office 365 side, please feel free to let us know.
In addition, about “I have had the users try to use OWA when it gets disconnected but they cannot get to that URL either. IE comes up with page not found”, I’d like to collect some information:
1. Does the issue only happen to IE? Have you tried logging in other browsers using the OWA address (like Chrome or Firefox)? Does it work?
2. Does only this user have the issue? Does it happen to other users?
3. Which version of Internet Explorer browser does the user use?
4. Could you provide us with the whole screenshot of the error message? You can post screenshots in our forum by clicking Use rich formatting and selecting the Insert Image icon.
Also, please try the following steps for troubleshooting:
a. Clear the IE caches and cookies when you log into Office 365 again.
b. Use the InPrivate Browsing of Internet Explorer to login.
c. Reset Internet Explorer’s settings, and try again.
d. Try to login in another network environment.
If there is any update, please let us know. I ’ll keep on monitoring this thread.
Best regards,
Jamie
===============================
As of today we still randomly experience this disconnect issue. Just today I had my test user call me to say she was disconnected. She is in location 2 where I have a test laptop also setup with her logged in. When she called I had her check the test laptop
and the outlook profile on that machine (same network) was still connected while her computer was not connected. I had her run the online analyzer tool on her machine (the one that would not connect) which ran for almost 2 hours. The tool finished right at
the same time that her outlook finally connected back to the server.
If anyone has any ideas/solutions please let me know.
Thanks in advance,
Brandon Smith
Cadence Communications Inc.Oddly enough my computer is right at this moment in this same disconnected state. Outlook shows an exclamation point in a yellow triangle. Its state is disconnected. If I go to portal.office.com I get to the login page but get page can't be displayed after
entering my credentials. I tried using google and found this for login
https://outlook.office365.com/owa/ it too times out and can't be displayed.
if I try and ping these sites I get:
====================================================================
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\brandon.CAD1>ping portal.office.com
Pinging us.portal.office.akadns.net [2a01:111:f100:4001::4625:61ea] with 32 byte
s of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 2a01:111:f100:4001::4625:61ea:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\brandon.CAD1>ping login.microsoftonline.com
Pinging aadg.windows.net.nsatc.net [168.62.24.150] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 168.62.24.150:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
===============================================================================
If I remote into another machine at a client site I can log into portal.office.com using my email account.
I ran the outlook connectivity analyzer tool and got this if it helps:
===============================================================
Testing Outlook connectivity.
The Outlook connectivity test completed successfully.
Additional Details
Elapsed Time: 41017 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to test Autodiscover for
[email protected].
Autodiscover was tested successfully.
Additional Details
Elapsed Time: 12161 ms.
Test Steps
Attempting each method of contacting the Autodiscover service.
The Autodiscover service was tested successfully.
Additional Details
Elapsed Time: 12161 ms.
Test Steps
Attempting to test potential Autodiscover URL
https://cadcom.us:443/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Elapsed Time: 475 ms.
Test Steps
Attempting to resolve the host name cadcom.us in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 184.168.55.1
Elapsed Time: 173 ms.
Testing TCP port 443 on host cadcom.us to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 149 ms.
Testing the SSL certificate to make sure it's valid.
The SSL certificate failed one or more certificate validation checks.
Additional Details
Elapsed Time: 152 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server cadcom.us on port 443.
The Microsoft Connectivity Analyzer wasn't able to obtain the remote SSL certificate.
Additional Details
The certificate couldn't be validated because SSL negotiation wasn't successful. This could have occurred as a result of a network error or because of a problem with the certificate installation.
Elapsed Time: 91 ms.
Attempting to test potential Autodiscover URL
https://autodiscover.cadcom.us:443/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Elapsed Time: 9000 ms.
Test Steps
Attempting to resolve the host name autodiscover.cadcom.us in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 132.245.92.232, 132.245.58.104, 132.245.3.136, 132.245.64.248, 132.245.82.56, 132.245.88.200, 132.245.81.200, 132.245.81.136, 2a01:111:f400:2c84::8, 2a01:111:f400:1014::8, 2a01:111:f400:2c61::8, 2a01:111:f400:2c5d::8, 2a01:111:f400:142a::8,
2a01:111:f400:5242::8, 2a01:111:f400:2414::8, 2a01:111:f400:4c0b::8
Elapsed Time: 304 ms.
Testing TCP port 443 on host autodiscover.cadcom.us to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
Tell me more about this issue and how to resolve it
Additional Details
A network error occurred while communicating with the remote host.
Elapsed Time: 8696 ms.
Attempting to contact the Autodiscover service using the HTTP redirect method.
The Autodiscover service was successfully contacted using the HTTP redirect method.
Additional Details
Elapsed Time: 2684 ms.
Test Steps
Attempting to resolve the host name autodiscover.cadcom.us in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 132.245.92.232, 132.245.58.104, 132.245.3.136, 132.245.64.248, 132.245.82.56, 132.245.88.200, 132.245.81.200, 132.245.81.136, 2a01:111:f400:2c84::8, 2a01:111:f400:1014::8, 2a01:111:f400:2c61::8, 2a01:111:f400:2c5d::8, 2a01:111:f400:142a::8,
2a01:111:f400:5242::8, 2a01:111:f400:2414::8, 2a01:111:f400:4c0b::8
Elapsed Time: 39 ms.
Testing TCP port 80 on host autodiscover.cadcom.us to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 57 ms.
The Microsoft Connectivity Analyzer is checking the host autodiscover.cadcom.us for an HTTP redirect to the Autodiscover service.
The redirect (HTTP 301/302) response was received successfully.
Additional Details
Redirect URL:
https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml
HTTP Response Headers:
Pragma: no-cache
X-FEServer: BY2PR07CA071
Connection: close
Content-Length: 0
Cache-Control: no-cache
Date: Tue, 21 Apr 2015 04:40:05 GMT
Location:
https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml
Server: Microsoft-IIS/8.0
X-Powered-By: ASP.NET
Elapsed Time: 47 ms.
Attempting to test potential Autodiscover URL
https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml
Testing of the Autodiscover URL was successful.
Additional Details
Elapsed Time: 2540 ms.
Test Steps
Attempting to resolve the host name autodiscover-s.outlook.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 132.245.24.82, 132.245.92.34, 132.245.92.194, 132.245.80.146, 157.56.239.194, 132.245.64.146, 2a01:111:f400:1414::2, 2a01:111:f400:2c2c::2, 2a01:111:f400:1428::2, 2a01:111:f400:4c32::2, 2a01:111:f400:2c40::2, 2a01:111:f400:5000::2
Elapsed Time: 345 ms.
Testing TCP port 443 on host autodiscover-s.outlook.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 44 ms.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Additional Details
Elapsed Time: 177 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover-s.outlook.com on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US, Issuer: CN=Microsoft IT SSL SHA1, OU=Microsoft IT, O=Microsoft Corporation, L=Redmond, S=Washington, C=US.
Elapsed Time: 119 ms.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name autodiscover-s.outlook.com was found in the Certificate Subject Alternative Name entry.
Elapsed Time: 0 ms.
Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.
Test Steps
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US.
One or more certificate chains were constructed successfully.
Additional Details
A total of 1 chains were built. The highest quality chain ends in root certificate CN=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE.
Elapsed Time: 18 ms.
Analyzing the certificate chains for compatibility problems with versions of Windows.
Potential compatibility problems were identified with some versions of Windows.
Additional Details
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
Elapsed Time: 3 ms.
Testing the certificate date to confirm the certificate is valid.
Date validation passed. The certificate hasn't expired.
Additional Details
The certificate is valid. NotBefore = 2/13/2015 12:38:15 AM, NotAfter = 2/13/2016 12:38:15 AM
Elapsed Time: 0 ms.
Checking the IIS configuration for client certificate authentication.
Client certificate authentication wasn't detected.
Additional Details
Accept/Require Client Certificates isn't configured.
Elapsed Time: 146 ms.
Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
The Microsoft Connectivity Analyzer successfully retrieved Autodiscover settings by sending an Autodiscover POST.
Additional Details
Elapsed Time: 1827 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL
https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml for user
[email protected].
The Autodiscover XML response was successfully retrieved.
Additional Details
Autodiscover Account Settings
XML response:
<?xml version="1.0"?>
<Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User>
<DisplayName>Brandon Smith</DisplayName>
<LegacyDN>/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon</LegacyDN>
<DeploymentId>5135be05-06e4-4e3b-9cbd-f39b6108647f</DeploymentId>
</User>
<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<Protocol Type="mapiHttp">
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<MailStore>
<ExternalUrl>https://outlook.office365.com/mapi/emsmdb/[email protected]</ExternalUrl>
</MailStore>
<AddressBook>
<ExternalUrl>https://outlook.office365.com/mapi/nspi/[email protected]</ExternalUrl>
</AddressBook>
</Protocol>
<Protocol>
<Type>WEB</Type>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<Internal>
<OWAUrl AuthenticationMethod="LiveIdFba, OAuth">https://outlook.office365.com/owa/</OWAUrl>
<Protocol>
<Type>EXCH</Type>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
</Protocol>
</Internal>
<External>
<OWAUrl AuthenticationMethod="Fba">https://outlook.office365.com/owa/cadcom.us/</OWAUrl>
<Protocol>
<Type>EXPR</Type>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
</Protocol>
</External>
</Protocol>
<Protocol>
<Type>EXHTTP</Type>
<Server>outlook.office365.com</Server>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
<OOFUrl>https://outlook.office365.com/EWS/Exchange.asmx</OOFUrl>
<OABUrl>https://outlook.office365.com/OAB/fb606d0b-79d8-4255-9c7b-552a0fccb72f/</OABUrl>
<UMUrl>https://outlook.office365.com/EWS/UM2007Legacy.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<SSL>On</SSL>
<AuthPackage>Basic</AuthPackage>
<EwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsUrl>
<EmwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EmwsUrl>
<SharingUrl>https://outlook.office365.com/EWS/Exchange.asmx</SharingUrl>
<EcpUrl>https://outlook.office365.com/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=cadcom.us</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=cadcom.us</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=cadcom.us</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=cadcom.us</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=cadcom.us</EcpUrl-sms>
<EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&exsvurl=1&FldID=<FldID>&realm=cadcom.us</EcpUrl-publish>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=cadcom.us</EcpUrl-photo>
<EcpUrl-connect>Connect/Main.aspx?rfr=olk&exsvurl=1&Provider=<Provider>&Action=<Action>&realm=cadcom.us</EcpUrl-connect>
<EcpUrl-tm>?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=cadcom.us</EcpUrl-tm>
<EcpUrl-tmCreating>?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=cadcom.us</EcpUrl-tmCreating>
<EcpUrl-tmEditing>?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=cadcom.us</EcpUrl-tmEditing>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=cadcom.us</EcpUrl-extinstall>
<ServerExclusiveConnect>On</ServerExclusiveConnect>
</Protocol>
</Account>
</Response>
</Autodiscover>
HTTP Response Headers:
request-id: 443c7500-1216-4307-b195-8d742873d0f0
X-CalculatedBETarget: co1pr04mb474.namprd04.prod.outlook.com
X-DiagInfo: CO1PR04MB474
X-BEServer: CO1PR04MB474
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Set-Cookie: ClientId=JYEVNJSG0UERWBME1PF2A; expires=Wed, 20-Apr-2016 04:40:07 GMT; path=/; secure; HttpOnly,EXOBasicAuth=compactTicket=&key=brandon%40cadcom.us+microsoft.exchange.autodiscover+157.56.138.143+&signature=QJdNVZ9GjQrYkxZg4iXgN8XbU7ZlhTifQyXVjqCwqbBgJL14yiG8oVRxKprB6LXqEBx90YDherBvRURQmGweF+XHW5Eg4gKIhRhSgy6XhMdQslO+PSV1TuZJIHB0g8KcM1MDr4LEuS19bT1HFPpLEUf7A+tmrfTQyy6l21zaUohb/Z0XZUn1o/pkbIcBBSb+tOVAemIsTyHN/p0VbbkA2AeMdVVJIz1wHLW7s9o7fCtJ7cM33Wzz9M6g5k/bNv/NAe9a2nbCZjpyqdmDkKrdmalekhBVkusIskPX5p8aVU8CuiTRtyIcRq8IWxvDhwyH3RiFnyVd5ytNy42M0r7+gQ==&puid=100300008CF2A4C2&expireTime=635651446880000000&membername=brandon%40cadcom.us&flags=False&userType=ManagedBusiness;
expires=Mon, 20-Apr-2015 16:38:08 GMT; path=/Autodiscover; secure; HttpOnly,[email protected]=u56Lnp2ejJqBzc6Znc7OmcjSnpnJzdLLx8qa0sfOyM/Sms7OyMzLyJmbms/HgZyem5yQktGKjIHNz87K0s/K0s3Oq8/LxcvPxc/HgZGeko+Nm8/L0Y+NkJvRkIqLk5CQlNGckJI=;
expires=Thu, 21-May-2015 04:40:08 GMT; path=/Autodiscover; secure; HttpOnly,[email protected]=u56Lnp2ejJqBzc6Znc7OmcjSnpnJzdLLx8qa0sfOyM/Sms7OyMzLyJmbms/HgZyem5yQktGKjIHNz87K0s/K0s3Oq8/LxcvPxc/H; expires=Thu, 21-May-2015 04:40:08 GMT; path=/Autodiscover;
secure; HttpOnly
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
X-FEServer: BY1PR10CA0031
Date: Tue, 21 Apr 2015 04:40:08 GMT
Content-Length: 4345
Elapsed Time: 1525 ms.
The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL
https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml for user
[email protected].
The Autodiscover XML response was successfully retrieved.
Additional Details
Autodiscover Account Settings
XML response:
<?xml version="1.0"?>
<Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User>
<DisplayName>Brandon Smith</DisplayName>
<LegacyDN>/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon</LegacyDN>
<DeploymentId>5135be05-06e4-4e3b-9cbd-f39b6108647f</DeploymentId>
</User>
<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<Protocol>
<Type>EXCH</Type>
<Server>[email protected]</Server>
<ServerDN>/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]</ServerDN>
<ServerVersion>73C18088</ServerVersion>
<MdbDN>/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]/cn=Microsoft Private MDB</MdbDN>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
<OOFUrl>https://outlook.office365.com/EWS/Exchange.asmx</OOFUrl>
<OABUrl>https://outlook.office365.com/OAB/fb606d0b-79d8-4255-9c7b-552a0fccb72f/</OABUrl>
<UMUrl>https://outlook.office365.com/EWS/UM2007Legacy.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<AuthPackage>Anonymous</AuthPackage>
<PublicFolderServer>outlook.office365.com</PublicFolderServer>
<EwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsUrl>
<EmwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EmwsUrl>
<SharingUrl>https://outlook.office365.com/EWS/Exchange.asmx</SharingUrl>
<EcpUrl>https://outlook.office365.com/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=cadcom.us</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=cadcom.us</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=cadcom.us</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=cadcom.us</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=cadcom.us</EcpUrl-sms>
<EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&exsvurl=1&FldID=<FldID>&realm=cadcom.us</EcpUrl-publish>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=cadcom.us</EcpUrl-photo>
<EcpUrl-connect>Connect/Main.aspx?rfr=olk&exsvurl=1&Provider=<Provider>&Action=<Action>&realm=cadcom.us</EcpUrl-connect>
<EcpUrl-tm>?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=cadcom.us</EcpUrl-tm>
<EcpUrl-tmCreating>?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=cadcom.us</EcpUrl-tmCreating>
<EcpUrl-tmEditing>?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=cadcom.us</EcpUrl-tmEditing>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=cadcom.us</EcpUrl-extinstall>
<ServerExclusiveConnect>off</ServerExclusiveConnect>
</Protocol>
<Protocol>
<Type>EXPR</Type>
<Server>outlook.office365.com</Server>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
<OOFUrl>https://outlook.office365.com/EWS/Exchange.asmx</OOFUrl>
<OABUrl>https://outlook.office365.com/OAB/fb606d0b-79d8-4255-9c7b-552a0fccb72f/</OABUrl>
<UMUrl>https://outlook.office365.com/EWS/UM2007Legacy.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<SSL>On</SSL>
<AuthPackage>Basic</AuthPackage>
<CertPrincipalName>msstd:outlook.com</CertPrincipalName>
<EwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsUrl>
<EmwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EmwsUrl>
<SharingUrl>https://outlook.office365.com/EWS/Exchange.asmx</SharingUrl>
<EcpUrl>https://outlook.office365.com/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=cadcom.us</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=cadcom.us</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=cadcom.us</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=cadcom.us</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=cadcom.us</EcpUrl-sms>
<EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&exsvurl=1&FldID=<FldID>&realm=cadcom.us</EcpUrl-publish>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=cadcom.us</EcpUrl-photo>
<EcpUrl-connect>Connect/Main.aspx?rfr=olk&exsvurl=1&Provider=<Provider>&Action=<Action>&realm=cadcom.us</EcpUrl-connect>
<EcpUrl-tm>?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=cadcom.us</EcpUrl-tm>
<EcpUrl-tmCreating>?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=cadcom.us</EcpUrl-tmCreating>
<EcpUrl-tmEditing>?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=cadcom.us</EcpUrl-tmEditing>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=cadcom.us</EcpUrl-extinstall>
<ServerExclusiveConnect>on</ServerExclusiveConnect>
<EwsPartnerUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsPartnerUrl>
<GroupingInformation>CO1PR04</GroupingInformation>
</Protocol>
<Protocol>
<Type>WEB</Type>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<Internal>
<OWAUrl AuthenticationMethod="LiveIdFba, OAuth">https://outlook.office365.com/owa/</OWAUrl>
<Protocol>
<Type>EXCH</Type>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
</Protocol>
</Internal>
<External>
<OWAUrl AuthenticationMethod="Fba">https://outlook.office365.com/owa/cadcom.us/</OWAUrl>
<Protocol>
<Type>EXPR</Type>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
</Protocol>
</External>
</Protocol>
<Protocol>
<Type>EXHTTP</Type>
<Server>outlook.office365.com</Server>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
<OOFUrl>https://outlook.office365.com/EWS/Exchange.asmx</OOFUrl>
<OABUrl>https://outlook.office365.com/OAB/fb606d0b-79d8-4255-9c7b-552a0fccb72f/</OABUrl>
<UMUrl>https://outlook.office365.com/EWS/UM2007Legacy.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<SSL>On</SSL>
<AuthPackage>Basic</AuthPackage>
<CertPrincipalName>msstd:outlook.com</CertPrincipalName>
<EwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsUrl>
<EmwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EmwsUrl>
<SharingUrl>https://outlook.office365.com/EWS/Exchange.asmx</SharingUrl>
<EcpUrl>https://outlook.office365.com/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=cadcom.us</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=cadcom.us</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=cadcom.us</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=cadcom.us</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=cadcom.us</EcpUrl-sms>
<EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&exsvurl=1&FldID=<FldID>&realm=cadcom.us</EcpUrl-publish>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=cadcom.us</EcpUrl-photo>
<EcpUrl-connect>Connect/Main.aspx?rfr=olk&exsvurl=1&Provider=<Provider>&Action=<Action>&realm=cadcom.us</EcpUrl-connect>
<EcpUrl-tm>?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=cadcom.us</EcpUrl-tm>
<EcpUrl-tmCreating>?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=cadcom.us</EcpUrl-tmCreating>
<EcpUrl-tmEditing>?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=cadcom.us</EcpUrl-tmEditing>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=cadcom.us</EcpUrl-extinstall>
<ServerExclusiveConnect>On</ServerExclusiveConnect>
</Protocol>
</Account>
</Response>
</Autodiscover>
HTTP Response Headers:
request-id: 4412d758-013f-4700-bde1-06dc5e66bf6d
X-CalculatedBETarget: co1pr04mb474.namprd04.prod.outlook.com
X-DiagInfo: CO1PR04MB474
X-BEServer: CO1PR04MB474
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Set-Cookie: ClientId=YVWYC2UW3EAOSJXJYJDCDW; expires=Wed, 20-Apr-2016 04:40:08 GMT; path=/; secure; HttpOnly,[email protected]=u56Lnp2ejJqBzc6Znc7OmcjSnpnJzdLLx8qa0sfOyM/Sms7OyMzLyJmbms/HgZyem5yQktGKjIHNz87K0s/K0s3Oq8/LxcvPxc/HgZGeko+Nm8/L0Y+NkJvRkIqLk5CQlNGckJI=;
expires=Thu, 21-May-2015 04:40:08 GMT; path=/Autodiscover; secure; HttpOnly,[email protected]=u56Lnp2ejJqBzc6Znc7OmcjSnpnJzdLLx8qa0sfOyM/Sms7OyMzLyJmbms/HgZyem5yQktGKjIHNz87K0s/K0s3Oq8/LxcvPxc/H; expires=Thu, 21-May-2015 04:40:08 GMT; path=/Autodiscover;
secure; HttpOnly
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
X-FEServer: BY1PR10CA0031
Date: Tue, 21 Apr 2015 04:40:08 GMT
Content-Length: 9631
Elapsed Time: 301 ms.
Autodiscover settings for Outlook connectivity are being validated.
The Microsoft Connectivity Analyzer validated the Outlook Autodiscover settings.
Additional Details
Elapsed Time: 0 ms.
Testing MAPI over HTTP connectivity to server outlook.office365.com
MAPI over HTTP connectivity was verified successfully.
Additional Details
HTTP Response Headers:
request-id: 2931fc03-73eb-4bb0-8ffc-34b9445369ed
X-FEServer: BY2PR09CA0048
Content-Length: 0
Date: Tue, 21 Apr 2015 04:40:08 GMT
Set-Cookie: ClientId=ZZCG7DWJLKIDNUIKMHP0Q; expires=Wed, 20-Apr-2016 04:40:09 GMT; path=/; secure; HttpOnly
Server: Microsoft-IIS/8.0
WWW-Authenticate: Basic Realm=""
X-Powered-By: ASP.NET
Elapsed Time: 3246 ms.
Test Steps
Attempting to resolve the host name outlook.office365.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 132.245.24.82, 132.245.92.34, 132.245.92.194, 132.245.80.146, 157.56.239.194, 132.245.64.146, 2a01:111:f400:2c40::2, 2a01:111:f400:5000::2, 2a01:111:f400:1414::2, 2a01:111:f400:2c2c::2, 2a01:111:f400:1428::2, 2a01:111:f400:4c32::2
Elapsed Time: 152 ms.
Testing TCP port 443 on host outlook.office365.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 70 ms.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Additional Details
Elapsed Time: 251 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server outlook.office365.com on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US, Issuer: CN=Microsoft IT SSL SHA1, OU=Microsoft IT, O=Microsoft Corporation, L=Redmond, S=Washington, C=US.
Elapsed Time: 141 ms.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name outlook.office365.com was found in the Certificate Subject Alternative Name entry.
Elapsed Time: 3 ms.
Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.
Test Steps
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US.
One or more certificate chains were constructed successfully.
Additional Details
A total of 1 chains were built. The highest quality chain ends in root certificate CN=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE.
Elapsed Time: 34 ms.
Analyzing the certificate chains for compatibility problems with versions of Windows.
Potential compatibility problems were identified with some versions of Windows.
Additional Details
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
Elapsed Time: 6 ms.
Testing the certificate date to confirm the certificate is valid.
Date validation passed. The certificate hasn't expired.
Additional Details
The certificate is valid. NotBefore = 2/13/2015 12:38:15 AM, NotAfter = 2/13/2016 12:38:15 AM
Elapsed Time: 0 ms.
Testing HTTP Authentication Methods for URL
https://outlook.office365.com/mapi/emsmdb/[email protected].
The HTTP authentication methods are correct.
Additional Details
The Microsoft Connectivity Analyzer found all expected authentication methods and no disallowed methods. Methods found: Basic
HTTP Response Headers:
request-id: 2931fc03-73eb-4bb0-8ffc-34b9445369ed
X-FEServer: BY2PR09CA0048
Content-Length: 0
Date: Tue, 21 Apr 2015 04:40:08 GMT
Set-Cookie: ClientId=ZZCG7DWJLKIDNUIKMHP0Q; expires=Wed, 20-Apr-2016 04:40:09 GMT; path=/; secure; HttpOnly
Server: Microsoft-IIS/8.0
WWW-Authenticate: Basic Realm=""
X-Powered-By: ASP.NET
Elapsed Time: 190 ms.
Testing the MAPI Address Book endpoint on the Exchange server.
The address book endpoint was tested successfully.
Additional Details
Elapsed Time: 1987 ms.
Test Steps
Testing the address book "Check Name" operation for user
[email protected] against server outlook.office365.com.
Check Name succeeded.
Additional Details
DisplayName: Brandon Smith, LegDN: /o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon
Elapsed Time: 1987 ms.
Testing the MAPI Mail Store endpoint on the Exchange server.
We successfully tested the Mail Store endpoint.
Additional Details
Elapsed Time: 594 ms.
Test Steps
Attempting to log on to the Mailbox.
We were able to log on to the Mailbox.
Additional Details
Elapsed Time: 594 ms.
Testing RPC over HTTP connectivity to server outlook.office365.com
RPC over HTTP connectivity was verified successfully.
Additional Details
HTTP Response Headers:
request-id: 64e2bf62-0b20-4e36-912d-005c7a017fb4
X-DiagInfo: BY2PR09CA0048
X-FEServer: BY2PR09CA0048
Content-Length: 0
Date: Tue, 21 Apr 2015 04:40:11 GMT
Set-Cookie: ClientId=SKGVNJCDX0OA7M7QPJFWLA; expires=Wed, 20-Apr-2016 04:40:12 GMT; path=/; secure; HttpOnly
Server: Microsoft-IIS/8.0
WWW-Authenticate: Basic Realm=""
X-Powered-By: ASP.NET
Elapsed Time: 25606 ms.
Test Steps
Attempting to resolve the host name outlook.office365.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 132.245.24.82, 132.245.92.34, 132.245.92.194, 132.245.80.146, 157.56.239.194, 132.245.64.146, 2a01:111:f400:2c40::2, 2a01:111:f400:5000::2, 2a01:111:f400:1414::2, 2a01:111:f400:2c2c::2, 2a01:111:f400:1428::2, 2a01:111:f400:4c32::2
Elapsed Time: 42 ms.
Testing TCP port 443 on host outlook.office365.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 61 ms.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Additional Details
Elapsed Time: 223 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server outlook.office365.com on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US, Issuer: CN=Microsoft IT SSL SHA1, OU=Microsoft IT, O=Microsoft Corporation, L=Redmond, S=Washington, C=US.
Elapsed Time: 121 ms.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name outlook.office365.com was found in the Certificate Subject Alternative Name entry.
Elapsed Time: 1 ms.
Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.
Test Steps
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US.
One or more certificate chains were constructed successfully.
Additional Details
A total of 1 chains were built. The highest quality chain ends in root certificate CN=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE.
Elapsed Time: 36 ms.
Analyzing the certificate chains for compatibility problems with versions of Windows.
Potential compatibility problems were identified with some versions of Windows.
Additional Details
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
Elapsed Time: 5 ms.
Testing the certificate date to confirm the certificate is valid.
Date validation passed. The certificate hasn't expired.
Additional Details
The certificate is valid. NotBefore = 2/13/2015 12:38:15 AM, NotAfter = 2/13/2016 12:38:15 AM
Elapsed Time: 0 ms.
Checking the IIS configuration for client certificate authentication.
Client certificate authentication wasn't detected.
Additional Details
Accept/Require Client Certificates isn't configured.
Elapsed Time: 173 ms.
Testing HTTP Authentication Methods for URL
https://outlook.office365.com/rpc/[email protected]:6002.
The HTTP authentication methods are correct.
Additional Details
The Microsoft Connectivity Analyzer found all expected authentication methods and no disallowed methods. Methods found: Basic
HTTP Response Headers:
request-id: 64e2bf62-0b20-4e36-912d-005c7a017fb4
X-DiagInfo: BY2PR09CA0048
X-FEServer: BY2PR09CA0048
Content-Length: 0
Date: Tue, 21 Apr 2015 04:40:11 GMT
Set-Cookie: ClientId=SKGVNJCDX0OA7M7QPJFWLA; expires=Wed, 20-Apr-2016 04:40:12 GMT; path=/; secure; HttpOnly
Server: Microsoft-IIS/8.0
WWW-Authenticate: Basic Realm=""
X-Powered-By: ASP.NET
Elapsed Time: 27 ms.
Attempting to ping RPC proxy outlook.office365.com.
RPC Proxy was pinged successfully.
Additional Details
Elapsed Time: 2099 ms.
Attempting to ping the MAPI Mail Store endpoint with identity:
[email protected]:6001.
The endpoint was pinged successfully.
Additional Details
The endpoint responded in 47 ms.
Elapsed Time: 5049 ms.
Testing the MAPI Address Book endpoint on the Exchange server.
The address book endpoint was tested successfully.
Additional Details
Elapsed Time: 6447 ms.
Test Steps
Attempting to ping the MAPI Address Book endpoint with identity:
[email protected]:6004.
The endpoint was pinged successfully.
Additional Details
The endpoint responded in 218 ms.
Elapsed Time: 4230 ms.
Testing the address book "Check Name" operation for user
[email protected] against server
[email protected].
Check Name succeeded.
Additional Details
DisplayName: Brandon Smith, LegDN: /o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon
Elapsed Time: 2216 ms.
Testing the MAPI Referral service on the Exchange Server.
The Referral service was tested successfully.
Additional Details
Elapsed Time: 6271 ms.
Test Steps
Attempting to ping the MAPI Referral Service endpoint with identity:
[email protected]:6002.
The endpoint was pinged successfully.
Additional Details
The endpoint responded in 640 ms.
Elapsed Time: 4630 ms.
Attempting to perform referral for user /o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon on server
[email protected].
We got the address book server successfully.
Additional Details
The server returned by the Referral service:
[email protected]
Elapsed Time: 1640 ms.
Testing the MAPI Address Book endpoint on the Exchange server.
The address book endpoint was tested successfully.
Additional Details
Elapsed Time: 923 ms.
Test Steps
Attempting to ping the MAPI Address Book endpoint with identity:
[email protected]:6004.
The endpoint was pinged successfully.
Additional Details
The endpoint responded in 62 ms.
Elapsed Time: 72 ms.
Testing the address book "Check Name" operation for user
[email protected] against server
[email protected].
Check Name succeeded.
Additional Details
DisplayName: Brandon Smith, LegDN: /o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon
Elapsed Time: 851 ms.
Testing the MAPI Mail Store endpoint on the Exchange server.
We successfully tested the Mail Store endpoint.
Additional Details
Elapsed Time: 4286 ms.
Test Steps
Attempting to ping the MAPI Mail Store endpoint with identity:
[email protected]:6001.
The endpoint was pinged successfully.
Additional Details
The endpoint responded in 656 ms.
Elapsed Time: 3656 ms.
Attempting to log on to the Mailbox.
We were able to log on to the Mailbox.
Additional Details
Elapsed Time: 628 ms.
=============================================================================
Maybe you are looking for
-
Is it possible to embed fiori launch pad into portal?
Hi guys, I'm not familiar with fiori launch pad, how does it work. But I need a quick feasibility check: is fiori launch pad some kind of an application url? Can I embed it into somewhere in my company portal? Regards, Aaron.
-
Upgrading weblogic 8.1 to jdk1.5.0_04
Has anyone performed this upgrade? Are there any known issues with this upgrade?
-
The new iMac puts 1920x1200 pixeles in 24". One of the cinema displays puts 1920x1200 in 23". If aspect ratio is the same, then the iMac display's pixel pitch should be not as good as the cinema display or perhaps even the 20" iMac. Is this correct?
-
Need to refresh Quality DB from its Production DB
Hi Forum , We have Production Oracle 11.2.0.3.0 Database and also have Quality DB with same version 11.2.0.3.0 . Both the Database's are available in different machines with different SID. Like: Production SID: EBP Quality SID: EQP OS: AIX Customer:
-
Hi dudes I am new to this forum. I am using iText pdf converter in my office. When i tried to create a dynamic pdf file, generates some runtime exceptions. It is compiling with out any problem I had run the same code in another system at my home with