Error Integrating TFS 2017 U3 with SQL Server 2016 Reporting Services - tfs

When I try to integrate TFS 2017 U3 with SQL Server 2017 Reporting Services, from TFS Administration Console, an error appear. Please see screenshot.
In the event viewer of TFS server, I see registered this error:
DCOM was unable to communicate with the computer servername using any of the configured protocols; requested by PID
1080 (C:\Program Files\Microsoft Team Foundation Server 2018\Tools\TfsMgmt.exe).
Error Image
I have had checked the following:
Windows Firewall is not blocking port 80
Reporting service is started
User Account has required permissions
WMI is running on the report Server
TFS databases are in the same server than reporting services and the TFS service is running without any problem.
Please, any idea how to revolve this error will be very appreciated

I was wrong when placing the error text messaage. I had performed a test from TFS 2018 that's the reason why I wrote with that description eror, but the productive environment is with TFS 2017 U3 and the error message is the same thing; the difference is the path where TfsMgmt.exe is located.
Thanks for your attention.
Audberto

Related

TFS 2015 deployment issue: The WinRM client cannot process the request

We are facing a issue when rolling out changes to application server, following are the two tasks in the release definition
Windows Machine File Copy - which works fine
PowerShell on Target Machine - Fails, Error : The WinRM client cannot process the request
Following things I've tried but still no luck
Allow traffic : Open firewall on port 5985/5986 for source/destination
WinRM service is running on target server
Configuration
TFS 2015
Source server : Windows Server 2012 R2
Target Server: Windows 2016 Serer
Could you please assist us on this, thanks in advance.

TFS31002: Unable to connect to this Team Foundation Server

We just upgraded our TFS 2013 to TFS 2015. We use VS2015 to communicate with it(we were already using it with our TFS2013). The server was not available during the time our IT made the upgrade.
After the ugprade, everybody started to work again with the server but I was seing it as Offline and I finally decided to remove the server and add it again.
When I add it again(200% sure of all the settings), I get this error:
I finally tried to do the same on our "old" installation of Visual Studio 2013(same computer, same account), and it works. I was at least capable to commit all my changes to the server.
I tried to go on the portal and click on `Open in Visual Studio", and I got another error(TFS400324):
Now I'm trying to regain access to TFS2015 with my VS2015. I can access the web portal.
Here is what I tried after some research:
Do a Repair of Visual Studio 2015
Check that I've no weird proxy
Check that there is no available update(already at VS2015 UPD 1)
Clear the cache of all my Internet explorer
Cleared %LocalAppData%\Microsoft\Team Foundation\*.*\Cache
Run VS2015 in admin
Disable my antivirus
Delete registry key HKEY_CURRENT_USER\Software\Microsoft\VSCommon\*.*\ClientServices\TokenStorage
Check that I've no proxy declared in: C:\Windows\Microsoft.NET\Framework\v*.*\Config\machine.config
I did a windows update.
I ran the command devenv.exe /resetuserdata
Any clue what is happening and how to solve it?
VS 2013 can connect to TFS 2015, but VS 2015 can't. So the issue is on client side. Try on another client machine to connect TFS 2015 with VS 2015 to check the result.
Clean the client cache: C:\Users\username\AppData\Local\Microsoft\Team Foundation\5.0\Cache and C:\Users\username\AppData\Local\Microsoft\Team Foundation\6.0\Cache. Make sure both 5.0 and 6.0 folder are cleaned.
Clean server cache on AT machine: C:\Program Files\Microsoft Team Foundation Server 12.0\Application Tier\Web Services_tfs_data, and C:\TfsData\ApplicationTier_fileCache
Remove all credentials in Control Panel\All Control Panel Items\Credential Manager.
Remove TFS server in Team Explorer: go to Manage Connections--Connect to Team Project--Servers, select TFS 2015, remove it and add it.
Connect TFS 2015 with it's IP address, not server name.
This answer will not please to anybody coming here for an answer, but I had to format my computer and do a whole clean install on it.
A little trick might help.
Change port 8080 to another port. I've changed to port 5000
I hope to be useful.

TFS 2013 Release Management Client not communicating with Server

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.

TFS 2010 TF31002: Unable to connect to this Team Foundation Server

i have installed TFS 2010 on WS 2008 R2 more than two years and every things worked fins till i have installed an app on the server which i think it change some seting on IIS/server. and after that i can not access tfs web services even on the TFS server localy!!.
what is the problem.
after that for resolving all security issues I changed TFS applicaion pool's identification to network administrator. tfs account is NT AUTHORITY\NETWORK SERVICE. i can create team project collection from the tfs administration console. i checked network traffic with fiddler for accessing http:///tfs and response was:
HTTP/1.1 404 Not Found
Server: Microsoft-IIS/7.5
Persistent-Auth: true
X-Powered-By: ASP.NET
Date: Tue, 16 Dec 2014 11:49:24 GMT
Content-Length: 0
If you have broken the server by installing something then I would recommend building a new dedicated TFS server.
Option 1) Create a new clean server for TFS. Install SQL and restore all of the databases from your old server. Then install TFS 2013.
Option 2) if you do not have room for a dedicated TFS server you should create a temporary instance to get working and then push all of your data to VSO (http://tfs.visualstudio.com)
If you run TFS locally you should be aware that TFS owned both the server and the database server that it is installed on. It is an application that includes those components.

while configuring TFS 2010 am getting this error

I am using SQL Server 2008R2 Express edition and intalled the analysis services n database"Adventure works" too. while configuring TFS 2010 am getting this error. how to solve it?
Error [ Reporting ] TF255344: Either a connection could not be made to the server that is running SQL Server Analysis Services, or the service is not running. For more information, review the following exception message: Error encountered when creating connection to Analysis Services. Contact your Team Foundation Server administrator..
Error [ Reporting ] TF255353: You cannot perform the initial setup and configuration because you do not have sufficient permissions on the server that is running SQL Server Reporting Services. Verify that your role membership on the report server allows you to manage content and system settings.
Error [ Reporting ] TF255151: Service is not installed: SQL Server Analysis Services
Try installing the TFS 2010 Power Tools from here: TFS 2010 power tools, then click Start, point to All Programs, point to Microsoft Team Foundation Server 2010 Power Tools, point to Microsoft Visual Studio Best Practices Analyzer, and then click TfsBpa.exe. It does a great job of diagnosing these kind of issues.

Resources