Results 1 to 7 of 7

Thread: I'm going nuts, and I give up, please help. OWAADMIN sucks

  1. #1
    Mostro Guest

    I'm going nuts, and I give up, please help. OWAADMIN sucks

    Server Error in '/OWAAdmin' Application.
    --------------------------------------------------------------------------------

    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".




    <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.




    <configuration>
    <system.web>
    <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
    </configuration>





    the above is all I get from my windows xp pro machine when I try to run
    owaadmin

  2. #2
    Mostro Guest
    I also get this when I try to run it directly from the server.
    Server Error in '/OWAAdmin' Application.
    --------------------------------------------------------------------------------

    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".



    <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.



    <configuration>
    <system.web>
    <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
    </configuration>

  3. #3
    Mostro Guest
    actually I pasted the wrong thing, this what I get when tying to run
    owaadmin directly from the server.


    Server Error in '/OWAAdmin' Application.

    --------------------------------------------------------------------------------

    Access is denied.
    Description: An unhandled exception occurred during the execution of the
    current web request. Please review the stack trace for more information
    about the error and where it originated in the code.

    Exception Details: System.ApplicationException: Access is denied.

    Source Error:

    An unhandled exception was generated during the execution of the
    current web request. Information regarding the origin and location of the
    exception can be identified using the exception stack trace below.



    Stack Trace:

    [ApplicationException: Access is denied.]
    System.Security.Principal.WindowsIdentity._Resolve Identity(IntPtr userToken)
    +0 System.Security.Principal.WindowsIdentity.get_Name () +71
    System.Web.Configuration.AuthorizationConfigRule.I sUserAllowed(IPrincipal
    user, String verb) +106
    System.Web.Configuration.AuthorizationConfig.IsUse rAllowed(IPrincipal user,
    String verb) +81 System.Web.Security.UrlAuthorizationModule.OnEnter (Object
    source, EventArgs eventArgs) +181
    System.Web.SyncEventExecutionStep.System.Web.HttpA pplication+IExecutionStep.Execute()
    +60 System.Web.HttpApplication.ExecuteStep(IExecutionS tep step, Boolean&
    completedSynchronously) +87




    --------------------------------------------------------------------------------

    Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET
    Version:1.1.4322.2032

  4. #4
    Steve Carr Guest
    do you have it installed on the Exchange server as a virtual directory on
    the Default Web Site? Do you have the security type set to Basic
    Authentication? It has to be on Basic Authentication and set as it's own
    application (I'm guessing that Basic Auth is the issue based on all the
    Access Denied errors).

  5. #5
    Mostro Guest
    I have it set up in the default web site. Dont know if as a virtual
    directory.

  6. #6
    Steve Carr Guest
    what is the security set to?
    You can tell a subfolder is a virtual directory configured as it's own
    application by looking at the icon, is it a big open package looking thing?

  7. #7
    Join Date
    Sep 2006
    Location
    Qatar
    Posts
    1

    OWAADMIN

    in windows server 2003

    install the update ASP.NET version 2.0.50727
    click start Programs then
    Administrative Tools

    click
    Internet Information Services (IIS) Manager

    Expand --- web sites- again ---expand ---- Default Web Site
    Right Click on ----OWAAdmin---- go to--- ASP.NET ----

    Tabe at teh ---ASP.NET --- version select 2.0.50727 then click OK and thats it!


    you have done

Similar Threads

  1. Problem with owaadmin
    By ibrahim najmi in forum Clients
    Replies: 1
    Last Post: 11-15-2005, 04:09 PM
  2. owaadmin install fail
    By Henry in forum Administration
    Replies: 3
    Last Post: 08-30-2005, 09:58 AM
  3. Replies: 5
    Last Post: 05-16-2005, 11:13 PM
  4. OWAadmin stop working after SP1
    By ddg in forum Administration
    Replies: 0
    Last Post: 04-19-2005, 06:36 AM
  5. Troubles with OWA since OWAADMIN installed
    By flo in forum Administration
    Replies: 0
    Last Post: 01-29-2005, 06:31 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Other forums: Access Forum - Microsoft Office Forum - CAD Forum