SBS 2008 not sending Server Reports to Outside Addresses.

[ArcommIT]

Hello, we have an SBS 2008 Server that is not sending Server Reports to any Addresses in the Other E-Mail Addresses field, and it gives the Error Message "An error has occurred while sending this report. As a result, some of the recipients will not receive this report in e-mail." I looked in console.log, and saw:

"[12976] 090921.150839.1492: AdminTME: Status: TaskId = TaskGenerateMonitoringReport, RootTaskId = TaskGenerateAndEmailReport, Success: True, Warning: False, Continue: True, Message:
[12976] 090921.150842.6916: Exception:
---------------------------------------
An exception of type 'Type: System.Net.Mail.SmtpException, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' has occurred.
Timestamp: 09/21/2009 15:08:42
Message: Failure sending mail.
Stack: at System.Net.Mail.SmtpClient.Send(MailMessage message)
at Microsoft.WindowsServerSolutions.SystemHealth.Monitoring.MailUtil.SendMail(String from, String[] to, String subject, Boolean isBodyHTML, String body, String inlineAttachmentPath, String[] attachments)
---------------------------------------
An exception of type 'Type: System.Net.WebException, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' has occurred.
Timestamp: 09/21/2009 15:08:42
Message: Unable to connect to the remote server
Stack: at System.Net.ServicePoint.GetConnection(PooledStream PooledStream, Object owner, Boolean async, IPAddress& address, Socket& abortSocket, Socket& abortSocket6, Int32 timeout)
at System.Net.PooledStream.Activate(Object owningObject, Boolean async, Int32 timeout, GeneralAsyncDelegate asyncCallback)
at System.Net.PooledStream.Activate(Object owningObject, GeneralAsyncDelegate asyncCallback)
at System.Net.ConnectionPool.GetConnection(Object owningObject, GeneralAsyncDelegate asyncCallback, Int32 creationTimeout)
at System.Net.Mail.SmtpConnection.GetConnection(String host, Int32 port)
at System.Net.Mail.SmtpClient.Send(MailMessage message)
---------------------------------------
An exception of type 'Type: System.Net.Sockets.SocketException, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' has occurred.
Timestamp: 09/21/2009 15:08:42
Message: No connection could be made because the target machine actively refused it 192.168.1.10:25
Stack: at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)

[12976] 090921.150847.5261: AdminTME: Status: TaskId = TaskEmailMonitoringReport, RootTaskId = TaskGenerateAndEmailReport, Success: False, Warning: False, Continue: False, Message:
[1148] 090921.150847.5261: AdminTME: Committer: Completed called
[1148] 090921.150847.5261: AdminTME: Committer: Task was cancelled.
[1148] 090921.150847.5261: AdminTME: Committer: Committer Completed."

I tried searching for some of those Errors, but nothing I found had anything to do with the Server Report. We are not using any smarthosts, and 192.168.1.10 is the IP Address of the SBS 2008 Server in question. Any help would be appreciated. Thank you.

 

[ArcommIT]

Okay... Well, after rebooting the Server, it now sends the alerts again, so never mind. Thank you!

 

[ShackDaddy]

Hey, no prob!

Dave Shackelford
ThirdTier.net

 

[ArcommIT]

... And now, a day after it was restarted, the problem is back... So, yeah. Any help would be appreciated... I don't think we can just set a task to restart the Server every day...

 

[ShackDaddy]

It looks like you are being blocked due to an anti-relaying measure on the server, but whatever it is, it's not the default setting, since out of the box I'm usually able to do what you are trying to do. I'll check on a few things and get back to you later this morning.

Dave Shackelford
ThirdTier.net

 

[ArcommIT]

Okay, thank you. Any help is appreciated.

 

[ArcommIT]

One more thing to note is that it was working for the first few weeks before it stopped sending them and started getting that error. There were no changes between when it was working and when it stopped working.

 

[ShackDaddy]

Are the addresses that it is not reaching local to the server, or are they outside? Try limiting the addresses to local ones and see if the same error gets generated. If it doesn't generate them anymore, then the issue is that the server isn't allowing a relay to an external address for some reason.

Did you set up any additional receive connectors since you set the server up, or is there still just the default connectors? Have you made any changes to those connectors?

Dave Shackelford
ThirdTier.net

 

[ArcommIT]

The problem is only sending to outside addresses. The connectors are default and have not been changed.

 

[ShackDaddy]

Does your server have more than one NIC or more than one IP bound to your single NIC?

Dave Shackelford
ThirdTier.net

 

[ArcommIT]

It only has the one NIC, and other than an unused IPv6 Address, it only has the one IP Address.

 

[ArcommIT]

Are the addresses that it is not reaching local to the server, or are they outside? Try limiting the addresses to local ones and see if the same error gets generated. If it doesn't generate them anymore, then the issue is that the server isn't allowing a relay to an external address for some reason.

Did you set up any additional receive connectors since you set the server up, or is there still just the default connectors? Have you made any changes to those connectors?"

I misunderstood your question. It is any address in the Other Addresses field, local or external. Don't worry too much about it, though. We have opened a case with Microsoft Support for it.

 

[ShackDaddy]

Please let us know how it gets resolved, so that you can...um...make the world a better place.

Dave Shackelford
ThirdTier.net

 

[ArcommIT]

We would still appreciate any help you could give us, in case Microsoft can't figure it out.

 

[ArcommIT]

An update:

It turns out that now it is not just outside addresses that generate the error, it happens even with no addresses in the outside addresses field. Restarting the transport service fixes it at least until the next scheduled report E-Mail, but then it stops working again. Any help is appreciated. Thank you.

 

[ArcommIT]

Hello, sorry it took so long, but we think we have found the problem. Microsoft Support discovered that if we disabled the AVG Antispam Agent in the Exchange Shell's Transport Agents, it would send the Reports. We contacted AVG's Support, and they couldn't find out what was causing it, but then when we upgraded to AVG 9, they started sending even with the Agent enabled. I'll let you know if it starts failing again, but so far it looks like it is fixed. Thank you!