Server Error in '/Monitoring' Application

[BoanHed]

I am getting the below error in the Monitoring and Reporting area:

Server Error in '/Monitoring' Application.

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed.

Details: To enable the details of this specific error message to be viewable on the local server machine, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly"/>
</system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="On" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
-----------------------------------

Also, I am getting a similar error with Backup's and Remote. Any way to fix this? Thanks.

[Viceman]

Go to 'windows\microsoft.net\framework\v1.1.4322' location and run the following command: aspnet_regiis -ir. This command will usually register ASP.NET with IIS. For more information visit this link - http://msdn2.microsoft.com/en-us/lib...8h(vs.71).aspx

[Mr. Boo Bear]

You can complete the procedure “To verify that the services are running,” and then scan the Dataservicecomponents log files in C:\Program Files\Windows Small Business Server\Logs\MonitoringServiceLogs to view any reported errors or exceptions. Just follow the steps given here to repair monitoring and reporting infrastructure from here - http://technet.microsoft.com/en-us/l...=ws.10%29.aspx

[BoanHed]

Thanks for the solution, the problem is solved now.

[NickBR]

Hi

I fllowed the instructions in post #3. Now I not only have no monitoring, but all access to RWW has gone!
I get a 404 error now whenever I try to login to /remote.
This applies whether I'm on the internet or the local WAN and it happens even from the server hosting SBS.

OWA is still accessible.

Anyone know how to undo the damage?

Nick