Problem

I have a lab environment configured with 4 machines. It is running in Network Isolation, and has workflow and test capability enabled.  The testing capability fails only on one machine. 

Solution

Adjust the binding order of your network adapters so that external adapter is first.  To do this bring up the Network Connections window and click on the Advanced menu.  If the Advanced menu is not showing press the Alt key to display it.

From the Advanced Menu selected Advanced Settings.  The Advanced Setting dialog will open.

Use this dialog to move the external network adapter to the top of the list.

Explanation

If you are getting a message like the one below:

"The machine is not ready to run tests because of the following error: Unable to connect to the controller on '<TestControllerFQDN>:6901'. Reason: No such host is known. Make sure the test controller is online and the firewall on the test controller is not blocking the connection."

The chances are if you try to ping the Test Controller machine from the lab machine it will fail.  If the internal network adapter binds first it may cause issues when trying to resolve network names.  Simply move the external network adapter to the first position.

Problem

My build agent state in Team Foundation Administrative Console states Ready but the icon shows stopped and I can't queue builds.

Solution

Either log in as the Service Account used to run the build agent or log in using any account and right click on IE and run as the Service Account.
1. Open Internet Explorer and go to Tools –> Internet Options
2. Choose the Connections tab
3. Click the “LAN settings” button
4. Uncheck the “Use a proxy server for your LAN” checkbox. 

Explanation

One of my builds collects code coverage results on a web application.  To do so the IE connection settings are configured to use a proxy while the data is collected and then returned to the original configuration afterwards.  However, if you are forced to stop a build the proxy will stay configured and lead to this problem. The key is to log in or run IE as the Service account to uncheck the proxy check box on the connection setting of IE.

Problem

When I run VMM I am given the error I don't have permissions to run VMM on localhost.

Solution

You have to have a current VMM administrator to add you to the Administrator role in VMM under Administration tab.

1. Start VMM
2. Click the Administration tab
3. Select User Roles
4. Double Click Administrator under Profile Type
5. Click the Members tab
6. Click Add… and add the user

Problem

Calling psexec from an invoke process activity on a 2008 Server and it is hanging.

Solution

Upgrade to 1.98 of psexec and use the -h switch to run with the account's elevated token.

Explanation

If the target system is Vista or higher, the -h allows the process to get past the UAC that is preventing the application from running as expected.

PSTools