locked
event id 33019 RRS feed

  • Question

  • This event log has been logged since the beginning of monitoring on this particular server - Windows 2008 R2, IIS 7. Only 1 website on this server. But every day I get a warning saying failed to perform website discovery. The Runas account is the local system account which has proper rights. I also gave the actual runasaccount rights just in case. The MP is Windows 2008 Server IIS7, 6.0.7600.0.

    Any suggestions please?

    Sunday, August 7, 2011 11:51 PM

Answers

  • I found a fix to my problem.  Hopefully it can help the OP or someone else in the future.  My issue had to do with the 'system.web.extensions' having a .NET 3.5 config while the machine.config was 4.0.  Changing the system.web.extensions to 4.0 in the web.config resolved the issue.  See below for the reference I used:

    http://www.asp.net/learn/whitepapers/aspnet4/breaking-changes

    • Proposed as answer by Dan7040 Friday, September 9, 2011 2:52 PM
    • Marked as answer by Dan Rogers Friday, September 9, 2011 3:46 PM
    Friday, September 9, 2011 2:52 PM

All replies

  • Hi

    The Alert usually gives more information about what to check - is there more information in the operationsmanager eventlog on the IIS Server.

    Cheers

    Graham


    New SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
    Monday, August 8, 2011 8:06 AM
  •  

    Hi,

     

    Regarding this event, I got the following information and would like to share with you for your reference:

     

    Event ID 33019 on IIS MP Version 6.0.7600

    http://social.technet.microsoft.com/Forums/en-us/operationsmanagergeneral/thread/47b65081-88b8-4dfd-a005-908581547952

     

    Event Log Rules for a Management Pack

    http://technet.microsoft.com/en-us/library/dd539393.aspx

     

    Meanwhile, please also verify the settings and configurations referring to the management pack as well as Kevin’s post:

     

    Windows Server Internet Information Services 7 Management Pack for System Center Operations Manager 2007

    http://www.microsoft.com/download/en/details.aspx?id=9815

     

    New IIS7 MP ships – support for Server 2008 R2 and IIS 7.5

    http://blogs.technet.com/b/kevinholman/archive/2010/02/09/new-iis7-mp-ships-support-for-server-2008-r2-and-iis-7-5.aspx

     

    Hope this helps.

     

    Thanks.
    Nicholas Li - MSFT
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, August 9, 2011 9:06 AM
  • Details of Warning..below is all i have - not much. I also have the same type of alert on my ftp site. 

    Both from Windows Server IIS 7 MP 6.0.7600.0

    Website:
    Error reading properties of website "sitename".
    Error 0x80070032
    Alert Rule - Failed to perform website discovery
    Details - the request is not supported.
    Workflow name: Microsoft.Windows.InternetInformationServices.2008.Discover96To100WebSites
    Instance name - IIS Web Server.
    Causes - either a corrupt IIS config.,or incorectly configured website.

    FTP Site:
    Event Description: Failed to retrieve the state of the following site: 'Default Web Site'. The operation will be retried.
    RESULT: 0x800710d8
    Details: The object identifier does not represent a valid object.
    One or more workflows were affected by this.
    Workflow name: Microsoft.Windows.InternetInformationServices.2008.WebSite.WebSiteStatusCheck.Monitor
    Instance name: Default Web Site
    Instance ID: {54477847-E883-9656-C68E-AAFC297948C2}

    Management group: FSS

    • Edited by LM0111 Tuesday, August 9, 2011 6:58 PM
    Tuesday, August 9, 2011 6:51 PM
  • This would happen if the web site rejects the calls. The tricky part here is that this discovery kicks in after the 95th web site is discovered.  It is very possible that one of your sites is configured incorrectly and causing this problem.
    Microsoft Corporation
    Tuesday, August 9, 2011 6:54 PM
  • Configured incorrectly how?  The site is online and operating as it should operate.
    Tuesday, August 9, 2011 7:54 PM
  • Hard to tell.  If you have over 95 sites, it is hard to say for certain that all of them respond to the configuration query without error.  You would need to review the configuraiton of each web site on that server to make sure it is not improperly configured.
    Microsoft Corporation
    Tuesday, August 9, 2011 8:43 PM
  • Whoa! We dont have 95 websites though!  There 1 website on this iis server and 1 ftp site on another ftp server. Our entire environment has maybe 20 websites total (varying between IIS7 and IIS6).

     

    Tuesday, August 9, 2011 9:32 PM
  • I am experiencing the same issue on our 4 identically configured webservs.  Each server has only 2 sites.  I receive the following two errors:

     

    Error: 0x80070032

    Details: The request is not supported.

    One or more workflows were affected by this.


    Workflow name: Microsoft.Windows.InternetInformationServices.2008.Discover24To32WebSites

    Instance name: IIS Web Server

    Instance ID: {84E84A8F-07AF-6F32-242D-D5CE829A5111}

    Error: 0x80070032

    Details: The request is not supported.

    One or more workflows were affected by this.


    Workflow name: Microsoft.Windows.InternetInformationServices.2008.Discover56To64WebSites

    Instance name: IIS Web Server

    Instance ID: {CC9E8411-BFF5-EDBE-0B93-3BE63333BF3B}

    All servers are IIS 7.  Not certain, but the problem seemed to arise after converting our Application Pools to 4.0. Did Microsoft or the OP find a solution?

     

    Thanks

    • Proposed as answer by Dan7040 Friday, September 9, 2011 2:48 PM
    • Unproposed as answer by Dan7040 Friday, September 9, 2011 2:48 PM
    Wednesday, September 7, 2011 3:35 PM
  • I found a fix to my problem.  Hopefully it can help the OP or someone else in the future.  My issue had to do with the 'system.web.extensions' having a .NET 3.5 config while the machine.config was 4.0.  Changing the system.web.extensions to 4.0 in the web.config resolved the issue.  See below for the reference I used:

    http://www.asp.net/learn/whitepapers/aspnet4/breaking-changes

    • Proposed as answer by Dan7040 Friday, September 9, 2011 2:52 PM
    • Marked as answer by Dan Rogers Friday, September 9, 2011 3:46 PM
    Friday, September 9, 2011 2:52 PM
  • This is good information.  Thanks Dan.
    Microsoft Corporation
    Friday, September 9, 2011 3:46 PM