RE: Unable to get OMA working

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Frans (Frans_at_discussions.microsoft.com)
Date: 08/31/04


Date: Tue, 31 Aug 2004 09:33:17 -0700

Paul (and others)

I had the same problem after a fresh install of Exchange 2003 + SP1.
Everything worked fine except OMA and Server Active Sync. Reinstalling Device
Update 4 didn't change a thing. Your post indirectly did lead me to the
solution:

It seems OMA wants to connect to the /exchange virtual directory on port 80
(See IIS log). Since OWA was configured for SSL access only (as recommended)
OMA cannot connect to the user's mailbox and you'll get the 403 error.
So I configured the /exchange virtual directory to NOT require SSL (in my
case the firewall forces the users to connect on 443 so that's not a real
problem) and OMA works fine!

"Paul Cotgrove" wrote:

> Hi
>
> I have had untold issues trying to get OMA working from an
> out-of-the-box installation of Exchange 2003. My configuration is a
> single server running Windows Server 2003 with all relevant
> WindowsUpdate hotfixes applied, Exchange 2003, EXCH2003 SP1 and
> associated hotfixes.
>
> OWA works like a dream and Exchange works superbly in all other
> aspects of its operation, i.e. SMTP, POP3, etc.
>
> I started to configure OMA as follows:
>
> Enable the Mobile Access within the ESM Global properties also
> allowing unsupported devices - enabled users with AD for Mobile Access
>
> This gave me a 403 failure after authentication so I read a few
> technet articles and removed and reinstalled the .NET framework 1.1
> Mobile Device Support 4.0
>
> This moved me on to an error which basically said that my mailbox
> could not be located - back to technet where I found an article
> telling me to correct the VirtualDir name in a registry string value.
> This value did not exist so I created it which lead me to the
> following error:
>
> Item no longer exists. The item you are attempting to access may have
> been deleted or moved.
>
> Again, I have read many articles within these newsgroups and chased
> links to technet articles that dont appear to exist anymore, even
> though this product is only a year or so old!!!!
>
> Anyway, one article I read said that the path for the OMA virtual
> directory should point to the same location as the Exchange virtual
> directory, something along the lines of
> \\.\BackOfficeStorage\mydomain.co.uk\mbx where mydomain.co.uk is the
> organisation that I have installed.
>
> Currently, the path is set to C:\Program Files\Microsoft
> Exchange\blah\blah\OMA\browse and I am seeing files in this location.
>
> When I point the path to \\.\BackOfficeStorage\mydomain.co.uk\mbx
> there are no files there and all I get is 404 Page not founds!!
>
> Does anybody have any idea why this is proving to be such a pain to
> get working? Also, can someone shed some light on the missing technet
> articles on the MS site?
>
> Many thanks in advance to anyone who can assist with this, I have no
> more hair to pull out!!!
>



Relevant Pages

  • Re: Unable to get OMA working
    ... using a Front End Server and with an out of the box Win2k3 ... (OMA) ... >> technet articles and removed and reinstalled the .NET ... Exchange virtual ...
    (microsoft.public.exchange.connectivity)
  • RE: OMA not accessible
    ... If this is not the case, your Exchange ... Microsoft Outlook or Microsoft Outlook Web Access to create your user ... This problem may occur if the Exchange Server 2003 computer is heavily ... the OMA virtual directory may corrupted on SBS. ...
    (microsoft.public.windows.server.sbs)
  • Re: OMA will not work, argh!!! Please HELP
    ... the "URL that OMA builds"? ... that mail is my server and not mail.mycompany.com? ... > If you have modified the HTTP identities then make sure you either go back ... >> Request from user XXX@xxxxxxx resulted in the Microsoft ...
    (microsoft.public.exchange.setup)
  • Re: OMA/ActiveSync debugging
    ... Here is what I associated with an OMA connect attempt in the HTTPERR log: ... Can I conclude that the inability to locate PropFind is causing my problem ... "Was the server a DC and you demoted it to a member server?" ... "Does OWA work?" ...
    (microsoft.public.exchange.admin)
  • Re: Exchange-oma
    ... Is this why I cannot run OWA and OMA? ... CEICW and told the server to open access to everything (OWA, OMA). ... I would like to kindly let you know that in SBS ...
    (microsoft.public.windows.server.sbs)