Test Agent 2012 - bug when installing on Windows XP - by opmet

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 785613 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 4/25/2013 11:46:53 AM
Access Restriction Public


when installing "Agents for Visual Studio 2012" (vstf_testagent.exe) on Windows XP the installer tries to download and install ".net 4.5". this fails as 4.5 cannot be installed on windows XP. error code is "0x800713ec - Asia".
in turn the test agent installer terminates.

workaround is to manually install ".net 4.0", first. after doing so the test agent installer no longer tries to install any .net framework prerequisite and continues installing the actual test agent.

however, this clearly is a bug in the installer logic that should get fixed.
Sign in to post a comment.
Posted by Microsoft on 5/7/2013 at 3:56 AM
Hi opmet,

Unfortunately we do not have any plans to change this experience but we shall make sure we have documented these limitations here.

Appreciate your thoughts on this issue and the feedback provided.

Thank you
Anudeep Sharma
Senior Dev Engineer, Visual Studio.
Posted by opmet on 5/6/2013 at 11:56 AM
will this be fixed with upcoming "Update 3"?
Posted by Microsoft on 5/2/2013 at 7:30 AM
Hi opmet,

Thank you for reporting this issue. The problem that you are experiencing is a known limitation of this installer on XP. The only way to use the Test Agent on XP is to install .net 4.0 before installing the Test Agent, as you have rightly mentioned in the workarounds.

As you may know, with VS2012 we stopped mainline support of XP in the mainline VS products. However to cater to the testing scenarios we decided to make an exception for Test Agent 2012. Due to a variety of reasons we could not improve the experience beyond what it is today.

I know that these steps have not been documented appropriately and we are working with the doc team to address the same.

We appreciate you taking the time to report this issue to us. Please feel free to get back if you need any further information.

Thank you
Anudeep Sharma
Senior Dev Engineer, Visual Studio.
Posted by Microsoft on 4/30/2013 at 2:05 AM
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 opmet on 4/26/2013 at 4:09 AM
attached some more files.
Posted by Microsoft on 4/25/2013 at 10:07 PM
Thanks for reporting the issue. In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

It may help if you provide us with:
a setup log file

You can get the log files with the following steps:
1) Download collect.exe from the link below. <http://go.microsoft.com/?LinkId=8967043>
2) You may choose to save the tool for later use, or to run directly.
3) The utility creates a compressed cabinet of all the VS and .NET logs to %TEMP%\vslogs.cab.

You can get more details about how to get the log files here:

Thanks again for your efforts and we look forward to hearing from you.
Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 4/25/2013 at 3:51 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)