locked
IIS MP Discovery errors ("The handle is invalid") RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    We have IIS MP 6.0.6539.0 installed. Sometimes this mp generates discovery-related errors like:

    Error doing IIS Discovery
 
Error: 0x80070006 
Details: The handle is invalid.
 

One or more workflows were affected by this.  

Workflow name: Microsoft.Windows.InternetInformationServices.2003.DiscoverWebApplications26to50 
Instance name: IIS Web Server 
Instance ID: {84A36108-A46C-8FB3-94E1-033C6234B2A1}

    This error appears only on W2K3 servers, looks like MP for 2008 works normally. IIS works OK on those servers. Application, System and Operations Manager logs doesn't contain any error or warning events except this error (source is Health Service Modules, event id is 31803)

    All of the servers are x86 with SP2 installed.


    I try to search same errors and solutions and cannot find anything that can resolve this error

    Tuesday, June 9, 2009 10:17 AM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    This is a known issue we are investigating/working on.

    Basically under *some* load conditions on IIS under W2K3 we can get an intermittent invalid handle back from an API call. We are logging an alert instead of retrying the operation.

    The error itself while annoying, is non-fatal and does not stop discovery from happening.

    At worst the discovery of those components will be delayed until next discovery interval, at which point they will be picked up.

    Nathan Downey [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. Use of attachments are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
    Tuesday, June 9, 2009 11:13 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    This is a known issue we are investigating/working on.

    Basically under *some* load conditions on IIS under W2K3 we can get an intermittent invalid handle back from an API call. We are logging an alert instead of retrying the operation.

    The error itself while annoying, is non-fatal and does not stop discovery from happening.

    At worst the discovery of those components will be delayed until next discovery interval, at which point they will be picked up.

    Nathan Downey [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. Use of attachments are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
    Tuesday, June 9, 2009 11:13 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks!
    We will wait the new version of the MP :)
    Wednesday, June 10, 2009 5:22 AM