Prev: SBS 2003 to SBS 2008 migration
Next: Directory services restore mode deadlock
From: Joao Carlos on 1 Nov 2009 06:49
Robin,

I have same error. After enable log, appears this errors:

#Software: Microsoft Exchange Server
#Version: 8.0.0.0
#Log-type: SMTP Receive Protocol Log
#Date: 2009-11-01T11:14:58.578Z
#Fields: date-time,connector-id,session-id,sequence-number,local-endpoint,remote-endpoint,event,data,context
2009-11-01T11:14:58.578Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,0,192.168.0.2:25,192.168.0.2:6549,+,,
2009-11-01T11:14:58.578Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,1,192.168.0.2:25,192.168.0.2:6549,*,None,Set Session Permissions
2009-11-01T11:14:58.578Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,2,192.168.0.2:25,192.168.0.2:6549,>,"220 GOLDENSRV02.goldentulip.local Microsoft ESMTP MAIL Service ready at Sun, 1 Nov 2009 09:14:58 -0200",
2009-11-01T11:14:58.578Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,3,192.168.0.2:25,192.168.0.2:6549,<,EHLO GOLDENSRV02,
2009-11-01T11:14:58.578Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,4,192.168.0.2:25,192.168.0.2:6549,>,250-GOLDENSRV02.goldentulip.local Hello [192.168.0.2],
2009-11-01T11:14:58.578Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,5,192.168.0.2:25,192.168.0.2:6549,>,250-SIZE,
2009-11-01T11:14:58.578Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,6,192.168.0.2:25,192.168.0.2:6549,>,250-PIPELINING,
2009-11-01T11:14:58.578Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,7,192.168.0.2:25,192.168.0.2:6549,>,250-DSN,
2009-11-01T11:14:58.578Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,8,192.168.0.2:25,192.168.0.2:6549,>,250-ENHANCEDSTATUSCODES,
2009-11-01T11:14:58.578Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,9,192.168.0.2:25,192.168.0.2:6549,>,250-STARTTLS,
2009-11-01T11:14:58.578Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,10,192.168.0.2:25,192.168.0.2:6549,>,250-X-ANONYMOUSTLS,
2009-11-01T11:14:58.578Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,11,192.168.0.2:25,192.168.0.2:6549,>,250-AUTH NTLM,
2009-11-01T11:14:58.578Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,12,192.168.0.2:25,192.168.0.2:6549,>,250-X-EXPS GSSAPI NTLM,
2009-11-01T11:14:58.578Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,13,192.168.0.2:25,192.168.0.2:6549,>,250-8BITMIME,
2009-11-01T11:14:58.578Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,14,192.168.0.2:25,192.168.0.2:6549,>,250-BINARYMIME,
2009-11-01T11:14:58.578Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,15,192.168.0.2:25,192.168.0.2:6549,>,250-CHUNKING,
2009-11-01T11:14:58.578Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,16,192.168.0.2:25,192.168.0.2:6549,>,250-XEXCH50,
2009-11-01T11:14:58.578Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,17,192.168.0.2:25,192.168.0.2:6549,>,250 XRDST,
2009-11-01T11:14:58.578Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,18,192.168.0.2:25,192.168.0.2:6549,<,AUTH ntlm,
2009-11-01T11:14:58.578Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,19,192.168.0.2:25,192.168.0.2:6549,>,334 <authentication response>,
2009-11-01T11:14:58.578Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,20,192.168.0.2:25,192.168.0.2:6549,*,,Inbound authentication failed as we reject well-known account authentication for GOLDENTULIP\Administrador
2009-11-01T11:15:03.594Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,21,192.168.0.2:25,192.168.0.2:6549,>,535 5.7.3 Authentication unsuccessful,
2009-11-01T11:15:03.594Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,22,192.168.0.2:25,192.168.0.2:6549,<,MAIL FROM:<Administrador(a)latinamericahotels.com.br>,
2009-11-01T11:15:08.594Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,23,192.168.0.2:25,192.168.0.2:6549,>,530 5.7.1 Client was not authenticated,
2009-11-01T11:15:08.594Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A0,24,192.168.0.2:25,192.168.0.2:6549,-,,Local
2009-11-01T11:19:53.534Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,0,192.168.0.2:25,192.168.0.2:6654,+,,
2009-11-01T11:19:53.534Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,1,192.168.0.2:25,192.168.0.2:6654,*,None,Set Session Permissions
2009-11-01T11:19:53.534Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,2,192.168.0.2:25,192.168.0.2:6654,>,"220 GOLDENSRV02.goldentulip.local Microsoft ESMTP MAIL Service ready at Sun, 1 Nov 2009 09:19:53 -0200",
2009-11-01T11:19:53.534Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,3,192.168.0.2:25,192.168.0.2:6654,<,EHLO GOLDENSRV02,
2009-11-01T11:19:53.534Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,4,192.168.0.2:25,192.168.0.2:6654,>,250-GOLDENSRV02.goldentulip.local Hello [192.168.0.2],
2009-11-01T11:19:53.534Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,5,192.168.0.2:25,192.168.0.2:6654,>,250-SIZE,
2009-11-01T11:19:53.534Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,6,192.168.0.2:25,192.168.0.2:6654,>,250-PIPELINING,
2009-11-01T11:19:53.534Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,7,192.168.0.2:25,192.168.0.2:6654,>,250-DSN,
2009-11-01T11:19:53.534Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,8,192.168.0.2:25,192.168.0.2:6654,>,250-ENHANCEDSTATUSCODES,
2009-11-01T11:19:53.534Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,9,192.168.0.2:25,192.168.0.2:6654,>,250-STARTTLS,
2009-11-01T11:19:53.534Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,10,192.168.0.2:25,192.168.0.2:6654,>,250-X-ANONYMOUSTLS,
2009-11-01T11:19:53.534Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,11,192.168.0.2:25,192.168.0.2:6654,>,250-AUTH NTLM,
2009-11-01T11:19:53.534Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,12,192.168.0.2:25,192.168.0.2:6654,>,250-X-EXPS GSSAPI NTLM,
2009-11-01T11:19:53.534Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,13,192.168.0.2:25,192.168.0.2:6654,>,250-8BITMIME,
2009-11-01T11:19:53.534Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,14,192.168.0.2:25,192.168.0.2:6654,>,250-BINARYMIME,
2009-11-01T11:19:53.534Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,15,192.168.0.2:25,192.168.0.2:6654,>,250-CHUNKING,
2009-11-01T11:19:53.534Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,16,192.168.0.2:25,192.168.0.2:6654,>,250-XEXCH50,
2009-11-01T11:19:53.534Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,17,192.168.0.2:25,192.168.0.2:6654,>,250 XRDST,
2009-11-01T11:19:53.534Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,18,192.168.0.2:25,192.168.0.2:6654,<,AUTH ntlm,
2009-11-01T11:19:53.534Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,19,192.168.0.2:25,192.168.0.2:6654,>,334 <authentication response>,
2009-11-01T11:19:53.581Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,20,192.168.0.2:25,192.168.0.2:6654,*,,Inbound authentication failed as we reject well-known account authentication for GOLDENTULIP\Administrador
2009-11-01T11:19:58.597Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,21,192.168.0.2:25,192.168.0.2:6654,>,535 5.7.3 Authentication unsuccessful,
2009-11-01T11:19:58.597Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,22,192.168.0.2:25,192.168.0.2:6654,<,MAIL FROM:<Administrador(a)latinamericahotels.com.br>,
2009-11-01T11:20:03.597Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,23,192.168.0.2:25,192.168.0.2:6654,>,530 5.7.1 Client was not authenticated,
2009-11-01T11:20:03.597Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A1,24,192.168.0.2:25,192.168.0.2:6654,-,,Local
2009-11-01T11:33:19.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,0,192.168.0.2:25,192.168.0.2:23766,+,,
2009-11-01T11:33:19.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,1,192.168.0.2:25,192.168.0.2:23766,*,None,Set Session Permissions
2009-11-01T11:33:19.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,2,192.168.0.2:25,192.168.0.2:23766,>,"220 GOLDENSRV02.goldentulip.local Microsoft ESMTP MAIL Service ready at Sun, 1 Nov 2009 09:33:18 -0200",
2009-11-01T11:33:19.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,3,192.168.0.2:25,192.168.0.2:23766,<,EHLO GOLDENSRV02,
2009-11-01T11:33:19.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,4,192.168.0.2:25,192.168.0.2:23766,>,250-GOLDENSRV02.goldentulip.local Hello [192.168.0.2],
2009-11-01T11:33:19.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,5,192.168.0.2:25,192.168.0.2:23766,>,250-SIZE,
2009-11-01T11:33:19.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,6,192.168.0.2:25,192.168.0.2:23766,>,250-PIPELINING,
2009-11-01T11:33:19.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,7,192.168.0.2:25,192.168.0.2:23766,>,250-DSN,
2009-11-01T11:33:19.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,8,192.168.0.2:25,192.168.0.2:23766,>,250-ENHANCEDSTATUSCODES,
2009-11-01T11:33:19.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,9,192.168.0.2:25,192.168.0.2:23766,>,250-STARTTLS,
2009-11-01T11:33:19.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,10,192.168.0.2:25,192.168.0.2:23766,>,250-X-ANONYMOUSTLS,
2009-11-01T11:33:19.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,11,192.168.0.2:25,192.168.0.2:23766,>,250-AUTH NTLM,
2009-11-01T11:33:19.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,12,192.168.0.2:25,192.168.0.2:23766,>,250-X-EXPS GSSAPI NTLM,
2009-11-01T11:33:19.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,13,192.168.0.2:25,192.168.0.2:23766,>,250-8BITMIME,
2009-11-01T11:33:19.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,14,192.168.0.2:25,192.168.0.2:23766,>,250-BINARYMIME,
2009-11-01T11:33:19.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,15,192.168.0.2:25,192.168.0.2:23766,>,250-CHUNKING,
2009-11-01T11:33:19.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,16,192.168.0.2:25,192.168.0.2:23766,>,250-XEXCH50,
2009-11-01T11:33:19.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,17,192.168.0.2:25,192.168.0.2:23766,>,250 XRDST,
2009-11-01T11:33:19.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,18,192.168.0.2:25,192.168.0.2:23766,<,AUTH ntlm,
2009-11-01T11:33:19.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,19,192.168.0.2:25,192.168.0.2:23766,>,334 <authentication response>,
2009-11-01T11:33:19.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,20,192.168.0.2:25,192.168.0.2:23766,*,,Inbound authentication failed as we reject well-known account authentication for GOLDENTULIP\Administrador
2009-11-01T11:33:24.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,21,192.168.0.2:25,192.168.0.2:23766,>,535 5.7.3 Authentication unsuccessful,
2009-11-01T11:33:24.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,22,192.168.0.2:25,192.168.0.2:23766,<,MAIL FROM:<Administrador(a)latinamericahotels.com.br>,
2009-11-01T11:33:29.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,23,192.168.0.2:25,192.168.0.2:23766,>,530 5.7.1 Client was not authenticated,
2009-11-01T11:33:29.248Z,GOLDENSRV02\Default GOLDENSRV02,08CC23289906A2A4,24,192.168.0.2:25,192.168.0.2:23766,-,,Local

There is a Authentication error, but i don't make any changes.

Thanks,

Guirau



v-robme wrote:

Hello yaro,Do you mean the report can be generated but cannot be sent to the
07-set-09

Hello yaro,

Do you mean the report can be generated but cannot be sent to the defined recipient unless it is a scheduled report? That is to say, if you manually click "Generate Report",
the report is created fine but if you click "Generate and e-mail report" the defined recipient will not get the emailed report. Is the correct? If so, please try to change the
recipient to another one or to Administrator and see if it receives the report this time.

Moreover, I would like to know the what is recorded in the corresponding log under "C:\Program Files\Windows Small Business Server\Logs\MonitoringServiceLogs" folder.
Please check the log file carefully and see if there is any record like "Report email sent...", otherwise, if the email is NOT sent, there may be any error messaged logged.

If the issue still occurs, please enable SMTP logging and check Receive Connector's Authentication with following steps:

Enable SMTP logging and check Receive Connector's Authentication
===================
First please check the Receive Connector Authentication which you are using for report email.

1. You may use the similar way as above to find the Receive connector you would like to modify. (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.

Second, let us enable the SMTP logging so that report email flow traffic should be recorded in the SMTP receive connector log if the report email has been indeed sent out.

1. Open the Exchange Management Console, and perform one of the following steps:

- To modify an existing Receive connector on a Hub Transport server, expand Server Configuration in the console tree, and select Hub Transport. In the result pane, select
the server that has the Receive connector that you want to modify, and then click the Receive Connectors tab.

2. In the work pane, select the Receive connector you would like to modify. (e.g. "Default servername" which use servername.domain.local as FQDN)
3. Under the name of the Receive connector in the action pane, click Properties to open the Properties page.
4. Click the General tab and use the drop-down box next to Protocol logging level to enable or disable protocol logging. None disables protocol logging, and Verbose
enables protocol logging.
5. After you make your protocol logging selection, click Apply to save changes and remain in the Properties page, or click OK to save changes and exit the Properties page.
6. Restart the Microsoft Exchange Transport server.

Then, please do a test to manually click "Generate and E-mail report" option in SBS Report console so that the report email flow traffic will be recorded in the SMTP receive
connector log if the report email has indeed been sent out.

Thereafter, please send the SMTP log files in the C:\Program Files\Microsoft\Exchange Server\TransportRoles\Logs\ProtocolLog\SmtpReceive folder to me at
v-robmen(a)microsoft.com for further research.

Thanks for your time and efforts.


Best regards,
Robbin Meng(MSFT)
Microsoft Online Newsgroup Support

==================================================================
Please post your SBS 2008 related questions to the SBS newsgroup on Connect website:
https://connect.microsoft.com/sbs08/community/discussion/richui/default.aspx

Please post your EBS related questions to the EBS newsgroup on Connect website:
https://connect.microsoft.com/ebs08/community/discussion/richui/default.aspx

If you want to use a newsreader other than a web forum to access these newsgroups,
please refer to the following blog to apply NNTP password and configure a newsreader:
http://msmvps.com/blogs/bradley/archive/2008/11/02/signing-up-for-the-sbs-2008-newsgroups.aspx
==================================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
==================================================================

Previous Posts In This Thread:

On segunda-feira, 10 de agosto de 2009 22:15
donmc wrote:

sbs 2008 not sending out reports
I no longer receive my summary or detailed network reports. I have also started
seeing Event ID 1020 in my error logs with the following info:

Log Name: Application
Source: MSExchangeTransport
Date: 8/10/2009 9:26:48 PM
Event ID: 1020
Task Category: SmtpReceive
Level: Warning
Keywords: Classic
User: N/A
Computer: Server.local
Description:
The account 'DOMAIN\Administrator' provided valid credentials, but is not
authorized to use the server; failing authentication.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeTransport" />
<EventID Qualifiers="32772">1020</EventID>
<Level>3</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-08-11T01:26:48.000Z" />
<EventRecordID>247940</EventRecordID>
<Channel>Application</Channel>
<Computer>Server.local</Computer>
<Security />
</System>
<DOMAIN\Administrator</Data>
<Data>Default Server</Data>
</EventData>
</Event>

Any ideas?

On quarta-feira, 12 de agosto de 2009 4:06
v-robme wrote:

Hello,Thanks for your post.
Hello,

Thanks for your post.

This error message may occur if there is any permission issue on the Exchange Server receive connectors. I suggest you re-run the Internet Address Management Wizard(IAMW) to reconfigure the
default receive connectors and accepted domains as well as adjusting corresponding permissions on your SBS 2008 server.

What Changes Does the IAMW Make
http://blogs.technet.com/sbs/archive/2008/10/17/introducing-the-internet-address-management-wizard-part-3-of-3.aspx

Introducing the Internet Address Management Wizard(IAMW): Part 1 of 3
http://blogs.technet.com/sbs/archive/2008/10/15/introducing-the-internet-address-management-wizard-part-1-of-3.aspx

Introducing the Internet Address Management Wizard(IAMW): Part 2 of 3
http://blogs.technet.com/sbs/archive/2008/10/16/introducing-the-internet-address-management-wizard-part-2-of-3.aspx

Here is another article explaining how to configure receive connector to use trusted SMTP relay:

How to Configure Trusted SMTP Relay in Exchange on SBS 2008
http://blogs.technet.com/sbs/archive/2008/09/18/how-to-configure-trusted-smtp-relay-in-exchange-on-sbs-2008.aspx


Hope this helps. Also, if you have any questions or concerns, please do not hesitate to let me know.



Best regards,
Robbin Meng(MSFT)
Microsoft Online Newsgroup Support

==================================================================
Please post your SBS 2008 related questions to the SBS newsgroup on Connect website:
https://connect.microsoft.com/sbs08/community/discussion/richui/default.aspx

Please post your EBS related questions to the EBS newsgroup on Connect website:
https://connect.microsoft.com/ebs08/community/discussion/richui/default.aspx

If you want to use a newsreader other than a web forum to access these newsgroups,
please refer to the following blog to apply NNTP password and configure a newsreader:
http://msmvps.com/blogs/bradley/archive/2008/11/02/signing-up-for-the-sbs-2008-newsgroups.aspx
==================================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
==================================================================

On domingo, 6 de setembro de 2009 16:21
Keven wrote:

Hi Robbin,Just got back from a vacation and one of my clients has an SBS08
Hi Robbin,

Just got back from a vacation and one of my clients has an SBS08 server that
stopped sending me emails and I have come to find it is having the Event ID
1020 issue "The account 'DOMAIN\Administrator' provided valid credentials,
but is not authorized to use the server; failing athentication." as was
posted by donmc here on 8/10. I have done as you suggested and it has not fixed
the issue at all, the server is still posting the same error on trying to
send the messages. Nothing else seems to be wrong with the machine that
we have found. Is there isomething else I could try to troubleshoot this?

Keven.

""Robbin Meng [MSFT]"" wrote:

On segunda-feira, 7 de setembro de 2009 4:50
v-robme wrote:

Hi Keven,Thanks for your update.
Hi Keven,

Thanks for your update.

As we discussed before, this error message may occur if the authentications and permissions settings of the Exchange receive connectors are wrong. Since the wizard did not
work, please double check if the Default Receive Connector configurations, e.g. Authentications and Permissions settings.

Related articles which might help to reset the Default Receive Connector configurations:

Error message when you run the Internet Address Management Wizard in Windows Small Business Server 2008: "The wizard cannot configure Exchange e-mail for your
domain"
http://support.microsoft.com/kb/961664/en-us

Fix My Network wizard (FNCW) Fails to Fix the Exchange SMTP Connectors in SBS 2008
http://blogs.technet.com/sbs/archive/2008/09/29/fix-my-network-wizard-fncw-fails-to-fix-the-exchange-smtp-connectors-in-sbs-2008.aspx

Please have a try.


Best regards,
Robbin Meng(MSFT)
Microsoft Online Newsgroup Support

==================================================================
Please post your SBS 2008 related questions to the SBS newsgroup on Connect website:
https://connect.microsoft.com/sbs08/community/discussion/richui/default.aspx

Please post your EBS related questions to the EBS newsgroup on Connect website:
https://connect.microsoft.com/ebs08/community/discussion/richui/default.aspx

If you want to use a newsreader other than a web forum to access these newsgroups,
please refer to the following blog to apply NNTP password and configure a newsreader:
http://msmvps.com/blogs/bradley/archive/2008/11/02/signing-up-for-the-sbs-2008-newsgroups.aspx
==================================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
==================================================================

On segunda-feira, 7 de setembro de 2009 12:21
Keven wrote:

Well I did run through those yesterday, and also approved a mess of updates
Well I did run through those yesterday, and also approved a mess of updates
awaiting approval and this morning it e-mailed me a status report! The thing
I do not understand though is if I tell it to send me one on demand it still
fails!



""Robbin Meng [MSFT]"" wrote:

On segunda-feira, 7 de setembro de 2009 23:00
v-robme wrote:

Hello yaro,Do you mean the report can be generated but cannot be sent to the
Hello yaro,

Do you mean the report can be generated but cannot be sent to the defined recipient unless it is a scheduled report? That is to say, if you manually click "Generate Report",
the report is created fine but if you click "Generate and e-mail report" the defined recipient will not get the emailed report. Is the correct? If so, please try to change the
recipient to another one or to Administrator and see if it receives the report this time.

Moreover, I would like to know the what is recorded in the corresponding log under "C:\Program Files\Windows Small Business Server\Logs\MonitoringServiceLogs" folder.
Please check the log file carefully and see if there is any record like "Report email sent...", otherwise, if the email is NOT sent, there may be any error messaged logged.

If the issue still occurs, please enable SMTP logging and check Receive Connector's Authentication with following steps:

Enable SMTP logging and check Receive Connector's Authentication
===================
First please check the Receive Connector Authentication which you are using for report email.

1. You may use the similar way as above to find the Receive connector you would like to modify. (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.

Second, let us enable the SMTP logging so that report email flow traffic should be recorded in the SMTP receive connector log if the report email has been indeed sent out.

1. Open the Exchange Management Console, and perform one of the following steps:

- To modify an existing Receive connector on a Hub Transport server, expand Server Configuration in the console tree, and select Hub Transport. In the result pane, select
the server that has the Receive connector that you want to modify, and then click the Receive Connectors tab.

2. In the work pane, select the Receive connector you would like to modify. (e.g. "Default servername" which use servername.domain.local as FQDN)
3. Under the name of the Receive connector in the action pane, click Properties to open the Properties page.
4. Click the General tab and use the drop-down box next to Protocol logging level to enable or disable protocol logging. None disables protocol logging, and Verbose
enables protocol logging.
5. After you make your protocol logging selection, click Apply to save changes and remain in the Properties page, or click OK to save changes and exit the Properties page.
6. Restart the Microsoft Exchange Transport server.

Then, please do a test to manually click "Generate and E-mail report" option in SBS Report console so that the report email flow traffic will be recorded in the SMTP receive
connector log if the report email has indeed been sent out.

Thereafter, please send the SMTP log files in the C:\Program Files\Microsoft\Exchange Server\TransportRoles\Logs\ProtocolLog\SmtpReceive folder to me at
v-robmen(a)microsoft.com for further research.

Thanks for your time and efforts.


Best regards,
Robbin Meng(MSFT)
Microsoft Online Newsgroup Support

==================================================================
Please post your SBS 2008 related questions to the SBS newsgroup on Connect website:
https://connect.microsoft.com/sbs08/community/discussion/richui/default.aspx

Please post your EBS related questions to the EBS newsgroup on Connect website:
https://connect.microsoft.com/ebs08/community/discussion/richui/default.aspx

If you want to use a newsreader other than a web forum to access these newsgroups,
please refer to the following blog to apply NNTP password and configure a newsreader:
http://msmvps.com/blogs/bradley/archive/2008/11/02/signing-up-for-the-sbs-2008-newsgroups.aspx
==================================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
==================================================================

EggHeadCafe - Software Developer Portal of Choice
Refreshing ASP.NET Cached Data on a timed basis to avoid delays
http://www.eggheadcafe.com/tutorials/aspnet/223319d8-6366-492a-8eae-e3c7a26c88a4/refreshing-aspnet--cache.aspx
 | 
Pages: 1
Prev: SBS 2003 to SBS 2008 migration
Next: Directory services restore mode deadlock