HI
Same problem here, except from the fact that my corrupt file is Area.789.dim.xml and its completely empty :-(
So what to put in there? I have two other similar files lying around in the OLAP\Data\TFSWarehouse.0.db named Area.786.dim.xml and Area.787.dim.xml with content. A quick windiff shows that these files are identical except from some timestamps and the string literals 786 vs. 787 scattered around in the appropriate files. So my plan is to 'fix' the 789 file based on the contents of one of the other files and see what happens. Please somebody stop me if i'm doing something monstruosly stupid that f***s up our installation (I'm doing it now so you probably want make it :-)
Brumlemann
Update 1:
Seems I got past that file but ran into another parse error (included below). I'll try the same stunt.
Update 2:
Well, not so easy. This is the end of file (line 46 as stated by the failing parser):
</ Annotations><Translations><Translation><Language>1033</Language><Caption>Work Item</Caption><Description/><DisplayFolder/></Translation></Translations><Attributes><Attribute><AttributeID>Work Item</AttributeID><AggregationUsage>Default</AggregationUsage><AttributeHierarchyEnabled>true</AttributeHierarchyEnabled><AttributeHierarchyVisible>false</AttributeHierarchyVisible><AttributeHierarchyOptimizedState>FullyOptimized</AttributeHierarchyOptimizedState></Attribute><Attribute><AttributeID>Previous State</AttributeID><AggregationUsage>Default</AggregationUsage><AttributeHierarchyEnabled>true</AttributeHierarchyEnabled><AttributeHierarchyVisible>true</AttributeHierarchyVisible><AttributeHierarchyOptimizedState>FullyOptimized</AttributeHierarchyOptimizedState></Attribute><Attribute><AttributeID>System_Id</AttributeID><AggregationUsage>Default</AggregationUsage><AttributeHierarchyEnabled>true</AttributeHierarchyEnabled><AttributeHierarchyVisible>true</AttributeHierarchyVisible><AttributeHierarchyOptimizedState>FullyOptimized</AttributeHierarchyOptimizedState></Attribute><Attribute><AttributeID>System_Title</AttributeID><AggregationUsage>Default</AggregationUsage><AttributeHierarchyEnabled>true</AttributeHierarchyEnabled><AttributeHierarchyVisible>true</AttributeHierarchyVisible><AttributeHierarchyOptimizedState>FullyOptimized</AttributeHierarchyOptimizedState></Attribute><Attribute><AttributeID>System_State</AttributeID><AggregationUsage>Default</AggregationUsage><AttributeHierarchyEnabled>true</AttributeHierarchyEnabled><AttributeHierarchyVisible>true</AttributeHierarchyVisible><AttributeHierarchyOptimizedState>FullyOptimized</AttributeHierarchyOptimizedState></Attribute><Attribute><AttributeID>System_Rev</AttributeID><AggregationUsage>Default</AggregationUsage><AttributeHierarchyEnabled>true</AttributeHierarchyEnabled><AttributeHierarchyVisible>true</AttributeHierarchyVisible><AttributeHierarchyOptimizedState>FullyOptimized</AttributeHierarchyOptimizedState></Attribute><Attribute><AttributeID>System_Reason</AttributeID><AggregationUsage>Default</AggregationUsage><AttributeHierarchyEnabled>true</AttributeHierarchyEnabled><AttributeHierarchyVisible>true</AttributeHierarchyVisible><AttributeHierar
So it ends rather abruptly. So I'm trying to use the content of Team System.2273.xml (which I for some reason have lying around). Wish me luck :-)
BTW, could it be possible for MS to straighten up their policy on nicing XML output? Always a problem to do diffs on XML when the lines are a mile long. Ever tried to resolve a conflict in a *.vsmdi file? Then u know what I mean :-(
I'll be back
Update 3:
That did the trick :-)
Brumlemann
--------------------
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): 04.09.2006 10:41:09
Machine: 540-SYSVAK
Application Domain: /LM/W3SVC/2/Root/Warehouse-1-128018256501820784
Assembly: Microsoft.TeamFoundation.Warehouse, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
Process Name: w3wp
Process Id: 2852
Thread Id: 3604
Account name: NO\TFSSERVICE
Detailed Message: The pending configuration changes were not successfully added to the cube because of the following error: Microsoft.AnalysisServices.OperationException: XML parsing failed at line 46, column 2253: Unexpected end of input.
.
Errors in the metadata manager. An error occurred when instantiating a metadata object from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\TFSWarehouse.0.db\Team System.2276.cub.xml'.
Errors in the metadata manager. An error occurred when instantiating a metadata object from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\TFSWarehouse.0.db\Team System.2276.cub.xml'.
at Microsoft.AnalysisServices.AnalysisServicesClient.SendExecuteAndReadResponse(ImpactDetailCollection impacts, Boolean expectEmptyResults, Boolean throwIfError)
at Microsoft.AnalysisServices.AnalysisServicesClient.Alter(IMajorObject obj, ObjectExpansion expansion, ImpactDetailCollection impact, Boolean allowCreate)
at Microsoft.AnalysisServices.Server.Update(IMajorObject obj, UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings, ImpactDetailCollection impactResult)
at Microsoft.AnalysisServices.Server.SendUpdate(IMajorObject obj, UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings, ImpactDetailCollection impactResult)
at Microsoft.AnalysisServices.MajorObject.Update(UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings)
at Microsoft.AnalysisServices.MajorObject.Update(UpdateOptions options)
at Microsoft.TeamFoundation.Warehouse.OlapCreator.CreateOlap(WarehouseConfig whConf, String accessUser, String dataReaderAccount, Boolean dropDB)
at Microsoft.TeamFoundation.Warehouse.AdapterScheduler.EnsureCubeIsUpToDate()
Solution Architect | 
index > Team Foundation Server - Reporting > Another TFS Warehouse problem...