My Windows Server 2012 is a DC with Exchange Server 2013 installed.   I also have an Exchange 2010 server on a Windows Server 2008 R2 box.   For several months, while my mailbox was on the Exchange 2010 server, I had no trouble connecting to my mailbox with the Outlook 2013 client installed on Windows Server 2012.

Today I moved my mailbox to the Exchange 2013 installed on Windows Server 2013.  For some reason, Outlook 2013 is unable to open my mailbox on the localhost.   I keep receiving the following error message: Cannot start Microsoft Outlook.  Cannot open the Outlook window.  The set of folders cannot be opened.  You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook file (.ost).

OWA works fine; all Exchange services are running.  Outlook 2013 has no issues connecting to the Exchange 2013 server from any other PC.   I tried removing and re-installing Office 2013 but it did not help.  Any idea on how to fix this?  Thanks.

My Windows Server 2012 is a DC with Exchange Server 2013 installed.   I also have an Exchange 2010 server on a Windows Server 2008 R2 box.   For several months, while my mailbox was on the Exchange 2010 server, I had no trouble connecting to my mailbox with the Outlook 2013 client installed on Windows Server 2012.

Today I moved my mailbox to the Exchange 2013 installed on Windows Server 2013.  For some reason, Outlook 2013 is unable to open my mailbox on the localhost.   I keep receiving the following error message: Cannot start Microsoft Outlook.  Cannot open the Outlook window.  The set of folders cannot be opened.  You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook file (.ost).

OWA works fine; all Exchange services are running.  Outlook 2013 has no issues connecting to the Exchange 2013 server from any other PC.   I tried removing and re-installing Office 2013 but it did not help.  Any idea on how to fix this?  Thanks.

If I understood you correctly, you are running Outlook on the same machine as the Exchange Server?

Yes, I am running Outlook on the same machine as the Exchange Server.

Exchange Server 2013 does not support direct MAPI/RPC connections from Outlook clients anymore. This means that each Outlook client connection is now Outlook Anywhere connection (which means encapsulated in HTTPS). Check your connection profile settings in the Outlook, maybe your client is still trying to use direct MAPI/RPC

Thanks, I know that Exchange 2013 does not support direct MAPI/RPC connections.   I have tried manually creating the Exchange profile forcing Outlook to use HTTPS but it still does not work.

OK...I think I found the problem but I don't know how to fix it.  I downloaded the Microsoft Connectivity Analyzer tool and ran it on several machines.   It had no issues except on the Windows Server 2012 that has Exchange 2013 installed.  It is complaining that autodiscover is not working when it runs on this server.  Here is the text:

OutlookAnywhereConnectitivyFailed

We were not able to successfully connect to your email server via the Outlook Anywhere feature.

MCA Client tool is attempting to test Autodiscover for <user>.

Testing Autodiscover failed.

Test Results

Attempting each method of contacting the Autodiscover service.

The Autodiscover service couldn't be contacted successfully by any method.

Test Results

Attempting to test potential Autodiscover URL https://server/AutoDiscover/AutoDiscover.xml

Testing of this potential Autodiscover URL failed.

Test Results

Attempting to test potential Autodiscover URL https://autodiscover.server.com/AutoDiscover/AutoDiscover.xml

Testing of this potential Autodiscover URL failed.

Test Results

Attempting to contact the Autodiscover service using the HTTP redirect method.

The attempt to contact Autodiscover using the HTTP Redirect method failed.

Test Results

Attempting to contact the Autodiscover service using the DNS SRV redirect method.

MCA Client tool failed to contact the Autodiscover service using the DNS SRV redirect method.

Test Results

MCA Client tool is attempting to retrieve an XML Autodiscover response from URL https://server.com/Autodiscover/Autodiscover.xml for user et.com.

MCA Client tool failed to obtain an Autodiscover XML response.

From this, it seems like your Autodiscover can't be located. Do you have autodiscover host created in your DNS? Autodiscover should be accessible by using at least one method tested in Connectivity Analyzer.

Yes, you are correct.  I fixed the DNS issue by adding an "autodiscover' CNAME and that works.  However, connectivity is still now working (see Microsoft Connectivity Analyzer text below):

OutlookAnywhereConnectitivyFailed We were not able to successfully connect to your email server via the Outlook Anywhere feature. MCA Client tool is attempting to test Autodiscover for erintell@rintenet.com. Autodiscover was tested successfully. Test Results Testing RPC/HTTP connectivity. The RPC/HTTP test failed. Test Results MCA Client tool is attempting to test Autodiscover for erintell@rintenet.com. Autodiscover was tested successfully. Test Results Attempting each method of contacting the Autodiscover service. The Autodiscover service was tested successfully. Test Results Autodiscover settings for Outlook Anywhere are being validated. MCA Client tool validated the Outlook Anywhere Autodiscover settings. Attempting to resolve the host name rintesvr.rintenet.com in DNS. The host name resolved successfully. Additional Details Testing TCP port 443 on host rintesvr.rintenet.com to ensure it's listening and open. The port was opened successfully. Testing the SSL certificate to make sure it's valid. The certificate passed all validation requirements. Test Results Checking the IIS configuration for client certificate authentication. The test passed with some warnings encountered. Please expand the additional details. Additional Details Additional Details: Client certificate authentication couldn't be determined because an unexpected failure occurred. WinHttpSendRequest failed with error 12030. Testing HTTP Authentication Methods for URL https://rintesvr.rintenet.com/rpc/rpcproxy.dll?467e33c4-98ff-496d-b019-afdc65ce1d28@rintenet.com:6002. The HTTP authentication test failed. Additional Details Additional Details: Exception details: 
Message: The underlying connection was closed: An unexpected error occurred on a send. 
Type: System.Net.WebException 
Stack trace: 
at System.Net.HttpWebRequest.GetResponse() 
at Microsoft.Exchange.Tools.ExRca.Extensions.RcaHttpRequest.GetResponse() 
Exception details: 
Message: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. 
Type: System.IO.IOException 
Stack trace: 
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) 
at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count) 
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) 
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) 
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest) 
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) 
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) 
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) 
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) 
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result) 
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size) 
at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size) 
at System.Net.ConnectStream.WriteHeaders(Boolean async) 
Exception details: 
Message: An existing connection was forcibly closed by the remote host 
Type: System.Net.Sockets.SocketException 
Stack trace: 
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)  Testing HTTP Authentication Methods for URL https://rintesvr.rintenet.com/rpc/rpcproxy.dll?467e33c4-98ff-496d-b019-afdc65ce1d28@rintenet.com:6002. The HTTP authentication test failed. Additional Details Additional Details: Exception details: 
Message: The underlying connection was closed: An unexpected error occurred on a send. 
Type: System.Net.WebException 
Stack trace: 
at System.Net.HttpWebRequest.GetResponse() 
at Microsoft.Exchange.Tools.ExRca.Extensions.RcaHttpRequest.GetResponse() 
Exception details: 
Message: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. 
Type: System.IO.IOException 
Stack trace: 
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) 
at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count) 
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) 
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) 
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest) 
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) 
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) 
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) 
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) 
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result) 
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size) 
at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size) 
at System.Net.ConnectStream.WriteHeaders(Boolean async) 
Exception details: 
Message: An existing connection was forcibly closed by the remote host 
Type: System.Net.Sockets.SocketException 
Stack trace: 
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) 

Hi,

You also need to include the autodiscover.domain.com host name to the certficate.

Thanks,

If you have feedback for TechNet Subscriber Support, contact tnsfl@microsoft.com

Thanks guys, I've been struggling with this problem for a week!!!  The Connectivity Analyzer Tool pointed out the problem in 5 minutes and now it's resolved.