Outlook clients unable to connect to Exchange / Windows user profile
Exchange 2010
Outlook 2010/2013
I've seen a dozen or so computers in the last few weeks with this problem. The user suddenly cannot connect to the Exchange server in Outlook. (Sorry, I don't have specific error messages for this part.)
If I try a repair on the Email account or try to create a new Mail profile, I get this error:
"The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
I have verified all Exchange and mail security settings. Outlook configuration is not the problem.
I tried deleting %appdata%\microsoft\outlook and %localappdata%\microsoft\outlook.
I tried a repair on Microsoft Office.
I tried creating a new Mail profile for a different email account.
The only thing that has fixed this problem is a completely new Windows user profile, which tells me there is something else broken in the user profile. Does anyone have any idea what it might be?
Blog /
Twitter
Hi,
Please try to access Exchange via OWA.
This issue may occur when the HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders registry key does not contain all of the required data. Specifically, these problems occur if the AppData string value is missing from this
registry key.
To resolve this issue, import the User Shell Folders registry key from a working Windows User Profile.
Steps to perform on a working computer
Start Registry Editor. Click Start , type regedit in the Search programs and files box, and then press Enter.
Locate and then select the following registry subkey: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
On the File menu, click Export.
Specify the name of the .reg file and then click Save.
Copy the .reg file to the computer exibiting this problem.
Close Registry Editor.
Steps to perform on the computer displaying the above error(s)
Start Registry Editor.
On the File menu click Import.
Locate and select the .reg file exported from the working computer.
Click Open.
Close Registry Editor.
Best Regards.
Similar Messages
-
Essbase client missing after creation of new windows user profile
I created a new windows user profile after an apparent corruption of my old one. However, when I open Excel, the Essbase client (add-in) is gone. Smartview is still there. The client doesn't show up after registering Essbase Add-In is executed. I can add the client by navigating to C:\Hyperion\products\Essbase\EssbaseClient\bin and selecting essxleqd.xla and essxcln.xll. The add-in then appears to be installed. However, when I try to connect to Essbase, the connection dialog box does not show up. I'm on version 11.1.1.3 and Excel 2007.
Is there a way to resolve this short of re-installing the client? Any advice would be appreciated.
Thanks in advance.
daveI remember the Essbase add-in used to be a small executable of a few MB that was easy to install. It's my understanding that they went to the global installer where they include various product assemblies. The files needed to run the global installer for a simple add-in amount to close to about 4GB in size. Our VPN for remote users is very slow and takes forever to install. I see ther is still a small executable for the Smartview install. Is there a small executable for the Essbase add-in somewhere that I'm not aware of? I can reinstall if that's what it takes. I was hoping there might something a bit less time consuming.
Thanks John.
Edited by: DAS80220 on Jun 28, 2011 7:50 AM -
External outlook clients can't connect to Exchange 2013
Currently running server 2012 r2 and exchange 2013 sp1...
Internally everything works fine, clients can also connect externally to owa/ecp. However when using an outlook client they are unable to connect. This is my first experience with exchange 2013 so I am at a loss. What steps should I be following to get this
working properly? Or if anyone has some suggestions to get more information I can do that as well.
Thanks!
Connecting from a mobile-phone using mail.mail.com works fine.
We are using a self-signed certificate for testing purposes..Testing Outlook connectivity.
The Outlook connectivity test failed.
Additional Details
Elapsed Time: 941 ms.
Test Steps
Testing RPC over HTTP connectivity to server mail.mail.com
RPC over HTTP connectivity failed.
Additional Details
Elapsed Time: 941 ms.
Test Steps
Attempting to resolve the host name mail.mail.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: xxx.xxx.xx.x
Elapsed Time: 535 ms.
Testing TCP port 443 on host mail.mail.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 176 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: 229 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server mail.mail.com on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=mail.mail.com, Issuer: CN=mail.mail.com.
Elapsed Time: 154 ms.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name mail.mail.com was found in the Certificate Subject Common name.
Elapsed Time: 0 ms.
Certificate trust is being validated.
Certificate trust validation failed.
Test Steps
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=mail.mail.com
A certificate chain couldn't be constructed for the certificate.
Tell me more about this issue and how to resolve it
Additional Details
The certificate chain didn't end in a trusted root. Root = CN=mail.mail.com
Elapsed Time: 33 ms. -
Hi all,
need urgent assistance on the following issue
this is my Exchange 2010 setup
2 x CAS/Hub servers with HP network teaming, and load balanced using Windows NLB multicast mode. There are 2 VIPs on the NLB, one for outlook anywhere, one for autodiscover
2 DNS records were created for the 2 VIPs
Clients use Outlook Anywhere (HTTPS) to connect to the CAS servers from external segment via a Palo Alto firewall, which also acts as a layer 3 router
static arp was set on the Palo Alto firewall, with both virtual MACs pointing to the primary virtual MAC used by the NLB.
Observations
1. within same segment - no issue accessing Exchange servers, even when one CAS node is offline
2. external segment (via firewall)
a. when both nodes are up
outlook client able to connect to Exchange CAS VIP on 443, but will disconnect after around 30 seconds. Client will retry and the pattern will repeat
Exchange CAS RPC logs shows client connections and disconnections to the outlook anywhere VIP address
Firewall logs shows allowed traffic from client to the VIPs
unable to complete profile creation
b. with only CAS2 (CAS1 stopped/deleted from NLB cluster)
no issues accessing Exchange servers, creating profiles etc
c. with only CAS1
same behaviour as (a)
reinstalled NLB, but doesn't resolve
deleted CAS1 from NLB cluster, and re-add. issue remain
Q1. is teaming supported? Teaming is currently set to automatic mode, instead of specified Fault Tolerant
Q2. are there additional settings we need to set or verify on the Palo Alto firewall, since the issue only happen to external segment? Thanks!Yes - I've been scarred with this for many years :(
If it is just CAS 1 that is causing issues, then focus in on that. The support statement for Win 2008 R2 is that NLB is still a 3rd party component and support may ask for it to be disabled.
http://support.microsoft.com/kb/278431
Does CAS1 and CAS2 have the same NICs (firmware as well), driver, teaming software, and teaming config?
I also want to ask what the network team did for configuring the switch ports on the servers? This will vary from vendor to vendor - did they do the same config on both?
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter: LinkedIn:
Facebook:
XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
Thanks Rhoderick, issue still persists
can you also help clarify what you meant by "configuring the switch ports on the servers"?
thanks again -
Unable to connect to Exchange 2013 using Outlook 2010/2013 with latest patch
Dear All,
I'm setting up Exchange 2013 CU2 coexist with Exchange 2010 SP3. Since we are still planning and testing, the internet is still pointing to 2010 for send/receive mails.
The 2013 environment are:-
2 X CAS server with MS NLB configured
2X MBX server with DA
Internal NLB/licent access: excas2013.int.my.domain
External access (current set on 2010 as well): webmail.my.domain
Certificate with valid subject name has been import to 2013 and 2010:
CN: webmail.mydomain
SAN: excas2013.int.my.domain
SAN: excas.int.my.domain (for 2010)
I am able to connect to my Exchange 2010 user thru 2013 CAS server and proxy to exhcnage 2010 by outlook. However, I cannot connect to Exchange 2013 user by outlook. During mail profile create of Exchange 2013 user by autodiscover (pointed to exchange 2013),
the process looks good:-
Establish network connection (checked)
Searching for [email protected] server settings (checked)
Log on to server
The process stop at "Log on to server" and a windows prompt, saying:
The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
Clicked OK, I can see:-
MS Exchange Server:
[email protected]
Mailbox:
=SMPT:[email protected]
WHen I click "Check Name", it said The name cannot be resolved.
I have no idea of what is going on. Just want some help~I have checked the iis log:-
2013-09-23 06:58:29 10.144.144.71 POST /autodiscover/autodiscover.xml &cafeReqId=99ed5467-a294-481c-95eb-9b21d6530404; 443 mydomain\training101 10.144.85.4 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7106;+Pro) 200 0 0 8018
2013-09-23 06:58:29 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f4652a19-2e8e-4652-a007-0cf0b7fb792e&cafeReqId=f4652a19-2e8e-4652-a007-0cf0b7fb792e; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:29 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=c48cda77-6008-423b-8e8b-d6d40f4d1b39&cafeReqId=c48cda77-6008-423b-8e8b-d6d40f4d1b39; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:29 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=033f1ce4-43ba-49b1-b226-f4cc357e7702&cafeReqId=033f1ce4-43ba-49b1-b226-f4cc357e7702; 443 - 10.144.85.4 MSRPC 401 1 2148074252
15
2013-09-23 06:58:29 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=d2424d25-ca9e-4867-922f-e527b041d9db&cafeReqId=d2424d25-ca9e-4867-922f-e527b041d9db; 443 - 10.144.85.4 MSRPC 401 1 64 0
2013-09-23 06:58:31 10.144.144.73 POST /autodiscover/autodiscover.xml &cafeReqId=ff35f49b-e418-4d55-b66c-dbae509cc12f; 443 - 10.144.92.17 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6662;+Pro) 401 1 2148074254 0
2013-09-23 06:58:31 10.144.144.73 POST /autodiscover/autodiscover.xml &cafeReqId=033f8ed6-d7ce-41b2-8ed2-e275e22e53be; 443 mydomain\tkchung 10.144.92.17 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6662;+Pro) 200 0 64 15
2013-09-23 06:58:37 10.144.144.71 POST /powershell serializationLevel=Full;ExchClientVer=15.0.712.24;clientApplication=ManagementShell;TargetServer=;PSVersion=3.0&sessionID=Version_15.0_(Build_711.24)=rJqNiZqNgbqnsr3Py9GWkYvRlZqc0ZyQkoHOxsvOxsbJzczNgcbQzczQzc/OzN/Ixc/KxczI376y&cafeReqId=5350aa81-6668-489e-b099-3b3647115f10;
80 mydomain\Administrator 10.144.144.71 Microsoft+WinRM+Client 500 0 0 180040
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f961c596-efff-4696-9188-611a0d151601&cafeReqId=f961c596-efff-4696-9188-611a0d151601; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=753d8852-ce19-459c-ac78-849c3e51e0a1&cafeReqId=753d8852-ce19-459c-ac78-849c3e51e0a1; 443 - 10.144.85.4 MSRPC 401 1 2148074254
15
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=c9e86049-c883-4b03-8546-143909361a80&cafeReqId=c9e86049-c883-4b03-8546-143909361a80; 443 mydomain\training101 10.144.85.4
MSRPC 404 0 64 78
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=327ace4c-b2c8-44c1-95ba-7871727f60ef&cafeReqId=327ace4c-b2c8-44c1-95ba-7871727f60ef; 443 mydomain\training101 10.144.85.4
MSRPC 200 0 64 109
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=a7c8daa9-e458-4f2d-b388-7300e8679dcd&cafeReqId=a7c8daa9-e458-4f2d-b388-7300e8679dcd; 443 - 10.144.85.4 MSRPC 401 1 2148074254
15
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=c40afede-dd8f-4ac7-a3dd-827872bb2e76&cafeReqId=c40afede-dd8f-4ac7-a3dd-827872bb2e76; 443 - 10.144.85.4 MSRPC 401 1 2148074254
15
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=2dc56148-1900-4044-b72a-4b13e5e871f0&cafeReqId=2dc56148-1900-4044-b72a-4b13e5e871f0; 443 mydomain\training101 10.144.85.4
MSRPC 404 0 64 15
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=9475aad3-9537-4dac-86cb-6fdb187fa148&cafeReqId=9475aad3-9537-4dac-86cb-6fdb187fa148; 443 mydomain\training101 10.144.85.4
MSRPC 200 0 64 31
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=11a54e96-d8d8-4649-8e01-f8138ebf7b8d&cafeReqId=11a54e96-d8d8-4649-8e01-f8138ebf7b8d; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=b1a3e503-1077-4144-84df-fcdb65a7eea4&cafeReqId=b1a3e503-1077-4144-84df-fcdb65a7eea4; 443 - 10.144.85.4 MSRPC 401 1 2148074254
15
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=5b5639ba-4c91-4351-bda6-bcec46d6b218&cafeReqId=5b5639ba-4c91-4351-bda6-bcec46d6b218; 443 mydomain\training101 10.144.85.4
MSRPC 404 0 0 15
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f200806f-3294-4210-8940-e3fee0385ccd&cafeReqId=f200806f-3294-4210-8940-e3fee0385ccd; 443 mydomain\training101 10.144.85.4
MSRPC 200 0 64 46
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=675d6515-85da-43fa-9cd8-0a18ac06a71f&cafeReqId=675d6515-85da-43fa-9cd8-0a18ac06a71f; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=b97b2c3e-5309-4927-8330-fe0f339b5930&cafeReqId=b97b2c3e-5309-4927-8330-fe0f339b5930; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=504d462a-db21-4e4b-8568-79e4099d78c1&cafeReqId=504d462a-db21-4e4b-8568-79e4099d78c1; 443 mydomain\training101 10.144.85.4
MSRPC 404 0 0 31
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=b4757b1e-8428-454a-91df-ca0a2153144f&cafeReqId=b4757b1e-8428-454a-91df-ca0a2153144f; 443 mydomain\training101 10.144.85.4
MSRPC 200 0 64 46 -
Windows XP SP3 and Outlook 2010 can't connect with Exchange 2010 or Exchange 2013
XP+SP3+Outlook 2010 can't connect to Exchange 2010&2013 in the internal network without safe mode.
Hi,
Did you get any error messages?
Do you have Outlook Anywhere and autodiscovery set up properly?
Can you ping the Exchange server?
Please use Test Email AutoConfiguration
to test if the Autodiscover service is configured properly. See:
https://hosting.intermedia.net/support/kb/default.asp?id=2150
We can also use the remote connectivity analyzer to troubleshoot the issue:
https://testconnectivity.microsoft.com/
In addition, turn off your firewall and anti-virus to check the result.
Hope this helps.
Best Regards,
Steve Fan
TechNet Community Support -
Hi all,
From time to time (at least once a day), the following message pops up on the user's screen:
"There is a problem with the proxy server's security certificate. Outlook is unable to connect to the proxy server . Error Code 80000000)."
If we click "OK" it goes away and everything continues to work although sometimes Outlook disconnects. It is quite annoying...
Any ideas?
Thank you in advanceHi,
For the security alert issue, I'd like to recommend you check the name in the alert windows, and confirm if the name is in your certificate.
Additionally, to narrow down the cause, when the Outlook client cannot connect again, I recommand you firstly check the connectivity by using Test E-mail AutoConfiguration. For more information, you can refe to the following article:
http://social.technet.microsoft.com/Forums/en-US/54bc6b17-9b60-46a4-9dad-584836d15a02/troubleshooting-and-introduction-for-exchange-20072010-autodiscover-details-about-test-email?forum=exchangesvrgeneral
Thanks,
Angela Shi
TechNet Community Support -
Outlook is unable to connect to the proxy server. (Error code 0)
Hello,
I have just commenced a Exchange 2007 SP3 to Exchange 2013 SP1 migration following the following guide: http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
As per the above guide, my 2007 environment is now known as legacy.company.com and my 2013, webmail.company.com.
I'm using the same certificate on both boxes and it has the names autodiscover.company.com, webmail.company.com and legacy.company.com. All that seems to be working fine.
OWA is functioning perfectly, hitting https://webmail.company.com will pass the user off to https://legacy.company.com if the mailbox is on 2007. Alongside this, Outlook also has no issues connecting to 2007 mailboxes with the client proxy settings
being reconfigured to https://legacy.company.com automatically.
My problem comes when a mailbox is migrated to 2013. OWA functions fine and presents the mailbox but Outlook is unable to connect, presenting the error:
There is a problem with the proxy server's security certificate.
The name on the security certificate is invalid or does not match the name of the target site webmail.company.com.
Outlook is unable to connect to the proxy server. (Error Code 0)
If I modify the Outlook client's settings and disable "Only connect to proxy servers that have this principal name in their certificate: msstd:webmail.company.com", Outlook connects and functions fine.
I'm at a loss and have tried everything I can think and find on google. Any suggestions would be greatly appreciated.Hi,
Please refer to the following article :
http://support.microsoft.com/kb/923575
Cause:
This issue may occur if one or more of the following conditions are true:
The connection to the server requires a certification authority (CA).
You have not trusted the certification authority at the root.
The certificate may be invalid or revoked.
The certificate does not match the name of the site.
A third-party add-in is preventing access.
Solution:
To examine the certificate, follow these steps:
In Microsoft Internet Explorer, connect to the RPC server or to the secure server. For example, type
https://www.<var>server_name</var>.com/rpc in the Address bar of the Web browser, and then press ENTER.
Note The <var>server_name</var> placeholder references the RPC server name or the secure server name.
Double-click the padlock icon that is located in the lower-right corner of the Web browser.
Click the Details tab.
Note the information in the following fields:
Valid to
The Valid to field indicates the date until which the certificate is valid.
Subject
The data in the Subject field should match the site name.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support -
Outlook is unable to connect to the proxy server.(Error Code 10) when users opened Outlook 2010
Hi All
Exchange Server - 2013 CU2 (Windows 2012 Standard)
AD Server - 2003 R2 SP2
exchange-svr01.domain.com - internal name
mail.company.net - external name
When users opened Outlook 2010, they will encountered
"There is a problem with the proxy server's security certificate. The name on the security certificate is invalid or does not match the name of the target site exchange-svr01.domain.com.
Outlook is unable to connect to the proxy server.(Error Code 10)"
I also used the Microsoft Remote Connectivity Analyzer to test RPC/HTTP connectivity.
The RPC/HTTP test completed successfully.
Validating the certificate name.
Certificate name validation failed.
Host name company.net doesn't match any name found on the server certificate CN=AMAZONA-U59HG9G.
Testing SSL mutual authentication with the RPC proxy server.
The test passed with some warnings encountered.
The certificate common name company.net doesn't match the mutual authentication string provided mail.company.net; however, a match was found in the subject alternative name extension.
please help.Hi PS CL
[PS] C:\Windows\system32>Get-OutlookAnywhere
RunspaceId : c457e8aa-a0f3-4a0f-aa02-9eff24d02821
ServerName : exchange-svr01
SSLOffloading : True
ExternalHostname : mail.company.net
InternalHostname : exchange-svr01.domain.com
ExternalClientAuthenticationMethod : Negotiate
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
XropUrl :
ExternalClientsRequireSsl : True
InternalClientsRequireSsl : True
MetabasePath : IIS://exchange-svr01.domain.COM/W3SVC/1/ROOT/Rpc
Path : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
AdminDisplayVersion : Version 15.0 (Build 712.22)
Server : exchange-svr01
AdminDisplayName :
ExchangeVersion : 0.20 (15.0.0.0)
Name : Rpc (Default Web Site)
DistinguishedName : CN=Rpc (Default Web
Site),CN=HTTP,CN=Protocols,CN=exchange-svr01,CN=Servers,CN=Exchange
Administrative
Group (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=domain,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=domain,DC=COM
Identity : exchange-svr01\Rpc (Default Web Site)
Guid : 33c3cb74-e490-487d-844c-4072334089a1
ObjectCategory : domain.COM/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged : 8/17/2013 10:14:55 AM
WhenCreated : 6/25/2013 1:47:50 PM
WhenChangedUTC : 8/17/2013 2:14:55 AM
WhenCreatedUTC : 6/25/2013 5:47:50 AM
OrganizationId :
OriginatingServer : ADserver.domain.COM
IsValid : True
ObjectState : Changed -
Outlook client can't connect in but OWA works
You need to make sure your OutlookAnywhere and AutoDiscover settings are setup properly along with Split-DNS. OutlookAnywhere and Split-DNS are vital for future-proofing your Exchange configuration and making it work properly now, regardless if you use Exchange 2007, 2010, or 2013. For Exchange 2013, OutlookAnywhere is a requirement and Split-DNS is Best Practice. If you are on Exchange 2007 or 2010, and you do not have OutlookAnywhere enabled, enable OutlookAnywhere and follow this guide.You should always use NTLM over Basic authentication, as Basic sends the username and password in the clear, and NTLM is Windows Authentication. On Exchange 2013, you also have a new option called Negotiate, which is recommended. As you follow this guide, you will set the ClientAuthenticationMethod (Internal and External if on Exchange 2013) to NTLM...
Outlook client can't connect in configured outlook on workstation but OWA works.
This topic first appeared in the Spiceworks Community -
Using Outlook (2010 & 2013) to connect to Exchange using EWS
First things first.
I know that Outlook on the PC platform uses MAPI to connect to Excahnge while the Mac flavor of Outlook uses EWS, however, i was cycling through some available EX and ExO PowerShell cmdlets and found a parameter for set-casmailbox named EWSAllowOutlook Which
leads me to believe that configuring this setting should allow Outlook to use EWS to connect to Exchange. (This is a separate parameter from EWSAllowMacOutlook).
I tried a manual configuration (entering in the EWS url and setting the correct Outlook Anywhere settings) with no success.
I also tried manual configuration of an outlook.com and activesync account and entering the EWS URL as well with no success.
Has anyone successfully configured Outlook for PC to connect to Exchange using EWS and how did you configure the client?
ThanksHi,
Sorry for the late reply.
About the EWSAllowOutlook parameter, I have something to clarify.
This parameter allow or disallow Outlook 2007 to access EWS for the user.
Outlook uses EWS for free/buzy, OOF settings, and calendar sharing.
Outlook connect to Exchange server by using MAPI is a by design behavior.
We cannot change this.
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support -
Outlook is unable to connect to the proxy server.(Error Code 10)
Hi,
I had problems with RPC proxy, I was trying to setup cutover migration.
So I read somewhere that i need to change the certprincipalname with Set-Outlookprovider.
But after this change my outlook was not working anymore
The settings before the change were:
Name Server CertPrincipalName TTL
EXCH
1
EXPR
1
WEB
1
So I set this back to the original (above) but this didn't helped...
Outlook 2013 and Exchange 2013
There is a problem with the proxy server's security certificate. The name on the security certificate is invalid or does not match the name of the target site mail.abc-company.com.
Outlook is unable to connect to the proxy server.(Error Code 10)Hi,
Please make sure the mail.abc-company.com is included in your Exchange certificate which has been assigned with IIS service.
If possible, please run the following command for double check:
Get-ExchangeCertificate | FL
For Autodiscover service, please run
Test E-mail AutoConfiguration to check if the connection is successful in Log tab and confirm the other services URL can use proper namespace in Results tab for request access.
If the Autodiscover service fails, please create a SRV record with mail.abc-company.com for Autodiscover service to have a try:
http://support2.microsoft.com/kb/940881/en-us
Regards,
Winnie Liang
TechNet Community Support -
OUtlook 2013 can not connect to exchange 2013 after exchange maibox member of DAG failed.
hi ALL
OUtlook 2013 can not connect to exchange 2013 after exchange maibox member of DAG failed.
Exchange environment contains 2 Exchange Mailboxesserver ,( one Failed , virtual Machine)
2 cas Servers
first databases could not be mounted but after we run the below command , users can use OWA but outlook could not connect
Start-DatabaseAvailabilityGroup -Identity DAG -MailboxServer MBX1
please support
thanksHi,
According to your description, I understand that Outlook client cannot connect to Exchange server 2013 while one member of DAG failed.
If I have misunderstand your concern, please do not hesitate to let me know.
I want to double confirm whether all account store in MBX1 experience this issue, users in MBX2 works fine.
Please run following command to double check the database status:
Get-MailboxDatabase –Status | select Name,Mounted,MountedOnServer
If it works in OWA, the issue may be related to Outlook side. Please run “Test E-mail AutoConfiguration” and “Outlook Connection Status” to get more details, expecial the setting of proxy server, it’s more helpful
for further troubleshooting.
Additional, please try to recreate a profile for testing. Besides, please move active DB back to MBX1.
Best Regards,
Allen Wang -
Outlook clients trying to connect
Current Exchange Server: 8.3.389.2 - 2007 SP3 update roll-up 15
We are seeing an issue with Outlook clients trying to connect anywhere from 1 minute to 20 minutes plus. We have Outlook 2010 and Outlook 2013 in the environment. All clients are up to date with the latest Microsoft Updates.
The issue will happen to multiple users and the same users have no issues connecting to web-mail or email on the phone. Its just the outlook client.
Outlook will just hang and sometimes haven't updated for hours or the previous day.
Office 2010 and Office 2013 are both updated.
I've tried disabling our Anti-Virus, turning the policy off and the issue is still present.
Email will update on phones and web-mail.
We've tried rebuilding profiles, repairing Office and nothing seems to fix the issue.
Any help or suggestions would be appreciated.Hi,
According to your description, I understand that Outlook client sometimes hang or can't auto sync mailbox, however ActiveSync and OWA works fine.
If I misunderstand you concern, please do not hesitate to let know.
I want to double confirm whether all Outlook client experience this question at same time or not, how about restart Outlook client while problem arise.
If so, please open Event log to collect relevant warning or error message for further troubleshooting. Meanwhile, please run ExBPA to test Exchange server.
On the contrary, this may be related to client side. Please try to run Outlook with safe mode to prevent virus and add-ins, or enable Cache mode.
Besides, uncheck “Download Shared Folder” for testing.
Best Regards,
Allen Wang -
We are receiving following error, while trying to deploy the application on Win Phone emulator. “Windows Phone Emulator is unable to connect to the Windows Phone operating system: The phone did not respond to the connect
request. Some functionality might be disabled.”
I have tried all possible ways that we found on blogs. We are still not able to solve this issueI have had a lot of issues with the emulator in the past.
Check out this troubleshooting guide. It might help:
https://msdn.microsoft.com/en-us/library/windows/apps/jj681694(v=vs.105).aspx
Also, I find that if I cancel my build/deploy while it is stuck on booting the OS and then wait a short while the phone OS will complete booting, and from that point I can deploy to the emulator. It's a workaround, but it works well for me.
I need to do that on Windows 10 tech preview, which may or may not be simply an incompatibility with the beta OS.
I'm a self-taught noob amateur. Please take this into account when responding to my posts or when taking advice from me.
Maybe you are looking for
-
Notice that says ' the server responded with an error'
I Cannot get rid of the message, and cannot shut down I have to force shut down.
-
Purchased itunes store films disappearing from library and store.
I purchased 'Home Alone' last Xmas and now it has gone from my itunes library and no longer available to download in the UK store, does anyone know why?
-
Hi All I am working on 12.2.3 build 165. I am trying to call web service dynamically providing url at the run time.. I tried using wizard way- giving url, then selecting operation and it works fine. But is it possible to give url as input at run time
-
hi, i have this xml <operacionDummy xmlns="http://sample.services.dummy/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <arg0 xmlns=""> <fechaOperacion>2010-04-29T16:17:34.687000-04:00</fechaOpera
-
Is there a way to lock up Mail so that anyone who launches it can't read my emails?
I tried going into Accounts and then deleting the password there but old emails are still visible. I tried using System Preferences to uncheck my Mail account but anyone who knows Macs can just go back in there and recheck it. Is there a "lock" type