Re: Server reports not emailed

From: Joe (joe_at_jretrading.com)
Date: 01/18/05


Date: Tue, 18 Jan 2005 19:24:33 +0000

In message <uFLpIrY$EHA.824@TK2MSFTNGP11.phx.gbl>, Allen M
<allenmiyake@majaro.com> writes
>Believe it or not I think a simple reboot will resolve your issue. Also
>check to make sure your Messenger service is running.
>
It was rebooted at least three times yesterday, and once today. It is
possible that one of yesterday's reboots shook some sense into it, but
by this morning it still didn't send the report. Messenger is running.

>
>"Joe" <joe@jretrading.com> wrote in message
>news:OMtgHlFy7U7BFwGr@jretrading.com...
>>A server running SBS 2003 Standard has been emailing me daily and
>>fortnightly reports for some months. It stopped doing so last Tuesday, and
>>I was able to investigate today. If I try to do it manually I get the
>>message:
>>
>> An error occurred while sending the Server Status Report. Verify that
>> report configuration settings are correct, and then try again.
>>
>> Needless to say, no email addresses have changed or been changed. I tried
>> re-running the wizard, no good. I tried restarting the monitoring service,
>> which in turn restarted the MSSQL$SBSMONITORING service, or tried to.
>> SQLAgent$SBSMONITORING reported that a dependency service failed to start.
>> Trying to start the latter manually gave a report that the service had
>> started and immediately stopped, and that some services were supposed to
>> do that. From then on the event log was filled with 19011 entries from the
>> non-starting service, followed by howls of protest from GroupShield and
>> regular complaints from SBS Monitoring. A reboot got rid of all this but
>> did not restore report emails.
>>
>> I've found three or four mentions over the last year of this kind of
>> problem, but only questions, no answers. I can find nothing in the logs at
>> the time the reports should be sent, and the Alert service still seems
>> able to send email to the same addresses. There were no unusual log
>> entries in the 24 hours before the first missing report. It is entirely
>> possible that I made some change that day that has caused the problem, but
>> nothing is logged and I didn't write anything down for that day, so any
>> work done must have been trivial and fairly routine.
>>
>> Any ideas where to start?
>> --
>> Joe
>
>

-- 
Joe


Relevant Pages

  • Re: dumprep - Spyware?
    ... This is loaded at startup if you had a crash and want to send a report to ... Set Page File to 0, ok your way out and reboot. ... Windows XP Problems if Your Profile Is Damaged ... How to Troubleshoot By Using the Msconfig Utility in Windows XP ...
    (microsoft.public.windowsxp.general)
  • RE: SBS 2003 and Exchange question
    ... This "anomoly" appeared in the morning report several hours after ... I rebooted the server. ... second store process and was free of critical/system errors or performance ... > service has been stopped and restarted (or server reboot). ...
    (microsoft.public.windows.server.sbs)
  • Re: Major crash & reboot: drag & drop files to CD burner
    ... > Recently I retreived a bunch of my pictures off of our church computer. ... > After the reboot, the computer sent a message to wherever it sends ... > messages to about a major system crash with a report. ...
    (microsoft.public.windowsxp.general)
  • Re: Instant reboot with FreeBSD 6.3 and > 2GB RAM
    ... I will test it also on FreeBSD 7.0, but i assume that it will fix it there too. ... Many users using FreeNAS reporting this reboot problem on their machines with RAM> 2GB. ... detailed but from your description it looks like loader is causing that. ... The report is about 6.2-R but at least I've checked loader code and 7.x ...
    (freebsd-questions)
  • Re: Instant reboot with FreeBSD 6.3 and > 2GB RAM
    ... I will test it also on FreeBSD 7.0, but i assume that it will fix it there too. ... Many users using FreeNAS reporting this reboot problem on their machines with RAM> 2GB. ... detailed but from your description it looks like loader is causing that. ... The report is about 6.2-R but at least I've checked loader code and 7.x ...
    (freebsd-stable)