Trace-Logging to Verify TFS mail sending status
-------------------------------------------------------------------
On a server with both TFS(Beta3) AND TeamBuild both installed.
Per following link:
I open on TFS Server: SrBuild
C:\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\Web.config
and I edit as follows in accordance with supporting link:
<system.diagnostics>
<assert assertuienabled="false" />
<!--
<trace autoflush="false" indentsize="4" />
-->
<!-- Trace Switches
Each of the trace switches should be set to a value between 0 and 4, inclusive.
0: No trace output
1-4: Increasing levels of trace output; see Systems.Diagnostics.TraceLevel
-->
<switches>
<add name="API" value="0" />
<add name="Authentication" value="0" />
<add name="Authorization" value="0" />
<add name="Database" value="0" />
<add name="General" value="3" />
<!-- Temp: Team Build trace switches -->
<add name="EqtTraceLevel" value="0" />
<!-- Temp: Shared TeamBuild/WorkItem trace switches -->
<add name="traceLevel" value="1" />
<!-- Temp: Shared BIS/Warehouse trace switches -->
<add name="eSwitch" value="1" />
</switches>
<trace autoflush="false" indentsize="4" >
<listeners>
<add name="myListener" type="System.Diagnostics.TextWriterTraceListener" initializeData="c:\tracelogs\myListener.log" />
<remove type="System.Diagnostics.DefaultTraceListener"/>
</listeners>
</trace>
</system.diagnostics>
I go to root C:\tracelogs drive in Windows Explorer and right click - selecting Properties:
Add TFS service account TESTLAB\builder to Security tab and share permissions with Full Access.
I start a build and it completes successfully.
I check the directoy C:\tracelogs on the build server and it is empty.
Just to be extra thorough I do a SEARCH on the entire hard drive of TFS Server SRBUILD
for all *.log files with time-stamps in the range of todays date 2/21/06.
I do however find: w3wpStsAppPool1.log under C:\Windows\Temp
3 02/01 12:17:41 1856 Windows SharePoint Services log file
3 02/06 16:07:31 2464 Windows SharePoint Services log file
0 02/06 17:12:12 2932 The Web site that is referenced here is not in the configuration database.
0 02/06 17:22:43 2932 The Web site that is referenced here is not in the configuration database.
3 02/07 10:54:46 1744 Windows SharePoint Services log file
0 02/07 10:54:48 1744 The Web site that is referenced here is not in the configuration database.
3 02/10 13:57:12 2600 Windows SharePoint Services log file
3 02/10 15:31:11 956 Windows SharePoint Services log file
3 02/10 16:19:19 4012 Windows SharePoint Services log file
0 02/10 16:45:10 2284 The Web site that is referenced here is not in the configuration database.
3 02/13 11:08:45 3448 Windows SharePoint Services log file
0 02/13 14:51:05 3448 The Web site that is referenced here is not in the configuration database.
3 02/14 11:04:57 4296 Windows SharePoint Services log file
3 02/15 12:12:29 1036 Windows SharePoint Services log file
3 02/16 08:40:23 4296 Windows SharePoint Services log file
3 02/17 07:21:05 3648 Windows SharePoint Services log file
3 02/20 10:21:43 3420 Windows SharePoint Services log file
3 02/21 07:57:34 3348 Windows SharePoint Services log file
And I note that I have taken w3wp process exceptions on Build.Notification earlier.
Event Type: Error
Event Source: TFS Services
Event Category: None
Event ID: 3043
Date: 2/20/2006
Time: 3:00:47 PM
User: N/A
Computer: SRBUILD
Description:
An unexpected condition has occurred in a Team Foundation component. The information contained here should be made available to your site administrative staff.
Technical Information (for the administrative staff):
Date (UTC): 2/20/2006 9:00:46 PM
Machine: SRBUILD
Application Domain: /LM/W3SVC/2/Root/services-4-127849426291571793
Assembly: Microsoft.TeamFoundation.Server, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
Process Name: w3wp
Process Id: 1060
Thread Id: 2256
Account name: SRBUILD\builder
Detailed Message: TF50285: Exception matching subscription: Microsoft.TeamFoundation.Server.SubscriptionOnServer: System.Threading.ThreadAbortException: Thread was being aborted.
at Microsoft.TeamFoundation.Build.Client.BuildNotificationFilter.RemoveRestrictedContent(String server, String[] userList, XmlDocument eventCopy, Restriction[]& restrictions)
at Microsoft.TeamFoundation.Server.NotificationCenter.FilterNotification(EventOnServer e, WebServiceNotification notification, SubscriptionOnServer s)
at Microsoft.TeamFoundation.Server.NotificationCenter.Notify(EventOnServer e)
Exception Message: Thread was being aborted. (type ThreadAbortException)
Exception Stack Trace: at Microsoft.TeamFoundation.Build.Client.BuildNotificationFilter.RemoveRestrictedContent(String server, String[] userList, XmlDocument eventCopy, Restriction[]& restrictions)
at Microsoft.TeamFoundation.Server.NotificationCenter.FilterNotification(EventOnServer e, WebServiceNotification notification, SubscriptionOnServer s)
at Microsoft.TeamFoundation.Server.NotificationCenter.Notify(EventOnServer e)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Just for fun I open OutLook express and send Email to smtpServer: 10.1.3.8 with service
accounts builder@identix.com AND builder@testlab.local and builder@SRBUILD and they all get through to my
PC client Email.
Still NO Email from TFS Build Notify and NO trace-log to get insight into what
is stopping the TFS Build.Notification.
<<<
QUESTION: What is wrong with C:\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\Web.config
modifications per the instructions of the two web pages to change
<add name="General" value="3" />
and add the trace block as follows:
<trace autoflush="false" indentsize="4" >
<listeners>
<add name="myListener" type="System.Diagnostics.TextWriterTraceListener" initializeData="c:\tracelogs\myListener.log" />
<remove type="System.Diagnostics.DefaultTraceListener"/>
</listeners>
</trace>
in <system.diagnostics>
>>>

Trace-Logging to Verify TFS mail sending status
twerling
You state that you are still using Beta3;
The RC has been released; perhaps upgrading to the RC will resolve the issue.
herman_d
remove the line:
<remove type="System.Diagnostics.DefaultTraceListener"/>
It is no longer compatible with tracing.