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

Similar Messages

Lync 2013. There was a problem connecting with the Exchange. Unable to load the magazine discussions.

Lync 2013. There was a problem connecting with the Exchange. Unable to load the magazine discussions.
Installed Lync Server Standart 2013, client PC MS Office 2013.
As the mail system - Lotus Notes Domino Server and Lotus Notes client, respectively.
Exchange is not installed at all.
question:
1 What is the message: "There was a problem connecting with Exchange. Unable to load the magazine discussions." and how it is fraught?
2 How can I fix this message? Cleaning the C: \ Users \% UserName% \ AppData \ Local \ Microsoft \ Office \ 15.0 \ Lync \ does not help
3 What are the disadvantages when using Lync Server Standart 2013 without Exchange? In principle, I put for Lync Exchange?
4 What are the advantages when using Lync Server Standart 2013 with Exchange?
5 Is it possible to work simultaneously Lync Server Standart 2013 + Exchange + Lotus Notes
Thank you.

1) That sounds like a strange translation. But basically, it wants to connect to Exchange and it's complaining.
2) You can attempt to go to Tools->Options->Personal and set Personal Information Manager to None, and in Lync Management Shell run set-csclientpolicy
http://technet.microsoft.com/en-us/library/gg398300.aspx with the following options:
DisableCalendarPresence $True
DisableEmailComparisonCheck $True
EnableExchangeContactSync $False
There may be more, I've never tried to completely disable Exchange features from Lync.
3) No conferencing plugin for meeting invites, no automatic presence management based upon your calendar, no searching your Outlook contacts for new contacts, no voicemail, no conversation history,no unified contact store, and more:
http://technet.microsoft.com/en-us/library/jj688098.aspx
4) This is just #3 in reverse :)
5) Depends on your goals, but the experience wouldn't be great. You'd want to keep your contacts and calendar in Exchange and your email in Notes. It would be confusing to your users.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

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

Problem connecting to MS Exchange 2007 on SBS 2008

I am having problems connecting to Exchange via cfexchangeconnection. Our ColdFusion environment is CF9 Enterprise on Win 2008, and the Exchange host is Win SBS 2008 (which uses IIS7).
After having worked through the documentation and following all procedures outlined at
http://help.adobe.com/en_US/ColdFusion/9.0/Developing/WSc3ff6d0ea77859461172e0811cbec14f31 -7fed.html
plus googling intensively, we have the following method to test the connection
<cfexchangeconnection action="open"
         connection="thisExchangeConnection"
         server="portal.mydomain.com"
         protocol="https"
         formBasedAuthentication="true"
         formBasedAuthenticationURL="https://portal.mydomain.com/owa/auth/owaauth.dll"
         mailboxname="myMailBox"
         username="myUsername"
         password="myPassword" />
<cfdump var="#thisExchangeConnection#">
<cfexchangeconnection action="close"
         connection="thisExchangeConnection" />
The IIS7 implementation in SBS 2008 is quite a lot different to Win 2008, so there are some question marks around some steps in the above documentation. However, we have made sure that:-
1) you can use the credentials above to login via a web browser
2) WebDav is on in IIS
3) there is no IWA and forms based authentication is on
4) certificates are installed correctly on both the CF and Exchange servers
5) the myUsernameaccount has correct permissions in iis/owa/exchange
Despite this, the net result is always
Access to the Exchange server denied.
Ensure that the user name and password are correct.
From research it seems that a lot of people have issues where the underlying problem is actually an Exchange 440 timeout error where the password in the IUSR_<servername> and IWAM_<servername> (IIS/Active Directory) is out of sync.
I was pinning my hopes on the above being the problem but now I find that in SBS 2008 there is no IWAM_<servername> server account.
All this leads me to ask is SBS 2008 actually compatible with the cfexchange tags in CF9? There is nothing in the documentation that I can find that syays that it isn't, but given the amount of time we've spent on what should be straightforward I am wondering if we are on a hiding to nothing. Anyone from Adobe care to comment?
If anyone has managed to get this to work specifically with SBS 2008, or has any advice I'd be grateful to here from you.

Hi,
As said by Sneff , I would also recommend to enable Logging to get more detailed information. Also follow
Configuration of POP/IMAP on SBS 2008 Refer to :
http://blogs.technet.com/b/sbs/archive/2008/09/19/how-to-configure-sbs-2008-to-host-pop3-imap4.aspx
http://blogs.technet.com/b/sbs/archive/2011/08/31/how-to-configure-outlook-for-pop3-imap-and-smtp-connectivity-in-sbs-2008-2011-standard.aspx
As per the error code, you need to follow
http://support.microsoft.com/kb/813514/EN-US
I would also disable AV on both Client machine and TEST , including the Filters of AV.
Binu Kumar - MCP, MCITP, MCTS , MBA - IT , Director Aarbin Technology Pvt Ltd - Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Problem connecting to godaddy exchange server via outlook client

I am pretty much having a very similar problem here:
https://social.technet.microsoft.com/Forums/exchange/en-US/437c5f8d-3a42-4689-90b4-13fd2749373f/go-daddy-ucc-certificate-exrca-can-only-validate-the-certificate-chain-using-the-root-certificate?forum=exchangesvr3rdpartyappslegacy
When I set up in outlook, I have noticed this in advanced connection settings:
the URL is required
mail.ex4.secureserver.net
Then check connect SSL only
Only connect to proxy servers with this principal name
msstd:mail.ex4.secureserver.net
When I use the connect principal, it works fine, but otherwise if it is not checked, it won't connect to the server.
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26423254.html
However, when I restart outlook, because I have multiple exchange accounts, they keep becoming "unchecked".
Everything worked fine about 48 hours ago, and now... all these problems.
Here is my log from the testing site:
Connectivity Test Failed
Test Details
   Testing Outlook connectivity.
    The Outlook connectivity test failed.
   Additional Details
Elapsed Time: 3897 ms.
   Test Steps
   Testing RPC over HTTP connectivity to server mail.ex4.secureserver.net
    RPC over HTTP connectivity failed.
   Additional Details
HTTP Response Headers:
Content-Type: text/html
Server: Microsoft-IIS/7.5
WWW-Authenticate: Negotiate,NTLM
X-Powered-By: ASP.NET
Date: Fri, 13 Feb 2015 01:07:27 GMT
Content-Length: 58
Elapsed Time: 3897 ms.
   Test Steps
   Attempting to resolve the host name mail.ex4.secureserver.net in DNS.
    The host name resolved successfully.
   Additional Details
IP addresses returned: 72.167.83.115
Elapsed Time: 95 ms.
   Testing TCP port 443 on host mail.ex4.secureserver.net to ensure it's listening and open.
    The port was opened successfully.
   Additional Details
Elapsed Time: 110 ms.
   Testing the SSL certificate to make sure it's valid.
    The certificate passed all validation requirements.
   Additional Details
Elapsed Time: 461 ms.
   Test Steps
   The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server mail.ex4.secureserver.net on port 443.
    The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
   Additional Details
Remote Certificate Subject: CN=mail.ex4.secureserver.net, O="Starfield Technologies, LLC.", L=Scottsdale, S=AZ, C=US, Issuer: SERIALNUMBER=10688435, CN=Starfield Secure Certification Authority, OU=http://certificates.starfieldtech.com/repository,
O="Starfield Technologies, Inc.", L=Scottsdale, S=Arizona, C=US.
Elapsed Time: 356 ms.
   Validating the certificate name.
    The certificate name was validated successfully.
   Additional Details
Host name mail.ex4.secureserver.net was found in the Certificate Subject Common name.
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=mail.ex4.secureserver.net, O="Starfield Technologies, LLC.", L=Scottsdale, S=AZ, 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 OU=Starfield Class 2 Certification Authority, O="Starfield Technologies, Inc.", C=US.
Elapsed Time: 39 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 = 11/29/2012 8:39:18 PM, NotAfter = 11/29/2015 8:39:18 PM
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: 232 ms.
   Testing HTTP Authentication Methods for URL https://mail.ex4.secureserver.net/rpc/rpcproxy.dll?mail.ex4.secureserver.net:6002.
    The HTTP authentication methods are correct.
   Additional Details
The Microsoft Connectivity Analyzer found all expected authentication methods and no disallowed methods. Methods found: Negotiate, NTLM
HTTP Response Headers:
Content-Type: text/html
Server: Microsoft-IIS/7.5
WWW-Authenticate: Negotiate,NTLM
X-Powered-By: ASP.NET
Date: Fri, 13 Feb 2015 01:07:27 GMT
Content-Length: 58
Elapsed Time: 146 ms.
   Attempting to ping RPC proxy mail.ex4.secureserver.net.
    RPC Proxy was pinged successfully.
   Additional Details
Elapsed Time: 224 ms.
   Attempting to ping the MAPI Mail Store endpoint with identity: mail.ex4.secureserver.net:6001.
    The attempt to ping the endpoint failed.
    Tell me more about this issue and how to resolve it
   Additional Details
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
Elapsed Time: 2626 ms.

Here is another test from the autodiscover:
    The Microsoft Connectivity Analyzer is attempting to test Autodiscover for [email protected].
    Autodiscover was tested successfully.
   Additional Details
Elapsed Time: 1745 ms.
   Test Steps
   Attempting each method of contacting the Autodiscover service.
    The Autodiscover service was tested successfully.
   Additional Details
Elapsed Time: 1745 ms.
   Test Steps
   Attempting to test potential Autodiscover URL https://MYDOMAIN.com:443/Autodiscover/Autodiscover.xml
    Testing of the Autodiscover URL was successful.
   Additional Details
Elapsed Time: 1745 ms.
   Test Steps
   Attempting to resolve the host name MYDOMAIN.com in DNS.
    The host name resolved successfully.
   Additional Details
IP addresses returned: xx.168.xx.74
Elapsed Time: 59 ms.
   Testing TCP port 443 on host MYDOMAIN.com to ensure it's listening and open.
    The port was opened successfully.
   Additional Details
Elapsed Time: 60 ms.
   Testing the SSL certificate to make sure it's valid.
    The certificate passed all validation requirements.
   Additional Details
Elapsed Time: 197 ms.
   Test Steps
   The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server MYDOMAIN.com on port 443.
    The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
   Additional Details
Remote Certificate Subject: CN=MYDOMAIN.com, OU=Domain Control Validated, Issuer: CN=Starfield Secure Certificate Authority - G2, OU=http://certs.starfieldtech.com/repository/, O="Starfield Technologies, Inc.", L=Scottsdale, S=Arizona, C=US.
Elapsed Time: 132 ms.
   Validating the certificate name.
    The certificate name was validated successfully.
   Additional Details
Host name MYDOMAIN.com was found in the Certificate Subject Common name.
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=MYDOMAIN.com, OU=Domain Control Validated.
    One or more certificate chains were constructed successfully.
   Additional Details
A total of 2 chains were built. The highest quality chain ends in root certificate OU=Starfield Class 2 Certification Authority, O="Starfield Technologies, Inc.", C=US.
Elapsed Time: 27 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: 4 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 = 7/2/2014 2:30:01 AM, NotAfter = 7/2/2015 2:30:01 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: 673 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: 754 ms.
   Test Steps
   The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://MYDOMAIN.com:443/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>[email protected]</DisplayName>
</User>
<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<Protocol>
<Type>IMAP</Type>
<Server>MYDOMAIN.com</Server>
<Port>993</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<SSL>on</SSL>
<DomainRequired>off</DomainRequired>
<SPA>off</SPA>
<AuthRequired>on</AuthRequired>
<LoginName>[email protected]</LoginName>
</Protocol>
<Protocol>
<Type>SMTP</Type>
<Server>MYDOMAIN.com</Server>
<Port>465</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<SSL>on</SSL>
<DomainRequired>off</DomainRequired>
<SPA>off</SPA>
<AuthRequired>on</AuthRequired>
<LoginName>[email protected]</LoginName>
</Protocol>
</Account>
</Response>
</Autodiscover>
HTTP Response Headers:
Keep-Alive: timeout=15, max=256
Connection: Keep-Alive
Content-Length: 1227
Content-Type: application/xml; charset="UTF-8"
Date: Fri, 13 Feb 2015 01:14:56 GMT
Server: Apache/2.2.27 (Unix) mod_ssl/2.2.27 OpenSSL/1.0.1e-fips DAV/2 mod_bwlimited/1.4 mod_fcgid/2.3.9
Elapsed Time: 754 ms.

Can we connect Outlook with Exchange 2013 with the default Self-signed certificate?

Hi,
the question is very simple, but after several days searching in this forums and in the web I have not been able to find a definitive answer YES or NOT. I know that Self-signed certificates are not for a production enviroment and only for labs and we must
purchase a third party certificate or get one from a internal CA.
Anyone can answer this question with no doubt?
Thanks in advance!
jspt

Hi Abhi,
I wrote this question because in a recent migration to 2013 from 2007 we've found with this problem: you can view it in the post http://social.technet.microsoft.com/Forums/exchange/en-US/1ddd1e81-1061-4461-95dd-13de653ef8fe/outlook-cant-connect-with-exchange-2013-after-migration-from-exchange-2007?forum=exchangesvrdeploy.
Also I have installed a new exchange 2013 in a lab enviroment and I also have unabled to connect from a Outlook 2013. The problem is the same Outlook is unable to detect the exchange server. Many people in this forums told me that have to be a certificate
problem and for that I posted this question. Honestly, I don't know how to do for Outlook can be connect with Exchange 2013. I don't know what I'm doing wrong.
Anyway thanks for your answer.
jspt

Connect Outlook to Exchange 2007 in separate domain

As part of a merger, we've been asked to discontinue our Exchange 2010 email environment. We would need to connect up our current email users (over a point to point connection with firewall in between) to the other organizations Exchange 2007 server
with completely new email accounts/addresses, via Outlook client. I'm wondering if this is even possible. Can our Outlook client talk to an Exchange 2007 server if Outlook exists in a native Exchange 2010 environment?

Yes you certainly should be able to do that. So long as you're able to connect to the remote Exchange server then you should simply be prompted for login details to access it, since obviously your local login details won't work, at which point you simply
enter the login details provided for the remote exchange server. Obviously you also need to add the remote domain before the username, eg <domain>\<username> to force it to authenticate with that domain login rather than it assuming you're logging
in using a login from your existing domain.
We've got several clients who have their mailboxes hosted on our exchange servers, most of which are running in domain environments, and in fact a few of which have old Exchange servers still running on their networks when we first set them up.

Error connecting to the Exchange Management Shell - and no one can connect w/ Outlook or OWA

Whew - I'm not sure what's happening but everything blew up this morning when another admin rebooted the server...
I can't connect to the Exchange Management shell - I get this:
[<servername>.<domainname>.local] Connecting to remote server failed with the following error message : WS-Management cannot process the request. The operation failed because of an HTTP error. The HTTP error (12152) is: The server returned
an invalid or unrecognized response . For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException
+ FullyQualifiedErrorId : PSSessionOpenFailed
And in digging around, re-running the sharepoint PSConfig appeard to be a fix for a related issue I was reading about, and since there didn't seemt to be any harm in running it again (I did find the technote and had manually ran it after SP1 was installed)
I ran it and this is an excerpt from the log:
09/08/2011 16:48:05 1 INF                      Entering function Farm.Clear
09/08/2011 16:48:05 1 INF                        Entering function CentralAdminServiceInstance.Reset
09/08/2011 16:48:05 1 INF                        Leaving function CentralAdminServiceInstance.Reset
09/08/2011 16:48:05 1 INF                      Leaving function Farm.Clear
09/08/2011 16:48:05 1 INF                    Leaving function Farm.TryIsJoinedToFarm
09/08/2011 16:48:05 1 ERR                    A failure has been encountered when trying to load the Farm
09/08/2011 16:48:05 1 INF                    Entering function StringResourceManager.GetResourceString
09/08/2011 16:48:05 1 INF                      Resource id to be retrieved is FarmIsJoinedFailureWhileUsingCommandLine for language English
(United States)
09/08/2011 16:48:05 1 INF                      Resource retrieved id FarmIsJoinedFailureWhileUsingCommandLine is Failed to detect if this
server is joined to a server farm. Possible reasons for this failure could be that you no longer have the appropriate permissions to the server farm, the database server hosting the server farm is unresponsive, the configuration database is inaccessible
or this server has been removed from the server farm. To diagnose this problem further, review the extended error information located at {0}. If this problem persists, run this wizard again to disconnect from the server farm. After disconnecting,
run the wizard again to create or connect to an existing server farm.
So I seem to have some massive permissions issues. Is there any kind of a technote or walkthrough that can step me through verifying what permissions should be where? The connect to Internet Wizard won't complete complaining it can't configure
the email and to run it again. That caused the Set Up your Internet Address wizard to not run, complaining you have to run the connect to Internet wizard.

Is there any update on the issue?
No. I gave up and rebuilt the server - this time inside of HyperV!
It's definetly a problem of some sort of a problem with IIS, that much is obvious. It's frustrating, because by not being able to get to the Exchange Management Shell it made recovery of the Exchange database VERY hard.
The rest of this will be a bit of a rant so feel free to stop reading here if you like :)
I'm pretty unhappy with the fragility of recovering an Exchange databas in general - there is a VERY narrow range of parameters to get mail back - and very many things that can prevent you from recovering. Had I suspected that there would have been
1/10th the pain in recovering mail, before I tried to connect the clients to the new exchange I would have made .PST files for everyone - which would have worked since they all had cached .OST files, even if the clients couldn't talk to Exchange due to the
aformentioned IIS problems. Anyway, it was a total nightmare, extremly frustrating and while many of my problems were probalby self-induced, the total lack of a coherant disaster recovery strategy has at least motivated me to be EXTREMLY diligent about
backups - and not just backups, but ensuring that the SBS backup is working and occasionally firing up a clone VM and doing a restore to ensure the one of two ways Exchange can be successfully backed up are indeed working.
With such an extreme dependence on IIS for client acces AND managemet of Exchange, there really, REALLY needs to be more documentation on how Exchange uses IIS, how to step through the registry and other low-level internals to troubleshoot and compare.
I must have read just about every technet article and literallly hundreds of blog entries on recovering Exchange - but the lack of information about Exchange's integration and dependancies on IIS were the most frustrating of all. Talk about putting all
your eggs in one basket and a huge single point of failure ticking time bomb!
And I think it was either SharePoint Express or an accidently applied SharePoint Express update that blew up IIS. A few days after that update got applied the server was restarted, and that's when everything went completly sideways. That's whats
even more frustrating - that so many applications are so dependant on a now essential layer is frustrating. I realize SBS is an exception to the rule - generally Exchange is installed on it's own server and this isn't a remote possiblity, but any update
(or installer) that messes with IIS really needs to check the environment it's going to go into, and if there is anything at all that could possibly cause a compatibility issue, the update should "fail open" and not install wtihout explicit confirmation
from the admin that he wants to isntall it. Then again, another admin either ran the installer or approved the SP Express update so that still may not have saved me - but if he saw an explicit warning he probably would not have just clicked through
it!
Oh well - thanks for reading if you went all the way through. I'm just glad that it's now over :)

I have a serious contacts redundancy problem. First I have multiple email account formats, e.g., 2011 MacOutlook, 2008 Entourage, 2007 Window Outlook, iPhone Exchange and these are all connected to the same account. The problem is I had up to 15 contact

I have a serious contacts redundancy problem.
First I have multiple email account formats,e.g., 2011 MacOutlook, 2008 Entourage, 2007 Window Outlook, iPhone Exchange and these are all connected to the same account. The problem is I had up to 15 contacts for the same person.
I deleted the Entourage contacts as that seemed to be the program that was causing the problems. When I synced this morning, now all my contacts are gone from every where.
How can I restore to my last back? If I restore, it will ask to restore to the back that was just made… which has no contacts?
Help would be greatly appreciated !!

I have a serious contacts redundancy problem.
First I have multiple email account formats,e.g., 2011 MacOutlook, 2008 Entourage, 2007 Window Outlook, iPhone Exchange and these are all connected to the same account. The problem is I had up to 15 contacts for the same person.
I deleted the Entourage contacts as that seemed to be the program that was causing the problems. When I synced this morning, now all my contacts are gone from every where.
How can I restore to my last back? If I restore, it will ask to restore to the back that was just made… which has no contacts?
Help would be greatly appreciated !!

Problem Outlook Autodiscovery and "Connect to Microsoft Exchange using HTTP"

Hi,
I have huge problem with Outlook Autodiscovery and RPC over HTTP. In my organization i have Exchange 2010. After server restart something happen with autodiscovery. When client connect to Exchange everything works fine, but.. When client close Outlook
(2010/13) and open again, can connect only using LAN (mapi). When i check settings "Connect to Microsoft Exchange using HTTP" is unchecked!! And all rpc settings (url, msstd:..) are gone!!! It drive me crazy :( When I change settings of course i
can connect thru rpc but only until autodiscovery change settings again :(
Please help
Regards
michadar
ps. I tried disable Outlook Anywhere end enable, restart IIS, restart Exchange. I also try on one computer to disable autodiscovery using regedit but what struck me it still happens :(

Did you try resetting virtual directory? You might have to do this for all CAS servers. Also, take a note of autodiscover vd settings, just to be on the safe side.
Here is the article I found on how to reset the virtual directory.
http://technet.microsoft.com/en-us/library/ff629372(v=exchg.141).aspx
I hope this helps.

Outlook problems connecting to Exchange server

I am using client version 5.0, PIX 506e and Microsoft IAS to vpn into a corporate network. Once connected some users have problems with their Outlook unable to connect to the Exchange server. Trying to figure out if I need to make a configuration change, or if a Microsoft issue. Thanks.

The problem could be because of MTU sizing. Reduce the MTU sizing of the tunnel on both ends till the end users do not face any such connectivity problems. Packet reassembly and fragementation are some of the main causes for connectivity loss.

Problem connecting to exchange server - Outlook 365

Hi I am a user of Exchange 365, have just got a new Surface Pro 2 128gb through work and am piloting it for the company.
I can't for the life of me get Outlook to recognise the exchange server and set up mail for my work address.
It tells me that an encrypted connection to the server is unavailable, and then when I am forced to enter in the server details manually it tells me that "The connection to msoft exchange is unavailable. Outlook must be online or connected to complete
this action
In the meantime I have to use the 365 web app. This is really frustrating me!
I've tried reinstalling multiple times. Can someone please help?

Hi
Thanks this has helped me solve the problem.
I used the Outlook Anywhere connectivity tester you suggested. Selected Outlook autodiscover.
It told me that it could not resolve things on any of the 4 tests.
I saw that using the last test "Attempting to contact the Autodiscover service using the DNS SRV redirect method", was the only one likely to work in my case.
I had already changed 3 entries in dns to point at my DDNS address but this had not worked, from the errors I could see that it was just the certificate name not matching so I changed the DNS entries for Autodiscover, autoconfig and _autodiscover._tcp
to be webmail.domain.com which is a CNAME to my ddns address for the broadband router, which in turn forwards ports 80 and 443 to the exchange server for owa and activesync access. I got an error message saying that I had an illegal entry in my SRV record
as a CNAME is not allowed, but it saved the change anyway.
I reran the test and it worked.I can now make new outlook clients attach teo exchange.
Thank you, after 8 hours yesterday of trying to reolve this I suddnely got it to work on one laptop but the other still would not and had lost track of what I could have changed so had no idea what actually made it work.
Thank you for your suggestion.

Outlook Anywhere Loosing connection : Outlook Event id 26 and Exchange IIS HTTPERR Log : Connection_Dropped_List_Full at the same time

Hi,
I have a Windows 2008R2 Updated / Exchange 2010 SP3 Rollup 7 (Role CAS,HUB,MBX) with only external users connection : ActiveSync, EWS, OWA, Outlook Anywhere.
4 processors and 24Go of memory are allocated to the Exchange server VM (VMWare).
Netscaller is used as reverse proxy in DMZ.
There is around 500 users connecting with Outlook Anywhere to Exchange. Users are using Outlook 2010 or 2013 with last updates and cache mode enabled (owner mailbox and delegations). Users are location all around the world (around 50 sites). So no users
is domain integrated.
Users are complaining about disconnection, and Outlook freeze (Outlook is not responding). This happened at any point of time during the day, and for different kind of actions (Outlook is just open, Try to press Send button, try to press Transfer button).
The freeze happened randomly for users. I have seen the problem, and Outlook sometimes freeze during few seconds, sometimes during 5 minutes without any reason. (no file copy, no action asked...)
I noticed that freeze are matching with the Outlook event id 26 on the workstation (Connection to the Microsoft Exchange Server has been lost. Outlook will restore the connection when possible). Also, at the same time, I can see around 200 lines in
the IIS HTTPERR Log (Exchange Server : C:\Windows\System32\LogFiles\HTTPERR) the following lines:
2014-11-20 10:39:43 NETSCALLERIP PORT EXCHANGEIP 443 HTTP/1.1 RPC_OUT_DATA /rpc/rpcproxy.dll?EXCHANGEFQDN:6004 - 1 Connection_Dropped_List_Full MSExchangeOutlookAnyWhere
2014-11-20 10:39:43 NETSCALLERIP PORT EXCHANGEIP 443 HTTP/1.1 RPC_OUT_DATA /rpc/rpcproxy.dll?EXCHANGEFQDN:6001 - 1 Connection_Dropped_List_Full MSExchangeOutlookAnyWhere
What has been already checked :
Check IOPS: seems to be normal
Check Processor consumption: seems to be normal
Netscaller TimeOut = 8h
Bandwidth where the server is hosted : more than enough
Bandwidth of client internet connection : Traffic do not increase when the problem happen
Firewall TimeOut : seems to be ok
Firewall Protocol Filter : seem to be ok
Workstation MTU : Ok : ping -l -f 1472 = Ok, so best MTU = 1500 (1472+28)
Outlook Profile : Clean Up OST, sync of all folders, download address book.
wireshark on workstation : nothing seems to be wrong but difficult to analyse, so I maybe missed something.
Configuration change on Exchange :
HKLM\Software\Policies\Microsoft\Windows NT\RPC\MinimumConnectionTimeout = 120
Disable throttling Policy
Adsiedit, change Max Memory alloc for ESE : msExchESEParamCacheSizeMax = 327680 (around 10GB) msExchESEParamCacheSizeMin = 131072 (around 4GB
Adsiedit, change Min Memory alloc for ESE : msExchESEParamCacheSizeMin = 131072 (around 4GB)
Host file : add hostname and FQDN of Exchange Server
Disable IPV6 : HKLM\System\CurrentControlSet\services\TCPIP6\Parameters\DisabledComponents = HEX 0xffffffff
IIS : system.applicationHost : webLimits : minBytesPerSecond = 0
Create dedicated IIS AppPool MSExchangeOutlookAnyWhere for /RPC and /RPCWithCert
AppPool MSExchangeOutlookAnyWhere : Regular Time Interval (minutes) : 0
AppPool MSExchangeOutlookAnyWhere : Queue Length : 20000 (Should be the solution but not working)
netsh int tcp set global chimney=disabled
netsh int tcp set global rss=disabled
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\MaxUserPort = 65534
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime : 300000
HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\MaxConcurrentAPI = 150
IIS machine.config : <system.web> : requestQueueLimit="65535"
Microsoft.Exchange.RpcClientAccess.Service.exe.config <add key=”LoggingTag” value=”ConnectDisconnect, Logon, Failures, ApplicationData, Warnings, Throttling”/>
Uninstall All agents (except Backup Agent)
Uninstall Antivirus
Will be done tonight :
Exchange and DCs : HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\MaxConcurrentAPI = 100
Exchange IIS : Increase AppPool MSExchangeOutlookAnyWhere Queue Length to 40000
Exchange : decrease HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime to 60000
You're welcome if you have any idea.
Thanks.
Jo.

Hi,
Thanks for your answer. Here are my comments :
1. Disable IPv6 then restart your Exchange server
Already done since the install of Exchange.
2. Confirm if there is any NLB device in your environment, please remove NLB firm client server
There is only one Exchange server in the Org. So no NLB installed on the server (NLB is used on the Netscaller used as a reverse proxy). In Addition, the article apply for Windows 2008, or the server is installed with Windows 2008 R2.
3. If there is a proxy server configured in IE, please uncheck it
I guess you are talking on the client side. There is no proxy on the client side, Outlook Anywhere connect directly to the internet.
4. Collect more error logs in Event Viewer in Exchange and collect the IIS logs in
folder “c:\inetpub\logs\logfiles\W3SVC1”
the error I reported in the description is from IIS, and always appear when end users report a problem. In W3SVC1 file, there is also errors, but those one appear even if Outlook clients are working fine. So I cannot isolate any specific
error. The most common from W3SVC1 log are :
2014-11-25 08:02:17 EXCHANGEIP POST /autodiscover/autodiscover.xml - 443 - NETSCALLERIP Microsoft+Office/15.0+(Windows+NT+6.1;+Microsoft+Outlook+15.0.4667;+Pro)
401 1 2148074254 0
2014-11-25 08:02:17 EXCHANGEIP POST /EWS/Exchange.asmx - 443 - NETSCALLERIP Mac_OS_X/10.9.5+(13F34)+CalendarAgent/176.2
401 1 2148074254 0
2014-11-25 08:02:18 EXCHANGEIP POST /EWS/Exchange.asmx - 443 - NETSCALLERIP Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro)
401 1 2148074254 0
Regards,
Jo.

The action cannot be completed. The connection to Microsoft Exchange is unavailable. outlook must be online or connected to complete this action

I have outlook 2013 and am trying to add an exchange 2010 multi-tenant account.
I have created a new profile.
I select Manual setup or additional server types
Then select Microsoft Exchange Server or compatible service
I enter the server settings. But the following error is returned when i click check name
"The action cannot be completed. The connection to Microsoft Exchange is unavailable. outlook must be online or connected to complete this action"
I have tried selecting more settings, selecting security, and then selecting the option:- Always propt for logon credentials.
But the same error is still returned
I tried deselecting the option Encrypt data between Microsoft outlook and Microsoft Exchange
But still continue to get the same error.
Reading from other forums I have tried restarting the Microsoft Exchange Address book service under services on the exchange server.
But this did not help either
i am able to access the email accout via outlook web access. I am also able to add the email account to my iphone with the server details and it adds fine onto my iphone but cannot add it to outlook 2013.
any help would be appreciated.
Thanks
Rehan Miah

Hi,
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.
NOTE: The \User Shell Folders key also contains a string value called
Local AppDatawhich is different from the value called AppData. The value that causes this problem (if it is missing) is the
AppData value.
To resolve this issue, import the User Shell Folders registry key from a working Windows User Profile.
For more information, please refer:
http://support.microsoft.com/kb/2264398
Hope this helps.
Best Regards,
Steve Fan
TechNet Community Support
I have looked in the registry and Appdata is not missing it has the following value "%USERPROFILE%\AppData\Roaming" also Local AppData is there with the following value "%USERPROFILE%\AppData\Local" i do not have a working machine to import the user shell
folders registry key so any other advice would be useful.
thanks
Rehan Miah
In order to test what you suggested i created a windows 7 virtual machine installed outlook 2003 however i also get the error on the virtual machine that i have created.
any further suggestions would be a great help.

You must connect to Microsoft Exchange with your current profile before you can synchronize your folders with your outlook data file (.ost).... OWA works but outlook 2013 does not, exchange server 2013 on Server standard 2012

I have read a lot of articles and tried a lot of things, but I cannot get outlook to connect to my exchange server. This is a test environment, I have tried making my own certificate and signing it through my own CA to no avail. I have completely disabled
windows firewall and stopped the service. I can ping between the two just fine by name or IP. I've tried not using cached mode, creating new profiles in outlook etc. I tried setting my CertPrincipalName to my FQDN in exchange powershell.
I am not an expert with exchange at all, but I feel like this should work with little to no configuration, instead I've wasted days on this. Half of the articles I've read don't seem to have solutions, and the other half have solutions that are not working
for me.
I can access OWA and send emails on a client computer through OWA with no problems.
I am running a test domain on the same network as my current exchange 2003/sbs 2003 active environment, I don't know why this would be an issue, but if it is I cannot figure out why. The only thing I can see holding me back right now is not having a signed
certificate from digicert etc, and an official internet domain set up, but I don't think either of those things matter in my situation.
Any help is greatly appreciated and I'll gladly provide any other information requested to solve this issue, thank you.

I have a similar setup and also have the same error. Did you find a solution for this?
In the managed availability - monitoring log I see the following errors:
EMSMDB.Connect() step of ComplianceOutlookLogonToArchiveRpcCtpProbe/Mailbox Database 0326619395 has failed against BESRVCOTEXCH001 proxying to BESRVCOTEXCH001 for [email protected].
Latency: 00:01:58.0150000
ActivityContext:
Outline: [15] RpcProxy connectivity verification; [117999][FAILED!] EMSMDB.Connect();
Likely root cause: HighLatency
Details:
Error: Error 0x71a (The remote procedure call was cancelled) from ClientAsyncCallState.CheckCompletion: RpcAsyncCompleteCall RPC EEInfo is not enabled or there is no error on this thread.
Log: RpcProxy connectivity verification
Task produced output:
- TaskStarted = 8/5/2014 7:47:11 AM
- TaskFinished = 8/5/2014 7:47:11 AM
- ErrorDetails =
- Latency = 00:00:00.0153816
- RpcProxyUrl = https://besrvcotexch001.hq.corp.cotrain.lan/rpc/[email protected]:6001
- ResponseStatusCode = OK
- RequestedRpcProxyAuthenticationTypes = ntlm
- RespondingHttpServer = BESRVCOTEXCH001
- RespondingRpcProxyServer = BESRVCOTEXCH001
- WebHeaderCollection = Persistent-Auth: true
X-DiagInfo: BESRVCOTEXCH001
X-BEServer: BESRVCOTEXCH001
Content-Length: 20
Content-Type: application/rpc
Date: Tue, 05 Aug 2014 05:47:11 GMT
Server: Microsoft-IIS/8.0
X-Powered-By: ASP.NET
RpcProxy connectivity verification completed successfully.
Mailbox logon verification
EMSMDB.Connect()
Task produced output:
- TaskStarted = 8/5/2014 7:47:11 AM
- TaskFinished = 8/5/2014 7:49:09 AM
- Exc
and
EMSMDB.Connect() step of OutlookRpcCtpProbe/Mailbox Database 0326619395 has failed against BESRVCOTEXCH001 proxying to BESRVCOTEXCH001 for [email protected].
Latency: 00:01:58.0250000
ActivityContext:
Outline: [13] RpcProxy connectivity verification; [118011][FAILED!] EMSMDB.Connect();
Likely root cause: HighLatency
Details:
Error: Error 0x71a (The remote procedure call was cancelled) from ClientAsyncCallState.CheckCompletion: RpcAsyncCompleteCall RPC EEInfo is not enabled or there is no error on this thread.
Log: RpcProxy connectivity verification
Task produced output:
- TaskStarted = 8/5/2014 7:23:20 AM
- TaskFinished = 8/5/2014 7:23:20 AM
- ErrorDetails =
- Latency = 00:00:00.0132417
- RpcProxyUrl = https://besrvcotexch001.hq.corp.cotrain.lan/rpc/[email protected]:6001
- ResponseStatusCode = OK
- RequestedRpcProxyAuthenticationTypes = ntlm
- RespondingHttpServer = BESRVCOTEXCH001
- RespondingRpcProxyServer = BESRVCOTEXCH001
- WebHeaderCollection = Persistent-Auth: true
X-DiagInfo: BESRVCOTEXCH001
X-BEServer: BESRVCOTEXCH001
Content-Length: 20
Content-Type: application/rpc
Date: Tue, 05 Aug 2014 05:23:20 GMT
Server: Microsoft-IIS/8.0
X-Powered-By: ASP.NET
RpcProxy connectivity verification completed successfully.
Mailbox logon verification
EMSMDB.Connect()
Task produced output:
- TaskStarted = 8/5/2014 7:23:20 AM
- TaskFinished = 8/5/2014 7:25:18 AM
- Exc

DLL Shell problems connecting outlook to exchange

Similar Messages

Maybe you are looking for