我们最近从2013年升级到2017年TFS，并且所有报告都已经过移除。但是，我在现有集合下创建了一个新项目，但没有构建报告。
我注意到在TFS_Warehouse数据库中，表DimTeamProject有一个名为ProjectPath的列为空。
我还注意到报告服务区域没有文件夹，基于上述内容我并不感到惊讶。我手动创建了这个并在那里添加了一些模板报告。当我运行它们时它们是空的但是如果我填充数据库中的ProjectPath字段是空的那么一切都很好。问题是，每晚都会被擦掉（必须是服务运行）。
我已经跟踪了从一个过程（prc_Dimension_DimTeamProject_AddUpdate）填充的字段，但这些值来自位于某处的XML文档（我不知道在哪里）。
我查看了服务器上的管理区域，报告路径似乎很好/ TfsReports / {my} Collection
我无法在前端看到任何指示报告已开启或关闭的内容。
我在TFS管理控制台中重建了2个数据库。 https://www.visualstudio.com/en-us/docs/report/admin/rebuild-data-warehouse-and-cube
然后我通过调用以下Web服务方法手动处理了2个数据库。
http://localhost:8080/tfs/TeamFoundation/Administration/v3.0/WarehouseControlService.asmx ProcessWarehouse ProcessAnalysisDatabase。
但是当涉及到手动处理时，我遇到了以下错误。
<Job Name="Test Management Warehouse Sync" JobProcessingStatus="Idle">
<LastRun QueueTimeUtc="2017-02-09T09:12:10.663Z" ExecutionStartTimeUtc="2017-02-09T09:12:10.707Z" EndTimeUtc="2017-02-09T09:12:11.927Z" Result="Failed">
<ResultMessage>
[Test Management Warehouse Sync]: ---> Microsoft.TeamFoundation.Warehouse.WarehouseException: TF221122: An error occurred running job Test Management Warehouse Sync for team project collection or Team Foundation server MYCollection. ---> System.Data.SqlClient.SqlException: The datediff function resulted in an overflow. The number of dateparts separating two date/time instances is too large. Try to use datediff with a less precise datepart. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryHasMoreRows(Boolean& moreRows) at System.Data.SqlClient.SqlDataReader.TryReadInternal(Boolean setTimeout, Boolean& more) at System.Data.SqlClient.SqlDataReader.TryNextResult(Boolean& more) at System.Data.SqlClient.SqlDataReader.NextResult() at Microsoft.TeamFoundation.TestManagement.Warehouse.WarehouseResultDatabase.ProcessResultDataSet(SqlDataReader reader, ProcessMappingDataCallback addedCallback, Mapping mapping, Boolean resolveIdentitesInBatch) at Microsoft.TeamFoundation.TestManagement.Warehouse.WarehouseResultDatabase.QueryTestPointData(SqlBinary watermark, SqlBinary endWatermark, Int32 limit, IEnumerable`1 areaIterationMap, ProcessRowCallback deletedCallback, ProcessMappingDataCallback addedCallback, ResolveIdentities resolveIdentitiesCallBack) at Microsoft.TeamFoundation.TestManagement.Warehouse.TeamTestWarehouseAdapter.QueryForTestPoints(WarehouseResultDatabase wrd, SqlBinary waterMark, Int32 limit) at Microsoft.TeamFoundation.TestManagement.Warehouse.TeamTestWarehouseAdapter.<>c__DisplayClass116_0.<ProcessIntegratedResults>b__0() at Microsoft.TeamFoundation.TestManagement.Warehouse.TeamTestWarehouseAdapter.ProcessDataWithDiagnosticInfoLogging[T](Func`1 processBatch, Int32 limit, T& highWaterMark) at Microsoft.TeamFoundation.TestManagement.Warehouse.TeamTestWarehouseAdapter.MakeDataChanges() at Microsoft.TeamFoundation.Warehouse.WarehouseSyncJobExtension`1.MakeDataChanges(IVssRequestContext requestContext, TeamFoundationJobDefinition jobDefinition, String& resultMessage) at Microsoft.TeamFoundation.Warehouse.WarehouseSyncJobExtension`1.RunInternal(IVssRequestContext requestContext, TeamFoundationJobDefinition jobDefinition, DateTime queueTime, String& resultMessage) at Microsoft.TeamFoundation.Warehouse.WarehouseJobExtension.Run(IVssRequestContext requestContext, TeamFoundationJobDefinition jobDefinition, DateTime queueTime, String& resultMessage) --- End of inner exception stack trace ---
</ResultMessage>
</LastRun>
<NextRun QueueTimeUtc="2017-02-09T09:31:55.777Z" JobState="QueuedScheduled"/>
</Job>
任何人都可以帮忙吗？
答案 0 :(得分：0)
升级到TFS 2017 RTM之后，我获得了相同的体验，事实证明，您在此处获得的关于“datediff函数导致溢出”的异常是该特定版本中的问题。我已经写过关于这种行为，以及在到达Microsoft之前需要准备哪些信息才能获得此处的帮助： https://dankovalkov.wordpress.com/2017/02/03/tfs-2017-resolving-tf221122-tf246018-tf400307-and-tf400797-issues/