Outlook 2013 Proxy error

Hello,
We have recently deployed some Microsoft Surface Pro 3's in my office.  All of them have Office 2013 Basic and work when in the office.  However, a user is getting an error message on one of them when he uses the Surface Pro while traveling. 
The errror message is:  "There is a problem with the Proxy servers security certificate.  The certificate is not from a trusted certifying authority.  Outlook is not able to connect to the proxy server <server.companyname.com>.
(Error Code 8). 
I have Googled and BING'd this all morning and am not making much progress.  Items I have verified. 
Date and time are correct on the device
User does NOT get this error when he is INSIDE the office.
After acknowledging the proxy error, the user receives two security alerts, stating there is a problem with the sites security certificate. 
We have a valid certificate from GoDaddy on my Exchange 2010 server. 
None of my Windows 7 users are receiving this error. 
Thank you in advance for your time. 

Hinte
Below are the results you requests.  Thank you. 
[PS] D:\temp>Get-OutlookProvider
Name                          Server                       
CertPrincipalName             TTL
EXCH                                                                                                
    1
EXPR                                                                                                    
1
WEB                                                                                                      1
Try running:
Set-OutlookProvider Exch msstd:<subjectnameofcert>
Set-OutlookProvider EXPR msstd:<subjectnameofcert>
I have seen issues where Outlook doesn't like this not being populated. 
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

Similar Messages

  • ICloud Outlook 2013 sync errors

    I'm using Win7 64-bit, Office 2013.
    Group policy was updated on the domain, it redirected My Documents from the local c:\ to the server (2008 R2 domain controller), for easy backup.
    Most Outlook files are stored in My Documents\Outlook Files, which are now on the server.
    Outlook stopped receiving e-mail to the local .PST.  The repair was to recreate the Outlook Profile.
    After recreation, iCloud stopped working.
    Uninstalling/reinstalling iCloud Control Panel has not worked.
    I ran a reinstall of Office, then a repair of iCloud, no change.
    I have a screen, as below.  When I choose the Outlook Sync, that is the error below.
    Any ideas?  I'm out of them.

    Please do try something else - Android is excellent. Everyone loves it. Windows as well I am sure.
    MamontovAndrey wrote:
    When I create note for meeting from Outlook, it is simply removed. But when I create note for meeting from iPad Calendar, it is sync.
    I think it is a shame for Apple, because they are talking about business users. And considering the replacement design for ios 7, problems with sync some apps (iBooks for example), non-availability large-sized iPhone, it is all added more reasons to try go to Android or Windows Phone(
    And there is no russian Siri, what a shame. However you are not speaking to Apple here, if you feel you need to feedback Apple it is done here.
    www.apple.com/feedback.
    I am sure they will find your opinion on size, IOS7 and Outlook 2013 invaluable.

  • Outlook 2013 "Unknown Error" Message Box

    I am running Outlook 2013 Professional and we have Exchange 2010. 
    Periodically when I am deleting messages I receive a box that says "Unknown Error" it doesn't say anything else and if I click OK it goes away... its more of an annoyance but we are going to start using 2013 more often and I want to see if anyone
    has any thoughts on the cause.
    Thanks
    Jessica Cochran

    Hi,
    I would suggest to try the methods list in the article below:
    http://www.howto-outlook.com/faq/deletemessage.htm
    Best regards,
    Rex Zhang
    TechNet Community Support

  • Outlook 2013 & Proxied accounts, FROM address not defaulting correctly

    Hello,
    We are hosted by Microsoft for our email. We have been on Outlook 2010 for a couple of years without any issues. I have proxy access to two other mailboxes for support purposes. Up until last Thursday, when I replied to an email in the support mailbox, the
    default FROM address was the address for that mailbox. Last Thursday, something changed somewhere so the default FROM address is now my personal mailbox. I do have access to send mail from the proxied accounts so it isn't a rights issue. I am able to change
    the FROM address each time I reply but this is cumbersome. My personal email should never be going out on replies but remembering has been a chore since it always used to work correctly.
    Our helpdesk had me install a plugin called unisend which did fix one related issue but didn't correct the issue I'm experiencing. I have talked with our senior network engineer and mail administrator and both confirm they did not make any changes. I did
    upgrade my PC to Office 2013 in hopes that something became corrupted with my installation (that the upgrade would fix) but that did not correct the problem.
    Ideas?

    Hi there,
    We have received many reports as your description since last week. It sounds like the sending behavior in Outlook 2010 has been changed by some Windows/Office update and goes back to the behavior before.
    Before we go any further, I have to mention some of the history for Outlook 2010. In Outlook 2010 without SP1, Mailto’s will use the default/principal account for message when you use Microsoft Outlook 2010 which has multiple accounts delivered to different
    data file. However, in later version (Outlook 2010 SP1/SP2), Outlook doesn’t use the default account set in Account settings for new messages. Instead, it uses the account associated with the mailbox or *.pst file you have in focus.
    Actually, this behavior is controlled by the registry keys. At this point, I suggest we check the following registry entries are exist and set it to the proper value.
    HKEY_CURRENT_USER\Software\Microsoft\Office\XX.0\Outlook\Options\Mail
    DWORD value: NewItemsUseDefaultSendingAccount
    Value type: REG_DWORD: 1 for force, 0 to disable.
    HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\XX.0\outlook\options
    Value Name: ForceAccountSelection
    Value type: REG_DWORD: 1 for force, 0 to disable.
    Close the registry editor and restart Outlook to check if the behavior what you want would come back.
    In addition, our Outlook MVP, Diane Poremsky has written an article with more detail information:
    http://www.slipstick.com/outlook/outlook-2010/multiple-accounts-and-the-default-account/
    By the way, we still cannot figure out which update is the root of the issue, if someone could test it and share the result here, I would appreciate that. Feel free to post back.
    Tony Chen
    TechNet Community Support

  • Outlook 2013 standard error cannot open the outlook window. Invalid XML.

    I have a user that tries to open outlook and gets this error.
    ( Cannot start microsoft outlook. cannot open the outlook window. Invalid XML, the view cannot be loaded.

    Hi,
    Try starting Outlook with the /ResetNavPane command.
    Steps:
    Open the run box (Win-button + R)
    Type: outlook.exe /resetnavpane
    http://wikiclouded.com/cannot-start-microsoft-outlook-invalid-xml-the-view-cannot-be-loaded/
    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
    Regards,
    George Zhao
    TechNet Community Support

  • Ribbon behavior using Outlook 2013 vs IE

    We are running CRM 2011 on-premise and using the 2011 CRM for Outlook client RU 18.
    Most users are still running Office 2007 and the issue below does not occur as far as I know.  However some users are now running office 365 and issue below occurs. It does not occur when using IE (users are on IE 11)
    Issue : When attempting to create a new record on a custom entity using outlook client via outlook 2013 an error occurs.
    The error received is from a web-api call that is custom built.  These web-api calls get fired when opening an existing record to determine user roles etc.  The buttons that fire these rules are not displayed unless the formstate = existing (among
    other rules). We did not have a similar rule on the ribbon button enable rule to check of formstate= existing.
    In IE this works fine. However using the new button in OUtlook it appears the enable rule still fires. In some cases these custom web-api calls are supposed to pass an entity guid, which in this case there is none yet. 
    We have modified the enable rules on several buttons to specifically account for the formstate rule and this seems to help.
    Has anyone heard of anything similar. Again as far as I know this started to happen when Office 365 /outlook 2013 was installed.
    Robert

    Hello IMPACTMatt,
    I'd say a cookie is suggesting the username. She has inherited a computer from someone else, right?
    Regardless of that, can she log in?
    Best regards George

  • There is a problem with the proxy server's security certificate (internal Outlook 2013 users)

    I am receiving the above message for internal Outlook 2013 users when they open Outlook. Despite this message, Outlook is fully functional. External OA users do not see this message. We are using an SRV record for our autodiscover and pointing it to the
    name on the single cert we have. I've also already changed the outlookprovider record in Exchange. Any ideas?
    TIA!

    Hi Alceryes,
    According to the error message, Outlook is unable to connect  to the proxy server (Error Code 10),
    it seems an issue on the Certificate side.
    FLAG_CERT_CN_INVALID 0x00000010
    More details to see following KB:
    http://support.microsoft.com/kb/923575
    Would you like to tell me the reason that why you are using SRV record for Autodiscover?
    I find a FAQ on Autodisocover for your reference, hope it is helpful:
    https://social.technet.microsoft.com/Forums/office/en-US/54bc6b17-9b60-46a4-9dad-584836d15a02/troubleshooting-and-introduction-for-exchange-20072010-autodiscover-details-about-test-email?forum=exchangesvrgeneral
    Thanks
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Mavis Huang
    TechNet Community Support

  • Outlook 2013: There is a problem with the proxy server's certificate

    Hello!
    One more question regarding Outlook 2013/Exchange2013SP1:
    There are three lab PCs: DC, Exch1, Exchange2. There's a wildcard certificate installed on Exch1 (https://social.technet.microsoft.com/Forums/en-US/6a440c99-47bd-4f48-8cc5-9f92e6b06496/wildcard-certificate-for-exchange-2013?forum=exchangesvrgeneral).
    OWA works perfect with this wildcard certificate.
    I install Outlook2013 on Exch1 and get the error:
    DC.Entreprise.Local is a computer certificate issued for the computer DC.Enterprise.Local.
    DC.Enterprise.Local IS NOT (and never was) the proxy for Exch1 or Exchange2:
    How Outlook could request DC's certificate if the proxy server = Exch1.Enterprise.Local???
    Thank you in advance,
    Michael

    Hello all,
    Thank you for your replies!
    Since I'm using a wildcard certificate I changed Outlook providers according to this:
    http://blogs.technet.com/b/exchange/archive/2013/08/02/part-2-reverse-proxy-for-exchange-server-2013-using-iis-arr.aspx
    If you do choose to use a wildcard certificate, you should also make sure that you
    change the EXPR Outlook Provider, so that Outlook Anywhere clients can successfully connect to the Exchange Server (this behavior can be a particular issue
    if you have Windows XP clients). If you do not make this change then end users may continue to receive a prompt for a certificate mismatch."
    ...and EXCH and EXPR are both set to *.Enterprise.Local.
    "I install Outlook2013 on Exch1" you mean you install Outlook on top of Exchange?"  - on the same server as Exchange, and in this case Outlook must use SCP, not DNS (the server and the client are in the same AD domain).
    "Without SCP, Exchange  try DNS autodiscover lookup, first site it will try is
    https://emaldomain/autodiscover/autodiscover.xml, which happen to be resolve to your domain controller."  - I think that's the case... I just don't understand why
    an internal client can't find the SCP that does exist and point to exch1.enterprise.local:
    Regards,
    Michael

  • Some Outlook clients getting internal FQDN of newly installed Exchange 2013 CAS server as Outlook Anywhere Proxy address

    Hello Folks,
    I have this problem and is making me crazy if anyone have any idea please shed some light on this:-
    1. Working Outlook 2010 and 2013 clients with webmail.xyz.com as Outlook Anywhere proxy address.
    2. Installed new Exchange 2013 server (server02)with CAS and Mailbox role, Exchange install wizard finished and server is rebooted.
    3. Server came up online started changing internal and external FQDN's of Virtual Directories and Outlook Anywhere to webmail.xyz.com
    4. As soon as Fqdn's changed some outlook clients create support request that Outlook suddenly white's out and after reopening it is giving error  cannot connect to exchange. upon checking Clients Exchange Proxy address is set to http://server02.xyz.com,
    even though OA/OWA/ECP/OAB/EWS/Autodiscover/ActiveSync FQDN's Point to webmail.xyz.com, on all servers if i create new outlook profile for same user it picks up correct settings through autodiscover and connects fine, this is happening to about 20% of outlook
    clients every time i am introducing new Exchange 2013 server in Organization. we have around 2000 users and planning on installing 4 exchange servers to distribute load and everytime changing outlook profile of close to 150-200 users is not possible.
    Any help is greatly appreciated.
    Thanks
    Cool

    Here are the EXCRA results
    Here IP (x.x.x.x) returned is my Load Balancer IP (Webmail.xyz.com).    
    Connectivity Test Successful with Warnings
    Test Details
         Testing Outlook connectivity.
         The Outlook connectivity test completed successfully.
              Additional Details
         Elapsed Time: 9881 ms.
              Test Steps
              The Microsoft Connectivity Analyzer is attempting to test Autodiscover for [email protected].
         Autodiscover was tested successfully.
              Additional Details
         Elapsed Time: 2063 ms.
              Test Steps
              Attempting each method of contacting the Autodiscover service.
         The Autodiscover service was tested successfully.
              Additional Details
         Elapsed Time: 2063 ms.
              Test Steps
              Attempting to test potential Autodiscover URL https://xyz.com:443/Autodiscover/Autodiscover.xml
         Testing of this potential Autodiscover URL failed.
              Additional Details
         Elapsed Time: 186 ms.
              Test Steps
              Attempting to resolve the host name xyz.com in DNS.
         The host name couldn't be resolved.
           Tell me more about this issue and how to resolve it
              Additional Details
         Host xyz.com couldn't be resolved in DNS InfoNoRecords.
    Elapsed Time: 186 ms.
         Attempting to test potential Autodiscover URL https://autodiscover.xyz.com:443/Autodiscover/Autodiscover.xml
         Testing of the Autodiscover URL was successful.
              Additional Details
         Elapsed Time: 1876 ms.
              Test Steps
              Attempting to resolve the host name autodiscover.xyz.com in DNS.
         The host name resolved successfully.
              Additional Details
         IP addresses returned: x.x.x.x
    Elapsed Time: 338 ms.
         Testing TCP port 443 on host autodiscover.xyz.com to ensure it's listening and open.
         The port was opened successfully.
              Additional Details
         Elapsed Time: 173 ms.
         Testing the SSL certificate to make sure it's valid.
         The certificate passed all validation requirements.
              Additional Details
         Elapsed Time: 318 ms.
              Test Steps
              The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.xyz.com on port 443.
         The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
              Additional Details
         Remote Certificate Subject: CN=webmail.xyz.com, Issuer: CN=VeriSign Class 3 Secure Server CA - G3, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US.
    Elapsed Time: 219 ms.
         Validating the certificate name.
         The certificate name was validated successfully.
              Additional Details
         Host name autodiscover.xyz.com was found in the Certificate Subject Alternative Name entry.
    Elapsed Time: 1 ms.
         Certificate trust is being validated.
         The certificate is trusted and all certificates are present in the chain.
              Test Steps
              The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=webmail.xyz.com, OU=Terms of use at www.verisign.com/rpa (c)05,.
         One or more certificate chains were constructed successfully.
              Additional Details
         A total of 1 chains were built. The highest quality chain ends in root certificate CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign,
    Inc.", C=US.
    Elapsed Time: 36 ms.
         Analyzing the certificate chains for compatibility problems with versions of Windows.
         Potential compatibility problems were identified with some versions of Windows.
              Additional Details
         The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature
    isn't enabled.
    Elapsed Time: 5 ms.
         Testing the certificate date to confirm the certificate is valid.
         Date validation passed. The certificate hasn't expired.
              Additional Details
         The certificate is valid. NotBefore = 1/3/2013 12:00:00 AM, NotAfter = 11/16/2015 11:59:59 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: 289 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: 756 ms.
              Test Steps
              The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.xyz.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>Test Exch1</DisplayName>
    <LegacyDN>/o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=add423106fbb47d5bf237462f52b8dab-Test Exch1</LegacyDN>
    <DeploymentId>4ec753c9-60d9-4c05-9451-5b24e2d527a7</DeploymentId>
    </User>
    <Account>
    <AccountType>email</AccountType>
    <Action>settings</Action>
    <Protocol>
    <Type>EXCH</Type>
    <Server>[email protected]</Server>
    <ServerDN>/o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]</ServerDN>
    <ServerVersion>73C0834F</ServerVersion>
    <MdbDN>/o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]/cn=Microsoft Private MDB</MdbDN>
    <ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
    <OOFUrl>https://webmail.xyz.com/ews/exchange.asmx</OOFUrl>
    <OABUrl>https://webmail.xyz.com/OAB/6a6a06ad-4717-4636-bd98-0b4fa3aaf4a5/</OABUrl>
    <UMUrl>https://webmail.xyz.com/ews/UM2007Legacy.asmx</UMUrl>
    <Port>0</Port>
    <DirectoryPort>0</DirectoryPort>
    <ReferralPort>0</ReferralPort>
    <PublicFolderServer>webmail.xyz.com</PublicFolderServer>
    <AD>DC-03.domain.xyz.com</AD>
    <EwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EwsUrl>
    <EmwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EmwsUrl>
    <EcpUrl>https://webmail.xyz.com/ecp/</EcpUrl>
    <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-um>
    <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-aggr>
    <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=domain.xyz.com</EcpUrl-mt>
    <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-ret>
    <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-sms>
    <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-photo>
    <EcpUrl-tm>?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tm>
    <EcpUrl-tmCreating>?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmCreating>
    <EcpUrl-tmEditing>?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmEditing>
    <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-extinstall>
    <ServerExclusiveConnect>off</ServerExclusiveConnect>
    </Protocol>
    <Protocol>
    <Type>EXPR</Type>
    <Server>webmail.xyz.com</Server>
    <ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
    <OOFUrl>https://webmail.xyz.com/ews/exchange.asmx</OOFUrl>
    <OABUrl>https://webmail.xyz.com/OAB/6a6a06ad-4717-4636-bd98-0b4fa3aaf4a5/</OABUrl>
    <UMUrl>https://webmail.xyz.com/ews/UM2007Legacy.asmx</UMUrl>
    <Port>0</Port>
    <DirectoryPort>0</DirectoryPort>
    <ReferralPort>0</ReferralPort>
    <SSL>On</SSL>
    <AuthPackage>Ntlm</AuthPackage>
    <EwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EwsUrl>
    <EmwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EmwsUrl>
    <EcpUrl>https://webmail.xyz.com/ecp/</EcpUrl>
    <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-um>
    <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-aggr>
    <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=domain.xyz.com</EcpUrl-mt>
    <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-ret>
    <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-sms>
    <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-photo>
    <EcpUrl-tm>?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tm>
    <EcpUrl-tmCreating>?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmCreating>
    <EcpUrl-tmEditing>?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmEditing>
    <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-extinstall>
    <ServerExclusiveConnect>on</ServerExclusiveConnect>
    <EwsPartnerUrl>https://webmail.xyz.com/ews/exchange.asmx</EwsPartnerUrl>
    <GroupingInformation>Default-First-Site-Name</GroupingInformation>
    </Protocol>
    <Protocol>
    <Type>WEB</Type>
    <Port>0</Port>
    <DirectoryPort>0</DirectoryPort>
    <ReferralPort>0</ReferralPort>
    <Internal>
    <OWAUrl AuthenticationMethod="Basic, Fba">https://webmail.xyz.com/owa/</OWAUrl>
    <Protocol>
    <Type>EXCH</Type>
    <ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
    </Protocol>
    </Internal>
    <External>
    <OWAUrl AuthenticationMethod="Fba">https://webmail.xyz.com/owa/</OWAUrl>
    <Protocol>
    <Type>EXPR</Type>
    <ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
    </Protocol>
    </External>
    </Protocol>
    <Protocol>
    <Type>EXHTTP</Type>
    <Server>webmail.xyz.com</Server>
    <ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
    <OOFUrl>https://webmail.xyz.com/ews/exchange.asmx</OOFUrl>
    <OABUrl>https://webmail.xyz.com/OAB/6a6a06ad-4717-4636-bd98-0b4fa3aaf4a5/</OABUrl>
    <UMUrl>https://webmail.xyz.com/ews/UM2007Legacy.asmx</UMUrl>
    <Port>0</Port>
    <DirectoryPort>0</DirectoryPort>
    <ReferralPort>0</ReferralPort>
    <SSL>On</SSL>
    <AuthPackage>Ntlm</AuthPackage>
    <EwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EwsUrl>
    <EmwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EmwsUrl>
    <EcpUrl>https://webmail.xyz.com/ecp/</EcpUrl>
    <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-um>
    <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-aggr>
    <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=domain.xyz.com</EcpUrl-mt>
    <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-ret>
    <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-sms>
    <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-photo>
    <EcpUrl-tm>?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tm>
    <EcpUrl-tmCreating>?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmCreating>
    <EcpUrl-tmEditing>?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmEditing>
    <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-extinstall>
    <ServerExclusiveConnect>On</ServerExclusiveConnect>
    </Protocol>
    <Protocol>
    <Type>EXHTTP</Type>
    <Server>webmail.xyz.com</Server>
    <ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
    <OOFUrl>https://webmail.xyz.com/ews/exchange.asmx</OOFUrl>
    <OABUrl>https://webmail.xyz.com/OAB/6a6a06ad-4717-4636-bd98-0b4fa3aaf4a5/</OABUrl>
    <UMUrl>https://webmail.xyz.com/ews/UM2007Legacy.asmx</UMUrl>
    <Port>0</Port>
    <DirectoryPort>0</DirectoryPort>
    <ReferralPort>0</ReferralPort>
    <SSL>On</SSL>
    <AuthPackage>Ntlm</AuthPackage>
    <EwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EwsUrl>
    <EmwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EmwsUrl>
    <EcpUrl>https://webmail.xyz.com/ecp/</EcpUrl>
    <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-um>
    <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-aggr>
    <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=domain.xyz.com</EcpUrl-mt>
    <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-ret>
    <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-sms>
    <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-photo>
    <EcpUrl-tm>?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tm>
    <EcpUrl-tmCreating>?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmCreating>
    <EcpUrl-tmEditing>?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-tmEditing>
    <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=domain.xyz.com</EcpUrl-extinstall>
    <ServerExclusiveConnect>On</ServerExclusiveConnect>
    </Protocol>
    </Account>
    </Response>
    </Autodiscover>HTTP Response Headers:
    request-id: 9d325a80-f1fd-4496-ac48-2be6bb782c28
    X-CalculatedBETarget: Server01.domain.xyz.com
    X-DiagInfo: Server01
    X-BEServer: Server01
    Persistent-Auth: true
    X-FEServer: Server01
    Content-Length: 11756
    Cache-Control: private
    Content-Type: text/xml; charset=utf-8
    Date: Mon, 25 Aug 2014 19:12:25 GMT
    Set-Cookie: X-BackEndCookie=S-1-5-21-1293235207-2459173341-1304346827-14544=u56Lnp2ejJqBypqcnsfJx5nSy8ucnNLLnJzP0sfKz8/Sy5nHmsiamZrMyZrLgYHPxtDNy9DNz87L387Gxc7Nxc3J; expires=Thu, 25-Sep-2014 00:12:26 GMT; path=/Autodiscover; secure; HttpOnly
    Server: Microsoft-IIS/8.5
    X-AspNet-Version: 4.0.30319
    X-Powered-By: ASP.NET
    Elapsed Time: 756 ms.
         Autodiscover settings for Outlook connectivity are being validated.
         The Microsoft Connectivity Analyzer validated the Outlook Autodiscover settings.
              Additional Details
         Elapsed Time: 0 ms.
         Testing RPC over HTTP connectivity to server webmail.xyz.com
         RPC over HTTP connectivity was verified successfully.
              Additional Details
         HTTP Response Headers:
    request-id: 835acf95-78b7-40ae-b232-117318d1577e
    Server: Microsoft-IIS/8.5
    WWW-Authenticate: Basic realm="webmail.xyz.com",Negotiate,NTLM
    X-Powered-By: ASP.NET
    X-FEServer: Server01
    Date: Mon, 25 Aug 2014 19:12:26 GMT
    Content-Length: 0
    Elapsed Time: 7817 ms.
              Test Steps
              Attempting to resolve the host name webmail.xyz.com in DNS.
         The host name resolved successfully.
              Additional Details
         IP addresses returned: x.x.x.x
    Elapsed Time: 107 ms.
         Testing TCP port 443 on host webmail.xyz.com to ensure it's listening and open.
         The port was opened successfully.
              Additional Details
         Elapsed Time: 180 ms.
         Testing the SSL certificate to make sure it's valid.
         The certificate passed all validation requirements.
              Additional Details
         Elapsed Time: 303 ms.
              Test Steps
              The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server webmail.xyz.com on port 443.
         The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
              Additional Details
         Remote Certificate Subject: CN=webmail.xyz.com, OU=Terms of use at www.verisign.com/rpa (c)05, Issuer: CN=VeriSign Class 3 Secure Server CA - G3, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign,
    Inc.", C=US.
    Elapsed Time: 224 ms.
         Validating the certificate name.
         The certificate name was validated successfully.
              Additional Details
         Host name webmail.xyz.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=webmail.xyz.com, OU=Terms of use at www.verisign.com/rpa (c)05,
         One or more certificate chains were constructed successfully.
              Additional Details
         A total of 1 chains were built. The highest quality chain ends in root certificate CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign,
    Inc.", C=US.
    Elapsed Time: 34 ms.
         Analyzing the certificate chains for compatibility problems with versions of Windows.
         Potential compatibility problems were identified with some versions of Windows.
              Additional Details
         The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature
    isn't enabled.
    Elapsed Time: 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 = 1/3/2013 12:00:00 AM, NotAfter = 11/16/2015 11:59:59 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: 298 ms.
         Testing HTTP Authentication Methods for URL https://webmail.xyz.com/rpc/[email protected]:6002.
         The HTTP authentication methods are correct.
              Additional Details
         The Microsoft Connectivity Analyzer found all expected authentication methods and no disallowed methods. Methods found: Basic, Negotiate, NTLMHTTP Response Headers:
    request-id: 835acf95-78b7-40ae-b232-117318d1577e
    Server: Microsoft-IIS/8.5
    WWW-Authenticate: Basic realm="webmail.xyz.com",Negotiate,NTLM
    X-Powered-By: ASP.NET
    X-FEServer: Server01
    Date: Mon, 25 Aug 2014 19:12:26 GMT
    Content-Length: 0
    Elapsed Time: 296 ms.
         Attempting to ping RPC proxy webmail.xyz.com.
         RPC Proxy was pinged successfully.
              Additional Details
         Elapsed Time: 454 ms.
         Attempting to ping the MAPI Mail Store endpoint with identity: [email protected]:6001.
         The endpoint was pinged successfully.
              Additional Details
         The endpoint responded in 0 ms.
    Elapsed Time: 1007 ms.
         Testing the MAPI Address Book endpoint on the Exchange server.
         The address book endpoint was tested successfully.
              Additional Details
         Elapsed Time: 2177 ms.
              Test Steps
              Attempting to ping the MAPI Address Book endpoint with identity: [email protected]:6004.
         The endpoint was pinged successfully.
              Additional Details
         The endpoint responded in 906 ms.
    Elapsed Time: 918 ms.
         Testing the address book "Check Name" operation for user [email protected] against server [email protected].
         The test passed with some warnings encountered. Please expand the additional details.
           Tell me more about this issue and how to resolve it
              Additional Details
         The address book Bind operation returned ecNotSupported. This typically indicates that your server requires encryption. The Microsoft Connectivity Analyzer will attempt the Address Book test again with encryption.
    NSPI Status: 2147746050
    Elapsed Time: 825 ms.
         Testing the address book "Check Name" operation for user [email protected] against server [email protected].
         Check Name succeeded.
              Additional Details
         DisplayName: Test Exch1, LegDN: /o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=add423106fbb47d5bf237462f52b8dab-Test Exch1
    Elapsed Time: 433 ms.
         Testing the MAPI Referral service on the Exchange Server.
         The Referral service was tested successfully.
              Additional Details
         Elapsed Time: 1808 ms.
              Test Steps
              Attempting to ping the MAPI Referral Service endpoint with identity: [email protected]:6002.
         The endpoint was pinged successfully.
              Additional Details
         The endpoint responded in 953 ms.
    Elapsed Time: 949 ms.
         Attempting to perform referral for user /o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=add423106fbb47d5bf237462f52b8dab-Test Exch1 on server [email protected].
         We got the address book server successfully.
              Additional Details
         The server returned by the Referral service: [email protected]
    Elapsed Time: 858 ms.
         Testing the MAPI Address Book endpoint on the Exchange server.
         The address book endpoint was tested successfully.
              Additional Details
         Elapsed Time: 626 ms.
              Test Steps
              Attempting to ping the MAPI Address Book endpoint with identity: [email protected]:6004.
         The endpoint was pinged successfully.
              Additional Details
         The endpoint responded in 156 ms.
    Elapsed Time: 154 ms.
         Testing the address book "Check Name" operation for user [email protected] against server [email protected].
         Check Name succeeded.
              Additional Details
         DisplayName: Test Exch1, LegDN: /o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=add423106fbb47d5bf237462f52b8dab-Test Exch1
    Elapsed Time: 472 ms.
         Testing the MAPI Mail Store endpoint on the Exchange server.
         We successfully tested the Mail Store endpoint.
              Additional Details
         Elapsed Time: 555 ms.
              Test Steps
              Attempting to ping the MAPI Mail Store endpoint with identity: [email protected]:6001.
         The endpoint was pinged successfully.
              Additional Details
         The endpoint responded in 234 ms.
    Elapsed Time: 228 ms.
         Attempting to log on to the Mailbox.
         We were able to log on to the Mailbox.
              Additional Details
         Elapsed Time: 326 ms.

  • Outlook anywhere testconnectivity error RPC 6004 (NSPI Proxy Interface)

    Greetings, community!
    We have next Exchange configuration:
    Exchange Server 2007 (With last RU) on Windows Server 2008R2. All roles, except Edge, are on this server.
    So, we have published OWA, ActiveSync successfully through ISA Server 2004. Testconnectivity tells us that all is correct and it's true)
    But we have strange problem with RPC over HTTPS:
    Testconnectivity tells us:
    RPC 6004 (NSPI Proxy Interface) and RPC_S_SERVER_UNAVAILABLE (0x6ba) in the details.
    We have already use all receipts from http://blogs.technet.com/b/exchange/archive/2008/06/20/3405633.aspx and http://www.tech-archive.net/Archive/Exchange/microsoft.public.exchange.setup/2004-07/1151.html articles.
    Enabling expert auditing of NSPI Proxy on Exchange server shows warning when Testconnectivity try to connect:
    NSPI Proxy listener thread (ID: 0xfec) could not connect to the server on transport .  The winsock subsystem returned error code:[0xRpc/HTTP].
    RPCPING utility tells us:
    Exception 1722 (0x000006BA)
    Number of records is: 2
    ProcessID is 6696
    System Time is: 2/8/2014 13:27:0:552
    Generating component is 14
    Status is 0x6BA, 1722
    Detection location is 1398
    Flags is 0
    NumberOfParameters is 2
    Long val: 0x4
    Long val: 0x6ba
    ProcessID is 6696
    System Time is: 2/8/2014 13:27:0:552
    Generating component is 13
    Status is 0x6BA, 1722
    Detection location is 1418
    Flags is 0
    NumberOfParameters is 0
    Out DC controllers are listening 6004 port. And Exchange server successfully connect with DC with information message:
    NSPI Proxy successfully connected to the NSPI Service on server DC.FQDN.NAME at endpoint 6004 on RPC protocol sequence ncacn_http.
    Additional information:
    Outlook 2003/2007/2010 can't connect to our Exchange through RPC/HTTPS. But Outlook 2013 do it without any problems!
    I don't know where I can continue to dig)

    Hi, Sathish!
    Thank you for reply.
    Service is started and IPv6 is disabled. Do you mean SRV-record for autodiscover? We don't use it for external users. We publish Autodiscover same way as Owa and it works correct (interconnectivity).
    I enable Expert level audit for NSPI Proxy and there is error:
    Source: MSExchangeSA
    EventID: 9040
    NSPI Proxy encountered an error while receiving a packet. The target Domain Controller or the network or a client might be down. The winsock subsystem returned the error:[0x2746]. The circuit that received this error is being closed.
    But DC is online and available. I'll reboot server tonight because I think there is a little trouble after disabling additional NIC.

  • Certificate errors with Exchange 2013 and Outlook 2013

    Hello, I wonder if someone could help.
    I've recently set up a network with one Windows 2012 domain controller and one windows 2012 server running Exchange 2013.
    Clients run Outlook 2013 and are all one the same Lan. Outlook's setup wizard finds the exchange server automatically and sets up the profile. However if I choose the manual setup and enter the server
    name and user name it does not find the server.
    When I check the server name in Outlook it shows as 
    [email protected] rather than the real name of the server: AYCEX01.AYC.local.
    When Outlook is opened there is a certificate error saying "The name on the security certificate is invalid or does not match the name of the site." and another error saying "There is
    a problem with the server's security certificate. The name on the security certificate is invalid or does not match the name of the target site mail.ardfernyacht.co.uk. Outlook is unable to connect to the proxy server. (Error code 10)
    The external address by which users connect to OWA and active sych is mail.ardfernyacht.co.uk. The
    certificate which is used is one automatically generated by Exchange.
    Any suggestions you may have would be appreciated.
    Many thanks,
    Ruaridh
    Ruaridh Mackintosh

    Self sign cert wont work With autodiscover.For that you need 3rd part or from Your own CA.
    Please follow this guide to install CA in Your domain:
    http://careexchange.in/how-to-install-certificate-authority-on-windows-server-2012/
    Please follow this guide to request New cert in Exchange 2013:
    http://exchangeserverpro.com/create-ssl-certificate-request-exchange-2013/
    Your cert must contain external hostname of Your mail.domain.com
    Also configure Your Virtual directories to contain internal and external hostname:
    http://blogs.msdn.com/b/mvpawardprogram/archive/2013/03/18/virtual-directories-exchange-2013.aspx
    Regarding servername when using autodiscover,it should automatically resolve mailbox guid instead of servername.
    Please check if Your DNS is setup With autodiscover.domain.local (which is pointed to Your Exchange server)
    Hope this helps!
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

  • Recieveing "OnUCAppointmentGetVisible" error in Outlook 2013 (64 bit) - "Custom UI Runtime Error in Lync Meeting Add-in for Microsoft Office 2013"

    Hi All,
    I originally posted this in the MS Support forums (http://answers.microsoft.com/en-us/office/forum/office_2013_release-outlook/recieveing-onucappointmentgetvisible-error-in/1a40eca2-8cd1-40f1-a92f-cb08f0af6b72), but was directed over here.
    I have recently upgraded an installation of Office 2010 to 2013 (both 64 bit) but am now receiving an error which says:
    Window Title - "Custom UI Runtime Error in Lync Meeting Add-in for Microsoft Office 2013"
    An error occured while calling the callback: "OnUCAppointmentGetVisible"
    This seem to happen when I initially open a calender entry, and when I close the entry (most only the first time I close the entry).
    I did have some developer tools installed for Office 2010 and VS 2010 which played around with Excel,2013 but I have now uninstalled these.
    In addition, BCM 2010 was installed (but for the time being has been uninstalled), but I don't think that is the culprit.
    The issue is being caused be an Outlook add-in. I have three COM add-in enabled, but the one causing the issue in the "Lync Meeting Add-in for Microsoft Office 2013".
    We are currently trialling Lync in a demo installation which is in a different domain to any of the Exchange accounts, but should this cause a problem? For the time being I have disable this add-in.
    Regards,
    Chris
    Chris

    Hi,
    Sorry for my misunderstanding. If the issue is determined to be caused by Lync Meeting Add-in, please remove this add-in from Outlook, then go to Control Panel to repair Office 2013 program. After repairing,
     this add-in would be automatically reinstalled. Please check whether the issue persists. About how to repair Office programs, please refer to:
    http://office.microsoft.com/en-us/outlook-help/repair-office-programs-HA010357402.aspx
    If the Lync Meeting Add-in is not automatically reinstalled, please try to manually add this add-in by the following steps:
    1. Starting Outlook 2013 as an Administrator (right click, run as Admin).
    2. Click File > Options > Add-ins, Manage Com Add-Ins Go... > Add..., C:\Program Files (x86)\Microsoft Office\Office15\UCAddin.dll, OK.
    3. Close Outlook and start it as a normal user.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Outlook 2013 set as default mail client but still shows error box saying it isn't?

    We have recently installed Office 2013 64-bit on 4 servers. We previously used Outlook 2007 64-bit.
    We set Outlook 2013 as the default mail client and do not have another mail client installed on the servers. However when you first login you get an error message box that says you have no default mail client 'either there is no default mail client or the
    current mail client cannot fulfill the messaging request'.
    I have checked all defaults to be for Outlook 2013.
    How can I solve this issue? I am an administrator.

    Try different Method to set Outlook 2013 as the default mail client to check the result. Thanks.
    Method 1:Set as default within outlook.
    -File > Options > General Tab >  select the "Make Outlook the default program for E-mail, Contacts, and Calendar"
    check box.
    Method 2: Set as default from the internet explorer.
    -Tool > Internet Options > Programs Tab > Set programs 
    Method 3: Set as default from control panel.
    1.Navigate to Control Panel\Default Programs\Set Default Programs
    2.Click on the outlook icon on the left hand side.
    3.Set as default.
    We may also try to create anther windows user profile in the same machine to check if the issue still persists. Thanks.
    Tony Chen
    TechNet Community Support

  • HT204150 icloud sync to outlook 2013 errors in setup

    I was having some issues with icloud syncing with outlook 2013 on my windows 8 PC, so i uninstalled it and re-installed.   Ever since then, i have not been able to even get icloud for windows set up.  I keep getting an error in the final stage of the setup after i tick the box on outlook calendar, contacts and tasks in the control panel.  The error i get is: "Your setup couldn't be started because the iCloud server stopped responding."  When I hit the report button, the following eror comes up in the email: Error: 0x80004005: HTTP Error 503. 
    have uninstalled, restarted, downloaded a fresh version and re-installed then restarted again but this didn't work. 
    Any new ideas?
    thanks

    Hockley7 wrote:
    I have been trying for hours and numerous with reinstals of the desktop but I can't get the BB 7.1 Desktop to recognize my Outlook 2013 profile (Windows 8) so I can configure syncronizing the contacts and the calendar.  It worked on Outlook 2010 and in Wondows 7.  Spent 3 hours on the phone with MS and the profiles are there but they don't show up when I need to select the platform.
    Hi and Welcome to the Community!
    I am sorry to have to reference you to these materials:
    KB12268 Synchronization support for BlackBerry Desktop Software for Windows
    http://us.blackberry.com/software/desktop/desktop-pc/system-requirements.html
    You will notice that Outlook 2013 does not appear in any of that. Which means it is not supported. Which means it cannot be expected to function.
    Again, sorry.
    Occam's Razor nearly always applies when troubleshooting technology issues!
    If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
    Join our BBM Channels
    BSCF General Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • Getting unknown error 0x8004011c. when trying to set up email account in Outlook 2013 with a Domain

    Hi all
    The title basically states the problem - Outlook 2013 wont set up with a Domain. This only seems to affect Windows 8.1 pro, Win 7 Pro has no problems.  If I log on to the computer itself (not the domain) Outlook runs no problem
    If anyone has any ideas I would be most grateful
    Thank you
    Fionnbarr

    Hi Fionnbarr,
    When you say "...with a Domain", do you mean login to the computer with a domain user account?
    Does this happen on all your Windows 8.1 clients? What's the error message in full? At which exact step will you get this error?
    So you have observed that "This only seems to affect Windows 8.1 pro", it could be an issue with this specific system. I would suggest we first check for Windows updates and install any available ones, then try again.
    Regards,
    Ethan Hua
    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]

Maybe you are looking for

  • Trying to do a system recovery

    Hi, so I have an HP notebook and a few days a ago I did a system recovery to its factory settings. Problem is, when it got to the second disk, around 60% it gave an error and stopped. I dont know why, the disks look like they are in tip top shape. I

  • Images stripped from Camera Data after Export from Lr

    Hi, I've just opened images in jpg format in Ps. The images were exported from Lr and for some reason all the Camera Data is gone... I went through all the settings in Ps and Lr and didn't find anything... I'm enclosing a screenshot.

  • EQ2 guide

    EQ2 guide The fiery peaks of EverQuest II’s Lavastorm zone have claimed the life of many unfortunate  adventurers.  Rivers of lava flow freely and hundreds of hostile goblins and lizards inhabit this  desolate place.  SOE has recently decided to reva

  • VLAN Membership with ACS

    I just want to implement 802.1x authentication, to dynamically assign into differente vlans, can you help me how it should be done? What is the best method? I see the PEAP is much more complex. Initially I'm thinking about Mac-Address based, so that

  • SD card empty or missing

    Hi everyone, I have have a z3 compact and i'm having issues with the SD card. I put some media in there via file commander like music or videos and some time later the SD card appears to be empty or missing. It's a 64gb card class 10. I've been trans