After upgrading to Release Management 2013.4, we tried creating a release in the client that's also on 2013.4. We've repaired the server (looks like it needed to install .NET 4.5.1) but the error still is the same:
An unhandled exception has occurred in the application: The remote server returned an error: (500) Internal Server Error.\n at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at Microsoft.TeamFoundation.Release.Data.WebRequest.PlatformHttpClient.EndGetResponse...
When we look at the logs, we get a ton of errors with system.servicemodel (webhost failed to process a request) and release management (data at the root level is invalid. line 2, position 1).
Any ideas what this is? We tried to enable detailed logging, but can't because we can't create a release.
Turns out that it's an issue with installing the RM server with HTTPS (default) when it needs to be HTTP. So when we uninstalled and reinstalled RM Server 2013.4 and configured it to HTTP, everything worked!
https://social.msdn.microsoft.com/Forums/vstudio/en-US/d0a9d3f1-05d1-4e4c-b44a-93e9bb4b9044/after-upgrading-to-release-management-update-2-i-cannot-deploy-anything?forum=tfsbuild
Related
I am facing below issue while switch VS2019 to VS2022. I am not able to run my API project its throwing below error. I Search on google and look many articals but not got success. Please suggest to resolve this problem. I checked and found that .netCore upper version not support to old version code.
HTTP Error 500.37 - ANCM Failed to Start Within Startup Time Limit
Common solutions to this issue:
ANCM failed to start after -1 milliseconds
Troubleshooting steps:
Check the system event log for error messages
Enable logging the application process' stdout messages
Attach a debugger to the application process and inspect
When I set up my project in TeamCity to connect to a version control system root on tfsonline. However, I keep getting a problem related to ServicePointManager claiming some proxy doesn't support HTTPS.
How can I fix this problem? Is there's some additional configuration needed to get it to work?
The error I get:
Server='https://XXXX.visualstudio.com/DefaultCollection/XXXX'
Username='fredrik#XXXXX'
ERROR - The ServicePointManager does not support proxies with the https scheme.
System.Exception: The ServicePointManager does not support proxies with the https scheme.
It was solved by installing Visual Studio 2012, updates on the server, and all available updates in Windows Update.
We have Jenkins 1.509.2 + Sonar 3.6.1. And receive the below error, We didn't have the same error with Sonar 3.4.1 from which we upgraded. Could you advise how can we fix the issue?
Exception in thread "main" org.sonar.runner.RunnerException: org.sonar.api.utils.SonarException: Unable to request: /batch_bootstrap/properties
at org.sonar.runner.Runner.delegateExecution(Runner.java:288)
at org.sonar.runner.Runner.execute(Runner.java:151)
at org.sonar.runner.Main.execute(Main.java:84)
at org.sonar.runner.Main.main(Main.java:56)
Caused by: org.sonar.api.utils.SonarException: Unable to request: /batch_bootstrap/properties
at org.sonar.batch.bootstrap.ServerClient.request(ServerClient.java:82)
at org.sonar.batch.bootstrap.ServerClient.request(ServerClient.java:72)
at org.sonar.batch.bootstrap.BatchSettings.downloadSettings(BatchSettings.java:96)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:150)
at java.net.SocketInputStream.read(SocketInputStream.java:121)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:275)
at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
The error is not received every time - more like 90%. After I have upgraded all the Installed plugins, the error disappeared, on the next day - it appeared again.
It appears for ALL the projects, small and big. The Jenkins server is far (network wise) - from the Sonar server on most of the projects, but we also have projects that are in the same location with Sonar - and still receive this issue. Is there a workaround at least to increase the timeout?
We are seeing a similar error after upgrading from 3.4.1 to 3.6. The problem is not as severe as your (maybe 30% rather than 90%). Like your experience it is not limited to one project (errors in 2 out of every 7 builds). Restarting Sonar seems to help but does not always make it go away. Also, call me crazy but adding a -X flag to the maven build command has so far been the most reliable workaround. FYI, our builds are running on the same machine as the Sonar server (and the MySQL server).
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.
Sometime i will encounter this error after multiple access of my web application
I am using Sun Application Server Platform Edition 8.2
What is the reason for encountering this error and how to resolve it.
File system permissions issue perhaps. Need more information for a better answer.