On my Windows 2008 R2 server, I have TFS 2010 installed.
I just installed Visual Studio 2010 test controller and test agent. When configuring test agent, I don't know what to enter for the controller name, as I want to register the agent I just installed with the controller I just installed.
Any ideas what the controller's default name and port is? Or how I can find out what it is?
Thanks in advance.
You can get the Controller Name from the TFS if you have installed it.
Go to Test Manager -> Lab Management -> Controllers
The default Port Number is 6901
127.0.0.1:6901
This did the trick. But feel free to add any comments you may have.
Related
MSDN says there should be an option in the Properties pane to change the port. There isn't.
How can you change the port of your local web server in Visual Studio 2015 community edition?
EDIT: I believe part of the problem may be that I'm doing a web site projet, not a web application project and those are different for how they allow you to access ports.
The bottom line is, I can't start up the server because something is using the same port.
The option doesn't exist in the enterprise edition either. It seems to be stored in
[My Documents]\Visual Studio 2015\Projects[Your Web Site Name].vs\config\applicationhost.config
You should search for the current port number and replace it.
Bases on #levininja's comment, I managed to solve the error by following the below instructions:
Open visual studio solution file *.sln in your project folder and look for:
VWDPort = "54638"
The default port number may be different than mine. In my case it is 54638.
Change the port to the port number you want.
on my computer I have a problem with connection to TFS 2013 using Visual Studio 2013 and 2015. This problem occurs on only one machine. Other users in the net can work without problems. In the same time I can connect to projects on Visual Studio Online. Problem happened after switching a few times between projects. Nothing was installed or changed either on my computer or on TFS Server. I've got following error: "Technical information (for administrator): The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF".
I've check this article:
https://msdn.microsoft.com/query/dev12.query?appId=Dev12IDEF1&l=EN-US&k=k(vs.tfc.connecttotfs.unabletoconnect)&rd=true
But in section: "You receive this error when you try to connect to an on-premises TFS from your client computer " I didn't found solution. I also reinstalled Visual Studio but it didn't solved my problem.
How to solve this? Is there a way to check some logs or events to find a reason? Thanks in advance for your help.
Regards Pawel
To narrow down this problem, try the following actions:
1.check whether there is something wrong with user account
a) Connect to TFS with the same user on another machine.
b) Login in tfs web access in web browser with your account
2.Clear TFS local cache http://www.ewaldhofman.nl/post/2009/07/06/Clear-the-cache-of-TFS.aspx For TFS 2013 the default path: C:\Users\XXX\AppData\Local\Microsoft\Team Foundation\5.0\Cache
I have a Visual Studio 2012 and a Microsoft Dynamics CRM 2013. I use the CRM SDK Visual Studio plugin to connect my VS to the CRM. On my machine it works, on my colleagues machine it does not work. He gets the following error message when clicking the login button:
The request for security token could not be satisfied because authentication failed
I set up all machines and my Windows client machine was added to the domain automatically. We added his machine, too (via Active Directory Users and Computers) but that did not help. We both use either default credentials or login with the domain administrator (domain\administrator) with the same results.
What do I have to configure to enable my colleague to login, too?
Detail information: Server is a Win2012 R2 Server, clients are both Win7.
Cheers,
Arne
We solved the problem. A look in the appropriate place in the event log showed that the Visual studio sends the wrong credentials when the login is performed
during startup of VS. When that is canceled, the startup completes and afterwards the connection to the CRM is made, VS sends the correct credentials
and the login works.
I hope that helps someone to save some time.
Cheers,
Arne
I'm attempting to remotely debug an application. I can connect to it without an issue but as I step through the code I can not see the values of the variables the way I do when debugging locally.
When I try to evaluate a variable in the watch window I get the message "internal error in the expression evaluator". Do I need to do anything different to resolve this?
It seems to be a bug that affects Visual Studio 2012 when you remote debug an application compiled for .NET 3.5 or previous versions.
See this link for more details.
As described in Microsoft blog by link Luca in previous post you need perform these steps to fix this:
Install "Visual Studio 2012 Update 2"
Take from GAC "Microsoft.VisualStudio.vil.dll" vesion=11.0.0.0 on machine where you installed update
Copy assembly from prev. step to GAC on remote machine which you want debug
Optionally you can update remote debug tools on remote machine by "Update 2"
After that watch window should work correctly!
I've upgraded our TFS 2010 to TFS 2012 without any issues. I can connect to the source control, checkin, everything I need to Work.
But if I go to the settings page for the team project I'm connected to, the following options work as expected:
Team project: Source Control
Team project: Portal settings
Team Project Collection: Source Control
Team Project Collection: Process Template Manager
But the rest of the options on the settings page just gives me this error
I've tried looking at the requests Visual Studio makes to the TFS server using Fiddler, and with the ones that don't work, no requests are actually being made to the server. So it seems like the server is never being contacted for those specific options.
I've tested this on two independent installations of Visual studio 2012, runnning on Windows 8.
EDIT
I just installed VS2010 SP1 on one of the machines, and I can just fine access all of the following settings options: Security, Group Membership, Areas and Iterations, Portal Settings and Source Control.
Looks like a VS2012 issue of some sort.
We resolved our issue with this by running VS 2012 with our domain credentials. We use VMs for development, so we do not directly login into the domain. To run VS, we use the following (as a batch file):
runas /netonly /user: username "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe"
where username is your domain credential.
It sounds like the code is still using some values that are cached on the client after the upgrade. How long ago was it that you upgraded the server?
To test whether that is it, rename your cache folder (with VS 2012 closed) and launch VS 2012 again so it recreates the cache from scratch.
C:\Users\\AppData\Local\Microsoft\Team Foundation\4.0