When I want to connect to a server in Microsoft Test Manager I got this error message:
Unable to connect to server 'tfsserver:8282'. Check that the server name is correct and that you have access to the server.
This is Microsoft Test Manager 2010.
I can access tfs server in that url throughout a web browser, using Visual Studio 2010, using Team Explorer 2012.
The TFS server is installed in Windows Server 2008 R2 Standar
The TFS installed version is: 11.0.50727.1 (RTM)
Configured virtual directory is: \tfs
Configured ports are: 8282
Service account: NT AUTHORITY\Network Service
Authentication: NTLSM
Notificacion url: http: //tfsserver:8282/tfs
Server url: http: //localhost:8282/tfs
Web Access url: http:// tfsserver:8282/tfs
Machine name: TFSSERVER
My PC and the server are under a windows domain. My domain user is included in the management console users in TFS.
What can be wrong?
this is compatibility issue you need
tfs 2010,test manager2010,team explorer2010
or
tfs 2012,test manager2012,team explorer2012
and the second solution for this is to download update patches from Microsoft Website to enable upward or downward compatibility.
Related
TFS Server : TFS 2018 Update 3
I am working on a TFS 2018 Update 3 release definition to deploy a website “MyWebSite” under “Default Web Site” on IIS server (Windows server 2012, IIS 8).
So it should be look like ServerName\Sites\Default Web Site\MyWebSite
I am using WinRM - IIS Web App Management Task. Under Website Name , I am using Default Web Site\MyWebSite
Website Name = Default Web Site\MyWebSite
I am getting the error System.Exception: ERROR ( message:Can not set attribute "name" to value "Default Web Site/MyWebSite". )
I checked this link TFS 2017 Release definition. WinRM - IIS Web App Management task. Create application under "Default web site" but it is for TFS 2017 and it is not working for me.
How to Fix this error? How can i have "MyWebSite" under "Default Web Site"
Thanks for help.
Microsoft added support to create virtual directories and virtual applications in version 2 (PreView) of the task. And it is working.
I am trying to configure Release Management Client to work with a Release Management Server for Microsoft TFS 2013 on a Windows Server 2008 R2 Standard.
I installed (without any errors) the following two from our subscription downloads:
en_release_management_server_for_team_foundation_server_2013_with_update_4_x64_web_installer_5920525
en_release_management_client_for_visual_studio_2013_with_update_4_x86_x64_web_installer_5920526
I have not installed any Microsoft Deployment Agents.
I have installed and configured the RM server for a SQLExpress db (different from the TFS db in our case) and for now I used my own network credentials (being a member of Administrators group on the server and a member of Default Collection Administrators on TFS, with "Make requests on behalf of others" set to "Allow" on TFS).
When I copy the RM Server URL from "Configure Release Management Server" screen (http://xxx:1000/ReleaseManagement) and paste it into a browser, the page loads without any errors.
However, when the same URL is used in RM Client Configuration, I get an error: "The server specified could not be reached":
We have VS2012 on the server and VS2013 Ultimate on my own dev machine.
I tried installing and configuring the client on both the server (Win Server 2008 R2 Standard) and my dev machine (Win 8.1 Pro), and I still get the same error (so I assume the version of VS is not an issue).
Looking at the event log, I get two errors.
ERROR ONE:
The remote server returned an error: (404) Not Found.: \r\n\r\n at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at Microsoft.TeamFoundation.Release.Data.WebRequest.PlatformHttpClient.EndGetResponse(IAsyncResult asyncResult)
at Microsoft.TeamFoundation.Release.Data.WebRequest.RestClientResponseRetriever.EndGetAsyncMemoryStreamFromResponse(IAsyncResult asyncResult, IPlatformHttpClient platformHttpClient)
.... [edited out for brevity]
Process Name: C:\Program Files (x86)\Microsoft Visual Studio 12.0\Release Management\Client\bin\ReleaseManagementConsole.exe
ERROR TWO:
Error communicating to the web server URL: http://xxx:1000/ReleaseManagement/account/releaseManagementService/_apis/releaseManagement/
Indeed, when I enter that URL in a browser, I get "404 - File or directory not found". Here is what the site structure is:
What I should do to be able to configure our Release Management Client without errors, please?
Additional observations:
I cannot see "Release Management" role on our server, but have seen in mentioned in relation to RM installs.
The client installer reads "Release Management Client for Visual Studio 2013 Update 4", whereas instructions here indicate it should be "Release Management Client for Team Foundation Server 2013 Update 4". Surprisingly, when I ran the installer recommended by that article, the title again read "...for Visual Studio" as opposed to "...for Team Foundation Server".
Many thanks in advance!
You're entering the wrong URL. The URL should be http://<RM Server Name>:<Port>. No /ReleaseManagement/.
The /ReleaseManagement/ folder is not for the desktop client, but rather for the approval dashboard.
I have a Team Foundation Server 2013 installed on a server on a domain. I can connect to this server from my domain account using VS 2012.
I also have a virtual machine which runs on Windows XP and NOT part of the domain (login as a local user). I have a VB6 project running on this VM and I want to connect to the TFS to share and control my VB6 code but I keep on getting The Request Failed with HTTP status 404: Not found.
I tried creating a local user on the server with the same name as the user I use for VM but it didn't work. I cannot join the VM to the domain as well.
Hope someone has tackled this and shed me some light.
After DCpromoing and then demoting the server that TFS runs on, we cannot use WSS ("Cannot connect to the configuration database") to manage team projects. I believe that if I could find the default permissions that are set up when TFS is first installed on a server that is joined to a domain - in terms of any service accounts that are created and which accounts various services should run as - I would be able to get it back up and running again. Does anybody know the default NT accounts and permissions for Team Foundation Server?
That error sounds like a SharePoint error. This technet article outlines the permissions (server, SQL, registry) that are required for a default WSS install.
I am unable to access Sharepoint Central Administration.
I installed MOSS 2007 successfully on Windows Server 2008 (IIS7 and SQL Server 2005), I launched the admin and got "Cannot connect to the configuration database" error.
Application pool is using NetworkService account which has access to SQL Server.
I can access the configuration databases through SQL Management Studio. SQL server is on the same machine.
Any help, suggestions on how to solve the problem? I am very new to SharePoint.
Maybe try running the SharePoint Products and Technologies configuration wizard again to see if that highlights what the issue might be.