Search

TFS Admin Console does not let you test SMTP server settings by Grant Holliday - MSFT

Closed
as Deferred Help for as Deferred

1
0
Sign in
to vote
Type: Bug
ID: 776847
Opened: 1/17/2013 4:41:03 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
The TFS Admin Console does not let you test SMTP server settings easily. This makes it a very difficult process to confirm that your email settings are correct. In the meantime, emails are queuing up or failing and users are getting frustrated.
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Team Foundation Server 2012

Steps to reproduce

Open TFS Admin Console
Change SMTP server settings to an invalid SMTP mail server
Save the settings

Product Language

English

Operating System

Windows Server 2012

Operating System Language

English

Actual results

Email sending fails. You then have to go and dig through the tbl_JobHistory, which you then find has a truncated error message telling you to set some registry setting.

Once you set that setting, you then have to wait for the email to be sent again, or generate a new one.

Sometimes there will be errors in the Application event log that help you determine the root cause.


There were errors or warnings during notification delivery.    0/4 emails delivered. 0/0 soap notifications delivered. 1 errors. 0 warnings.    Set /Service/Integration/Settings/NotificationJobLogLevel in the TF registry to 2 to see errors and warnings.    

Expected results

After entering/changing your SMTP server settings, you should be able to:

1. Verify that TFS can send a test email successfully (i.e. submit a new message using smtpClient.send())
2. Enter in an email address to send a test message to, so you can verify that you actually received it.
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 1/30/2013 at 11:24 AM
Thank you for your feedback! We added this feature to our backlog for future releases.
Posted by Microsoft on 1/17/2013 at 7:14 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 1/17/2013 at 4:52 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.