I have installed and configured Team Foundation Server 2015 Update 3 in one of our server a few weeks ago.
All was going well until the pc unexpectedly was shut down due to electrical problem. After turning on again we now get:
Error 500 internal server error.
Tried to access the web server and got the HTTP Error
403.14 - Forbidden.
TFS administration console seems fine. I'm not sure where to look next. Help would be greatly appreciated.
First, please check your Event View on your TFS server machine to see if there are more detail info or error message for trouble shooting.
For Error 500 internal server error. There's no much value for now.
For 403.14-Forbidden error, this may related to IIS server. Suggest you try to restart the TFS applicaton on IIS. And also clean all cache of TFS server, located at%LOCALAPPDATA%\Microsoft\Team Foundation\7.0\Cache
To narrow down the issue, you could also use Visual Studio to connect TFS server. If this works, suggest you to clear IE cache and try again.
Besides, since the PC unexpectedly shut down, please also check if the related TFS service started properly, if not manually start them.
In case someone else runs across this issue, we had the same problem and it turned out to be the system time on our TFS SQL Server had gotten out of sync. It was off by a number of hours. When I reset the time to be correct, I was able to connect to the TFS instance again without issue.
I got this error when I was migrating from TFS 2013 to AzureDevops Server 2020 using XAML Build. The error on Event Viewer from Application Tier Server was "Exception Message: The protocol binding ':443:.domain.com.br' is not valid for 'https'. This might be because the port number is out of range. (type UriFormatException)". I adjusted on IIS the https bindings to accept requests from IP Server.
enter image description here
Related
Trying to upgrade our on-premise server from 2015 to 2018. For some reason I get this message in the error log:
Team Foundation Server could not connect to the database. Verify that
the instance is specified correctly, that the server that is hosting
the database is operational, and that network problems are not
blocking communication with the server.
Why would this happen on step 909 only? Previous steps were already manipulating database so if access is the problem why would it error out on this specific step only?
Tried to re-rerun patch again but giving me the same error log.
I opened the Windows Event Viewer and got multiple errors on this event:
A timeout occurred while waiting for memory resources to execute the
query in resource pool 'internal'
For anyone having the same issue. Base on the Windows Event error I considered maybe the RAM was the problem. Checked and the server only had 2 GIG RAM.
Pretty weird since TFS alone was saying it was a database server issue. Anyway, upgrading the ram to 4 GIG solved the issue.
Hopefully this can help someone having the same issue.
I've just started to work on a MVC project. It's a web portal. I've set my sites on my local IIS 6.0
But when I want to start debugging, I get this error:
Unable to start debugging on the web server. The debugger cannot
connect to the remote computer. The debugger was unable to resolve the
specified computer name.
I don't understand that when I want to debug my project locally, what "Remote computer" it's talking about??!!
Please help me guys, this is my first task in this company and I have to overcome this error.
Check all the steps outlined here: https://msdn.microsoft.com/en-us/library/dwesw3ee.aspx?f=255&MSPPError=-2147217396
If you're using a hosts file, make sure you have an entry for the site in question. That was the problem for me, when I encountered this message.
I have similar problem.
My first solution delete url site from iis repositories and project properties write localhost and port number if is it. And debug began working without restart. I also think, may be if add new url in windows host file this can fix this trouble but may be need restat iis or visual studio.
IIS
Project properties
I have been working on restoring a build server (tfs 2012) from a backup and all manner of things got messed up (the tfsservice account password had been altered and I had to go to every service and app pool on the box and update it). Once sql was backup I was able to update the password via the TFS admin console app. Then I was able to re-register the build service and add a controller and a build agent. It starts briefly and shows green for a few seconds before stopping and a "details ..." button appears next to the Build Service. If I click the details button I see the following
"Please contact your administrator. There was an error contacting the server. Technical information (for administrator): HTTP code 500: System.ServiceModel.ServiceActivationException"
I have checked the http bindings in iis for the tfs site and there is only the one "*:8080"
I tried hardcoding it to the ip on the box and I still get the same error. If I go to one of the client machines and try and queue a build it shows the build server as being offline.
I have also checked for multiple host headers and the memory utilization which are the most common responses to this particular issue. Neither of them seem to be the cause or the solution.
Any ideas or suggestions are welcome I have run out of ideas to try here. Thanks in advance for any help you have to offer.
EDIT -- also found this in the log: Build machine MyMachine lost connectivity to message queue tfsmq://buildservicehost-25/.
I have 5.0.44.598 - Mahon version of Plastic SCM, the latest one by today(25 Aug,2014)
This is the first time I will be using Plastic SCM.
I keep getting "An error occured processing your request" error message when I click on branch explorer. Also whenever client software is opening first time.
I have win7 machine and also a win server 2012 on azure; have the same problem in both systems.
Does any one have the same problem, or any resolution?
I think it is a bug.
Could you enable the Plastic client log? (http://www.plasticscm.com/infocenter/technical-articles/kb-enabling-logging-for-plastic-scm-part-i.aspx), and send the stack trace to: support#codicesoftware.com
I´ve tested the same version in my local Win7 machine and the branch explorer is properly working.
Could you delete the file: "C:\Users\xxx\AppData\Local\plastic4\guivisualstate.xml" and restart the Plastic client.
If you create a new workspace, does the issue persist?
Do you have enabled any external extension (issue tracker...)?
UPDATE: Reviewed the logs and sent a solution to #freewill. If a similar issue happens again please contact to: support#codicesoftware.com
Regards.
I have installed TFS 2012 Express on my computer but I can't get TFS web access portal to work. If I try to view a page with work items I get error:
TF400893: Team Foundation Server services are not available.
This is most likely caused by a network error.
Please check your connection and try again.
It's weird because other parts of the TFS web portal works (e.g. source) so I don't think it's network error. If I connect to the TFS server from Visual Studio everything is working, so I suppose TFS service is running.
I tried to reinstall TFS, but it didn't help :-(
Any ideas what can be wrong?
Try an other browser. I have used Opera and got the error. Using IE should work.
Try changing the account from Applicaiton Tier on TFS Administration Console to your current domain and user info. The default value is NT AUTHORITY.
You should check for any firewalls or other IPS devices between the browser and the application tier for SQL injection attack rules. WIQL being sent from the browser in the AJAX request looks far too much like regular SQL so gets canned by such rules.
As we were experiencing this issue where I work, I decided to take a network packet capture of the browser traffic on a machine experiencing the problem. This yielded a whole bunch of TCP retransmits on the packet containing the plain-text WIQL. Upon presenting this evidence to the company's network team, they located the offending IPS rule which was triggering on these packets, disabled it for packets targeting the TFS Application tier and the problem was solved.
I just got the same error while adding a comment to a work item which included a SQL Statement to drop some tables.
After changing my language to not include explicit T-SQL "DROP TABLE" syntax, I was able to add the comment. My guess is something trying to prevent SQL injection.