reports not emailing

Discussion in 'Windows Small Business Server' started by mugen, Jun 6, 2010.

  1. mugen

    mugen Guest

    have an sbs 2008 install that generates daily reports but doesn't email
    if i do it manually they generate and email to the correct address. so there
    seems to be nothing wrong with the process in that instance.

    in the log file "Monitoring Report Detailed Network Report
    2010-06-06-06-00-00-0135.log" i get the results below.
    is there another log file i can look at that will give more detail as to the
    error, or does anyone know a solution.


    2010-05-07T06:00:00.826868 : Logger started at: 2010-05-07T06:00
    2010-05-07T06:00:00.826868 : ***************** Starting
    GenerateMonitoringReport task... *****************
    2010-05-07T06:00:00.826868 : Generating Summary Network Report...
    2010-05-07T06:01:04.590244 : XML generated...
    2010-05-07T06:01:04.786264 : HTML generated...
    2010-05-07T06:01:04.802265 : Report stored in archives...
    2010-05-07T06:01:07.64855 : Failed to send report email.
    2010-05-07T06:01:07.64955 : Generating Summary Network Report finished.
    2010-05-07T06:01:07.64955 : ***************** GenerateMonitoringReport task
    finished. *****************
    mugen, Jun 6, 2010
    1. Advertisements

  2. mugen

    Joe Guest

    There is provision for detailed SMTP logging, but it is not enabled by
    default, and still may not help. If there is software blocking mail,
    there may be no entries in the SMTP logs.

    The first question is whether the AV/security software on your server
    has provision for preventing email from being sent, with some programs
    being listed as exceptions. The McAfee system does that, under the
    heading of Access Protection. If so, check the log for an entry around
    the time the report should have been sent. If you find one for
    DataCollectorSvc.exe, that's your report mailer, and you need to add it
    to the list of exceptions.
    Joe, Jun 6, 2010
    1. Advertisements

  3. Hello,

    Thanks for your post.

    As you found, reports are being scheduled and sent within the Windows SBS Manager service. Check the service execution log files under \program files\windows small
    business server\logs\MonitoringServiceLogs.

    The service controls multiple tasks and some of those tasks conflict with each other. If something else conflicts with the daily report and that conflicting task has started running
    before the daily report task, the report will be sent delayed until the execution of that conflicting task is finished.

    Moreover, if we manually generate and send the report, the report is sent as your currently logon user. But if it's a scheduled report, the scheduled report is sent as built-in
    account. Therefore make sure the SBSMonAcct account is not disabled. Then please also check the Exchange Receive Connector Authentication
    which you are using for report email.

    1. You may open Exchange server 2007 management console(EMC)to find the Receive connector you would like to modify under Server Configuration, Hub Transport. (e.g.
    "Default servername" which use servername.domain.local as FQDN).

    2. Open the Authentication tab, make sure the "Transport Layer Security(TLS)", "Basic Authentication", "Exchange Server Authentication" and "Intergrated Windows
    authentication" are all checked.

    3. On the Permission Groups tab, make sure "Exchange users", "Exchange servers", "Legacy Exchange Servers" are selected.

    Then reboot the server and test the issue again. If the issue still persists, we may need to enable the Exchange Receive Connector protocol logging and look for further log
    information next.

    Hope it helps.

    Best regards,
    Robbin Meng(MSFT)
    Microsoft Online Newsgroup Support
    This posting is provided "AS IS" with no warranties, and confers no rights.
    Robbin Meng [MSFT], Jun 9, 2010
  4. Joe, I read with interest your reply to the failed Server Report email issue. I just did a swing migration and also have the same issue. The server elsewise is fine and the older server has been retired. As the previous entry indicated the server report is generated fine and can be manually emailed. This client is using AVG Network Edition with the excludes entered already and no idication of any blocked email at 3:45 A.M. when the report is generated. I have used the Exchange Message Tracking to see if any problems exist at the time of the supposed email creation and it reports no issues found. While this is not a show stopper it still would be nice to receive this report. Oddly enough we manage about 7 of these SBS 2008 servers and this is the first one to fail in the report generation. Your thoughts on this would be very much appreciated.
    Darwin Steele, Dec 28, 2010
  5. mugen

    Joe Guest

    I don't think I can add anything more. I've had this problem with an
    SBS2003 for the last six years, and have long since given up trying to
    guess what the cause is. I was luckier with a new SBS2008.

    You may have noticed that this newsgroup is now extremely quiet, which
    is because Microsoft has abandoned Usenet. You may have better luck
    with this question on:
    Joe, Dec 28, 2010
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.