How to enable trace logs in the build environment?

by Xavier Dilip Kumar 18. March 2014 11:19

Explanation:

Following are the steps to enable trace logs in the build environment

1. On the Build machine (both controller and agent) ,  copy the attached .config file (TFSBuildServiceHost exe.config (2.25 kb)) to C:\Program Files\Microsoft Team Foundation Server 2010\Tools.

2. Create a new directory named c:\logs and ensure that the account under which the service Visual Studio Team Foundation Build Service Host has write permission on c:\logs.

3. Restart the build controller/agent service (net stop tfsbuildservicehost & net start tfsbuildservicehost).

4. Trace log will be generated under c:\logs

Steps to enable log in the windows event viewer 

1. On the Build machine, go to Event Viewer and navigate to the following path:

  • Application and Services Logs\Microsoft\Team-Foundation-Server\Build-Services.

 2. We want a detailed level tracing:

  • Go to the ‘View’ menu and select ‘Show Analytic and Debug Logs’. Once you do that there will be 2 channels available under this event source, Operational and Analytic

** The operational log is always on and provides high-level auditing of failures and events, while the Analytic log is off by default and provides very detailed information about activities in the build machine.

 

** You can enable the Analytic log, by right click and select Enable Log.


 

Tags:

Team Build | TFS 2010 | TFS 2012 | TFS 2013

TF259137: The following account does not have sufficient permissions to complete the operation: DOMAIN\user. The following permissions are needed to perform this action: Write.

by Xavier Dilip Kumar 10. March 2014 10:02

Solution:

Check whether the "[PROJECT NAME]\Project Administrators" group has permissions for the team project

Command to view current permissions

tfslabconfig.exe permissions /collection:<CollectionURL> /Url:VSTFS:///LabManagement/TeamProject/<TeamProject> 

Command to grant permissions

tfslabconfig.exe permissions /collection:<CollectionURL> /Url:VSTFS:///LabManagement/TeamProject/<TeamProject> 

/Group:"[PROJECT NAME]\Project Administrators" /allow:*

Tags:

TFS 2010 | TFS 2012 | TFS 2013

How to clone a build definitions from one project to another within a same collection?

by Xavier Dilip Kumar 7. March 2014 12:31

Solution:

You can use TFS power tools command line utility to clone a build definition across projects

Note: You can download and install TFS Power Tools from http://visualstudiogallery.msdn.microsoft.com/b1ef7eb2-e084-4cb8-9bc7-06c3bad9148f

1. Open "Visual Studio" command prompt

2. You can use the following command to preview the build definition clone

tfpt builddefinition /clone "<Source Team Project Name>\Build Definition" "<Target Team Project Name>\Build Definition" /Collection:http://tfs:8080/tfs/DefaultCollection /preview

3. You can use the following command to clone the build definition

tfpt builddefinition /clone "<Source Team Project Name>\Build Definition" "<Target Team Project Name>\Build Definition" /Collection:http://tfs:8080/tfs/DefaultCollection

Only the well-defined build definition can be cloned using this approach meaning the build source build definition should have all the mandatory (required) properties filled with values

For example:

The source build definition without Build controller name cannot be cloned using this approach.

You can also use * wildcard character to clone all build definitions at one shot, provided you have well-defined build definition at source team project.

tfpt builddefinition /clone "<Source Team Project Name>\*" "<Target Team Project Name>\"  /Collection:http://tfs:8080/tfs/DefaultCollection

Remember to update the following build properties to the cloned build definition. 

1. Disable build definition to prevent accidental triggering.

2. Change workspace mapping to target team project source.

3. Change drop location.

4. Change the build process template to point to the right projects.

5. If you use custom build workflow/tasks, make sure your build controller custom assembly references are pointed to target team project source control

6. Enable the build definition.

 

Tags: , ,

TFS 2010 | TFS 2012 | TFS 2013

How to change the work item maximum attachment size?

by Xavier Dilip Kumar 14. February 2014 08:16

Explanation:

By default, The maximum WI attachments size is set to 4 MB but the attachment size can be increased up to 2GB

Solution:

  1. Log on to the application-tier server for TFS.

  2. open the URL: http://localhost:8080/tfs/<Collection Name>/WorkItemTracking/v1.0/ConfigurationSettingsService.asmx?op=SetMaxAttachmentSize

  3. Enter the size in bytes, and then choose Invoke. For 9.5 MB, enter  10000000.

    SetMaxAttachmentSize, ConfigurationSettingsService

Solution:

INSERT INTO [<Collection DB Name>].[dbo].[tbl_RegistryItems] VALUES (1,'#\Service\WorkItemTracking\Settings\','MaxAttachmentSize\',10000000);

Tags:

TFS 2010 | TFS 2012 | TFS 2013

What are the access levels in Team Web Access ? And How to set the access levels and enable the features?

by Xavier Dilip Kumar 5. February 2014 20:02

Explanation:

Following are the access levels

Limited: This level of access restricts the user so that they can only view work items that they create in Team Web Access (also known as Work Item Only View). No other features, such as team pages, are available to users in this group.

License Required: No client access license (CAL) is required for this level of Team Web Access.

Features available:

  • View my work items

Standard: This is the default level of access in Team Web Access for your users. Members of this group can view all Team Web Access features except for: sprint planning and backlog views any of the features for requesting feedback from users and managing that feedback. 

License Required:Team Foundation Server (TFS) CAL is required for all users with this level.

Features available:

  • View my work items

  • Standard features (home page, team queries, access to source and build pages)

  • Agile boards (Kanban board, task boards)

  • Backlog and sprint planning tools

  • Chart viewing

Full: This level is reserved for users who are licensed to use all features available in Team Web Access, including the sprint planning and backlog management tools and the Request and Manage Feedback tools.

License Required Visual Studio Test Professional with MSDN, Visual Studio Premium with MSDN, or Visual Studio Ultimate with MSDN. These MSDN subscriptions each include a TFS CAL for the subscriber.

Features available:

  • View my work items

  • Standard features

  • Agile boards

  • Backlog and sprint planning tools

  • Request and manage feedback

  • Test case management

  • Team rooms

  • Agile portfolio management

  • Chart viewing

  • Chart authoring

To set access levels:

  1. Goto TFS home page (http://TFSServer:8080/tfs). You need to have TFS Administrator permission to set the access levels

  2. Add the user or group.

    Add the user or group

Reference

Tags:

TFS 2012 | TFS 2013

TFS Install and Configuration Requirements

by Xavier Dilip Kumar 5. February 2014 09:59
TFS Server install requirements TFS 2012 TFS 2013 TCP Ports  Accounts
Server Operating System          
Versions        
Windows Server 2008 SP2 (Standard, Enterprise, Datacenter) Yes No    
Windows Server 2008 R2 SP1 (Standard, Enterprise, Datacenter) Yes Yes    
Windows Server 2012 (Essentials, Standard, Datacenter) Yes Yes    
Windows Small Business Server 2011 (Essentials, Standard, Premium Add-On) Yes Yes    
Windows Home Server 2011 Yes No    
Windows Server 2012 R2 (Essentials, Standard, Datacenter) No Yes    
Default Ports        
Team Foundation Server     8080  
Team Foundation Server Proxy     8081  
Service accounts        
TFS        TFSSERVICE
TFS Proxy        TFSPROXY
SQL Server          
Versions        
SQL Server 2008 R2 (Express, Standard Edition, Enterprise Edition) Yes No    
SQL Server 2012 (Standard Edition, Enterprise Edition) Yes No    
SQL Server 2012 SP1 Yes Yes    
Features & configuration        
SQL Core        
Database Engine Services Yes Yes    
Full-Text and Semantic Extractions for Search Yes Yes    
Reporting        
Reporting Services – Native Yes Yes    
Analysis Services Yes Yes    
Collation settings        
Must be accent sensitive Yes Yes    
Must not be case sensitive Yes Yes    
Must not be Binary Yes Yes    
Must not be Binary - code point Yes Yes    
Authentication        
Windows authentication Yes Yes    
Service accounts        
SQL Server        SQLSERVICE
SSRS        TFSREPORTS
Default Ports        
SQL Service (Database Engine)     1433  
SQL Browser Service (Database Engine)     1434  
SQL Server Analysis Services Redirector      2382  
SQL Server Analysis Services     2383  
SQL Server Reporting Services     80  
SharePoint        
Versions        
Windows SharePoint Services 3.0 (Foundation, Standard, Enterprise) Yes No    
Microsoft Office SharePoint Server 2007 (Foundation, Standard, Enterprise) Yes No    
Microsoft SharePoint Server 2010 (Foundation, Standard, Enterprise) Yes Yes    
Microsoft Office SharePoint Server 2010 (Foundation, Standard, Enterprise) Yes Yes    
Microsoft SharePoint 2013 (Foundation, Standard, Enterprise) Yes Yes    
Microsoft Office SharePoint Server 2013 (Foundation, Standard, Enterprise) Yes Yes    
Default Ports        
Default website     80  
SharePoint Central Administration     17012  
Service accounts        
SharePoint Products        WSSSERVICE
Team Build OS         
Versions        
Windows Server 2008 SP2 (Standard, Enterprise, Datacenter) Yes No    
Windows Server 2008 R2 SP1 (Standard, Enterprise, Datacenter) Yes Yes    
Windows Small Business Server 2011, with latest SP Yes Yes    
Windows Server 2012 (Essentials, Standard, Datacenter) Yes Yes    
Windows Server 2012 R2 (Essentials, Standard, Datacenter) Yes Yes    
Windows 7 32-/64-bit (Home Premium, Professional, Enterprise, Ultimate), with latest SP Yes Yes    
Windows 8 32-/64-bit (Basic, Pro, Enterprise) Yes Yes    
Windows 8.1 (Basic, Pro, Enterprise) Yes Yes    
Default Ports        
Build     80  
Service accounts        TFSBUILD
Team Foundation Build      9191  
Project Server        
Versions        
Project Server 2007 Yes No    
Project Server 2010 Yes Yes    
Project Server 2013 Yes Yes    

 Reference : 

 

Tags: ,

TFS | TFS 2012 | TFS 2013

About Test Attachment Cleaner

by Xavier Dilip Kumar 30. January 2014 11:37

Explanation:

A command line tool that only removes the attachments. It does not touch the test runs, which contain the pass/fail data. So, running Test Attachment Cleaner will not impact the record of the test runs.

You need to Test Attachment Cleaner if you:

  1. Do manual test runs and want to delete attachments without deleting the test runs
  2. Do automated test runs and want to delete attachment for builds which have been deleted already, but the build definition’s retention policy was not set to delete “test results” (because this is turned off by default)

You do not need the Test Attachment Cleaner if you:

  1. Have automated test runs triggered by a build, and you have configured the build definition’s retention policy to delete “test results” (which is not set by default)
  2. Delete the Test Runs manually (as this deletes the attachments)

 SQL Query to get the attachment type associated with the team project.

Select projects.ProjectName, SUBSTRING(attachments.filename,

len(attachments.filename)-CHARINDEX('.',REVERSE(attachments.filename))+2,999) as Extension, sum(f.compressedlength)/1024/1024 as SizeInMB
From tbl_Attachment as attachments
INNER JOIN tbl_File as f on attachments.TfsFileId=f.fileid
INNER JOIN tbl_TestRun as tr on attachments.TestRunId = tr.TestRunId
INNER JOIN tbl_Project as projects on tr.ProjectId = projects.ProjectId
Group by projects.ProjectName, SUBSTRING(attachments.filename,len(attachments.filename)-CHARINDEX('.',REVERSE(attachments.filename))+2,999)
Order by sum(f.compressedlength) desc


Download Attachment Cleaner

Command to preview the attachments before delete
tcmpt attachmentcleanup /collection:TfsUrl /teamproject:TeamProjectName /settingsfile:SettingsFile /outputfile
:<Output dir>/teamproject.log /mode:preview
Command to delete the attachments
tcmpt attachmentcleanup /collection:TfsUrl /teamproject:TeamProjectName /settingsfile:SettingsFile /outputfile:<Output dir>/teamproject.log

Sample settingsfile

<DeletionCriteria>
  <TestRun/>
  <Attachment>
    <SizeInMB GreaterThan="50"/>   
  </Attachment>
  <LinkedBugs>
    <Excludestate="New"/>
    <Excludestate="Committed"/>
    <Excludestate="Approved"/>
  </LinkedBugs>
</DeletionCriteria>

Tags:

MTM | TFS 2010 | TFS 2012 | TFS 2013

Unknown domain users displayed in the work items "assigned to" field

by Xavier Dilip Kumar 29. January 2014 16:57

Description:

IT administrators account get populated in the work item "assigned to" field.

By default, [TEAM FOUNDATION]\Valid Users include [TEAM FOUNDATION]\Team Foundation Administrators which holds [BUILT IN]\Administrators.

Workaround:

In the TFS Server Administration Console

1. Select Application Tier and clicked Group Membership. I

2. Double-click on [TEAM FOUNDATION]\Team Foundation Administrators 

3. Remove [BUILT IN]\Administrator

Tags:

TFS 2010 | TFS 2012 | TFS 2013

How to query build controller and agent details in a collection database

by Xavier Dilip Kumar 2. January 2014 08:51

Solution:

SELECT a.ControllerId "Controller ID", a.DisplayName "Controller Name" , a.Status "Controller Status(1 - Active)",

b.AgentId "Agent ID", b.DisplayName "Agent Name", b.Status  "Agent Status(1 - Active)" FROM tbl_BuildController a , tbl_BuildAgent b where a.ControllerId = b.ControllerId

Tags:

TFS | TFS 2010 | TFS 2012 | TFS 2013

w3wp.exe process is missing after TFS app tier reboot

by Xavier Dilip Kumar 23. December 2013 11:12

Explanation:

w3wp.exe an Internet Information Services (IIS) worker process is a windows process which runs Web applications, and is responsible for handling requests sent to a Web Server for a specific application pool. W3wp.exe process will not be started automatically after App tier reboot or IIS restart or application pool restart. w3wp.exe will be launched once the first request is made to the TFS Application.

Solution:

1. Try accessing TFS application once http://tfs:8080/tfs. See whether the w3wp.exe is available in "Windows Task Manager" --> "Processes Tab"

2. You can configure Worker process started automatically by adding startMode attribute to TFS application pool to AlwaysRunning in your applicationHost.config

<applicationPools>

   <add name="Default App Pool" startMode="AlwaysRunning" />

</applicationPools>

Solution 2 will work for IIS 7.5 or newer

Tags:

TFS | TFS 2010 | TFS 2012 | TFS 2013

About the author

My name is Xavier Dilip Kumar Jayaraj and I am a Software Configuration Management Engineer with a background in application development, Build & packaging using Install Shield.

Profile in LinkedIn

  

Quotes I Like

"Failure will never overtake me if my determination to succeed is strong enough."  - Dr. APJ. Abdul Kalam

"Always be yourself, express yourself, have faith in yourself, do not go out and look for a successful personality and duplicate it." - Bruce Lee

"Technology is just a tool. In terms of getting the kids working together and motivating them, the teacher is the most important." - Bill Gates

"Innovation distinguishes between a leader and a follower." - Steve Jobs

Disclaimer

The information provided here is based on my expreriences, troubleshooting and online/offline findings. It can be used as is on your own risk without any warranties and I impose no rights.

Month List