vehastings
asked on
Server status reports not getting sent
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:
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.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Sorry, typo not 1.4 but 1.1.4
ASKER
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
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
Try to follow this guide about same problem you're encountering
http://www.eggheadcafe.com/forumarchives/windowsserversbs/Oct2005/post24693836.asp
http://www.eggheadcafe.com/forumarchives/windowsserversbs/Oct2005/post24693836.asp
ASKER
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"
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"
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.
ASKER
Hi I have restarted the server today and there has been no change to the problem.
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.
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.
ASKER
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.
I have checked the IIS settings - there was not a host header assigned.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Also, run SBS 2003 BPA, it might give an info what's wrong:
http://www.microsoft.com/downloads/details.aspx?FamilyId=3874527A-DE19-49BB-800F-352F3B6F2922&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=3874527A-DE19-49BB-800F-352F3B6F2922&displaylang=en
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
all fixed
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.
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.