In addition to following the instructions on all of the KB articles noted above, I also followed these instructions:http://www.ureader.com/message/47285.aspx Aug 13, 2008 3:45 PM Helpful (0) Reply options Link to this Verify that the Exchange mailbox Server is working correctly. So you need to make sure ExchangeVDir points to /exchange-oma. We only had the issue on our Exchange 2003 SP2 back-end clusters. http://chatflow.net/event-id/event-id-9646-exchange-2013.html
If the problem persists, contact your administrator. We show this process by using the Exchange Admin Center. Join & Ask a Question Need Help in Real-Time? As you finish projects in Quip, the work remains, easily accessible to all team members, new and old. - Increase transparency - Onboard new hires faster - Access from mobile/offline Try
I also tried to create a another VirtualDir like explained here: http://www.petri.co.il/problems_with_forms_based_authentication_and_ssl_in_activesync.htm But I still receive the same errors. Simon. 0 Message Author Comment by:kitkit201 ID: 162509712006-03-21 Hi Simon- Does OMA work? -->OMA works on a PC and works on the mobile we are trying to configure (Tmobile MDA) Solution: 1.Start the Internet Information Services (IIS) Microsoft Management Server (MMS) snap-in on the Windows SBS 2003-based computer. 2.Expand Server_Name\Web Sites\Default Web Site. 3.Right-click Exchange-OMA, and then follow these steps: 1.Verify
All rights reserved. The article suggested "In almost every circumstance, it is faster and more reliable to restore from a backup than to perform a hard repair on the database. ” Should I do We show this process by using the Exchange Admin Center. There is no delete menu item in the right click menu.
After removing the alias IP addresses the error went away and mobile phones could sync with the Exchange server again. Microsoft Kb Article 817379 I followed those instructions when I setup the server at the first time. From the server event log, I see constantly blow error message. I increased the user's mailbox limit and asked the user to clean up, then restored original limit.
On the web site tab select "Advanced" 6. United States Copyright © Apple Inc. In the Value data box, you must enter a forward slash (/) following by exchange-oma. Thanks Comment by Stepan -- February 6, 2013 @ 3:44 pm | Reply I shall correct my day-old comment.
First set the Primary email address of the users mailbox. 2. The users can use OWA and OMA without any issues. Event Id 3005 Exchange 2013 I checked with KB937635 that my exchange virtual dirs are correctly set. There's a note for SBS 2003 server, that /exchange-oma is already configured.
Restart IIS Admin Service. (Open command prompt, type "iisreset" and hit enter) x 53 Homer T. Check This Out I am estatic this finally worked out... Exchange iPhone Exchange 2013: Creating an Accepted Domain Video by: Gareth In this video we show how to create an Accepted Domain in Exchange 2013. The CommManager has the Microsoft DirectPush button.
Forum Software © ASPPlayground.NET Advanced Edition Help Register Log in Remember Me? A: Exchange Server ActiveSync and Exchange OMA use the Exchange virtual directory to access the user's mailbox which is located on OWA templates and DAV on Exchange back-end servers, Exchange running This is also to be expected (or so I've read).- I've tried putting the domain in my username and leaving it out, and I've tried deleting and recreating the mail configuration Source Restarted IIS and then my co-worker informed me that it just started to work.
Engineer This what fixed it for me on two different 2003 servers: 1. One of the userswas synchronizing with an iPhone with no trouble, the other could not get Active Sync to work on the iPhone. However with the requirement for SSL off, but only port 443 open, everything works correctly.
Forcing SSL on the /exchange virtual folder breaks EAS. Creating exchange-oma fixed the problem. I would suppose that other measures, deleting and recreating his mailbox would have worked, too (offload Outlook items to a PST file first). I upgraded my system to 2003 all of them without a hitch.
Aug 10, 2008 4:27 AM Helpful (0) Reply options Link to this post by snottywong, snottywong Aug 13, 2008 3:45 PM in response to snottywong Level 1 (0 points) Aug 13, We tried some other items and that killed OWA and we had to roll back. Apply fix ME817379 2. have a peek here Went through the various (excellent) IIS configuration check posts available here and on the Internet to no effect.
And I noticed that only the IPhone users are unable to connect to the Exchange server 2003. It makes an internal communication over http to the /exchange virtual folder. Contact your Exchange Server administrator. Maybe you ran into something this week that could shed some more light on this situation.