Problem connecting outlook 2013 to exchange server

Hello,
I recently bought a new windows laptop for emailing (our company is otherwise only using Mac).
Setting up Outlook with the intended email address failed, and at this point, when clicking Outlook, I get the following message:
"The connection to Microsoft Exchange is unavailable. Outlook must be be online or connected to complete this action."
The only option is to click "ok".
The following window is then opened:
"Microsoft Exchange"
It has only one tab, containing:
"Microsoft Exchange server" window, in which I've entered the server address.
"Mailbox" window, in which I've entered the email address. There is a button called "Check Name".
If clicked, the following message shows up:
"The name can not be resolved. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
By clicking "ok" anyway, the following message appears:
"Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The file C:\xxxxxxxxxxx.ost is not an Outlook datafile (.ost)."
The problem seems to be that there is nothing I can do to change these messages. I have access to the correct server name, address etc.
What to do?
Thank you for your help!

Hi Scout,
Thank you for your question.
As Ronomatic said, we could clear the present profile and re-build profile by the following link:
http://support2.microsoft.com/kb/829918/en-us
The problem seems to be that there is nothing I can do to change these messages. I have access to the correct server name, address etc.
Notice: We will make sue the client could resolve the FQDN of Exchange server by
Ping or Nslookup；
Waiting your reply.
Best Regard,
Jim

Similar Messages

Problems using Outlook 2013 with Exchange Server Small Business Server 2003

Hello,
We have just upgraded our Office suite from Office 2007 Pro to Office 2013 Pro. When I try to configure Outlook 2013 to connect to Exchange Server 6.5 (SMS 2003) I get an error "Outlook 2013 being blocked by current version of Exchange Server".
Outlook 2013 at present is not communicating with Exchange server 6.5
Are there any fixes I have to install on our SMS 2003 server to allow Outlook 2013 to work with SMS 2003 Exchange Server?
Any configuration changes I need to make? Any help is appreciated.
Thx
John G.
John Grace

Hi
Outlook 2013 is not supported with exchange 2003:
http://technet.microsoft.com/en-us/library/ee624351.aspx#section10
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Strange Exchange name when connecting with Outlook 2013 to Exchange server 2013 SP1

I've setup a test environment with Windows Server standard 2012 R2 and Exchange Server 2013 SP1...
In- and outbound SMTP works fine, as well as connecting with OWA and Mac Outlook client...
Oddly though when setting up an Outlook 2013 connection....it recognizes the email address correctly, but later on can't connect and shows a dialog to enter the server and email account manually....though the profiled fields show something like:
Exchange Server: [email protected]
Mailbox: =SMTP:[email protected]
When I fill in the right fields....it won't connect and falls back to the values above...
Something wrong in the Exchange setup?

Hmm...found aguide here:
http://enterpriseit.co/microsoft-exchange/2013/ssl-certificate-request/
Though it doesn't mention anything that with the self-signed certs it won't allow Outlook 2013 to connect...
So from my point of view Outlook 2013 should be able to connect anyway...as during the connect process you can install the self-signed cert.....so must be something else then...

Outlook 2013, intermittent "exchange server not avaliable"

I have a virtualised environment.
----The setup:-----
two vHosts, vmware 5.5, 4 CPU, 196 GB RAM, Storewize v3700, 20 10K disks in RAID10
two win 2012 exchange 2013 servers
two win2012 DCs
five (5) Win2008R2 RDS hosts + 1 2008R2 Connection broker
60 users on the RDS server in outlook online-mode. no cache
Office 2013 on the servers
-----the problem:---
Some random users have random problems opening outlook.
A user tries to open outlook and gets the message "exchange server not avaliable".. he says OK, and outlook closes. - opens outlook again, and everything works..
This happens at random times for random users
CPU, disk and network activity are very low on both vhosts and there is a lot of avaliable RAM on all guests
I don't know if its related, but the larger the mailbox is, the longer it takes to open outlook.. some times up to 6-10 seconds.. At idle times, outlook opens in less than a second..
Any ideas?

Hi,
According to your description, the issue randomly happens on random users and all users use online mode. Thus, I recommend you use performance monitor to double check if the issue is caused by performance and we can also check if there is any 9646 error
code in the event log.
http://technet.microsoft.com/en-us/library/dd335215(v=exchg.141).aspx
We can use performance monitor to check the change of the counters: RPC request, RPC average latency and RPC operation/sec
Referring to others’ suggestions, the issue may be caused by E1000 vNICs. Maybe we can temporarily try to update to E1000e. Alternatively, you can ask for help from the VMAS support.
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support
Thanks for your reply Angela.
The vNICs are already E1000e. The next step for me is to try upgrading them to VMXNET3. There are no errors in the event log related to this. I have not yet gone the perfmon-way, because I figured that when disk activity and CPU / RAM consumption is
so low, it wouldn't be an issue.
I was connected to the system yesterday evening where I experienced this error. There were a total of 8 users connected to the system, having only the ERP system running. I was the only user on that particular RDS host, and vmware performance metrics say
the servers are under very low load-level..

Outlook 2013 with Exchange Server - Changed custom form for contacts is not shown

Hello,
Our infrastructure:
Exchange Server 2010
Outlook 2010
Outlook 2013
Windows 7 Pro, Windows 8 Pro and Windows 8.1 Pro
The situation:
We've used an old custom form for contacts, worked perfectly fine
I've updated the form (adding some new custom fields and checkboxes) using Outlook 2013 and publishing the form (with a new name) to the Exchange folder
I've set the form as default form in our contacts folder
I've used this Script to set the new form for the existing contacts and the name of the new form is saved correctly
BUT if I open a contact in our Exchange contacts folder, Outlook 2013 (Outlook 2010) still shows the old form
Steps I've taken so far:
Cleared Outlook forms cache
Repeated the above steps 1-4 in Outlook 2010
Switched Cached Exchange Mode off and back on
Allowed Scripts in Trust Center Settings
Used a new clean Windows installation with a new Outlook 2013 installation
Used different Exchange users on different systems, but some behavior when opening contacts
I'm out of options I can think of, so maybe somebody else has some new view on this problem.
Thank you very much in advance!
Greetings,
Karl

Hi,
Is the Exchange folder in which the custom form is published available to all users?
From the description, the script used to work for the old custom form, correct? Which version of Outlook did you use with the old custom contact form? Outlook 2010/Outlook 2013 or an earlier version? If you used the script with an earlier version of Outlook,
we can't make sure it will still work with Outlook 2010/Outlook 2013.
In addition we may also try creating a new contact form and test the steps to see if it will work.
Please let me know the result.
Regards,
Steve Fan
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Cannot Connect Outlook 2013 to Exchange 2013

I have an exchange 2013 server running on a Windows Server 2012 R2 box that is also a domain controller and performs DNS. I have installed an SSL certificate for mail.domainname.com installed and listed as valid in ECP. When I try to connect
a local computer running Outlook 2013 on Windows 7 I get asked for login and password which it won't accept. I have tried my user and my administrator credentials, either work.
It then says that "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
I can connect via OWA and don't get any certificate errors. My internal host name and external host name are both mail.domainname.com according to the Get-OutlookAnywhere | ft internalhostname,externalhostname.
Any help is greatly appreciated.
Robert

I probably should have stated from the beginning that I am not an IT professional. I am an architect. Not a network architect, but an "I design buildings" architect. I am simply the most knowlegable member of the firm when it comes to IT.
I have been administering our SBS server for the last 14 years. We just purchased a new server to replace our tired old beast and I have been working to get it read to roll out to the office. I have everything set except Outlook. We are a
very small firm, only three people, so if manual configurations are needed I can do that.
I don't understand what I am reading in the Configure Outlook Anywhere article. It looks like it is about using Outlook from a remote location without a VPN. I am trying to get configured to use Outlook internally. Not sure if they both
work the same way.
Thank you,
Robert

Problem appearing olders emails outlook 2013 with Exchange 2007 SP2

hi everyone,
recently i have problem with user mailbox OST more than 20 Gb (configured with outlook 2013 and exchange 2007 SP2 ) and if i scroll down in the olders mails in the Inbox Folder it's stoped in 2011 but i have more than this year ! i tried to add regedit keys
such as Maxlargesize... and no changes and tried also with exporting this ost to PST File (i proceed with computer 32 bits ....) and always stop in 2011
Please if you have ideas to resolve this
best regards
vote if you think useful

Hi,
OST file is a local copy of your email messages, calendar, and other items that are on the Exchange server, it is always synchronized with the items on the server. So, the first thing we need to check is to login to OWA and check if you can see older
emails from there.
If you can't see the old email from OWA, it means the emails are removed from the server. In this case, you'll need to contact your Exchange admin to see if your old emails are archived. We can also check if you have enabled AutoArchive feature in your Outlook,
which may move your emails from your OST file to a local PST file. See:
https://support.microsoft.com/kb/830119?wa=wsignin1.0
If you can see the old emails from OWA, your OST file may be corrupt. We can exit Outlook, find the .OST file and rename it to .old, and then restart Outlook to let it sync a new one. By default, the OST file are save in:
drive:\Users\%username%\AppData\Local\Microsoft\Outlook
Please let me know the result.
Regards,
Steve Fan
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

DLL Shell problems connecting outlook to exchange

dear all,
Poster this in the community forums and was directed to the exchange 'zone'.
Hope somebody can help!
regards
Dominique
DLL problem with Windows 8.1 on surface pro 3 and Outlook 2013 and exchange account
Dear all,
Just got my new surface pro 3 in.
Happy....
but, after a full day in getting stuff from the old laptop to work on the surface, the 1 thing i expected to Be a breeze proves very difficult!
I have (Yep, spent some extra euro's) a brand new instal of office 2013 Dutch Language.
Outlook.
Installed My mail account (imap). Easy.
then My work email. Exchange.
Problem starts.
I get a 'dll Shell' error.
Trier:
-complete renstal of office
-scan trom the c:/ prompt for corrupt system files
My feeling (it is a brand new machine right out of the box!!): it It NOT a 'corrupt' thing, but something wit authentications or rights or so.
My collegae has bought the same machine and has the same problems!
Mail Works fine over the 'mail' app. but NOT in Outlook.
And since this is My work machine, i need outlook to function!!
Any ideas?
tnx in Advance!
Regards
Dominique

Hi Dominique,
From your description, "Mail Works fine over the 'mail' app, but NOT in Outlook.", the issue should be related to Outlook side. Actually, we have a dedicated support team regarding the Microsoft Office. I recommend you ask your question on our Microsoft
Office forum which is staffed by more experts specializing in this kind of problems. Thanks for your understanding.
For your convenience:
https://social.technet.microsoft.com/Forums/office/en-US/home?forum=outlook
Hope this can be helpful to you.
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Amy Wang
TechNet Community Support

Outlook 2013 with Exchange 2007 - out of office problem

We are using outlook 2013 with Exchange 2007. When users select their out of office it will work fine for the first day, however there after the Out of Office replies stop working. Out of Office is set correctly within Outlook, but what we have found
is that if the user opens Outlook the Out of Office starts to work again. Also when the user opens Outlook it takes around two minutes before it registers that Out of Office is on.
Any Ideas?

Hi,
How do you configure your OOF? From standard OOF wizard or define an automatic reply template from Rule wizard?
If you are using a template, Outlook must be running for the Rules Wizard to automatically reply. Please refer to the Note in the following KB:
http://support.microsoft.com/kb/311107
If it is configured by using standard Out of Office assistance in File > Automatic Replies, please remove OOF settings in Outlook and set it from OWA 2007, then check whether the issue can be reproduced.
Regards,
Winnie Liang
TechNet Community Support

Connecting Outlook 2013 for a local user

We’re having trouble connecting a users connecting a domain user’s Outlook 2013 to our Exchange 2013 server. The user has a domain user account, and an Exchange mailbox.
However;
The user in question uses a PC that is physically connected to the network, but isn’t a domain-joined machine. The user is using a locally-provisioned account on the PC.
The machine can query internal DNS servers, and has network connectivity through to the Exchange server.
The user can successfully log in to OWA, where everything functions as normal. The user wishes to use Outlook 2013 for archiving of PST files.
We are having issues creating a mail profile for the user, whether manually configuring or utilising autodiscover.
With autodiscover, the user enters her name, email address and password in the initial wizard in Outlook 2013. 2 of the 3 steps succeed, before ‘The action cannot be completed. The name cannot be matched to a name in the address list’ error window is displayed.
Is this because Exchange is having issues with the account being used to create the profile (the local user account on the PC)?
Now what’s really odd, is that when using Outlook 2013 away from the network (at home), with any PC, the autodiscover method succeeds. What is causing it to fail internally?
So, with the autodiscover method out of the window, we turned to manually configuring the profile.
The local name of the Exchange server is entered for the server name, with the user’s email address for the username.
In ‘More Settings’, the connection tab is configured to ‘Connect to Microsoft Exchange using HTTP’.
The URL used to connect the proxy server for Exchange, is the external name used for OWA. This is the same address used when the user is using OWA internally/externally, which works without issue.
Options ‘Connect using SSL only’, along with ‘Only connect to proxy servers that have this principal name in their certificate’ are selected with
msstd:<external FQDN name> being entered.
Basic Authentication is selected for the proxy authentication settings section.
The user is then prompted for credentials. The following formats have been attempted;
Domain.local\username
Email Address
[email protected]
The correct password is used, but nothing is accepted.
How can we get Outlook 2013 configured for this non-domain joined PC?
Many thanks.

We’re having trouble connecting a users connecting a domain user’s Outlook 2013 to our Exchange 2013 server. The user has a domain user account, and an Exchange mailbox.
However;
The user in question uses a PC that is physically connected to the network, but isn’t a domain-joined machine. The user is using a locally-provisioned account on the PC.
The machine can query internal DNS servers, and has network connectivity through to the Exchange server.
The user can successfully log in to OWA, where everything functions as normal. The user wishes to use Outlook 2013 for archiving of PST files.
We are having issues creating a mail profile for the user, whether manually configuring or utilising autodiscover.
With autodiscover, the user enters her name, email address and password in the initial wizard in Outlook 2013. 2 of the 3 steps succeed, before ‘The action cannot be completed. The name cannot be matched to a name in the address list’ error window is displayed.
Is this because Exchange is having issues with the account being used to create the profile (the local user account on the PC)?
Now what’s really odd, is that when using Outlook 2013 away from the network (at home), with any PC, the autodiscover method succeeds. What is causing it to fail internally?
So, with the autodiscover method out of the window, we turned to manually configuring the profile.
The local name of the Exchange server is entered for the server name, with the user’s email address for the username.
In ‘More Settings’, the connection tab is configured to ‘Connect to Microsoft Exchange using HTTP’.
The URL used to connect the proxy server for Exchange, is the external name used for OWA. This is the same address used when the user is using OWA internally/externally, which works without issue.
Options ‘Connect using SSL only’, along with ‘Only connect to proxy servers that have this principal name in their certificate’ are selected with
msstd:<external FQDN name> being entered.
Basic Authentication is selected for the proxy authentication settings section.
The user is then prompted for credentials. The following formats have been attempted;
Domain.local\username
Email Address
[email protected]
The correct password is used, but nothing is accepted.
How can we get Outlook 2013 configured for this non-domain joined PC?
Many thanks.
The first problem is, if this Exchange 2013 then the server name in Outlook isn't really a server name, it is in actuality the ExchangeGUID of the mailbox.
Since you are trying to access the mailbox from a machine that is not on the domain you will need to make sure the externalURLs resolve properly internally. Meaning either the user can access them by going out to the internet and getting routed back
in (not ideal) or you configure them to resolve to the internal IPs on your internal DNS servers.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread
Thank you for your reply.
As I mentioned, this machine can query internal DNS servers without issue. Autodiscover is working in a fashion, as the name of the mail server is hashed.
In an update to the post, I have exported a working profile from the registry of the machine for a domain user, and have imported for a local user. This actually works, but I'd still like to know the reason for not being able to configure it in the first
instance.

Outlook no resolving Exchange Server name , resolving another name like SID Object

Hello All ,
I Have Exchange 2013 installed on windows server 2012 , Outlook no resolving Exchange Server name , resolving another name like SID Object . Please see the attached file below .
how can fix the issue ?
Thank you

Hi,
Please run following command to verify whether the Outlook resolved the correct Exchange Server GUID:
Get-Mailbox MailboxName | FL name, ExchangeGUID
Following Screenshot is the test result in my lab, for your reference:
If we get the correct GUID, it means we have already connected to Exchange Server successfully.
The GUID format for the server name in Exchange 2013 is an expected behavior.
Found a similar thread for your reference:
Outlook is not resolving CAS server Name
http://social.technet.microsoft.com/Forums/exchange/en-US/5868d45a-ee93-4c55-927b-4dd2b9eaeec5/outlook-is-not-resolving-cas-server-name?forum=exchange2010
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Outlook 2013 with Exchange 2013 keeps giving read receipts

Hello experts,
We have an Exchange 2013 server. All users are joint to the domain, except one user (Windows 8.1) which is in a Workgroup, and using Outlook 2013 with IMAP protocol.
This particular user is having a problem. When he send's any email from Outlook and requests a read receipt, after that he keeps getting hundreds of read receipts in his inbox. I have tried disabling (for temporarily) the Windows server 2012 firewall, but
still having the same issue.
Is this a known bug in Outlook 2013 with Exchange 2013? Any help troubleshooting this?

Hi,
According to your description, I understand that IMPA account get hundreds of read receipts while he requests a read receipt.
If I misunderstand you concern, please do not hesitate to let me know.
Whether are all account or some special user experience this question? Please do a test in external with IMAP account to double confirm.
How about the “Request a Delivery Receipt”?
Also, please run message tracking log to get more details about message mail flow:
Get-MessageTrackingLog –Server “mailbox server” –Sender “[email protected]” –Recipient “[email protected]” –MessageSubject “Read: message subject” | Select Timestamp, ClientHostname,ServerHostname,Source,EventID,Recipients,RecipientStatus,Sender | ConvertTo-Html > “C:\Test\Test.xml”
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

TS4532 My iPhone V will not connect to a Microsoft Exchange server. It says that the User Name or Password are incorrect even though they're not and I can log on directly to Exchange using the web browser. The connection worked until IOS 6.1.2 was Install

My iPhone V will not connect to a Microsoft Exchange server. It says that the User Name or Password are incorrect even though they're not and I can log on directly to Exchange with the same parameters using the web browser.
I bought the phone when it came out last October. The connection did not work at first, then started without warning in December. It worked perfectly for 2 months then stopped again when IOS 6.1.2 was Installed.
Help please!

I have forwarded these questions about the version of Exchange server that is being used and whether Microsoft host the mai themselves to the IT Dept but I will not get a reply from them until tomorrow.
In the meantime I have also tried:
Deleting and re-creating the account AGAIN!
And re-setting the phone (recommended as a solution to a similar problem with an iPad in another forum.
But please remember that:
The phone would not connect for 2 months after I bought it
Then started working unexpectedly in December
Then stopped working again when IOS 6.1.2. was installed
Also why am I the only person affected by this when colleagues with iPhone 3s and 4s who use the same mail system are not (I am still trying to find one with an iPhone V to see if their's works).
Like I said I think that there must be a fault, either with my own phone or with iPhone Vs in general.

Daily Problems with Mail Synchronizing with Exchange Server

Our office uses Comcast Business Class Service, which uses 2007 Exchange Servers, for internet access and email. I upgraded my MacPro from 10.5.8 to Snow Leopard 10.6.2, using the Upgrade DVD. The upgrade process kept my original Leopard Mail settings, which were using POP. At that time, I had not problems with email.
Unfortunately, awhile ago my Mail Preferences became corrupt, and I had to delete them. Upon relaunching Mail, the application wanted to use the new Autosync method to connect to the Comcast Exchange Server. Using POP was not an option.
I must say that I am less than impressed with the way Mail integrates with Exchange Servers. I have daily problems, and experience these problems multiple times per day. When they happen, they slow my email communication down to a crawl; sometimes for as much as an hour.
Specifically, the problem appears to be with Mail's ability (or inability) to properly synchronize with Exchange Servers. I get he spinning pizza icons next to the two Exchange email accounts I have in my Mailboxes source column. Opening the Activity window shows that the synchronizing process has slowed everything down. This results in not being able to send or receive email until the synchronizing is complete. And as I said, that can sometimes take as long as an hour.
Stopping the process in the Activity window does not resolve the issue. Nor does quitting and relaunching Mail. Because the next time Mail attempts to connect to the Exchange Server, it will try to synchronize yet again. The problem has become so chronic, that I often have to resort to using Webmail while waiting of the synchronizing process to complete.
Incidentally, the mailboxes that are synchronizing are empty! I am meticulous about keeping my Inbox, Sent, Drafts, and Trash mailboxes empty at all times. I do not use To-Do's, Notes, or Calendars of any kind on the Exchange Server, so there is no data to even sync!
Has anyone else experienced this problem and found a fix? Other email accounts I have, which use POP or IMAP, do not have this issue. There does not appear to be away to abandon the Autosync Mail setup and revert back to POP. If there is, I will do it in a heartbeat.
Thanks.

Found a solution that works for me. Delete the problem account that's using AutoDiscover to sync with the exchange server. Before doing that, however, you will want to clear out the Inbox, Sent and even Trash folder for that account, as deleting it will remove the messages that currently reside in those folders. Just simply move them to another folder. You can move them back after re-creating the account.
The second step is to re-create the account. Do this as you would normally, and enter in your name, username and password. THE TRICK: Press and hold the Option key when you click Continue. After Mail connects to the server and verifies your account information, you will then have a pull down menu that will allow you to choose Exchange Server, IMAP and POP. Simply select POP or IMAP, then fill out the rest of the fields.
Viola! No more problematic Exchange Server syncing issues.

Connect to files on exchange server

How can i connect to files on Exchange Server 2010. I have established a VPN connection but i cannot see any of the files on the server?

See under "Access Network Drives from a Mac" on this page:
Use your Macbook on the Corporate Windows-only Network

Problem connecting outlook 2013 to exchange server

Similar Messages

Maybe you are looking for