TF53018: The application tier SERVER is attempting to connect to a data tier with an incompatible version

Question

There is such error in event log on try to connect to source control:

------ BEGIN OF ERROR

TF53010: An unexpected condition has occurred in a Team Foundation component. The information contained here should be made available to your site administrative staff.
Technical Information (for the administrative staff):
Date (UTC): 10/23/2006 5:01:26 AM
Machine: SOLARIS
Application Domain: /LM/W3SVC/3/Root/VersionControl-6-128060532856161741
Assembly: Microsoft.TeamFoundation.VersionControl.Server, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
  Process Name: w3wp
  Process Id: 620
  Thread Id: 3180
  Account name: DOMAIN\tfsservice

Detailed Message: TF53018: The application tier SERVER is attempting to connect to a data tier with an incompatible version.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
------ END OF ERROR

It was some sequence of installing TFS1 SP1 Beta, repair TFS V1, installing SP1, installing again, uinstalling SP1, repair TFS V1, installing SP1 again. Such admistrative activity may look very, very odd but .... happens...

I need to get it to work. Can you help me?

It is single-server installation of TFS.

 

Answer 1

OK, I've resolved the problem myself.

I don't recommend these scenario to anyone but I've detached TFS databases, uinstalled TFS, installed again, installed TFS SP1 Beta, detached new databases, attached all databases, install TFS SP1 Beta again

 btw - this scenario lasts very, very long

Answer 2

I found a partial workaround to this problem, which seems to be common, as I have seen it in several places. The problem is the consequence of a mismatch between the Reporsitory version reported in the tbl_Repository table of TfsVersionControl database and the version that the Microsoft.TeamFoundation.VersionControl.Server.dll assembly looks for. In my case, after installing TFS Service Pack 1 (RTM), I got this version numbers:

TfsVersionControl database -> tbl_Repository table -> Row 1 -> SchemaVersion: 8.50727.327

Microsoft.TeamFoundation.VersionControl.Server.dll -> Global class -> Initialize() method: 8.50727.138

So, the thing here is that, for some reason, the Microsoft.TeamFoundation.VersionControl.Server.dll was never replaced with the new SP1 version, even when the corresponding table was. I don't know the reason why this happened. Maybe the error I got when first trying to uninstall SP1 Beta left this 2 guys in a inconsistent state.

Solution: Just change the table version from 8.50727.327 to 8.50727.138 and that's it! You should be able to connect to version control again.

Warning: I don't really know what are the collateral effects of my proposed solution.

I think that maybe running again the SP1 installation (uninstall and then reinstall) may copy the correct assembly. But, for now, I don't have time for that, as I have spent a whole day trying to find the cause of this problem. Maybe some Microsoft guy can give us some explanation to this.

Ohh, by the way, thanks a lot to Lutz Roeder's Reflector utility, as using that program was the easiest way to find the version that the assembly was looking for.

If someone finds a way to get the correct assembly installed, please let me know.

Answer 3

Running SP1 installation again (uinstall and then reinstall) don't help.


1. I had SP1 Beta installed, TfsVersionControl.tbl_Repository.SchemaVersion was 8.50727.327 and all was working.

2. After installing SP1 it was TF53018 error.

3. After uinstalling and reinstalling SP1 it still was TF53018 error.

4. After applying your workaround it was no error!!! (congratulations to you for find such workaround!) but it was new EventViewer error: "TF53010: An unexpected condition [...] Microsoft.TeamFoundation.WorkItemTracking.Adapter: Exception during Run - System.Data.SqlClient.SqlException: Procedure or function GetWarehouseData has too many arguments specified [...]"

5. I've decided to uinstall SP1 and install SP1 Beta again.

6. TF53018 was back! So I've used your workaround and I've still TFSWarehouse error TF53010 in EventViewer (so SP1 Beta and SP1 works the same in this detail).

I think the problem is that Microsoft.TeamFoundation.VersionControl.Server.dll and other dll's are not updated to correct versions.

I've used "/l* TFSSP1.LOG" option for SP1 installation (maybe I should use "/l*v" ?).

In the TFSSP1.LOG it was huge number of errors:

DEBUG: Error 2745: Transform T2_102ToU186_102 invalid for package D:\WINDOWS\Installer\d4dbbc.msi. Expected language 1036, found language 1033.

1: 2745 2: T2_102ToU186_102 3: D:\WINDOWS\Installer\d4dbbc.msi 4: 1036 5: 1033

(and many similar with different transform name and different expected language)

There are also severeal errors similar to this:

DEBUG: Error 2746: Transform T2_36ToU186_36 invalid for package D:\WINDOWS\Installer\d4dbbc.msi. Expected product {44E1B36C-E46E-4BB3-A43B-5A7010BC1539}, found product {50E5D44C-550B-4B61-AC95-0B05F45A7CB2}.

1: 2746 2: T2_36ToU186_36 3: D:\WINDOWS\Installer\d4dbbc.msi 4: {44E1B36C-E46E-4BB3-A43B-5A7010BC1539} 5: {50E5D44C-550B-4B61-AC95-0B05F45A7CB2}

Answer 4

Update to my previous post:
------------------------------
Finally we discovered that installation after your workaround is not good because some operations fail (Branch, Compare, Lock, Merge, TfsWarehouse).
The reason IMHO is that real SchemaVersion is ".327" but TFS binaries try to use it as it would be ".138" (because these binaries are indeed older - from TFS V1 not from TFS SP1).

Workaround of my collegue is to stop TFSServerScheduler and copy all newer dll's and exe's from another, "fresh" instalation of TFS V1 + TFS SP1 Beta.

(may be the same would work with fresh instalation of TFS V1 + TFS SP1, but for now I'm tired fighting with TFS).

Answer 5

And another off topic suggestion: if you execute many [un]installations of TFS I recommend before [un]installation one of these steps:
1. Delete %ProgramFiles%\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\VersionControl\Data\
--OR--
2. This directory can be very big (in my company about 500000 files, 600MB occuping 5GB of HDD - many small files) so faster would be move this directory outside TFS (for example to root or temp folder)
--OR--
3. Change location of TFS VC Cache permanently with this:
http://msdn2.microsoft.com/en-us/library/ms400793(VS.80).aspx
(How to: Change Cache Settings for an Application-Tier Server)

The reason is that during [un]installation setup scans whole TFS directory and it takes very long with this directory (I've discovered this with FileMon from Sysinternals).

Best regards

Answer 6

Yes Andrzej, you are right, my workaround is not really a solution to the problem. I also found later that several features of TFS are broken after that. But the main benefit I found of using that workaround is that I was finally able to get my source code from version control, as before that there was no way of getting my source back.

I'm also wishing to apply your workaround (copy all newer dlls and exes from another, "fresh" installation of TFS V1 + TFS SP1) but I don't really know which are the dlls that TFS SP1 adds or updates. Do you know which are those dlls? Can you please tell me how did you know which dlls should you copy?

Thanks,

Answer 7

This is caused by a known issue with the SP1 Beta installer corrupting the MSI database.  To fix the problem and snsure that the product can be properly patched in the future please follow these steps:

 

1)      Uninstall SP1

2)      Run the following from the command-line:

a.       Msiexec.exe  /package <path to RTM install media>\vs_setup.msi ADDLOCAL=ALL

3)      Re-install SP1 RTM

 

 

 

 

Answer 8

Happy New Year wishes to Julio and to Ed.
Thank you Ed for advice I will try it soon!

Firstly, Julio, I recommend Ed's solution. I haven't check it yet but I'm sure it is far more proffesional advice that mine.
But if you would still need the list of files here you are:

.\widbloc.exe
.\coveran\msdia80.dll
.\tf setup\authenticationfilter.dll
.\tf setup\microsoft.teamfoundation.build.server.agent.dll
.\tf setup\microsoft.teamfoundation.client.dll
.\tf setup\microsoft.teamfoundation.common.dll
.\tf setup\microsoft.teamfoundation.server.dll
.\tf setup\microsoft.teamfoundation.workitemtracking.client.dll
.\tf setup\tfsquiesce.exe
.\tfsserverscheduler\microsoft.teamfoundation.client.dll
.\tfsserverscheduler\microsoft.teamfoundation.common.dll
.\tfsserverscheduler\microsoft.teamfoundation.server.dll
.\tfsserverscheduler\microsoft.teamfoundation.workitemtracking.client.dll
.\tools\microsoft.teamfoundation.client.dll
.\tools\microsoft.teamfoundation.common.dll
.\tools\microsoft.teamfoundation.server.admin.dll
.\tools\microsoft.teamfoundation.server.dll
.\tools\microsoft.teamfoundation.versioncontrol.client.dll
.\tools\microsoft.teamfoundation.workitemtracking.client.dll
.\tools\microsoft.visualstudio.qualitytools.common.dll
.\tools\setupwarehouse.exe
.\web services\build\bin\microsoft.teamfoundation.workitemtracking.client.dll
.\web services\build\bin\microsoft.visualstudio.qualitytools.agentobject.dll
.\web services\services\bin\microsoft.teamfoundation.client.dll
.\web services\services\bin\microsoft.teamfoundation.common.dll
.\web services\services\bin\microsoft.teamfoundation.server.dll
.\web services\services\bin\microsoft.teamfoundation.workitemtracking.client.dll
.\web services\services\bin\plugins\microsoft.teamfoundation.workitemtracking.server.eventfilter.dll
.\web services\versioncontrol\bin\microsoft.teamfoundation.versioncontrol.server.dll
.\web services\versioncontrol\bin\microsoft.teamfoundation.workitemtracking.client.dll
.\web services\warehouse\bin\microsoft.teamfoundation.warehouse.dll
.\web services\warehouse\bin\microsoft.teamfoundation.workitemtracking.client.dll
.\web services\warehouse\bin\plugins\microsoft.teamfoundation.versioncontrol.adapter.dll
.\web services\warehouse\bin\plugins\microsoft.teamfoundation.workitemtracking.adapter.dll
.\web services\warehouse\bin\plugins\microsoft.teamfoundation.workitemtracking.server.dataaccesslayer.dll
.\web services\warehouse\bin\plugins\microsoft.teamfoundation.workitemtracking.server.dll
.\web services\warehouse\bin\plugins\microsoft.visualstudio.qualitytools.agentobject.dll
.\web services\warehouse\bin\plugins\microsoft.visualstudio.qualitytools.warehouseadapter.dll
.\web services\workitemtracking\bin\microsoft.teamfoundation.workitemtracking.server.dataaccesslayer.dll
.\web services\workitemtracking\bin\microsoft.teamfoundation.workitemtracking.server.dataservices.dll
.\web services\workitemtracking\bin\microsoft.teamfoundation.workitemtracking.server.dll

Answer 9

Thanks Ed. Seems like now the SP1 installed successfully, but now I can't enter the https://www.mydomain.com:myport/services/v1.0/serverstatus.asmx page. I keep getting a "Internet Explorer cannot display the webpage" error. How can I see some kind of trace or log of the webservice to find out which might be the problem? By the way, I'm using TFS over the internet using SSL.

Thanks,

Answer 10

Hi,

I have try the Ed's solution... but the command line :

Msiexec.exe  /package <path to RTM install media>\vs_setup.msi ADDLOCAL=ALL

Crash here ! It close the install windows suddently and when I check in the event viewer it tells :

Product: Microsoft Visual Studio 2005 Team Foundation Server - ENU -- Configuration failed.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

So, I have even not try to restart the SP1 install !!

Answer 11

I followed Ed's steps, and it resolved the issue for me. 

Jimmy

Answer 12

 

When I try to connect to my TFS server via Visual Studio Team Explorer 2008 , I got this error message :

       Team Foundation services are not available from server [my server name].

Technical information (for administrator):

 TF53018: The application tier [my server name] is attempting to connect to a data tier with an incompatible version  (9.20507.00)is incompatible with the application tier version 9.20904.00).

 

Answer 13

I had this problem. Fixed it by reapplying SP1 whilst logged in as administrator. I wasn't using Beta version though.