locked
HTTP 503 Error.The module c:\windows\system32\inetsrv\iisetw.dll failed to load. The data is the error RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    We have Exchange 2007 CAS server running on windows 2008 R2 Server. Lastweek our c drive went full and then after this we are getting HTTP 503 Error when we access our webmail. When we check the eventviewer we are getting this message

    HTTP 503 Error.The module c:\windows\system32\inetsrv\iisetw.dll failed to load. The data is the error

    The application pools are not starting.

    Pls help to fix this

    SI

    Wednesday, July 17, 2013 3:23 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    HTTP 503 Error.The module c:\windows\system32\inetsrv\iisetw.dll failed to load.

    This error is related to IIS. You may refer to this post:  IIS 7 Service Unavailable 503

    http://forums.iis.net/t/1164908.aspx

     

    For IIS query, please ask here:

    http://forums.iis.net/

    TechNet Subscriber Support |If you have any feedback on Technet forum, please contact tnmff@microsoft.com.

    Thursday, July 18, 2013 3:20 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You should rather post it in Exchange Forums.

    Can you open IIS Console and make sure all the Application Pools (Under Server Name), are started?

    Then try to access /owa

    Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

    Thursday, July 18, 2013 5:21 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    HTTP 503 Error.The module c:\windows\system32\inetsrv\iisetw.dll failed to load.

    This error is related to IIS. You may refer to this post:  IIS 7 Service Unavailable 503

    http://forums.iis.net/t/1164908.aspx

     

    For IIS query, please ask here:

    http://forums.iis.net/

    TechNet Subscriber Support |If you have any feedback on Technet forum, please contact tnmff@microsoft.com.

    Thursday, July 18, 2013 3:20 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You should rather post it in Exchange Forums.

    Can you open IIS Console and make sure all the Application Pools (Under Server Name), are started?

    Then try to access /owa

    Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

    Thursday, July 18, 2013 5:21 AM