From the metabase file, it appears this issue has something to do with the
installation of Sql server reporting service
Normally after installing reporting service, we can go to "Reporting Service
Configuration" tool to configure the virtual directory for Report Server and
Report Manager under a given Website.
Somehow for this case, I see Report Server and Report Manager are also
<IIsConfigObject Location="/LM/W3SVC/6" />
<IIsConfigObject Location="/LM/W3SVC/6/Root" />
<IIsWebVirtualDir Location="/LM/W3SVC/6/Root/Reports" AccessFlags ..>
When WSUS setup traverse the metabase to look for Websites, it also
traverses at this <IISConfigObject> node, for which the Keytype attribute is
not of type INHERIT, thus the detection logic bailed out.
I wonder how you configure the reporting service that resulted in the vdir
being configured under the location of <IIsConfigObject> rather than a
website (<IIsWebServer>) ?
For now, the workaround will be to configure the vdirs for reporting
services to be under an existing web sites on IIS using "Reporting Service
Configuration" tool , then do the following:
1. cd /d C:\Inetpub\AdminScripts
2. C:\Inetpub\AdminScripts>adsutil.vbs Delete /w3svc/6
3. restart IIS service.
This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
"APlus" < XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...