更新 SQL Server 2008 Warhouse Cube 时出现问题

更新 SQL Server 2008 Warhouse Cube 时出现问题

我们有一个在 SQL Server 2008 上运行的 TFS 2008 作为基础(Windows Server 2003 R2 32 位版本)。

不久前,我发现仓库数据(报告和分析服务使用的数据)没有更新。因为我们几乎从来没有使用过这些报告,所以它自“2010 年 9 月”以来就坏了

如果我检查服务器日志,我会发现以下事件消息:

Date (UTC): 10.03.2011 11:28:06
Machine: XXXXXXXXXXXXXX
Application Domain: /LM/W3SVC/1048316701/Root/Warehouse-5-129441362809652769
Assembly: Microsoft.TeamFoundation.Warehouse, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
  Process Name: w3wp
  Process Id: 3116
  Thread Id: 3268
  Account name: ourdomain\generic

Detailed Message: The pending configuration changes were not successfully added to the cube because of the following error: 
System.SystemException: The trust relationship between the primary domain and the trusted domain failed.

   at System.Security.Principal.NTAccount.TranslateToSids(IdentityReferenceCollection sourceAccounts, Boolean& someFailed)
   at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean& someFailed)
   at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)
   at System.Security.Principal.NTAccount.Translate(Type targetType)
   at Microsoft.TeamFoundation.Warehouse.OlapCreator.AddAccountToRole(Role role, String accountName, Boolean needToUpdate)
   at Microsoft.TeamFoundation.Warehouse.OlapCreator.SetupAnalysisDatabase(Server server, String analysisDBName, String accessUser, String[] dataReaderAccounts)
   at Microsoft.TeamFoundation.Warehouse.OlapCreator.CreateOlap(WarehouseConfig whConf, String accessUser, String[] dataReaderAccounts, Boolean dropDB, Boolean processCube)
   at Microsoft.TeamFoundation.Warehouse.AdapterScheduler.EnsureCubeIsUpToDate()

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

有人知道该怎么办吗?重新启动服务和服务器没有帮助。

答案1

我目前正在迁移我们公司的 TFS,在经历这个地狱般的经历时,我在第一步中遇到了您的错误。

通过谷歌搜索,我找到了几个解决方案,但都没有用,唯一能解决问题的方法是从域中删除服务器并重新加入域。

希望你会觉得这有用。

相关内容