2017-07-10 76 views
0

我在TFS2015.4上遇到特定團隊項目集合的問題。這個集合在我以前還想升級TFS時也會引發問題。我能夠在TFS2013.3中分離它,然後進行升級。現在我想升級到TFS2017,我不知道如何解決這個集合的問題。TFS 2015.4無法啓動或分離集合

TF400868: Job definition not found for JobId d891ac97-ddf1-42df-8242-3cd4bd607790 

這是當前的狀態:

  • 不會脫離
  • 不會啓動
  • 狀態 - > ApplyPatch - >將不執行
  • 保持脫機狀態
  • 裏面的一個項目,並保持'刪除'狀態

如果我嘗試啓動,我得到這個錯誤:

TF400783: The host 'MyDAS' cannot be started. The host is in the process of being serviced. The servicing may have failed and needs to be restarted and completed before the host can be started. 

我做了一個預生產升級到TFS2017並有與使我未能完成升級這個集合的狀態驗證錯誤。

General tab Detaching result Status tab ApplyPatch Rerun Team Projects tab

詳細的日誌ApplyPatch重辦只有一個故障點:

[12:29:58.457] +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 
[12:29:58.457] Executing step: Populate commit changes 
[12:29:58.457] Executing step: 'Populate commit changes' Git.M83PopulateCommitChanges (1017 of 1201) 
[12:29:58.477] [Error] TF400868: Job definition not found for JobId d891ac97-ddf1-42df-8242-3cd4bd607790. 
[12:29:58.480] Microsoft.TeamFoundation.Framework.Server.JobDefinitionNotFoundException: TF400868: Job definition not found for JobId d891ac97-ddf1-42df-8242-3cd4bd607790. 
[12:29:58.480]  at Microsoft.TeamFoundation.Framework.Server.TeamFoundationJobService.ResolveJobPriorityClasses(IVssRequestContext requestContext, IEnumerable`1 jobReferences, ITFLogger logger) 
[12:29:58.480]  at Microsoft.TeamFoundation.Framework.Server.TeamFoundationJobService.QueueJobsRaw(IVssRequestContext requestContext, IEnumerable`1 jobReferences, JobPriorityLevel priorityLevel, Int32 maxDelaySeconds, ITFLogger logger, Boolean queueAsDormant) 
[12:29:58.480]  at Microsoft.TeamFoundation.Server.Deploy.TFCollection.GitStepPerformer.M83PopulateCommitChanges(IVssRequestContext requestContext, ServicingContext servicingContext) 
[12:29:58.480]  at Microsoft.TeamFoundation.Framework.Server.TeamFoundationStepPerformerBase.PerformHostStep(String servicingOperation, ServicingOperationTarget target, IServicingStep servicingStep, String stepData, ServicingContext servicingContext) 
[12:29:58.480]  at Microsoft.TeamFoundation.Framework.Server.TeamFoundationStepPerformerBase.PerformStep(String servicingOperation, ServicingOperationTarget target, String stepType, String stepData, ServicingContext servicingContext) 
[12:29:58.480]  at Microsoft.TeamFoundation.Framework.Server.ServicingStepDriver.PerformServicingStep(ServicingStep step, ServicingContext servicingContext, ServicingStepGroup group, ServicingOperation servicingOperation, Int32 stepNumber, Int32 totalSteps) 
[12:29:58.480] Step failed: Populate commit changes. Execution time: 23 milliseconds. 
[12:29:58.480] [StepDuration] 0.0236576 
[12:29:58.480] [GroupDuration] 0.2517195 
[12:29:58.480] [OperationDuration] 0.2517302 
[12:29:58.587] Clearing dictionary, removing all items. 

====================================================================================================== 
Step execution times in descending order 
====================================================================================================== 
Updates all rows in tbl_GitCommit and sets the Status to ... (GitToDev14M83Collection, ToDev14M83Collection) - 227 milliseconds 
Populate commit changes (GitToDev14M83Collection, ToDev14M83Collection)          - 23 milliseconds 
Write service level to stamp (StartInstallUpdates, StartInstallUpdates)          - 20 milliseconds 
Configure framework servicing tokens (VsspToDev14M71Collection, VsspToDev14M71Collection)     - 20 milliseconds 
Setup integration environment (TestManagementToDev12M65FinalConfiguration, ToDev12M65FinalConfiguration)  - 3 milliseconds 
Setup Git environment (GitToDev14M74Collection, ToDev14M74Collection)          - 1 millisecond 
Setup Git environment (GitToDev14M83Collection, ToDev14M83Collection)          - 1 millisecond 
Set the collection partition id tokens in servicing context (GitToDev14M83Collection, ToDev14M83Collection) - 1 millisecond 

====================================================================================================== 
Execution times by group in descending order 
====================================================================================================== 
GitToDev14M83Collection (ToDev14M83Collection)                - 250 milliseconds 
StartInstallUpdates (StartInstallUpdates)                 - 20 milliseconds 
VsspToDev14M71Collection (VsspToDev14M71Collection)               - 20 milliseconds 
TestManagementToDev12M65FinalConfiguration (ToDev12M65FinalConfiguration)         - 3 milliseconds 
GitToDev14M74Collection (ToDev14M74Collection)                - 1 millisecond 

我琢磨的事實,這是需要一個胭脂工作手動從數據庫中刪除,但我很不對。任何指針都會很好地+1。

+0

您是否在事件視圖中看到任何相關的日誌錯誤信息? –

+0

這種特殊情況沒有得到任何生成的事件查看器記錄 – DoomerDGR8

回答

0

最終,有沒有辦法恢復的集合。所以我使用admin命令來永久刪除集合。在我的情況下,一個人回到我身邊,詢問收集的地方,因此解決了我的問題。我正在運行最新的TFS 2017.2,其餘的開發人員都很高興。

1

的主要原因是TFS無法升級團隊項目集合通常是他們的數據已經或者損壞不全,或卡模式版本之間

您需要聯繫客戶支持,以獲取有關解決這些數據問題的幫助,並讓您的數據回到可行狀態。

因爲裏面只有一個項目。如果你不關心源代碼管理歷史並且擁有項目的備份。粗糙(不推薦)的方式應該是刪除特殊項目集合,從SQL Server中刪除數據庫並創建一個新集合,然後恢復項目。

也看看這個類似的問題,用相同的錯誤你:Starting a team project collection after detaching and attaching again