Udostępnij za pośrednictwem

My Experience Setting Up TFSWindows SeverSQL Server 2008

  • Artykuł

Set up *another* VPC today. This is my first personal install of TFS 2008 ATDT on Windows Server 2008 with WSS 3.0 and Katmai (SQL Server 2008). I say personal because I’ve set one up for someone else before. Anyway, I did as I always recommend to my customers…

  • Start with CLEAN hardware (clean disk with no previous OS).
  • Get the latest TFS install guide and read it “front to back” for your type of install *before* starting.
  • Take it slow, follow the instructions to the letter and don’t skip anything.

…and I had no issues at all – the install completed without a hitch and I was up and running with a TFS 2008 SP1 / SQL Server 2008 / Windows Server 2008 ATDT install… or so I thought. Keep reading.

ISSUE 1 – RedX on Reports in Team Explorer

Following my successful setup I installed Team Explorer on the server and performed the TFS Litmus Test: Team Project Creation. It worked but there was something odd: even though the project was created successfully I had a Red-X on the REPORTS node in Team Explorer. Now if you’re like me, that makes very little sense to you. Nine times out of ten a Red-X on a node in Team Explorer means you have a permissions issue (in the case of Reports (SQL Server Reporting Services) and Documents (Windows SharePoint Services)), or TFS is completely hosed somehow (in the case of a Red-X on Work Items). Anyway, I came to discover that I had not installed Team Explorer 2008 SP1 on there and this Red-X on Reports when connecting to SSRS 2008 is a known issue with TE 2008 RTM. If you’re seeing this issue, update your Team Explorer to 2008 SP1.

 

ISSUE 2 – Constant Password Prompting For Local Web Sites

The second issue I encountered on this new VPC was constant password prompting whenever I’d hit localhost or folders under there,  even though I was logged into the PC as the ADMIN. I am still not 100% sure what was causing this, but I resolved it (with Jim’s (Saunders) help) by doing this:

  1. Open IE (7 in my case)
  2. Open Tools>Internet Options
  3. Go to the Security tab and click Local Intranet
  4. Click Sites, then Advanced
  5. Add your TFS AT to this list and OK your way back to the Options screen
  6. With Local Int**ra**net still selected, click "Custom level…”
  7. Scroll to the bottom and you should see a section titled “User Authentication” and a radio option under there titled “Automatic logon only in Intranet zone”. If this is not already selected, select it.

That should suppress the password prompts on this PC and you can probably use the same procedure for others as well.

 

ISSUE 3 – No Reports Working

So I ran through the nodes in Team Explorer after project creation (and after updating my TE to 2008 SP1, of course <g>) just to make sure everything was working. I created a few bugs, ran some queries, accessed some items under DOCUMENTS and tried to view some reports; the reports didn’t work. I was told that the cube had not been processed yet, which made sense since it was a recent install. I invoked the TFS warehouse service via the controller web service, but my reports *still* told me the cube was unprocessed. Checking my Application Event Log, I found a number of these errors:

Log Name: Application
Source: TFS Warehouse
Date: 10/16/2008 6:01:23 PM
Event ID: 3000
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: <BOX>
Description:
TF53010: The following error has occurred in a Team Foundation component or extension:
Date (UTC): 10/16/2008 10:01:23 PM
Machine: <BOX>
Application Domain: /LM/W3SVC/284281188/ROOT/Warehouse-5-128686630632089377
Assembly: Microsoft.TeamFoundation.Warehouse, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
Process Name: w3wp
Process Id: 3412
Thread Id: 2424
Account name: <BOX>\<USER>
Detailed Message: Create OLAP failed
Exception Message: Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
OLE DB error: OLE DB or ODBC error: Cannot open database "TfsWarehouse" requested by the login. The login failed.; 42000.
Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'TfsWarehouseDataSource', Name of 'TfsWarehouseDataSource'.
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Run', Name of 'Run' was being processed.
Errors in the OLAP storage engine: An error occurred while the 'Run ID' attribute of the 'Run' dimension from the 'TfsWarehouse' database was being processed.
Server: The operation has been cancelled.
OLE DB error: OLE DB or ODBC error: Cannot open database "TfsWarehouse" requested by the login. The login failed.; 42000.
Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'TfsWarehouseDataSource', Name of 'TfsWarehouseDataSource'.
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Run', Name of 'Run' was being processed.
Errors in the OLAP storage engine: An error occurred while the 'Remote Run' attribute of the 'Run' dimension from the 'TfsWarehouse' database was being processed.
(type OperationException)

…

Processing the cube manually in SQL Server Analysis Services produced similar errors. Now I am not sure why this happened, and I’ve only heard of it once before, but the gist of the issue is this:

  • There’s a data source in Analysis Services named “TfsWarehouseDataSource”
  • This DS connects to the TfsWarehouse database in the Data Engine part of SQL
  • This DS is configured to impersonate the SQL Analysis Services service (MSSQLServerOLAPService) account.
  • My MSSQLServerOLAPService service was configure to run under the NETWORK SERVICE account.

To end the long story, the NETWORK SERVICE account had no permissions on the TfsWarehouse database in the Data Engine part of SQL. Looking closely at this DB in the SQL Data Engine I found that NETWORK SERVICE was not even listed as a user!

FIX: Add NT AUTHORITY\NETWORK SERVICE as a user to the TfsWarehouse database in the SQL Data Engine, and add it to the TfsWarehouseDataReader database role. You can do that manually, or through a SQL script like this (run it from a SQL Management Studio query when connected to the SQL Data Engine):

USE TfsWarehouse
CREATE USER [NT AUTHORITY\NETWORK SERVICE] FOR LOGIN [NT AUTHORITY\NETWORK SERVICE]
EXEC sp_addrolemember N'TfsWarehouseDataReader', N'NT AUTHORITY\NETWORK SERVICE'

Hope this helps!
Trevor Hancock

Technorati Tags: TFS,Team Foundation Server,OLAP,SQL Reporting Services,Team Explorer

Comments

  • Anonymous
    November 04, 2008
    The Developer Support Team Foundation Server Blog on My Experience Setting Up TFSWindows ServerSQL...

  • Anonymous
    November 10, 2008
    The Developer Support Team Foundation Server Blog on My Experience Setting Up TFSWindows ServerSQL...

  • Anonymous
    November 19, 2008
    The comment has been removed

  • Anonymous
    November 20, 2008
    The comment has been removed

  • Anonymous
    November 21, 2008
    ShivKumar, I would try the following article: http://support.microsoft.com/kb/951756 MMJ

  • Anonymous
    December 10, 2008
    I can't find Team Explorer 2008 SP1 anywhere.  Can you tell me where I can get it?

  • Anonymous
    December 10, 2008
    TE SP1 is actually part of Visual Studio 2008 SP1 - it is not its own download or package. You can find VS 2008 SP1 here: http://www.microsoft.com/downloads/details.aspx?familyid=FBEE1648-7106-44A7-9649-6D9F6D58056E&displaylang=en

  • Trevor Hancock

  • Anonymous
    December 11, 2008
    Today I decided to create a TFS 2008 VPC environment using Windows Server 2008 and SQL 2008. In general

  • Anonymous
    December 15, 2008
    Many, many thanks for posting this. I'd tracked my reporting issue down to a database login issue on TfsWarehouse, your post saved me a lot of time working out what was going on from there!

  • Anonymous
    January 08, 2009
    Problem description : You can&#39;t create new team projects. You see a red X on Report in Team Explorer

  • Anonymous
    January 08, 2009
    Verify your ReportServerUri path - tfsadminutil has a bug in TFS 2008 SP1 and that can cause the TF30207 and the red X on Reports! -Neno

  • Anonymous
    January 08, 2009
    Problem description : After a clean install of TFS 2008 SP1 I was wondering about this message in the

  • Anonymous
    February 16, 2009
    First I installed Visual Studio on the clients and after that SP1 and THEN Team Explorer. Than I installed TFS2008 on a virtual server but I got the red x problem with Reports and I was not able to create a new Team Projekt on a client machine although I've got enough rights and permissions to do that. Ive searched a lot but without success. The problem was that I first installed the Visual Studio SP1 and after that the Team Explorer, you have to do this contrariwise because the SP1 updates some files of the Team Explorer. After reinstalling the SP1 it works fine for me, I'm now able to create new Team Projects and the red x problem disappeared. Greets

  • Anonymous
    June 16, 2009
    Many thanks, I'd made my way through most of your list before finding it on the reports problems. Saved me a heap of time!   Not having fun.

  • Anonymous
    August 12, 2009
    Tanks alot and alot. But I need more help. I had a problem about Reporing (TFS Reporting not work). I follow a method which descripted in this post: http://blogs.microsoft.co.il/blogs/shair/archive/2009/06/25/cannot-open-database-quot-tfswarehouse-quot-requested-by-the-login.aspx I do all of works exactly except one! In MS SQL Server Managemenet Studio I set '[ServerName]TFSService' schema as owned by user dbo. Then I found my mistake (I should set Network Service instead) but I could not uncheck this item again, so I went to the Schemas and set schema owner for [ServerName]TFSService schema to [ServerName]TFSService user. But TFS reports shows the same error message again. Would you please help me? I thinks its better to reinstall clean windows and setup TFS again.

  • Anonymous
    August 13, 2009
    We would be glad to help Armin, but I'll have to ask you to call us at support. You can start here: https://support.microsoft.com/oas/default.aspx?gprid=10453&st=1

  • Anonymous
    August 13, 2009
    Tanks Trevor again, I solved it! The point was this: Connecting to Analysis services>  database > tfswarehouse > roles > set the tfswarehousedatareader role permissions to full control process database! Thanks

  • Anonymous
    September 03, 2009
    Thanks man! You rule!!! What a great 'experience' doing the TFS2008+SQL2008 installation... So straightforward... Were it not for the VM snapshots I would have jumped off a cliff by now :P Now I still have this guys' problem http://social.msdn.microsoft.com/Forums/en-US/tfsreporting/thread/440e0f48-245a-4c28-9a5d-ed8a309845cb (Bugs found without corresponding tests Report not working (Hotfix KB969210 applied)) but I am sure I'll get over it somehow.

  • Anonymous
    September 04, 2009
    Ah shucks. :-) That final issue with the "Bugs found without corresponding tests" report is caused by a SSRS issue, not one with TFS. It actually should not happen any more if you have at lease one BUG in your team project. Or, you can apply the fix in this KB and that should clear it up too, regardless of how many BUGS are in your TP: http://support.microsoft.com/kb/969235. Loop back and let me know what you do and the results. I'll get this info added to OUR article too. TrevorH