Monitoring and Reporting showing "Page cannot be displayed"

I took over support for this SBS 2003 Standard R1 with SP1.

Monitoring and Reporting and Backups were not configured. Despite three
NICs being installed in the SBS 2003 server, only one is in use. (I could go
on, but...)

When I tried to get a report, I got a "page cannot be displayed". I ran the
setup, and I got an email the next day saying 404 NOT FOUND.

I have tried the steps previously mentioned in similar strings: I have
uninstalled Monitoring and Reporting, removing registry entries and folders,
and rebooted, and reinstalled Monitoring and Reporting. I have rerun the
setup for Monitoring again. I have re-registered the mof files.

Still no joy.

On Aug 2, 10:32 am, Greg Kirkpatrick
<GregKirkpatr...@discussions.microsoft.com> wrote:
> I took over support for this SBS 2003 Standard R1 with SP1.
>
> Monitoring and Reporting and Backups were not configured. Despite three
> NICs being installed in the SBS 2003 server, only one is in use. (I could go
> on, but...)
>
> When I tried to get a report, I got a "page cannot be displayed". I ran the
> setup, and I got an email the next day saying 404 NOT FOUND.
>
> I have tried the steps previously mentioned in similar strings: I have
> uninstalled Monitoring and Reporting, removing registry entries and folders,
> and rebooted, and reinstalled Monitoring and Reporting. I have rerun the
> setup for Monitoring again. I have re-registered the mof files.
>
> Still no joy.

Im having the same issue. I hope someone has a resolution to this.

Hi Greg,

You've gone through these steps?

http://msmvps.com/blogs/bradley/arch.../12/83381.aspx
------------------------------------------------------------
Both the Monitoring and Reporting email and the console display an HTTP 404
error.

CAUSE
--------
The Web Request is redirect by stsfltr ISAPI filter bound to Default Web
Site. However, there is no "Windows SharePoint Services" Web Service
Extensions for stsfltr filter, so, the owssvr.dll cannot be found and 404
NOT FOUND error is given in this situation.

RESOLUTION
---------------
I. Set the ISAPI filter for Default website to default.
1. Open the IIS console and open the properties page of Default Web Site
2. Click to select ISAPI Filters
3. Please delete the stsfltr Filter. The correct and default filters are
listed as followings

SBSFLT C:\inetpub\sbsflt\sbsflt.dll
Fpexedll.dll C:\Program Files\Common Files\Microsoft Shared\Web
Server Extensions\50\bin\fpexedll.dll
OwaLogon C:\Program Files\Exchsrvr\ExchWeb\bin\auth\OwaAuth.dll

II. Use the following steps to create correct Web Service Extensions.
1. Open IIS, and select Web Service Extensions,
2. Right click "Web Service Extensions" and select Add a new Web Service
extension...
3. Specify "Windows SharePoint Services" as the Extension name.
4. Click Add to add the following DLL to the list.

Program Files\Common Files\Microsoft Shared\web server
extensions\60\ISAPI\_VTI_ADM\admin.dll
Program Files\Common Files\Microsoft Shared\web server
extensions\60\ISAPI\_VTI_AUT\author.dll
Program Files\Common Files\Microsoft Shared\web server
extensions\60\ISAPI\owssvr.dll
Program Files\Common Files\Microsoft Shared\web server
extensions\60\ISAPI\shtml.dll

4. Check Set extension status to Allowed, and then click OK.
------------------------------------------------------------

--
Merv Porter [SBS-MVP]
============================

"Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
message news:7CA5E929-96BA-4649-A307-F020552ED89E@microsoft.com...
>I took over support for this SBS 2003 Standard R1 with SP1.
>
> Monitoring and Reporting and Backups were not configured. Despite three
> NICs being installed in the SBS 2003 server, only one is in use. (I could
> go
> on, but...)
>
> When I tried to get a report, I got a "page cannot be displayed". I ran
> the
> setup, and I got an email the next day saying 404 NOT FOUND.
>
> I have tried the steps previously mentioned in similar strings: I have
> uninstalled Monitoring and Reporting, removing registry entries and
> folders,
> and rebooted, and reinstalled Monitoring and Reporting. I have rerun the
> setup for Monitoring again. I have re-registered the mof files.
>
> Still no joy.

Perhaps this will help
http://www.smallbizserver.net/Defaul...1&postid=23955

--
Cris Hanna [SBS-MVP]
-------------------------------------------------
Microsoft MVPs
Independent Experts (MVPs do not work for MS)
Real World Answers
---------------------------------------------------------
Please do not contact me directly regarding issues

"Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in message news:7CA5E929-96BA-4649-A307-F020552ED89E@microsoft.com...
I took over support for this SBS 2003 Standard R1 with SP1.

Monitoring and Reporting and Backups were not configured. Despite three
NICs being installed in the SBS 2003 server, only one is in use. (I could go
on, but...)

When I tried to get a report, I got a "page cannot be displayed". I ran the
setup, and I got an email the next day saying 404 NOT FOUND.

I have tried the steps previously mentioned in similar strings: I have
uninstalled Monitoring and Reporting, removing registry entries and folders,
and rebooted, and reinstalled Monitoring and Reporting. I have rerun the
setup for Monitoring again. I have re-registered the mof files.

Still no joy.

OK the article from Chris solved my problem. I needed to add in 127.0.0.1 IP
to the default web site.

"Cris Hanna [SBS-MVP]" wrote:

> Perhaps this will help
> http://www.smallbizserver.net/Defaul...1&postid=23955
>
> --
> Cris Hanna [SBS-MVP]
> -------------------------------------------------
> Microsoft MVPs
> Independent Experts (MVPs do not work for MS)
> Real World Answers
> ---------------------------------------------------------
> Please do not contact me directly regarding issues
>
> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in message news:7CA5E929-96BA-4649-A307-F020552ED89E@microsoft.com...
> I took over support for this SBS 2003 Standard R1 with SP1.
>
> Monitoring and Reporting and Backups were not configured. Despite three
> NICs being installed in the SBS 2003 server, only one is in use. (I could go
> on, but...)
>
> When I tried to get a report, I got a "page cannot be displayed". I ran the
> setup, and I got an email the next day saying 404 NOT FOUND.
>
> I have tried the steps previously mentioned in similar strings: I have
> uninstalled Monitoring and Reporting, removing registry entries and folders,
> and rebooted, and reinstalled Monitoring and Reporting. I have rerun the
> setup for Monitoring again. I have re-registered the mof files.
>
> Still no joy

Merv, I think I have gone through the steps in Susan Bradley's blog, but I
cannot confirm it right now, as her blog is down for the moment.

I did, however, follow the steps under section I in your message's
RESOLUTION section. Section II was not necessary, as the extensions were
already created in just that manner.

Now, I am no longer getting a "Page cannot be displayed" when I click on
Monitoring and Reporting. Instead, I get the header for the Server
Performance Report, along with today's date and time, the Windows Small
Business Server logo, and a PRINT button -- but no data.

Server Performance Report for [logo appears here on
the right]
Report created on 8/2/2007 at 6:59 PM


Chris, I did see that page on the M&M's smallbizserver.net site, and yes, I
applied all the steps suggested, without success.



"Richard K" wrote:

> OK the article from Chris solved my problem. I needed to add in 127.0.0.1 IP
> to the default web site.
>
> "Cris Hanna [SBS-MVP]" wrote:
>
> > Perhaps this will help
> > http://www.smallbizserver.net/Defaul...1&postid=23955
> >
> > --
> > Cris Hanna [SBS-MVP]
> > -------------------------------------------------
> > Microsoft MVPs
> > Independent Experts (MVPs do not work for MS)
> > Real World Answers
> > ---------------------------------------------------------
> > Please do not contact me directly regarding issues
> >
> > "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in message news:7CA5E929-96BA-4649-A307-F020552ED89E@microsoft.com...
> > I took over support for this SBS 2003 Standard R1 with SP1.
> >
> > Monitoring and Reporting and Backups were not configured. Despite three
> > NICs being installed in the SBS 2003 server, only one is in use. (I could go
> > on, but...)
> >
> > When I tried to get a report, I got a "page cannot be displayed". I ran the
> > setup, and I got an email the next day saying 404 NOT FOUND.
> >
> > I have tried the steps previously mentioned in similar strings: I have
> > uninstalled Monitoring and Reporting, removing registry entries and folders,
> > and rebooted, and reinstalled Monitoring and Reporting. I have rerun the
> > setup for Monitoring again. I have re-registered the mof files.
> >
> > Still no joy

I just tried to rerun Setup Monitoring Reports and Alerts, and after the
Monitoring Configuration Wizard appeared, and I clicked NEXT, the wizard
disappeared, and did not finish.

"Greg Kirkpatrick" wrote:

> Merv, I think I have gone through the steps in Susan Bradley's blog, but I
> cannot confirm it right now, as her blog is down for the moment.
>
> I did, however, follow the steps under section I in your message's
> RESOLUTION section. Section II was not necessary, as the extensions were
> already created in just that manner.
>
> Now, I am no longer getting a "Page cannot be displayed" when I click on
> Monitoring and Reporting. Instead, I get the header for the Server
> Performance Report, along with today's date and time, the Windows Small
> Business Server logo, and a PRINT button -- but no data.
>
> Server Performance Report for [logo appears here on
> the right]
> Report created on 8/2/2007 at 6:59 PM
>
>
> Chris, I did see that page on the M&M's smallbizserver.net site, and yes, I
> applied all the steps suggested, without success.
>
>
>
> "Richard K" wrote:
>
> > OK the article from Chris solved my problem. I needed to add in 127.0.0.1 IP
> > to the default web site.
> >
> > "Cris Hanna [SBS-MVP]" wrote:
> >
> > > Perhaps this will help
> > > http://www.smallbizserver.net/Defaul...1&postid=23955
> > >
> > > --
> > > Cris Hanna [SBS-MVP]
> > > -------------------------------------------------
> > > Microsoft MVPs
> > > Independent Experts (MVPs do not work for MS)
> > > Real World Answers
> > > ---------------------------------------------------------
> > > Please do not contact me directly regarding issues
> > >
> > > "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in message news:7CA5E929-96BA-4649-A307-F020552ED89E@microsoft.com...
> > > I took over support for this SBS 2003 Standard R1 with SP1.
> > >
> > > Monitoring and Reporting and Backups were not configured. Despite three
> > > NICs being installed in the SBS 2003 server, only one is in use. (I could go
> > > on, but...)
> > >
> > > When I tried to get a report, I got a "page cannot be displayed". I ran the
> > > setup, and I got an email the next day saying 404 NOT FOUND.
> > >
> > > I have tried the steps previously mentioned in similar strings: I have
> > > uninstalled Monitoring and Reporting, removing registry entries and folders,
> > > and rebooted, and reinstalled Monitoring and Reporting. I have rerun the
> > > setup for Monitoring again. I have re-registered the mof files.
> > >
> > > Still no joy

Upon login to SBS 2003 with an administrator, I am now getting a Data
Execution Protection error in MCW module (mcw.exe), which closes the program
(3 times).

"Greg Kirkpatrick" wrote:

> I just tried to rerun Setup Monitoring Reports and Alerts, and after the
> Monitoring Configuration Wizard appeared, and I clicked NEXT, the wizard
> disappeared, and did not finish.
>
> "Greg Kirkpatrick" wrote:
>
> > Merv, I think I have gone through the steps in Susan Bradley's blog, but I
> > cannot confirm it right now, as her blog is down for the moment.
> >
> > I did, however, follow the steps under section I in your message's
> > RESOLUTION section. Section II was not necessary, as the extensions were
> > already created in just that manner.
> >
> > Now, I am no longer getting a "Page cannot be displayed" when I click on
> > Monitoring and Reporting. Instead, I get the header for the Server
> > Performance Report, along with today's date and time, the Windows Small
> > Business Server logo, and a PRINT button -- but no data.
> >
> > Server Performance Report for [logo appears here on
> > the right]
> > Report created on 8/2/2007 at 6:59 PM
> >
> >
> > Chris, I did see that page on the M&M's smallbizserver.net site, and yes, I
> > applied all the steps suggested, without success.
> >
> >
> >
> > "Richard K" wrote:
> >
> > > OK the article from Chris solved my problem. I needed to add in 127.0.0.1 IP
> > > to the default web site.
> > >
> > > "Cris Hanna [SBS-MVP]" wrote:
> > >
> > > > Perhaps this will help
> > > > http://www.smallbizserver.net/Defaul...1&postid=23955
> > > >
> > > > --
> > > > Cris Hanna [SBS-MVP]
> > > > -------------------------------------------------
> > > > Microsoft MVPs
> > > > Independent Experts (MVPs do not work for MS)
> > > > Real World Answers
> > > > ---------------------------------------------------------
> > > > Please do not contact me directly regarding issues
> > > >
> > > > "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in message news:7CA5E929-96BA-4649-A307-F020552ED89E@microsoft.com...
> > > > I took over support for this SBS 2003 Standard R1 with SP1.
> > > >
> > > > Monitoring and Reporting and Backups were not configured. Despite three
> > > > NICs being installed in the SBS 2003 server, only one is in use. (I could go
> > > > on, but...)
> > > >
> > > > When I tried to get a report, I got a "page cannot be displayed". I ran the
> > > > setup, and I got an email the next day saying 404 NOT FOUND.
> > > >
> > > > I have tried the steps previously mentioned in similar strings: I have
> > > > uninstalled Monitoring and Reporting, removing registry entries and folders,
> > > > and rebooted, and reinstalled Monitoring and Reporting. I have rerun the
> > > > setup for Monitoring again. I have re-registered the mof files.
> > > >
> > > > Still no joy

I have gone through steps for Issues 1 and 2 on the link you mentioned from
Susan Bradley's blog -- the other issues do not apply for this SBS 2003
server.

"Merv Porter [SBS-MVP]" wrote:

> Hi Greg,
>
> You've gone through these steps?
>
> http://msmvps.com/blogs/bradley/arch.../12/83381.aspx
> ------------------------------------------------------------
> Both the Monitoring and Reporting email and the console display an HTTP 404
> error.
>
> CAUSE
> --------
> The Web Request is redirect by stsfltr ISAPI filter bound to Default Web
> Site. However, there is no "Windows SharePoint Services" Web Service
> Extensions for stsfltr filter, so, the owssvr.dll cannot be found and 404
> NOT FOUND error is given in this situation.
>
> RESOLUTION
> ---------------
> I. Set the ISAPI filter for Default website to default.
> 1. Open the IIS console and open the properties page of Default Web Site
> 2. Click to select ISAPI Filters
> 3. Please delete the stsfltr Filter. The correct and default filters are
> listed as followings
>
> SBSFLT C:\inetpub\sbsflt\sbsflt.dll
> Fpexedll.dll C:\Program Files\Common Files\Microsoft Shared\Web
> Server Extensions\50\bin\fpexedll.dll
> OwaLogon C:\Program Files\Exchsrvr\ExchWeb\bin\auth\OwaAuth.dll
>
> II. Use the following steps to create correct Web Service Extensions.
> 1. Open IIS, and select Web Service Extensions,
> 2. Right click "Web Service Extensions" and select Add a new Web Service
> extension...
> 3. Specify "Windows SharePoint Services" as the Extension name.
> 4. Click Add to add the following DLL to the list.
>
> Program Files\Common Files\Microsoft Shared\web server
> extensions\60\ISAPI\_VTI_ADM\admin.dll
> Program Files\Common Files\Microsoft Shared\web server
> extensions\60\ISAPI\_VTI_AUT\author.dll
> Program Files\Common Files\Microsoft Shared\web server
> extensions\60\ISAPI\owssvr.dll
> Program Files\Common Files\Microsoft Shared\web server
> extensions\60\ISAPI\shtml.dll
>
> 4. Check Set extension status to Allowed, and then click OK.
> ------------------------------------------------------------
>
> --
> Merv Porter [SBS-MVP]
> ============================
>
> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
> message news:7CA5E929-96BA-4649-A307-F020552ED89E@microsoft.com...
> >I took over support for this SBS 2003 Standard R1 with SP1.
> >
> > Monitoring and Reporting and Backups were not configured. Despite three
> > NICs being installed in the SBS 2003 server, only one is in use. (I could
> > go
> > on, but...)
> >
> > When I tried to get a report, I got a "page cannot be displayed". I ran
> > the
> > setup, and I got an email the next day saying 404 NOT FOUND.
> >
> > I have tried the steps previously mentioned in similar strings: I have
> > uninstalled Monitoring and Reporting, removing registry entries and
> > folders,
> > and rebooted, and reinstalled Monitoring and Reporting. I have rerun the
> > setup for Monitoring again. I have re-registered the mof files.
> >
> > Still no joy.
>
>
>

....and MCW (mcw.exe) is, of course, the Monitoring and Reporting Wizard.

As I have already gone through the steps to uninstall Monitoring and
Reporting, and reinstalled it, I'm thinking that some other related process
(SQL?) is preventing its proper execution. Any suggestion?

"Greg Kirkpatrick" wrote:

> Upon login to SBS 2003 with an administrator, I am now getting a Data
> Execution Protection error in MCW module (mcw.exe), which closes the program
> (3 times).
>
> "Greg Kirkpatrick" wrote:
>
> > I just tried to rerun Setup Monitoring Reports and Alerts, and after the
> > Monitoring Configuration Wizard appeared, and I clicked NEXT, the wizard
> > disappeared, and did not finish.
> >
> > "Greg Kirkpatrick" wrote:
> >
> > > Merv, I think I have gone through the steps in Susan Bradley's blog, but I
> > > cannot confirm it right now, as her blog is down for the moment.
> > >
> > > I did, however, follow the steps under section I in your message's
> > > RESOLUTION section. Section II was not necessary, as the extensions were
> > > already created in just that manner.
> > >
> > > Now, I am no longer getting a "Page cannot be displayed" when I click on
> > > Monitoring and Reporting. Instead, I get the header for the Server
> > > Performance Report, along with today's date and time, the Windows Small
> > > Business Server logo, and a PRINT button -- but no data.
> > >
> > > Server Performance Report for [logo appears here on
> > > the right]
> > > Report created on 8/2/2007 at 6:59 PM
> > >
> > >
> > > Chris, I did see that page on the M&M's smallbizserver.net site, and yes, I
> > > applied all the steps suggested, without success.
> > >
> > >
> > >
> > > "Richard K" wrote:
> > >
> > > > OK the article from Chris solved my problem. I needed to add in 127.0.0.1 IP
> > > > to the default web site.
> > > >
> > > > "Cris Hanna [SBS-MVP]" wrote:
> > > >
> > > > > Perhaps this will help
> > > > > http://www.smallbizserver.net/Defaul...1&postid=23955
> > > > >
> > > > > --
> > > > > Cris Hanna [SBS-MVP]
> > > > > -------------------------------------------------
> > > > > Microsoft MVPs
> > > > > Independent Experts (MVPs do not work for MS)
> > > > > Real World Answers
> > > > > ---------------------------------------------------------
> > > > > Please do not contact me directly regarding issues
> > > > >
> > > > > "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in message news:7CA5E929-96BA-4649-A307-F020552ED89E@microsoft.com...
> > > > > I took over support for this SBS 2003 Standard R1 with SP1.
> > > > >
> > > > > Monitoring and Reporting and Backups were not configured. Despite three
> > > > > NICs being installed in the SBS 2003 server, only one is in use. (I could go
> > > > > on, but...)
> > > > >
> > > > > When I tried to get a report, I got a "page cannot be displayed". I ran the
> > > > > setup, and I got an email the next day saying 404 NOT FOUND.
> > > > >
> > > > > I have tried the steps previously mentioned in similar strings: I have
> > > > > uninstalled Monitoring and Reporting, removing registry entries and folders,
> > > > > and rebooted, and reinstalled Monitoring and Reporting. I have rerun the
> > > > > setup for Monitoring again. I have re-registered the mof files.
> > > > >
> > > > > Still no joy

In almost all cases i have fouund that wen sharepoint components do not work it is because the components do not support asp.net 2.0.
if you go into iis and change the problematic component to asp.net 1 and restart iis you wil find the 404 errors go away.

Please don't use techarena.in
Post Directly to microsoft.public.windows.server.sbs
Because 90% of the world right now has no idea what you are taking about or
referring to.

Thanks
Russ

--
Russell Grover - SBITS.Biz
Microsoft Gold Certified Partner
Microsoft Certified Small Business Specialist
World Wide 24hr SBS Remote Support - http://www.SBITS.Biz


"bmn" <bmn.3mxyne@DoNotSpam.com> wrote in message
news:bmn.3mxyne@DoNotSpam.com...
>
> In almost all cases i have fouund that wen sharepoint components do not
> work it is because the components do not support asp.net 2.0.
> if you go into iis and change the problematic component to asp.net 1
> and restart iis you wil find the 404 errors go away.
>
>
> --
> bmn
> ------------------------------------------------------------------------
> bmn's Profile: http://forums.techarena.in/members/bmn.htm
> View this thread:
> Monitoring and Reporting showing "Page cannot be displayed"
>
> http://forums.techarena.in
>