Please Read: Significant Update Planned, Migrating Forum Software This Month

See more
See less

OMA error

  • Filter
  • Time
  • Show
Clear All
new posts

  • OMA error

    I configured oma and it was working fine. Now whenever I try to log in to oma I recieved this error message
    Runtime Error

    Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

    Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

    <!-- Web.Config Configuration File --><configuration> <system.web> <customErrors mode="Off"/> </system.web></configuration>
    Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

    <!-- Web.Config Configuration File --><configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web></configuration>

    Do any one got solution of this problem. I read on one internet forum that deleting exchange virtual directories in IIS and restarting exchange server will create those virtual directories back automatically and oma will start working. I tired that solution but did not help. Even it didnot create virtual directories back. I had to configure them by myself again. Please help me in this issue

  • #2
    Re: OMA error

    The lack of recreation of the virtual directories is an issue.
    What instructions did you follow?

    Should have been these:

    The most common reason for the error you have posted is a net framework version issue - with net framework 2.0 set, when Exchange 2003 is a net framework 1.1 application. Net framework 2.0 is NOT backwards compatible.

    However you need to look at why the directories did not recreate. Follow the instructions from Microsoft again.

    Simon Butler
    Exchange MVP

    More Exchange Content:
    Exchange Resources List:
    In the UK? Hire me:

    Sembee is a registered trademark, used here with permission.