Invitation meeting from OWA 2003

Posted on 2006-06-06
Last Modified: 2009-10-16

Any time I send invitation meeting to any user using my OWA connection I get a Delivery Status Notification (Delay) and then after tow days I get Undeliverable: Delivery Status Notification (Failure).
The user receive and response to the invitation without any problem.
I don’t get this message when I send invitation using my outlook client.

The actual error message: (  Your message did not reach some or all of the intended recipients.
Sent:      6/1/2006 5:15 PM

The following recipient(s) could not be reached:

  System Attendant on 6/3/2006 5:48 PM
  Could not deliver the message in the time limit specified. Please retry or contact your administrator.
  <ServerName.DomainName #4.4.7>

Exchange 2003
OWA 2003
Outlook 2002
Question by:Manzour
    LVL 3

    Expert Comment

    Does your meeting request include any resources eg. a meeting room. Outlook Web Access doesn't support direct booking a resource, this is an Outlook feature, not Exchange server. If you need to reserver resources using OWA and you're using Exchange 2003 SP1, you should look into Auto Accept Agent. Here's a link to great article about Auto Accept Agent:

    And here's a link to Microsoft Deployment Guide:

    Just remember not to register a resource mailbox for bot Direct Booking and Auto Accept Agent:;EN-US;903290


    LVL 1

    Author Comment

    Thank you for the response, but I went through the documents and all about the Auto Accept Agent (AAA) with Resource Mailboxes. Nothing got to do with the error I’m getting!! But over all, it’s a good link.

    LVL 3

    Expert Comment

    Sorry, I was a bit hasty in supplying you with the information about Auto Accept. I investigated the problem a bit more and found some information about the problem you're having.

    What version of Exchange are you using? Which service pack?

    If you have a front-end/back-end topology, does this happen when you logon directly to the back-end OWA.

    The error might also be caused by dublicate Exchange System Attendant mailboxes on the server you're using. Use Exchange System Manager to check. If you have two, delete one of them.

    You should also check the registry key on the server specied in the error message HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeFBPublish\Pa­rameters\<server_name>, check the registry key SystemAttendantDN. The value should look like this:

    /o=<Your Organization>/ou=<Your AdministrativeGroup>/cn=Configuration/cn=Servers/cn=<server_name>/cn=Micros­o
    ft System Attendant

    Lastly, start ADSI Edit on the server specified on the error message
    Expand Configuration, CN=Configuration,DC=<domain>,DC=<com> -> CN=Services -> CN=Microsoft Exchange  -> CN=<Organization Name>  -> CN=Administrative Groups  -> CN=<First Administrative Group>  -> CN=Servers CN=<Server Name>.

    Open Microsoft System Attendant Properties. Under Attributes click ProxyAddresses. Make sure there's a valid email address there.


    LVL 1

    Author Comment

    Thank you Kristofer!
    I have back/front end topology.
    2 servers 5.5 Backend
    2 servers 2003 SP2 backend  
    1 server 2003 SP2 frontend (OWA)

    Dublicate Exchange System Attendant accounts sounds good…I will check on this now…Let you know!

    LVL 1

    Author Comment

    Yes…I have 5 System Attendant accounts on each server. Which one I should keep or should keep all? If so, how I delete the one I don’t need?

    Thanks again!
    LVL 3

    Accepted Solution

    You should be able to check the different System Attendant mailboxes using Exchange System Manager. The System Manager mailbox is used for:

    Processing server monitor messages
    Updating free/busy calendar information for Microsoft Office® Outlook Web Access users
    Processing Mailbox Manager notifications
    Moving mailboxes to other databases

    So the correct mailbox should be last logged on by NT AUTHORITY\SYSTEM at the last time any of the above things happened or when the server was last restarted. According to my tests, you shouldn't even be able to remove the correct mailbox, only the extra ones.

    Make sure you have a current backup before trying and try removing the extra mailboxes first on the server that was mentioned in the error message.


    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Looking for New Ways to Advertise?

    Engage with tech pros in our community with native advertising, as a Vendor Expert, and more.

    Find out how to use dynamic social media in email signatures with this top 10 DOs & DON’Ts.
    ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
    In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
    To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

    737 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    22 Experts available now in Live!

    Get 1:1 Help Now