1. Credentials are not persisted when a user wants to access reports and use Team Foundation Server in a single-server, workgroup deployment.
Details: When you visit the reporting Web site in a single-server, workgroup deployment of Team Foundation Server, you are prompted for credentials on the first visit. On subsequent visits, you receive no prompt for credentials and you cannot view reports.
Workaround: Configure Internet Explorer to always prompt for user name and password in the Local Intranet Zone.
- In Control Panel, open Internet Options.
- On the Security tab, click Local Intranet, and then click Custom Level. The Security Settings dialog box appears.
- In the User Authentication section, under Logon, select Prompt for user name and password, and then click OK.
- In the Internet Options dialog box, click OK, and then restart Internet Explorer.
2. New fields in custom work items marked as reportable do not appear in the Team System cube.
Details: Sometimes, the OLAP database becomes out of sync with the relational warehouse database. When this occurs, fields added to custom work item types do not appear in the Team System cube, even though they are configured as reportable in the work item type definition.
Workaround: On the application tier, invoke the Run method of the Warehouse Web services on: http://localhost:8080/Warehouse/v1.0/warehousecontroller.asmx?op=Run
3. After you customize a work item type, false errors from the Work Item Tracking adapter appear in the event log: "Microsoft.TeamFoundation.WorkItemTrackingAdapter: Unrecognized field type 160 in the Work Item Tracking database."
Details: If you customize the definition of a work item type, you may find errors in the event log that indicates that the Work Item Tracking adapter in the data warehouse found an unrecognized field type. These errors are being generated incorrectly.
Workaround: You can safely ignore these errors.
4. SQL Server 2005 Analysis Services fails when you try to slice the Work Item History Count measure by the Area classification while manually selecting members.
Details: If you use Microsoft Excel and the Office Web Components (OWC) to analyze the data cube, you may experience the following error when you add a Work Item History Count and then select or clear one or more Areas: "Internal error: An unexpected error occurred (file 'mdsubcube.cpp', line 2632, function 'MDBaseSubcube::NormalizePCKeys')".
5. Reports are not updating despite sufficient elapsed time.
Details: If an English edition of SQL Server 2005 is installed on an operating system that is using non-English regional settings, reports are not automatically updated because of a known issue. In the Application event log on the Team Foundation Server application-tier computer, you may find a cube process run-time error that indicates the conversion of a char data type to a datetime data type resulted in an out-of-range datetime value.
Workaround: Change The warehouse web.config file on the Team Foundation Server application-tier computer that is located at %ProgramFiles%\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\Warehouse\web.config, and add the following key in the
6. The Quality Indicators and the Reactivations report process guidance does not match the report.
Details: The Quality Indicators and the Reactivations reports were updated after the final release updates for the process guidance. Therefore, the images in the process guidance do not match the reports.
Workaround: Ignore the images in the process guidance. Look at the actual report to see how it looks.
7. There are no dates on the X-axis when I examine the following reports: Bug rates, Reactivations, Remaining Work, Unplanned Work.
Details: When the Internet Explorer language settings differ from the Team Foundation Server product language, there is bug that hides the dates on the X-axis.
Workaround: Switch the language settings of Internet Explorer to match the language of Team Foundation Server.
- In Internet Explorer, select the Tools menu and click Internet Options.
- Click Languages.
- Click Add and choose the Team Foundation Server product language.