Solved

Server status reports not getting sent

Posted on 2008-10-29
14
1,593 Views
Last Modified: 2009-05-20
I have a SBS 2003 box that for some reasoon will not send status reports.
I have tried reruning the "server monitoring and reporting setup"
I have checked the settings for the monitoring and reporting. ie email address, account sent from...
When i try to send a test report i get this error " An error occurred while sending the Server Status Report. Verify that report configuration settings are correct, and then try again"
Ive checked the logs and the only error i can find is this one below:
Event Type:	Error
Event Source:	ServerStatusReports
Event Category:	None
Event ID:	1
Date:		29/10/2008
Time:		10:55:49
User:		N/A
Computer:	SERVER1
Description:
Server Status Report:
	URL:		http://localhost/monitoring/perf.aspx?reportMode=1&allHours=1
	Error Message:	General network error.  Check your network documentation.
	Stack Trace:	   at usage.globalFn.connectDataSource(Boolean pingFirst)
   at usage.frmPerf.renderReportWorker()
   at usage.frmPerf.renderReport()
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Open in new window

0
Comment
Question by:vehastings
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 7
  • 6
14 Comments
 
LVL 5

Assisted Solution

by:gratex_ssd
gratex_ssd earned 40 total points
ID: 22831868
This looks like .net framework error. Check that .NET 2.0 is not selected on default website properties in the .NET tab, in IIS. If it is, set it to 1.4 and see if it helps.
0
 
LVL 5

Expert Comment

by:gratex_ssd
ID: 22831922
Sorry, typo not 1.4 but 1.1.4
0
 

Author Comment

by:vehastings
ID: 22832676
Hi
I do not have a APS.NET tab in my IIS > defualt website properties.....
I only have ASP.NET v 1.1.4322 installed.
any other ideas?
thanks
0
Transaction Monitoring Vs. Real User Monitoring

Synthetic Transaction Monitoring Vs. Real User Monitoring: When To Use Each Approach? In this article, we will discuss two major monitoring approaches: Synthetic Transaction and Real User Monitoring.

 
LVL 5

Expert Comment

by:gratex_ssd
ID: 22832735
Try to follow this guide about same problem you're encountering

http://www.eggheadcafe.com/forumarchives/windowsserversbs/Oct2005/post24693836.asp
0
 

Author Comment

by:vehastings
ID: 22833500
I have looked at your idea above and i have not got any problems with the reports themselves.... i can see them on the server. BUT it will not send them.
So to recap..
I can set up reports fine.
I can view reports fine
i get a email notification saying that i have set up reports.
But when i go to send the report i get the following error
" An error occurred while sending the Server Status Report. Verify that report configuration settings are correct, and then try again"
0
 
LVL 5

Expert Comment

by:gratex_ssd
ID: 22836524

From where you're trying to sent the report and get that error message?  From the console's "Change Server Status Report Settings"?

Try to reboot your server when you have chance and see what it does.
0
 

Author Comment

by:vehastings
ID: 22843425
Hi I have restarted the server today and there has been no change to the problem.
0
 
LVL 5

Expert Comment

by:gratex_ssd
ID: 22845512
Alright, check this: (courtesy SBS DIVA http://forums.techarena.in/small-business-server/1055598.htm)

Go to IIS, Default Web Site, Web Site tab, Advanced. Verify the IP address
Default does not have a host header. Removed any host header assiged to
Default.
If you have to assign a host header to the default website, please add
127.0.0.1 with port 80 and NO host header to the default website.


NOTE: Monitoring and Reporting, and Backup snapin in Server Management
communicate with the IIS Default Website using 127.0.0.1. Make sure
127.0.0.1 port 80 is availalbe and no host header is assigned to 127.0.0.1.
0
 

Author Comment

by:vehastings
ID: 22850156
Hi I checked out the link but didn't help me much. thanks thou.
I have checked the IIS settings - there was not a host header assigned.
0
 
LVL 5

Assisted Solution

by:gratex_ssd
gratex_ssd earned 40 total points
ID: 22850333
Alright. Please do answer me my previous questions to be able to assist you further:

From where you're trying to sent the report and get that error message?

Do you indeed have 127.0.0.1 specified on Default Website?

Thanks
0
 
LVL 5

Expert Comment

by:gratex_ssd
ID: 22850417
0
 

Accepted Solution

by:
vehastings earned 0 total points
ID: 22867208
Hi thanks for all your helps guys.
I decided to go to microsoft in the end as i wasn't getting anywhere.
Here is the solution!

Go to> IIS > Server > websites > default website properties.
Home directory tab > Check the local path
Should be:
C:\inetpub\wwwroot         (mine was c:\inetpub - so just changed it and it worked!!!! )
Apply
Try to resend the report.

All working happy days!.
0
 

Author Comment

by:vehastings
ID: 22867238
all fixed
0
 

Expert Comment

by:CmcDoITO
ID: 23877550
There's a more universal solution that I came around while having the same problem.
After hours of debugging, checking permissins and folder contents, I fired up ProcMon
to find out what's happening, and... BINGO! The 'mssbsssr.exe' program that is used
for sending the reports seems to have a hardcoded lookup for a directory called
"Monitoring" at the same level as the root directory of your default website, i.e.
calling something like "..\Monitoring"

The solution is so simple and astonishing that it can't be found anywhere yet:
Just copy the whole C:\INetPub\Monitoring directory to the path where your
default website root resides, i.e. if your web root is D:\INetPub\Default,
copy it to D:\INetPub\Monitoring. That's it, your reports get sent again! :-)

Of course you could also move the folder, but I would suggest leaving it there,
just in case a patch or service pack touches it and would not find it then.
0

Featured Post

Why You Need a DevOps Toolchain

IT needs to deliver services with more agility and velocity. IT must roll out application features and innovations faster to keep up with customer demands, which is where a DevOps toolchain steps in. View the infographic to see why you need a DevOps toolchain.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Written by Glen Knight (demazter) as part of a series of how-to articles. Introduction One of the biggest consumers of disk space with Small Business Server 2008(SBS) is Windows Server Update Services, more affectionately known as WSUS. For t…
The SBS 2011 release date (RTM) is supposed to be around Christmas, 2011.  This article is a compilation of my notes -- things I have learned first hand.  The items are in a rather random order, but I think this list covers most of what is new and d…
This video Micro Tutorial shows how to password-protect PDF files with free software. Many software products can do this, such as Adobe Acrobat (but not Adobe Reader), Nuance PaperPort, and Nuance Power PDF, but they are not free products. This vide…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…

688 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question