"Microsoft Root Certificate Authority 2010 or 2011 is missing and can cause installation failures for some signed packages. For more info, see http://support.microsoft.com/kb/931125."

by Xavier Dilip Kumar 25. March 2014 12:24

Explanation:

VS 2012 update 3 failed to install on Windows 7 64 bit OS due to Microsoft Root Certificates

Exception: 

"Microsoft Root Certificate Authority 2010 or 2011 is missing and can cause installation failures for some signed packages.  For more info, see http://support.microsoft.com/kb/931125."

Solution:

Note: You may see "Update for Root Certificates For Windows XP" in the site page. But the executable work on win 7 and also fix the issue.

  • Try to install VS 2013 Update 3 again.

 

Tags:

Visual Studio 2012

Could not connect to TFS server within Eclipse plugin from linux OS

by Xavier Dilip Kumar 25. March 2014 07:35

Explanation:

TFS user was not able to connect to TFS through Eclipse plugin from linux box. TFS connection hangs forever. When I tried to debug, I found the user was not able connect to intranet\internet within Eclipse IDE.

Solution:

Enabled the proxy settings in the Eclipse IDE. Following are the steps

1. Open Eclipse

2. Go to "Windows" --> " Preferences" menu

3. Expand "general"

4. Select  "Network Connections"

5. Select "Active Provider" as manual

6. Select " HTTP " --> click "Edit"  --> Enter Host as "Your proxy server" and port as "Your proxy server port (usually 80)" --> click "ok" --> click "ok" --> click "apply"

7. Restart "Eclipse"

8. Try connecting to TFS Server.

 

Tags:

TFS | TFS 2012 | TFS 2013

How to enable the TFS add-in for excel?

by Xavier Dilip Kumar 18. March 2014 11:33

Solution:

  • Open Excel
  • Click on “File” --> “Option” menu
  • Click on “Add-Ins”
  • Search for “Team Foundation Add-in”
  • If you see “Team Foundation Add-in” under “Disabled Application Add-in”
  • Select “Disabled Items” and click “Go” button  
  •  
  • Select “Team Foundation Add-in” and click “Enable”
  •  
  • Close and reopen excel

Tags:

TFS 2010 | TFS 2012 | TFS 2013

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

Virtual Drives created using "subst" command not available in Windows Explorer

by Xavier Dilip Kumar 11. March 2014 14:04

Workaround:

Execute the "subst" command with no administrator privileges.

subst Z: "C:\Folder 1"

Now you should see the virtual drive in the windows explorer

Tags:

General

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

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