Announcement

Collapse
No announcement yet.

befuddled: OWA displays different mailbox contents than Outlook2k3 client, same acct

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

  • befuddled: OWA displays different mailbox contents than Outlook2k3 client, same acct

    I am trying to configure the Exchange 2003 email portion of this Small Business Server 2003 box. My configuration is the Single server: In this scenario, you have only one server that is configured to function as a Domain Controller, a Global Catalog, an Exchange computer, and an RPC proxy server. This article discusses the single-server configuration in detail.

    I was finally able to get RPC over HTTP working (thanks to tutorial on this site) so now my "test user account" can log in though both Outlook Web Access and through the Outlook 2003 client using the profile I set up on the client machine to connect using RPC over HTTP.

    Here's where things get weird. No inbound or outbound email flow appears to be working correctly.

    When I send an email to the test account from say a Yahoo account, I get an NDR:

    This is an automatically generated Delivery Status Notification.
    Delivery to the following recipients failed.

    [email protected]

    Final-Recipient: rfc822;[email protected]
    Action: failed
    Status: 5.0.0


    When I try to send email out, I dont get any NDR's or anything, but the emails never arrive at the destination.

    The weird part is that the OWA "Sent Items" folder display different emails (ones I attempted to send out for testing) than the "Sent Items" folder I see when I log on via the Outlook 2k3 client. Each method only displays the Sent Items that I tried to send via that method. But if I log off and log back on, they will still be there--as if these Sent emails have actually been persisted to 2 different email boxes!

    I also tried using telnet to deliver a sample email to my test user account. Everything seemed to work fine using Microsofts tutorial. The SMTP service on the server reported the "mail was queued for delivery." But it never arrived (I checked the inbox using both OWA and Outlook 2k3 client methods).

    Does anyone have any idea of whats happening? Could it be related to my domain being mydomain.local internally? Or maybe something to do with the SmallBusiness SMTP Connector that i see was automatically created ?

  • #2
    Re: befuddled: OWA displays different mailbox contents than Outlook2k3 client, same

    Did you keep a list of the things you setup and changed?
    Personally, and I would wait for other input first, I would run the ICW and get email working again. Once you have that functioning I would worry about RPC/HTTPS.
    I will assume email worked before you started so it seems likely it isn't a firewall/AV port blocking.
    cheers
    Andy

    Please read this before you post:


    Quis custodiet ipsos custodes?

    Comment


    • #3
      Re: befuddled: OWA displays different mailbox contents than Outlook2k3 client, same

      Turn on message tracking on the server properties and use that to see what Exchange did with the message.
      SBS should always be configured using the wizards, so ensure that the Connect to the Internet and Email wizard has been run correctly and completes without errors.
      Ensure that Outlook is not set to deliver email to a personal folder, but to the mailbox. That would account for the differences in the messages.

      Simon.
      --
      Simon Butler
      Exchange MVP

      Blog: http://blog.sembee.co.uk/
      More Exchange Content: http://exchange.sembee.info/
      Exchange Resources List: http://exbpa.com/
      In the UK? Hire me: http://www.sembee.co.uk/

      Sembee is a registered trademark, used here with permission.

      Comment


      • #4
        Re: befuddled: OWA displays different mailbox contents than Outlook2k3 client, same

        OK, I reran the ICW wizard as suggested and although it said it configured everything successfully, I am still having the same problem.

        I did enable Message Tracking and have 2 clues from that:

        1) When sending an outbound email (to external internet email address) from my test account, I can then search for the message in Message Tracking center. I do see the message. When I click on it, only one line appears in the message flow box however: "SMTP Store Driver: Message Submitted from Store". However there are no other lines after that. Looking at tutorials online it seems that I might next expect to see a line like "SMTP: Message submitted to Advanced Queuing". I do not see this line or any other lines for that matter.

        2) When I try to submit a sample inbound email to the SMTP service using telnet, I go through the routine and when it's done the SMTP service says "Queued mail for delivery" as if everything worked. But it never arrives in inbox and Message Tracking center cannot locate it in any searches.

        NOTE: This is a new dedicated server hosted at a remote location by a hosting company. Thus, email has never worked yet on this new box. I am trying to migrate from an old server to the new server. So I change the A record for exchange.mydomain.com to point from the old IP to the new IP and then run the tests.

        PS. Simon, you were right about the "Delivery to personal folder" explaining the difference. Now Outlook 2k3 and OWA show the same contents. Still having the mail flow problem though.

        Comment


        • #5
          Re: befuddled: OWA displays different mailbox contents than Outlook2k3 client, same

          This looks like interference.
          What else is on the machine? AV, Antispam, something like that?
          When you telnet to the machine, does Exchange answer or is it something else?

          Simon.
          --
          Simon Butler
          Exchange MVP

          Blog: http://blog.sembee.co.uk/
          More Exchange Content: http://exchange.sembee.info/
          Exchange Resources List: http://exbpa.com/
          In the UK? Hire me: http://www.sembee.co.uk/

          Sembee is a registered trademark, used here with permission.

          Comment


          • #6
            Re: befuddled: OWA displays different mailbox contents than Outlook2k3 client, same

            The ESMTP service is answering the Telnet; it looks pretty similar to another (working) exchange box. I've also ruled out interference from AV or such.

            However, you did point me in a direction and I may have an important clue now. I am wondering if this problem is due to the fact the hosting guys first erroneously installed Windows Server 2k3 and then I had to call them and make them do SBS 2003 instead. Maybe in this process something was not reset correctly or perhaps they reinstalled IIS after Exchange?

            The reason I am wondering is because I used MetaEdit to look at IIS's metabase and check the value for SmtpAdvQueueDll. My path is coming back pointing to "C:\WINDOWS\system32\inetsrv\aqueue.dll" which is the original Windows Server 2k3 value for IIS. However another online source says:

            "The SMTP stack provided by IIS' SMTP svc in Exchange Server 2003/2000 changes significantly when Exchange is installed on a Windows server. Some ESMTP extensions are added to support Exchange, it gets Exchange's Advanced Queuing Engine (AQE) implemented in phatq.dll, and the Categorizer (phatcat.dll). The mailroot path is moved from IIS' default (\inetpub\mailroot) to \exchsrvr\mailroot. Post-Exchange install, you cannot use IIS to manage SMTP - management functionality is provided by Exchange System Manager (ESM)."

            So i don't have the new phatq.dll which explains why the "Submitted to Advanced Queuing" line never occurred in Message Tracking. Also, I can still edit the Default SMTP Virtual Server through IIS and when I looked at my other Exchange box, it was no longer available in the IIS snapin. However at least some of the values in the IIS metabase did use the exchsrvr\mailroot path so apparently some of the changes did persist through.

            NOTE: another concerning thing is that a good number of custom domains appear in the Default SMTP Virtual Server (as seen through the IIS snapin). There is only one default domain , but several custom domains seem to be clones (maybe from my various attempts at running CIEW wizard?) of that. There is no context menu item available for Delete on them though. Another post online mentioned this may occur due to some sort of mislinking in the IIS metabase.

            Can someone definitively say that Exchange in Small Business Server 2003 should have phatq.dll and the other values mentioned above that I am missing?

            What is my best way to fix this? There is a website running through the IIS so I'd like to avoid reinstalling that if possible (although the domains that are missing "Delete" from the context menu do scare me). If I dismount the stores can I just reinstall Exchange portion of SBS?

            Comment


            • #7
              Re: befuddled: OWA displays different mailbox contents than Outlook2k3 client, same

              If I was looking at that server, particularly as it is SBS there is only one option I would suggest. A wipe and rebuild. The server should not be hosting a public web site, that is not what SBS is designed for and you are putting yourself at risk by doing so. You are inviting anonymous traffic to an internal server. With the cost of hosting it makes no sense to try and host everything on one machine.

              If the integration between Exchange and IIS has been broken, then the only solution is a removal of both Exchange and IIS. In my experience reinstalling IIS rarely fixes the connection between IIS and Exchange.

              Certainly it sounds like the hosting company have made a lot of errors - if they are a hosting company then they probably do not know how to install and configure SBS correctly.

              Simon.
              --
              Simon Butler
              Exchange MVP

              Blog: http://blog.sembee.co.uk/
              More Exchange Content: http://exchange.sembee.info/
              Exchange Resources List: http://exbpa.com/
              In the UK? Hire me: http://www.sembee.co.uk/

              Sembee is a registered trademark, used here with permission.

              Comment


              • #8
                Re: befuddled: OWA displays different mailbox contents than Outlook2k3 client, same

                Simon, you are right about this configuration being less than ideal. Unfortunately it wasn't my decision.

                In any case, I wanted to post my solution in case anyone else has this problem. It was half a nightmare in fixing it.

                The problem is when someone installs/reinstalls IIS after Exchange has already been installed on the box. Various things can go wrong. In my case, mail flow was not occurring and Message Tracking demonstrated that the emails were never making it to the Advanced Queuing phase.

                The problem can be proven definitively by examing the IIS metabase with MetaEdit or Metabase Explorer and looking for the value of SmtpAdvQueueDll key. If the path points to aqueue.dll, you are in trouble. Exchange linkage will replace the aqueue.dll (default Windows Server 2k3 value) with phatq.dll, so the SMTP engine will route through Exchange's Advanced Queuing DLL. Unfortunately there are many other linkages that have been stomped on, so the only option is to reinstall both IIS and Exchange --and in that order.

                1) Follow the directions here to retain your users and mail store contents during the process:

                How to remove and to reinstall IIS on a computer that is running Exchange Server
                http://support.microsoft.com/kb/320202

                Note: For SBS 2003 boxes, reinstalling Exchange is initiated through the Add/Remove programs, "Small Business Server" line entry. It will seem like the setup is occurring all over from scratch, but the setup program will read your configuration first and retain those settings. You will probably be asked for installation CDs during the process.

                2) For SBS 2003 only, you will need to rerun the Configure Email and Internet Connection Wizard to re-establish various permissions and other required configuration.

                3) At this point, I became aware that the Exchange-related virtual directories (Exchange, Exadmin, OMA, Public, etc.) within the Default Web site were corrupted. The <Invalid Application Pool> was showing up in the Properties tabs and there's no way to fix it from the GUI. Fortunately, there is a great way to force Exchange to rebuild the directories. Follow these instructions and then reboot the machine:

                Repairing damaged OWA virtual directories in Exchange Server 2003
                http://searchexchange.techtarget.com/tip/0,289483,sid43_gci1319471,00.html

                4) Lastly, my website was displaying strange "page not found" errors. I could not figure it out, but finally fixed it. The old IIS and ASP.net accounts were deleted during the reinstall so the ACLs on some of the folders still had the Unknown Account in the Security & Permissions tab, due to the orphaned SID. I deleted the orphaned SIDs and redid permissions and things began working.

                Hope this helps someone.

                Comment

                Working...
                X