Announcement

Collapse
No announcement yet.

Attempting to login to OWA returns an "Unspecified Error"

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Attempting to login to OWA returns an "Unspecified Error"

    Hi Everyone,

    I have three Exchange 2003 servers in a “Front-End Back-End” type configuration. The front-end server is (imaginatively) called “mailserver” which sends and receives e-mail on behalf of the two back-end servers: “mailstore1” and “mailstore2”. Messages are flowing freely everything appears to fine until…

    …you try and log into your mailbox via the front-end server. If you try and access your mailbox using OWA via the front-end server, you receive an “HTTP 500 - Internal server error” message. If you turn off Internet Explorer’s “Friendly HTTP Errors” and try logging in to OWA, again through the front-end server, you get an “Unspecified error” message. However, if you happen to know which of the two back-end servers hosts your mailbox, you can login to that server with no problems whatsoever…

    No additional errors or events are logged in the server’s event viewer when this problem occurs.

    Active Directory is installed on other servers and not on any of our Exchange boxes.

    All our servers run Windows 2003.

    The only other software installed on these servers is Symantec Mail Security for Microsoft Exchange.

    This is our second year running Exchange 2003 on a Windows 2003 OS. This problem started three months ago when we added the three current e-mail servers in an attempt to replace the ageing hardware that we used to use for our Exchange environment. Our migration process involved running the new servers in parallel with the old ones, moving the mailboxes across to the new hardware before decommissioning the old machines.

    If anyone has any ideas, I’d be happy to hear them.

    Many thanks,

    Graeme

  • #2
    Re: Attempting to login to OWA returns an "Unspecified Error"

    When logging in how are you typing in the username? Default config requires domain\username

    Just a thought...
    Server 2000 MCP
    Development: ASP, ASP.Net, PHP, VB, VB.Net, MySQL, MSSQL - Check out my blog http://tonyyeb.blogspot.com

    ** Remember to give credit where credit is due and leave reputation points sigpic where appropriate **

    Comment


    • #3
      Re: Attempting to login to OWA returns an "Unspecified Error"

      We've tried logging in using that method but to no avail...

      Comment


      • #4
        Re: Attempting to login to OWA returns an "Unspecified Error"

        Is your front-end in the DMZ of your network yet?
        Server 2000 MCP
        Development: ASP, ASP.Net, PHP, VB, VB.Net, MySQL, MSSQL - Check out my blog http://tonyyeb.blogspot.com

        ** Remember to give credit where credit is due and leave reputation points sigpic where appropriate **

        Comment


        • #5
          Re: Attempting to login to OWA returns an "Unspecified Error"

          No, the front-end server is on the same network segment as the back-end servers.

          Comment


          • #6
            Re: Attempting to login to OWA returns an "Unspecified Error"

            Please upgrade to the latest Win 2003 hotfixs + service pack + Exchange hotfixs + service pack and review:

            http://support.microsoft.com/kb/841561

            Regards,

            Yuval
            Best Regards,

            Yuval Sinay

            LinkedIn: https://www.linkedin.com/in/yuval14, Blog: http://blogs.microsoft.co.il/blogs/yuval14

            Comment


            • #7
              Re: Attempting to login to OWA returns an "Unspecified Error"

              I have encountered this same error a couple of times since summer. I just installed Exchange 2003 SP2 and it did not solve the problem. I tried many things, but what I think solved the issue, was to go to the Front End Server, bring up the properties in the Exchange System Manager. Go down to the server, and the checkbox that says this is a Front End Server, uncheck it. Click Apply. After Apply, recheck it, and Apply it. You will need to reboot the server. Let me know if anyone else has encountered this and finds that it solves the problem.

              Thanks,

              Ron Kramer
              Consultants On Call
              [email protected]
              www.4coc.com

              Comment

              Working...
              X