Announcement

Collapse
No announcement yet.

OMA breaks ActiveSync

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

  • OMA breaks ActiveSync

    Ok, so got a tough one here...and Google is no help

    I can't get OMA working and started to try and resolve it.

    I deleted Exchange directories and re-created using KB883380
    This re-created OMA runing ASP.NET v2
    If I revert OMA to v1.1, OMA works but breaks ActiveSync
    Putting OMA back to v2 fixes ActiveSync and breaks OMA

    vdir "exchange-oma" is in place and working (KB817379)

    Is this typical?

    I guess you really wouldn't need both working, but it would be nice to have a fix.

    Any ideas?

    One side note...not sure if it's the cause:
    I updated this Exchange 2003 server to run .NET 3.5 but still have v1.1 and v2 frameworks installed.

    Thanks!

  • #2
    Re: OMA breaks ActiveSync

    No part of Exchange 2003 is .net framework 2.0 compatible. Therefore that is your first problem. .net framework is not backwards compatible. They are effectively seperate applications. All of the Exchange virtual directories should be set to version 1.1. If the reset procedure is setting them to 2.0 then something else is wrong with the server unconnected to Exchange. Certainly nothing in Exchange 2003 should work with net framework 2.0 selected.

    817379 also has some flaws in its configuration and can actually fail to work correctly. Therefore I would suggest that you undo those changes, reset the folders again. Then before making any changes to the web site, test it again. Do ensure that the require SSL open is not set on every virtual directory as that can cause problems.

    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


    • #3
      Re: OMA breaks ActiveSync

      First, thanks for replying in both forums!

      Tried your advice:
      - Removed 817379KB mods
      - Reset IIS directories (This still put OMA at .NET v2)

      I tried two different ways to get back to v1.1
      - went to vdir properties of OMA
      - used aspnet_regiis -sn W3SVC/1/ROOT/OMA

      Still no luck. So, I reset the directories, followed 817379, and ActiveSync works again...but /oma does not.

      Do you know which directories require SSL? Maybe that would help.
      From what I see, only "Exchange" and "Public" require SSL.

      Also, do you think installing .NET 3.5 could cause these issues?

      Many thanks.

      Comment


      • #4
        Re: OMA breaks ActiveSync

        No part of Exchange requires the setting "require SSL". I do not set that setting on any site I manage because I don't simply don't need to - as port 80 isn't open on the firewall.

        .net framework 3.5 would not have caused the problem. I have that on a number of sites.

        When you reset the virtual directories, are they going back to 1.1 or staying with 2.0? If they are being changed to 2.0 then something else is doing that. Anything else installed on the server that could be making that change?

        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

        Working...
        X