What causes the OWA 2013 login loop?












0














When attempting to login to OWA with valid credentials, the login screen reappears without any form or sort of error message. Despite this the logon procedure has succeeded, because when I re-enter the OWA URL my mailbox is opened.



I am unsure as to the cause of this problem. The strange thing is that it does not happen all the time. Exchange is installed on the domain controller, but other than that I can't think of any possible causes.



Could it be a misconfiguration somewhere? Perhaps something to do with the IIS or DNS configuration?










share|improve this question














bumped to the homepage by Community 2 days ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Try clearing browser caches. Also try a different browser and see if the symptoms persist.
    – Kinnectus
    May 22 '14 at 6:34










  • I have seen it happen on almost every browser, from Internet Explorer to Firefox and Chrome. Also, clearing the browser caches seems to have no effect.
    – Mark
    May 22 '14 at 6:40










  • Are you able to get any logs from IIS (they are in %windir%system32logfiles I would recommend stopping IIS services renaming the latest file, start services and recreate the problem to limited the amount of data in the log file.
    – CharlesH
    May 22 '14 at 13:41
















0














When attempting to login to OWA with valid credentials, the login screen reappears without any form or sort of error message. Despite this the logon procedure has succeeded, because when I re-enter the OWA URL my mailbox is opened.



I am unsure as to the cause of this problem. The strange thing is that it does not happen all the time. Exchange is installed on the domain controller, but other than that I can't think of any possible causes.



Could it be a misconfiguration somewhere? Perhaps something to do with the IIS or DNS configuration?










share|improve this question














bumped to the homepage by Community 2 days ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Try clearing browser caches. Also try a different browser and see if the symptoms persist.
    – Kinnectus
    May 22 '14 at 6:34










  • I have seen it happen on almost every browser, from Internet Explorer to Firefox and Chrome. Also, clearing the browser caches seems to have no effect.
    – Mark
    May 22 '14 at 6:40










  • Are you able to get any logs from IIS (they are in %windir%system32logfiles I would recommend stopping IIS services renaming the latest file, start services and recreate the problem to limited the amount of data in the log file.
    – CharlesH
    May 22 '14 at 13:41














0












0








0







When attempting to login to OWA with valid credentials, the login screen reappears without any form or sort of error message. Despite this the logon procedure has succeeded, because when I re-enter the OWA URL my mailbox is opened.



I am unsure as to the cause of this problem. The strange thing is that it does not happen all the time. Exchange is installed on the domain controller, but other than that I can't think of any possible causes.



Could it be a misconfiguration somewhere? Perhaps something to do with the IIS or DNS configuration?










share|improve this question













When attempting to login to OWA with valid credentials, the login screen reappears without any form or sort of error message. Despite this the logon procedure has succeeded, because when I re-enter the OWA URL my mailbox is opened.



I am unsure as to the cause of this problem. The strange thing is that it does not happen all the time. Exchange is installed on the domain controller, but other than that I can't think of any possible causes.



Could it be a misconfiguration somewhere? Perhaps something to do with the IIS or DNS configuration?







microsoft-outlook login outlook-web-access exchange-2013






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked May 22 '14 at 6:19









MarkMark

111




111





bumped to the homepage by Community 2 days ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 2 days ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.














  • Try clearing browser caches. Also try a different browser and see if the symptoms persist.
    – Kinnectus
    May 22 '14 at 6:34










  • I have seen it happen on almost every browser, from Internet Explorer to Firefox and Chrome. Also, clearing the browser caches seems to have no effect.
    – Mark
    May 22 '14 at 6:40










  • Are you able to get any logs from IIS (they are in %windir%system32logfiles I would recommend stopping IIS services renaming the latest file, start services and recreate the problem to limited the amount of data in the log file.
    – CharlesH
    May 22 '14 at 13:41


















  • Try clearing browser caches. Also try a different browser and see if the symptoms persist.
    – Kinnectus
    May 22 '14 at 6:34










  • I have seen it happen on almost every browser, from Internet Explorer to Firefox and Chrome. Also, clearing the browser caches seems to have no effect.
    – Mark
    May 22 '14 at 6:40










  • Are you able to get any logs from IIS (they are in %windir%system32logfiles I would recommend stopping IIS services renaming the latest file, start services and recreate the problem to limited the amount of data in the log file.
    – CharlesH
    May 22 '14 at 13:41
















Try clearing browser caches. Also try a different browser and see if the symptoms persist.
– Kinnectus
May 22 '14 at 6:34




Try clearing browser caches. Also try a different browser and see if the symptoms persist.
– Kinnectus
May 22 '14 at 6:34












I have seen it happen on almost every browser, from Internet Explorer to Firefox and Chrome. Also, clearing the browser caches seems to have no effect.
– Mark
May 22 '14 at 6:40




I have seen it happen on almost every browser, from Internet Explorer to Firefox and Chrome. Also, clearing the browser caches seems to have no effect.
– Mark
May 22 '14 at 6:40












Are you able to get any logs from IIS (they are in %windir%system32logfiles I would recommend stopping IIS services renaming the latest file, start services and recreate the problem to limited the amount of data in the log file.
– CharlesH
May 22 '14 at 13:41




Are you able to get any logs from IIS (they are in %windir%system32logfiles I would recommend stopping IIS services renaming the latest file, start services and recreate the problem to limited the amount of data in the log file.
– CharlesH
May 22 '14 at 13:41










2 Answers
2






active

oldest

votes


















0














I've been digging through this for serveral hours. It was for a certificate. Uninstall your current certificate (Get-ExchangeCertificate/Remove-ExchangeCertificate) and resetiis.






share|improve this answer





















  • The OP makes no mention of a certificate error. Could you go into a bit more detail on the process?
    – Burgi
    May 18 '16 at 11:19



















0














Old thread, but I had exactly the same issue and the problem was certificates.
I was using an ad-enrolled web server certificate from an internal ca.



As it turns out I had to use a Windows Server 2003 Enterprise (100.4) certificate instead of a Windows Server 2008 (100.3) certificate.






share|improve this answer





















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f757332%2fwhat-causes-the-owa-2013-login-loop%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    I've been digging through this for serveral hours. It was for a certificate. Uninstall your current certificate (Get-ExchangeCertificate/Remove-ExchangeCertificate) and resetiis.






    share|improve this answer





















    • The OP makes no mention of a certificate error. Could you go into a bit more detail on the process?
      – Burgi
      May 18 '16 at 11:19
















    0














    I've been digging through this for serveral hours. It was for a certificate. Uninstall your current certificate (Get-ExchangeCertificate/Remove-ExchangeCertificate) and resetiis.






    share|improve this answer





















    • The OP makes no mention of a certificate error. Could you go into a bit more detail on the process?
      – Burgi
      May 18 '16 at 11:19














    0












    0








    0






    I've been digging through this for serveral hours. It was for a certificate. Uninstall your current certificate (Get-ExchangeCertificate/Remove-ExchangeCertificate) and resetiis.






    share|improve this answer












    I've been digging through this for serveral hours. It was for a certificate. Uninstall your current certificate (Get-ExchangeCertificate/Remove-ExchangeCertificate) and resetiis.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered May 17 '16 at 8:46









    pmanpman

    1




    1












    • The OP makes no mention of a certificate error. Could you go into a bit more detail on the process?
      – Burgi
      May 18 '16 at 11:19


















    • The OP makes no mention of a certificate error. Could you go into a bit more detail on the process?
      – Burgi
      May 18 '16 at 11:19
















    The OP makes no mention of a certificate error. Could you go into a bit more detail on the process?
    – Burgi
    May 18 '16 at 11:19




    The OP makes no mention of a certificate error. Could you go into a bit more detail on the process?
    – Burgi
    May 18 '16 at 11:19













    0














    Old thread, but I had exactly the same issue and the problem was certificates.
    I was using an ad-enrolled web server certificate from an internal ca.



    As it turns out I had to use a Windows Server 2003 Enterprise (100.4) certificate instead of a Windows Server 2008 (100.3) certificate.






    share|improve this answer


























      0














      Old thread, but I had exactly the same issue and the problem was certificates.
      I was using an ad-enrolled web server certificate from an internal ca.



      As it turns out I had to use a Windows Server 2003 Enterprise (100.4) certificate instead of a Windows Server 2008 (100.3) certificate.






      share|improve this answer
























        0












        0








        0






        Old thread, but I had exactly the same issue and the problem was certificates.
        I was using an ad-enrolled web server certificate from an internal ca.



        As it turns out I had to use a Windows Server 2003 Enterprise (100.4) certificate instead of a Windows Server 2008 (100.3) certificate.






        share|improve this answer












        Old thread, but I had exactly the same issue and the problem was certificates.
        I was using an ad-enrolled web server certificate from an internal ca.



        As it turns out I had to use a Windows Server 2003 Enterprise (100.4) certificate instead of a Windows Server 2008 (100.3) certificate.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered May 15 '18 at 21:21









        slimer64slimer64

        1




        1






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f757332%2fwhat-causes-the-owa-2013-login-loop%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            How to make a Squid Proxy server?

            Is this a new Fibonacci Identity?

            19世紀