Quantcast
Channel: Team Foundation Server - General forum
Viewing all articles
Browse latest Browse all 6687

Issues with TFS-Warehouse rebuild on 2013.4 (after upgrade from RTM)

$
0
0

Hi!

we have just updated our TFS server and all its buildservers, testcontrollers and agents from 2013 RTM directly to version 2013 Update 4. Everything was fine except our reporting is not working any longer. We found many posts regarding 2013.2 and its workaround of just deleting the warehouse databases and rebuilding them from scratch by clicking the "Rebuild"-button in TFSMgmt. Apparently that did not help. The exact Exception message from the TfsJobAgent log file is as follows:

TfsJobAgent.exe Error: 0 : [Error, PID 5620, TID 5164, 2015/02/23 09:17:03.573, 171141 ms, General] TF53010: The following error has occurred in a Team Foundation component or extension:
Date (UTC): 23.02.2015 09:17:03
Machine: TFS2013
Application Domain: TfsJobAgent.exe
Assembly: Microsoft.TeamFoundation.Framework.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v4.0.30319
Service Host:
Process Details:
  Process Name: TFSJobAgent
  Process Id: 5620
  Thread Id: 5164
  Account name: <*DOMAIN*NAME*CENSORED*>\TFSSERVICE

Detailed Message: TF30065: An unhandled exception occurred.
Exception Message: Operation is not valid due to the current state of the object. (type InvalidOperationException)
Exception Stack Trace:    at Microsoft.TeamFoundation.Framework.Server.TeamFoundationRequestContext.ValidateRequestContext(Boolean throwOnError)
   at Microsoft.TeamFoundation.Framework.Server.TeamFoundationRequestContext.To(TeamFoundationServiceHost targetHost)
   at Microsoft.TeamFoundation.Framework.Server.TeamFoundationRequestContext.To(TeamFoundationHostType hostType)
   at Microsoft.TeamFoundation.Warehouse.LockResources..ctor(TeamFoundationRequestContext requestContext)
   at Microsoft.TeamFoundation.Warehouse.WarehouseExecutionContext..ctor(TeamFoundationRequestContext requestContext)
   at Microsoft.TeamFoundation.Warehouse.WarehouseSyncJobExtension`1.CheckSchemaLockQueue(Object source)

We investigated the log file in more detail and found out that the log messages originating from the same thread (according to the "TID"-value above) are those:

TfsJobAgent.exe Information: 0 : [Info, PID 5620, TID 5164, 2015/02/23 09:17:03.526, 171094 ms, General] OurCollectionArchive: Microsoft.TeamFoundation.VersionControl.Adapter.VersionControlWarehouseAdapter: Checking schema lock queue

TfsJobAgent.exe Information: 0 : [Info, PID 5620, TID 5164, 2015/02/23 09:17:03.526, 171094 ms, General] TF30065: An unhandled exception occurred.

And that's it. There are no other log entries from the same thread previous to these.

Additional Information:

- We have two collections attached: "OurCollection" and "OurCollectionArchive"
- Our process template / workitem types have been customized (this was no problem with reporting in RTM)
- SQL-Server runs on a different host than the application-tier

Can anyone help please?


Viewing all articles
Browse latest Browse all 6687

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>