Developer Support Team System

Available Updates for Visual Studio 2010 Testing Tools

Teodora Stanev - MSFT — Mon, 20 May 2013 04:36:00 GMT

List of all available updates for Visual Studio 2010 Testing Tools:

You experience slow performance when there are many builds in Team Foundation Server in Microsoft Test Manager 2010

http://support.microsoft.com/kb/2253789

Update for Microsoft Visual Studio 2010 Lab Management

http://support.microsoft.com/kb/983578

Update for Microsoft Visual Studio 2010 Video Data Adapter

http://support.microsoft.com/kb/2160831

Description of the hot-fix roll up package for Microsoft Test Manager 2010: October 2010

http://support.microsoft.com/kb/2387011

The Visual Studio 2010 Test Prerequisite for Microsoft Visual Studio 2010 Feature Pack 2 hot-fix roll up is now available

http://support.microsoft.com/kb/2403277

Description of Visual Studio 2010 Service Pack 1

http://support.microsoft.com/kb/983509

Microsoft Visual Studio 2010 Service Pack 1 (Installer)

http://www.microsoft.com/en-us/download/details.aspx?id=23691

An update roll-up is available for the testing tools in Visual Studio 2010 SP1

http://support.microsoft.com/kb/2544407

An update roll-up for Visual Studio 2010 SP1 is available to update the testing tools: July 28, 2011

http://support.microsoft.com/kb/2443428

FIX: "The Maximum number of data series per chart is 255" error when you use Excel 2010 to create an Excel load test report

http://support.microsoft.com/kb/2591428

FIX: WorkingDirectory appSetting element in the QTAgentService.exe.Config file does not work when you run a load test in Visual Studio 2010 SP1

http://support.microsoft.com/kb/2634636

FIX: The "Expected Result" field is blank in Test Manager 2010

http://support.microsoft.com/kb/2625302

FIX: Tests are canceled when you run unit tests in parallel by using Visual Studio 2010 or MSTest.exe

http://support.microsoft.com/kb/2619410

FIX: Test Management Warehouse Sync job times out in Visual Studio TFS 2010 SP1

http://support.microsoft.com/kb/2629068

FIX: Test controller crashes or stops responding when you run web tests in Visual Studio 2010 if the test results are large

http://support.microsoft.com/kb/2626667

FIX: The value of a variable is truncated if you set the variable to a long data-string value in Test Manager 2010

http://support.microsoft.com/kb/2637735

FIX: Expected results are not displayed if a test case is imported from an Excel spreadsheet by using copy and paste in Microsoft Test Manager 2010

http://support.microsoft.com/kb/2656136

FIX: Visual Studio 2010 SP1 IDE stops responding when you start an application in debug mode after you open Test View or Test List Editor

http://support.microsoft.com/kb/2658067

FIX: "No such host is known" error message when you run a load test on a test agent and a test controller in Visual Studio Team Agents 2010

http://support.microsoft.com/kb/2643086

FIX: Attachments in the test results are missing when you stop an automated test run in MTM 2010

http://support.microsoft.com/kb/2674121

FIX: Test Manager crashes when you run a manual test case that has some diagnostic data adapters selected in Visual Studio 2010

http://support.microsoft.com/kb/2674713

An update roll-up that resolves issues in Test Manager 2010 SP1 is now available

http://support.microsoft.com/kb/2673532

An update is available for Visual Studio 2010 that resolves some deadlock issues

http://support.microsoft.com/kb/2695610

FIX: An update is available to enable customization of control identification for the Coded UI Test extension model in Visual Studio 2010 SP1

http://support.microsoft.com/kb/2696646

FIX: A recorded HTTP request does not match the actual HTTP request when you use a custom Web Test Recorder plugin in Visual Studio 2010

http://support.microsoft.com/kb/2708915

FIX: A hot-fix roll up is available for Team Foundation Server 2010

http://support.microsoft.com/kb/2722491

FIX: Test controller crashes when a Web test returns a large result file in Visual Studio 2010 or in Test Manager 2010

http://support.microsoft.com/kb/2616171

FIX: System.InvalidOperationException exception when you run a test on a test agent in Visual Studio 2010

http://support.microsoft.com/kb/2700656

FIX: Incorrect number of transactions in load test results in Visual Studio 2010

http://support.microsoft.com/kb/2770576

Missing - The hot-fix associated KB 2777842 is being withdrawn because it is included in the hot-fix associated with KB 2801364

http://support.microsoft.com/kb/2777842

FIX: An update is available that enables you to obtain the status of test agents by using a command line in Visual Studio 2010

http://support.microsoft.com/kb/2801364

FIX: ObjectDisposedException exception occurs when you run a load test in Visual Studio 2010 and in Test Manager 2010

http://support.microsoft.com/kb/2780448

FIX: IP address of a virtual user changes when you run a load test if IP switching is enabled in Visual Studio 2010

http://support.microsoft.com/kb/2769120

FIX: The status of a blocked test case is not updated in the report after you reset it in Microsoft Test Manager 2010

http://support.microsoft.com/kb/2856157

How to run Load test from Team Build 2012

Teodora Stanev - MSFT — Mon, 29 Oct 2012 22:40:00 GMT

Create a new Build Definition using the Default Process Template in TFS 20120.

For a complete walk through, please see:

Run Tests in Your Build Process

http://msdn.microsoft.com/en-us/library/ms253138%28v=vs.110%29.aspx

NOTE:

When you edit the Build definition, make sure to select "MSTest" to run the tests.

For more information, please see

http://msdn.microsoft.com/en-us/library/ms253138(v=vs.110).aspx#Runner_MSTest

In the Add/Edit test run dialog box, add as an additional command line argument:

/TestContainer:C:\Builds\1\...\....\ LoadTest1.loadtest

Also, see:

Running a Single Load Test from the Command-Line

http://msdn.microsoft.com/en-us/library/ms182588.aspx#Single

If you get an error similar to the following:

TF270015: 'MSTest.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details.

From the drop folder open the ActivityLog.AgentScope.1.xml.

Search for the MSTestActivity and see what arguments you are passing to MS Test.

You should see something similar to the following:

The MSTestActivity was invoked without a value for Platform or Flavor. The values Any CPU and Debug were used……………………………………………………………………

test:LoadTest1.loadtest

Invalid switch "test".

For switch syntax, type "MSTest /help"

Handle Test Run Exception00:00:00

If testException is NOT TestFailureException00:00:00

Inputs

Condition: True

TF270015: 'MSTest.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details.

In the sample above, Team Build cannot find the actual LoadTest1.loadtest.

Once you provide the correct command line arguments,
you should be able to run load tests from Team Build 2012.

Test Attachment Cleaner for VS2010 - everything you need to know

Teodora Stanev - MSFT — Mon, 08 Oct 2012 17:50:00 GMT

TFS2010: Test Attachment Cleaner and why you should be using it

http://blogs.msdn.com/b/granth/archive/2011/02/12/tfs2010-test-attachment-cleaner-and-why-you-should-be-using-it.aspx

2. Test Attachment Cleaner for Visual Studio Ultimate 2010 & Test Professional 2010 – download page

http://visualstudiogallery.msdn.microsoft.com/3d37ce86-05f1-4165-957c-26aaa5ea1010

3. A hotfix that can reduce the size of the test data saved to the TFS database is available for Team Foundation Server 2010 Service Pack 1

http://support.microsoft.com/kb/2608743

This is a hot-fix to reduce the size of the attachments added in TFS database – in another words after installing the hot-fix you will not see such growth in your TFS database

You will still need to run the TAC tool to clean your TFS Database from old attachments

4. These are the best practice recommendations for using the Test Attachment Cleaner:

Experiment with the tool in preview mode - this is sample command line

tcmpt.exe attachmentcleanup /mode:preview /collection:"http://teddytfs:8080/tfs/defaultcollection" /teamProject:GeneralTests /settingsFile:"C:\Program Files (x86)\Microsoft\Test Attachment Cleaner\SampleSettings\Test.xml" /outputFile:Output_preview.log

This will generate log similar to the following

</Attachment>

</DeletionCriteria>

----------- Command Line Parameters ------------

Project Collection: http://teddytfs:8080/tfs/defaultcollection

Team Project: GeneralTests

Mode: Preview

Settings File: C:\Program Files (x86)\Microsoft\Test Attachment Cleaner\SampleSettings\Test.xml

------ Settings File Parameters ------

TestRun: False

Attachment: True

Size Greater Than 1 MB

LinkedBugs: True

----------- Execution Details ------------

The following attachments have been identified for deletion:

AttachmentName Size LinkedTo Bug IDs

-------------- ---- ----------------

ScreenCapture.xesc, 1.6 MB ( 1645362 bytes),

ScreenCapture.xesc, 2.0 MB ( 2117644 bytes),

ScreenCapture.xesc, 59.3 MB ( 62219836 bytes),

ScreenCapture.xesc, 3.6 MB ( 3805764 bytes),

ScreenCapture.xesc, 2.3 MB ( 2397380 bytes),

ScreenCapture.xesc, 2.6 MB ( 2693314 bytes),

ScreenCapture.xesc, 15.0 MB ( 15766286 bytes),

ScreenCapture.xesc, 20.5 MB ( 21471042 bytes),

ScreenCapture.xesc, 11.4 MB ( 11982358 bytes),

ScreenCapture.xesc, 3.9 MB ( 4053566 bytes),

ScreenCapture.xesc, 25.6 MB ( 26815510 bytes),

ScreenCapture.xesc, 2.0 MB ( 2069308 bytes),

------------ Summary ------------

Number of attachments affected: 12

Total size of attachments: 149.8 MB

Elapsed time was 22.64 seconds

Look at the total size of attachments to be deleted – make sure it is not bigger than 500 MB
Run the same command line with the same settings in delete mode
Check how long will take for SQL to clean the ghost records
Once the ghost records are cleared, delete another chunk of ~ 500 MB

5. Here is a short write-up on the ghost cleanup task and what it does provided from our SQL Team:

What are ghost records?

Sql Server stores data in terms of 8 K pages. Each page belongs to a particular object i.e. user or system table.

When you delete data from Sql Server table, we shall change metadata in the page header to indicate that there are deleted rows in particular page.

In more technical terms, when a record is deleted from a clustered index data page or secondary index leaf page, the record is not always physically removed from the page. Rather, the record may be marked as a ghost record and removed later.

What is the ghost cleanup task?

Every Sql Server installation shall have one thread dedicated for doing ghost cleanup. Note that it is a single thread that is responsible for cleaning up ghost records across ALL databases on Sql Server. On a busy server with several databases, you may notice that the background ghost cleanup task never catches up with volume of deletes happening. Since this is a single task for the entire SQL Server and works on one database, ten PFS pages at a time, the number of ghost records may keep increasing with the task falling behind.

Who uses the ghost cleanup task?

Pretty much any delete activity shall result in ghost records. For LOB data, we typically do in place deletes i.e. do not enqueue for ghost cleanup rather de allocate in place. However, for the TAC tool database we have Read Committed Snapshot Isolation turned on – under which we actually end up enqueuing the page into ghost cleanup.

How to monitor the ghost cleanup task?

You can monitor the number of ghost records by table by using the following query

SELECT object_name(object_id) as Name, record_count, GHOST_RECORD_COUNT,Version_ghost_record_count,INDEX_TYPE_DESC, ALLOC_UNIT_TYPE_DESC

FROM sys.dm_db_index_physical_stats (DB_ID(N'<dbname>'), object_id('<TableName'), NULL, NULL , 'DETAILED')

Note that this is a resource intensive query so you typically do not want to run it during business hours.

Another option to monitor ghost cleanup is to use Xevents as outlined here:

http://sqlblog.com/blogs/jonathan_kehayias/archive/2010/12/15/an-xevent-a-day-15-of-31-tracking-ghost-cleanup.aspx

The output of this Xevent will show us how the enqueuing is happening.

Is there a way to speed up the ghost cleanup process?

No. It is a background task. The best thing you can do is to monitor the ghost record count via the query and Xevent given above.

What are the known issues around ghost cleanup task?:

Make sure that you are using SQL version that includes the following FIX: ghost_record_count values keep increasing in SQL Server 2008 R2 or in SQL Server 2008

http://support.microsoft.com/kb/2622823

How to avoid issues around ghost cleanup task?

• Do not do huge deletes in place

• Delete data in smaller number of rows and allow ghost cleanup to clear out the deleted rows before repeating.

Depends on the SQL version the fix for ghost_record_count is in different CUs:

SQL Server 2008 Service Pack 3 - Cumulative update package 4 for SQL Server 2008 Service Pack 3 and after

http://support.microsoft.com/kb/2673383

SQL Server 2008 R2 - Cumulative update package 10 for SQL Server 2008 R2 and after

http://support.microsoft.com/kb/2591746

SQL Server 2008 R2 Service Pack 1 - Cumulative Update package 4 for SQL Server 2008 R2 Service Pack 1

http://support.microsoft.com/kb/2633146

How to determine the version and edition of SQL Server and its components:

http://support.microsoft.com/kb/321185

Issues while configuring TFS 2010 with the test controller in different domain

Nitish Nagpal — Mon, 01 Oct 2012 13:26:00 GMT

Problem Description:

You may face issue while configuring TFS 2010 with the test controller which is in different domain.

Resolution:

If you want to register a test controller that is in a workgroup or a different domain that does not have a two-way trust with the domain for your Team Foundation Server, you must also create a local user account with the same user name and password on the Team Foundation Server machine and the test controller machine. This local user account must also be added as a member of the following Team Foundation Server group: [Project Collection]\Project Collection Test Service Accounts. Then you can register the test controller using this local user account when you run the test controller configuration tool.

In case this fails, these are possible checks:

(a) In case you still face the issue, login with the account which you are using to configure test controller.

(b) Add the DNS entry for the controller in the TFS AT host file and vice versa.

Content developed by: Deepak Mittal
Content reviewed by: Teodora Stanev

Issues with some of the counters missing while adding them to the load test settings on non-English OS

Nitish Nagpal — Mon, 01 Oct 2012 13:21:00 GMT

Problem Desc:

You may face issue with some of the counters missing while adding them to the load test settings on non-English OS.

Resolution:

A possible workaround to this problem:

For the specific OS culture, you will find the files related to performance counter.

Like for French, you will have:

In Windows\System32, replacing the below files

perfc00C.dat

perfd00C.dat

perfh00C.dat

perfi00C.dat

by the corresponding (copy-rename) files

perfc009.dat

perfd009.dat

perfh009.dat

perfi009.dat

First, remove all perfx00C file from the folder and then copy-paste the perfx009 and then rename the copied file to perx00C. It should resolve the issue.

Content developed by: Deepak Mittal
Content reviewed by: Teodora Stanev

CssIteration attribute defined in the test case to update the Iteration path does not perform the operation as expected

Nitish Nagpal — Mon, 01 Oct 2012 13:17:00 GMT

Problem Description:

CssIteration attribute which you define in the test case to update the Iteration path does not perform the operation as expected out of it, during the migration of test cases using TCM.exe to Test case workitem.

Resolution:

This attribute currently does not update the iteration path as you all might think.

Work around:

There are two workaround possible to overcome this:

a. After migrating the test cases, export the test cases to excel and change the iteration path and import them back.

b. Make a query for all the work item which you just migrated in team explorer and change the iteration path like below:

Query all the test cases which you have imported.

Select them in the results and say “Edit selected work items”

This is from TSWA 2012, but same should be possible with 2010 as well.

-Change the “iteration path” field to your desired value.

Hope this should help.

Content developed by: Deepak Mittal
Content reviewed by: Teodora Stanev

Performance Issue with Coded UI Test while searching for the HTMLHyperLink control in case you have several controls of this type on the web page

Nitish Nagpal — Thu, 24 May 2012 11:31:00 GMT

Problem description:

Performance issue with the CodedUI test while searching for the HTMLHyperLink control in case you have several controls of this type on the web page.

Resolution:

You may notice that CodedUI test will take time to search for the HTMLHyperLink control. By default CodedUI test generate "innerText" and "TagInstance" properties for the control.

To make the search faster for this control, please add the ID and Name property as well for the control and use them as a search property to make the search faster for this control. With this, in one of a case, I was able to reduce the search time from 10 seconds to not even 1 second.

Note: It is always good to have ID and Name for the controls while working with web plug-in with the CodedUI test.

Content developed by: Deepak Mittal

Content reviewed by: Teodora Stanev

MFC controls not getting recognized on XP machine

Nitish Nagpal — Thu, 24 May 2012 11:26:00 GMT

Problem Description:

Recently got an issue where after migration of the VC++6.0 application to VC++10.0, controls were not getting recognized by CodedUI test builder tool.

Resolution:

In this kind of scenario, first check if the Inspect tool is able to recognize the control or not.

You can download Inspect tool from Windows SDK.

More info for Inspect

http://msdn.microsoft.com/en-us/library/dd318521(VS.85).aspx

2. If inspect tool also throws the error in recognizing the controls, then definitely this is not an error with CUIT product.

3. Though, MFC controls uses MSAA technology by default for identification of the controls, still check if Inspect tool is able to recognize them using UI Automation, this actually was the case in the scenario which I was troubleshooting.

4. If controls are getting recognized by UIA, then you need to enforce CUIT to use UIA instead of MSAA for identification of MFC controls.

5. There is no direct way to perform steps 4, you need to write a plug-in for the same, please refer below blog which has the sample:

http://blogs.msdn.com/b/thejs_blog/archive/2011/05/17/modifying-technology-used-for-identifying-control.aspx

6. You need to modify the sample for the controls, check the class name for the controls and put a condition for that class to use native support in the sample.

With the above steps, I was able to resolve the issue. Hope this would help.

Content developed by: Deepak Mittal

Content reviewed by: Teodora Stanev

Issue while running test from MTM when both MTM and TFS are in different domain and TFS is configured on SSL

Nitish Nagpal — Thu, 12 Apr 2012 19:19:00 GMT

Issue description:

If you have configured TFS 2010 in domain environment A along with SSL configuration and trying to run your tests in MTM from a different domain B,

You may get the error below:

The underlying connection was closed: could not establish trust relationship for the SSL\TLS secure channel

Solution:

TFS is configured in domain environment with SSL configuration and trying to run the test from MTM in domain B, you will be able to connect to TFS from MTM however, while running the test, you will get the error mentioned in the issue description above.

2. Enable tracing in the MTM, you can follow the below blog:

Refer:

http://blogs.msdn.com/b/gautamg/archive/2011/01/20/how-to-enable-tracing-for-mtm.aspx

You may see error in the MTM log as below:

<?xml version="1.0" encoding="utf-8"?>

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<soap:Body>

<soap:Fault>

<soap:Code>

<soap:Value>soap:Sender</soap:Value>

<soap:Subcode>

<soap:Value>WebException</soap:Value>

</soap:Subcode>

</soap:Code>

<soap:Reason>

<soap:Text xml:lang="en">The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.</soap:Text>

</soap:Reason>

</soap:Fault>

</soap:Body>

</soap:Envelope>

I, 2840, 1, 2012/04/10, 13:20:01.932, PLI-T500_CB\mtm.exe, MTR : Perf : Create manual test run: 1149ms

E, 2840, 1, 2012/04/10, 13:20:01.934, PLI-T500_CB\mtm.exe, The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.

Note: you may see other errors as well related to authentication and file not found in the log files, those are not related to the current scenario.

Please check the Server URL setting on TFS admin console, it should be something like: https\\abc.xyz.com\tfs

Try to access the web access "https:\\abc.xyz.com\tfs\web from the server and client both.
If the https:\\abc.xyz.com\tfs\web is not accessible from server and while running it from client, throws the error as mentioned in the error above, then it can be an issue with the client certificate not installed on server.
To run test in MTM when TFS is configured on SSL, you need to have client certificate installed on the server. Reason is:

In TFS 2010, when a user attempts to run a test from MTM, the server makes an outbound web service call to itself aka server-to-server call using the ‘Server Url’ as base address. So in this case, both server and client are in the same machine and the missing certificate led to the issue. The server-to-server call happens only when we attempt test run, hence all other MTM operations will continue to work.

Content developed by: Deepak Mittal
Content reviewed by: Teodora Stanev

Issue while triggering the load test from VS2010

Nitish Nagpal — Mon, 09 Apr 2012 11:52:00 GMT

Issue description:

You may face issue while triggering the load test from VS2010 and controller and agents on different machines, status of the tests always in "In pending" status.

Error message in controller log file:

(QTController.exe,PID 6244, Thread 12) ControllerExecution.DoDeployment: System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
121.121.121.001:12345

Server stack trace:

at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)

at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)

at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket(EndPoint ipEndPoint)

at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()

at System.Runtime.Remoting.Channels.RemoteConnection.GetSocket()

at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String machinePortAndSid, Boolean openNew)

at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.SendRequestWithRetry(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream)

at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)

at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]:

at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

at Microsoft.VisualStudio.TestTools.Common.FileCopyService.get_DeploymentFlags()

at Microsoft.VisualStudio.TestTools.Controller.ControllerExecution.<DoDeployment>b__6(FileCopyService fileCopyService)

at Microsoft.VisualStudio.TestTools.Execution.RemoteObjectContainer`1.InvokeAsRemoteUser(Action`1 invoke)

atMicrosoft.VisualStudio.TestTools.Controller.ControllerExecution.DoDeployment()

atMicrosoft.VisualStudio.TestTools.Controller.ControllerExecution.RunStateDeploying()

Event log on the controller machine:

Log Name: Application

Source: VSTTExecution

Date: 2/3/2012 3:30:57 PM

Event ID: 0

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: ABC.XYZ.local

Description: The description for Event ID 0 from source VSTTExecution cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

(devenv.exe, PID 7620, Thread 32) Test run 'tfsservice@XYZ.local 2012-02-03 15:28:53' could not be executed. Timed out waiting for agent plugins to initialize. the message resource is present but the message is not found in the string/message table

Event Xml:

<Channel>Application</Channel>

<Computer>ABC.XYZ.local

</Computer>

</System>

<Data>(devenv.exe, PID 7620, Thread 32) Test run 'tfsservice@XYZ.local
2012-02-03 15:28:53' could not be executed. Timed out waiting for agent plugins
to initialize.</Data>

</EventData>

</Event>

Note: in the above error message, IP address and port number, domain name and computer name are not actual one.

Resolution:

Load test triggered from VS2010 on one machine and controller and agents are on different machines.

When we triggered the test from VS2010, it was always in "In pending" status.

There was error message in the controller log and event entry in the controller machine as mentioned above.

Enabling logging on controller:

http://blogs.msdn.com/b/aseemb/archive/2009/11/28/how-to-enable-test-controller-logs.aspx

Architecture of communication between VS2010, controller says that when visual studio communicated with controller, it does that on 6901 port and controller communicates with the visual studio on a random port.

Looking at the error messages, it might be an issue when controller wants to communicate with visual studio on random port.

Please check the following to resolve this kind of issue:

Check if controller can communicate on random ports properly.
Check if any firewall exception set in the group policy in the infrastructure for communication on the random ports.
If both a) and b) are fine, it might be an issue with server hardening which generally infrastructure team does for security reasons.
Also you can create the below registry key and client will use ports from this range while receiving data from controller.

HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\VisualStudio\10.0\EnterpriseTools\QualityTools\ListenPortRange\PortRangeStart

HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\VisualStudio\10.0\EnterpriseTools\QualityTools\ListenPortRange\PortRangeEnd

Hope it would help.

Content developed by: Deepak Mittal
Content reviewed by: Teodora Stanev