My TFS was installed on MS SQL Enterprises Trial, after upgrade to full version I cann't process warehouse and I getting this message (after Run methid http://localhost:8080/Warehouse/v1.0/warehousecontroller.asmx)

Event Type: Error
Event Source: TFS Warehouse
Event Category: None
Event ID: 3000
Date: 08/29/2006
Time: 17:39:02
User: N/A
Computer: ALITFS
Description:
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): 8/29/2006 3:39:02 PM
Machine: ALITFS
Application Domain: /LM/W3SVC/3/Root/Warehouse-1-128013394391204495
Assembly: Microsoft.TeamFoundation.Warehouse, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
Process Name: w3wp
Process Id: 5684
Thread Id: 2760
Account name: ALICE\TFSSERVICE

Detailed Message: The pending configuration changes were not successfully added to the cube because of the following error: Microsoft.AnalysisServices.OperationException: MdxScript(Team System) (4, 46) The '[Str]' function does not exist.
The END SCOPE statement does not match the opening SCOPE statement.
MdxScript(Team System) (6, 1) The END SCOPE statement does not match the opening SCOPE statement.
MdxScript(Team System) (8, 46) The '[Str]' function does not exist.
The END SCOPE statement does not match the opening SCOPE statement.
MdxScript(Team System) (10, 1) The END SCOPE statement does not match the opening SCOPE statement.
MdxScript(Team System) (12, 48) The '[Str]' function does not exist.
The END SCOPE statement does not match the opening SCOPE statement.
MdxScript(Team System) (14, 1) The END SCOPE statement does not match the opening SCOPE statement.
MdxScript(Team System) (16, 46) The '[Str]' function does not exist.
The END SCOPE statement does not match the opening SCOPE statement.
MdxScript(Team System) (18, 1) The END SCOPE statement does not match the opening SCOPE statement.
MdxScript(Team System) (4, 7) The hierarchy '[System_Id]' was not found in the cube when the string, [Work Item].[System_Id].[System_Id], was parsed.
The END SCOPE statement does not match the opening SCOPE statement.
MdxScript(Team System) (11, 1) The END SCOPE statement does not match the opening SCOPE statement.
MdxScript(Team System) (4, 46) The '[Str]' function does not exist.
The END SCOPE statement does not match the opening SCOPE statement.
MdxScript(Team System) (6, 1) The END SCOPE statement does not match the opening SCOPE statement.
MdxScript(Team System) (8, 46) The '[Str]' function does not exist.
The END SCOPE statement does not match the opening SCOPE statement.
MdxScript(Team System) (10, 1) The END SCOPE statement does not match the opening SCOPE statement.
MdxScript(Team System) (12, 48) The '[Str]' function does not exist.
The END SCOPE statement does not match the opening SCOPE statement.
MdxScript(Team System) (14, 1) The END SCOPE statement does not match the opening SCOPE statement.
MdxScript(Team System) (16, 46) The '[Str]' function does not exist.
The END SCOPE statement does not match the opening SCOPE statement.
MdxScript(Team System) (18, 1) The END SCOPE statement does not match the opening SCOPE statement.

at Microsoft.AnalysisServices.XmlaClient.SendExecuteAndReadResponse(Boolean skipResults, Boolean throwIfError)
at Microsoft.AnalysisServices.AnalysisServicesClient.CommitTransaction()
at Microsoft.AnalysisServices.Server.CommitTransaction()
at Microsoft.TeamFoundation.Warehouse.OlapCreator.ProcessOlap(Boolean schemaUpdated, UpdateStatusStore updateStatus)
at Microsoft.TeamFoundation.Warehouse.AdapterScheduler.EnsureCubeIsUpToDate()

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

I have try all methods found on forums, any idea???

Hi,

Have you been able to resolve this issue? If not, please let me know and I can find someone to help.

Thanks,
-Matt

Hi Matthew,

It seems that your install is in a state in which TFS tries to process the cube before the adapters were able to run for the first time to apply the appropriate schema changes. Calculations in the cube are referring to certain dimensions attributes that are not created yet hence a possible cause for the error you are seeing.

A work around for your issue would be to connect to the your Data tier using SQL Server Management Studio and opening the dbo._WarehouseConfig table in the TFSWarehouse database and modifying the CubeChangeTimeStamp setting so that it shows a time that is after the ConfigChangeTimeStamp(1 second later would be enough). This will enable the adapters to run and the cube to be rebuild and processed as expected.

Let me know if this does not solve your issue.

Thanks,
Othmane

I was troubleshooting a similar issue today with a customer and a change in the Analysis Services configuration fixed the issue. Posting back to this thread in case others encounter this.

This might occur if Analysis services cannot find the msmdvbanet.dll binary, the path to this dll is specified in the file VBAMDX.0.asm.xml ; The xml file can generally be found under Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data ; editing the xml file to point to the location of the dll should fix the problem and enable SQL AS to parse the calculations correctly and successfully process the cube. This might occur if the data folder was moved or deleted or if SQL AS is not configured properly to find it. You can check the setting by connecting to SQL AS using MS SQL Server management Studio and right clicking on the database and selecting Properties. The path to the folder is specified under ?œDataDir??

Thanks,
Othmane