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.
Related
I am trying to deploy my project to IIS using TFS Winrm:IIS web app deployment task. I am new to this.
I am getting the following error'
"Deployment failed on machine xxx with following message : System.Management.Automation.Remoting.PSRemotingTransportException: Connecting to remote server xxx failed with the following error message : The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". "
I was able deploy the project to the same remote server using TFS Winrm: windows machine file copy task which is the prior step for web app deployment to IIS. Winrm service is running and when it type the "winrm quickconfig i am getting "winrm is already been configured".
What am i missing here ? please suggest. Thanks in advance.
The Winrm:IIS task is actually MSDeploy from Machine A to Machine B so for this to work you need to install MSDeploy on Machine B. You should then be ok to deploy from Machine A. Check this article out for more information and to see if you have all the pre-requisite. Also these articles have a bit more info.
https://learn.microsoft.com/en-us/azure/devops/pipelines/apps/cd/deploy-webdeploy-iis-winrm?view=azure-devops
https://marketplace.visualstudio.com/items?itemName=ms-vscs-rm.iiswebapp
The issue was resolved when i enable remote powershell remoting my remote machine using the command Enable-PSRemoting –force
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
i would like to upgrade my production TFS 2017 to TFS 2018.
according to the requirement, it need SQL Server 2016 SP1, because some reason, i decide use a new production server for it.
Before doing the production upgrade, i do the upgrade test in my testing enviroment, the step is
Install SQL Server 2016 SP1
Restore the TFS 2017 Database
Install TFS 2018 Update 1
Start the TFS Upgrade Wizard using my existing db
Confirm the 8080 port is allow to connect
After finish, i can access the TFS web on the testing environment server by using http://localhost:8080/tfs or http://SERVERNAME:8080/tfs (btw Chrome only can access using localhost)
When i connect http://SERVERNAME:8080/tfs on client pc, it doesn't work, it show me
ERR_CONNECTION_REFUSED
All my server have join domain and i try troubleshoot from tfs application to firewall, no any result on it.
Is there any step wrong or other problem on it?
UPDATE:
After i reinstall Windows OS, it's work.
Try below items to narrow down the issue:
Using IP instead of the SERVERNAME in the URL, then try it
again.
Clean local caches from the client machine (TFS caches, Browser
caches)
Restart the TFS wensite from IIS manager.
Restart IIS with command: iisreset /noforce
Try changing the port number for you TFS
Rebuild the client cache.
After you move, restore, rename, or fail over a data-tier or
application-tier server, you must refresh the cache for tracking work
items and users must refresh the version control cache on client
computers.
UPDATE1:
Just try below things:
Add the client machine name/IP to the hosts file. (The hosts file should be located under c:\windows\system32\drivers\etc\hosts)
Try to detach the collection then reattach it again
Try to reconfigure the TFS.
UPDATE2:
Based on geraldlim's comment below : Turn out that after reinstalling the OS and install IIS and TFS in a clear environment, it's working.
I have created a windows service which is successfully installed on my machine as well as some other local machines.
But when I try to install the same on client's server which is Windows Server 2012 R2 it is getting error stack as below:
The inner exception System.ComponentModel.Win32Exception was thrown with the following error message: The service did not respond to the start or control request in a timely fashion.
For this, I have tried some solution as below:
Adding ServicePipeTimeout in regedit so that it can increase the timeout.
Comparing Microsoft .Net Framework's version used in windows service and Windows Server 2012 R2.
Both of the solutions did not work for me. Can someone guide me through this issue?
I have a build/test server which is currently running Jenkins for my continuous integration and it also is acting as my test server where code will be deployed to once built (i hope to rectify this and seperate these at a later date when budget allows)
I have a .NET web solution (nothing complex just Umbraco essentially) that i have in SVN and Jenkins is now building correctly. I now want to deploy it onto the same server using MSDeploy. After the build completes the package is generated but the deploy fails with the error
ERROR_DESTINATION_NOT_REACHABLE: Web deployment task failed. (Could not connect to the remote computer ("xxxxx.xxxxxxx.xxx.xxxx"). On the remote computer, make sure that Web Deploy is installed and that the required process ("Web Management Service") is started
Here is my msbuild parameters that Jenkins uses
/P:Configuration=Release
/P:DeployOnBuild=True
/P:MSDeployPublishMethod=WMSVC
/P:DeployTarget=MSDeployPublish
/P:PublishProfile=GetSomePixels
/P:MsDeployServiceUrl=https://build.########
/P:AllowUntrustedCertificate=True
/P:CreatePackageOnPublish=True
/P:UserName=#######
/P:Password=########
I've checked the server and the Web Management Service is running and is starting up manually
I've also gone into IIS 8 manager (server 2012) and checked the "Allow Remote Connections" box under "Management Service". Restarted IIS and the WMSVC and still not working.
If i go to https://myserver.co.uk:8172/MsDeploy.axd in a browser it resolves (gives you the warning about an untrusted cert) and then displays a blank page.
Anyone got any ideas as to what i can do? I thought that it may be firewall related and even though it had added an exception to windows firewall for 8172 i have turned the entire firewall off to completely rulle that out and still no luck.
Have run this on the server to check its listening on the correct port
C:\Users\Administrator>netstat -a | findstr 8172
TCP 0.0.0.0:8172 GSP-BUILD:0 LISTENING
TCP [::]:8172 GSP-BUILD:0 LISTENING
Ok i've resolved this. It appears you have to activate the web management service first and then install web deploy and i'd done it the other way round. I uninstalled WebDeploy and re-installed it, restarted the server and its working
Agree with comment.
We had a similar issue. Initial installation even post Web Management Service activation appeared to be incomplete. In our case, even though the service said it was started we couldn't achieve the "green tick" when testing the connection from the Publish dialog when defining a profile.
Reinstalling WebDeploy 3.6 made it function properly.