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.
Related
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
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 an application named “LeafTest” which has Server Edition and Client Edition. The server Service is “Mss.exe” which is running under account “stepup” account which I checked from “services.msc” and system configuration is 2003 server 32bit standard edition with SP2. But yesterday means November 20 it suddenly stopped , I don’t know what is the reason behind it.
When I checked my application logs I can see these errors just before it reported service stopped
The entries in event log are
Following error also i can see somewhere
Event ID ( 8500 ) in Source ( LeafTest)
cannot be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote computer.
When I go0gled somewhere its mentioning my application may not be installed properly or registered or I need to work with registry. Can any body tell me what will be the reason behind the service stpped by reading logs which i have posted
A service may halt if there is an unhandled exception. Check that you are handling all exceptions. Also, if the service uses any COM objects I have, in the past, had exceptions that could not be caught in my .NET 2.0 applications.
We have a situation where our builds have stopped executing in a stable manner.
At a rate of about one every three we receive either TF215096 or TF215097 errors & the Build fails.
If we then restart the Build controller, it works again - until next time.
The errors we get are:
TF215096: An error occurred while connecting to controller vstfs:///Build/Controller/1: There was no endpoint listening at ht*p://XXXX that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
TF215096: An error occurred while connecting to controller XXX - Controller: Could not connect to ht*p://XXX. TCP error code 10061: No connection could be made because the target machine actively refused it 192.168.XXX.XXX:XXX.
TF215097: An error occurred while initializing a build for build definition \XXX: Team Foundation services are not available from server ht*p://XXX. Technical information (for administrator): The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
TF215097: An error occurred while initializing a build for build definition \YYY: An error occurred while receiving the HTTP response to ht*p://XXX. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.
Server logs provide with little info, at least we 've found nothing that helps us resolve the situation. Various searches in the Net were also not productive.
Does anybody had these/similar issues? Any ideas on how/where to look for a resolution?
Thank you very much in advance for any input!
Yeah it does sound like you have some connectivity issues. You can try enabling SOAP tracing on both the build machine and the server (if possible) to see if there is any error. If it still does not give you any new information, contact Microsoft by filing a Connect Bug to get help.
I am not sure if it will help you but I have ran into similar issues with build agents and ended up just deleting and re-creating the agent. You may try deleting your controller/agent and adding it back in. A brute-force solution but a good starting point. If that doesn't resolve the issue at least you can eliminate the controller/agent as the issue and take a look at network/server related issues.
Today is a happy day, since we managed to get to the bottom of the matter. Sorry #Duat that I'm taking away the 'answer' checkmark - but it turned out that the problem was quite different from what you (and anybody else) has predicted.
In my last update I was about to forward the matter to MS, when we realized that our Firewall was misbehaving in the name resolution. So we assumed this was the culprit & awaited for this to resolve. After this was resolved, we STILL had the same issues and we went again re-examining the situation.
We isolated the problem within our Build Process, more specific with a custom code activity included in our build solution.
I had implemented a code activity that would kick in at the final steps of every build. This activity was about gathering BuildDetails about the running build & add them as a new line in a 'BuildLog.xls'. Implementation made use of Microsoft.Office.Interop.Excel.This excel sheet resides in another server (NOT on the Servers where the controller/agents reside).
During development of this activity I was faced with issues like this, but after I was done no instances of EXCEL were left hanging. So I thought this was done & dealt with.
With try & error, we observed that when this activity wouldn't ran, no problems would occur.
With this activity running, the very first build after a build-controller reset would succeed, any next build had a certain chance to fail. Once any build failed, no other would succeed until another build-controller reset.
I have only a general understanding of what the problem was (Excel-call is DCOM, TFS services are WCF : How on earth would they interfere?! Why would this sometimes succeed and sometimes fail?! ).
The provided diagnostics were no help either, in fact they mislead us into a loop that continued for months.
If I ever find the time, I 'd like to cleanly reproduce the error & make a Server Fault question out of it...
After removal of this activity it works! I now searched in SO & found this, where J.Saunders comments: "In general, you should never use Office Interop from a server environment". It's ironic that once you get to the bottom of any difficult issue, the whole universe seems to have known about it except you...
I’m trying to add a team project collection to a TFS2010 instance. The instance already has project collections set-up and in use, but when I try to add another I get warnings from the Data Tier Configuration. The warnings are as follows:
TF255153: Service is not set to start automatically: SQL Server Database Services:
TF255437: An error occurred while querying the Windows Management Instrumentation (WMI) interface on the following computer: MYTFSSERVER. The following error message was received: .
TF255437: An error occurred while querying the Windows Management Instrumentation (WMI) interface on the following computer: MYTFSSERVER. The following error message was received: .
(TF255437 is reported twice)
I’ve had a good look around, and found a couple of articles that implied TF255437 is caused by WMI compatibility not being enabled in IIS (TFS2010 is running on IIS7.5). However, this is enabled as far as I can tell.
Has anyone come across either of these errors before? The admin console seems happy for me to create the TPC regardless, but without understanding the errors fully, I’m reluctant to do so.
This was all caused by the "SQL Server Agent" service not being started on the server.