This document lists the installation and product issues you might encounter while using this release of the Microsoft Visual Studio Code Name "Orcas" product.
Details: If you try to install Team Foundation Server on a 64-bit operating system with Microsoft SQL Server 2005 (32-bit), setup does not detect the SQL Server services and blocks installation.
Workaround: Use dual-server deployment, complete the installation steps for the Team Foundation data tier using Microsoft SQL Server (64-bit). For more information, see the topics "Team Foundation System Requirements" and "Overview of Team Foundation Server Dual-Server Deployment" in the Installation Guide.
Details: If setup must restart, and the antivirus application is set to clean the \temp directory on start, required setup files will be deleted and setup will fail with a program not found error.
Workaround: Restart setup after restarting the computer.
Details: In this release, high latency in communication between the Team Foundation Server application and database tiers may cause time-out errors when you are trying to transfer large files between the two tiers.
Workaround: Minimize the number of network hops between the Team Foundation Server application and database tiers.
Details:
When you use the provided answer file to install SQL Server 2005, you may
receive the following error:
"SQL Server Setup could not validate the service accounts. Either the
service accounts have not been provided for all the services being installed,
or the specified username or password is incorrect. For each service, specify a
valid username, password, and domain, or specify a built-in system
account."
Workaround: The answer file provided with Team Foundation Server contains English user account names that will cause setup to fail on non-English editions of Windows Server 2003. Modify the answer file to use the correct localized names for the specified accounts.
Details: If you install Team Foundation Server on a server that is already using TCP port 8080, Team Foundation Server setup will fail because the port is required for the Team Foundation Server Web site. This happens even if the existing Web site on port 8080 is stopped during setup.
Workaround: Make sure TCP port 8080 is not already being used before you install Team Foundation Server. Delete all Web sites bound to port 8080 or change their port number.
Details: If you install Team Foundation Server Proxy on a server that is already using TCP port 8081, Team Foundation Server Proxy setup will fail because the port is required for the Team Foundation Server Proxy. This happens even if the existing Web site on port 8081 is stopped during setup.
Workaround: Make sure TCP port 8081 is not already being used before you install Team Foundation Server Proxy. Delete all Web sites bound to port 8081 or change their port number.
Details: When you run Team Foundation Server (services) Setup, you may receive the following error:
Error 28918.TFServerStatusValidator: ErrorMakingWebServiceCall - the tool did not succeed calling Tfs Registration Web service. Either IIS is not running or is not configured correctly.
The default settings for the URLScan Security Tool installed on IIS can cause this error. If the URL contains more than one period, such as http://localhost:8080/services/v1.0/registration.asmx, URLScan rejects the request.
Workaround: Configure the URLScan Security Tool in the urlscan.ini file to allow for multiple periods in requested URLs by setting AllowDotInPath=1. For more information, see How to configure the URLScan Tool.
Details: Although some Unicode characters are allowed in Windows passwords, Team Foundation Server setup may fail if Unicode characters are used in passwords.
Workaround: Do not use Unicode characters in passwords.
Details: If you previously installed MSDN Library for Visual Studio 2005 or if you use locally installed Help for Team Foundation or Team Explorer as the primary source of documentation, you might have outdated or missing Help documentation.
Workaround: Download and install the most recent edition of the MSDN Library to make sure that you have the latest product documentation for Team Foundation and Team Explorer. For more information, visit the Team System Documentation Directory at http://go.microsoft.com/fwlink/?LinkId=62213.
Details: The most efficient way to install SQL Server 2005 is to use the answer files instead of the installation wizard.
Workaround:
For single server installation, see the answer file procedure in “How to: Install
Microsoft SQL Server 2005 for Team Foundation Server (Single-Server
Deployment)” in the Installation Guide.
For the data-tier of a dual server installation, see the answer file procedure in
“How to: Install Microsoft SQL Server 2005 for Team Foundation Server
(Dual-Server Deployment)” in the Installation Guide. For the application-tier
of a dual server installation, see the answer file procedure in “How to:
Install Microsoft SQL Server 2005 Reporting Services for Team Foundation Server
(Dual-Server Deployment)” in the Installation Guide.
Details: Setup was unable to confirm the application-tier server name. In the MSI log, you find the following entry: "Failed to load EventService proxy object: TF30076: The server name
Workaround: Open the registry and delete the registry key HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\TeamFoundation\Servers, and then restart setup.
Details:
Installation of Team Foundation Server fails with Error 32000. "The Commandline D:\Program Files\Common
Files\Microsoft Shared\Web Server Extensions\60\Bin\Stsadm.exe ...' returned non-zero value: -2130242250." because the Windows SharePoint Services administration site is not setup and Team Foundation Server cannot configure
the site.
The site should be set up during installation of Windows SharePoint Services but if the Internet Information Services (IIS) root directory was moved from the Inetpub folder to
another folder and the AdminScripts subfolder was not included in the move, the setup fails silently.
Workaround:
Details: System Health Check uses remote Windows Management Instrumentation (WMI) when you install the application tier. WMI requires that the remote administration port be open on the data tier. If this port in not open, you receive warnings that the data tier does not appear to be correctly configured.
Workaround: Verify that the port is open on the data tier and then continue past the System Health check. If you have the Microsoft Firewall enabled, the data-tier setup opens the required ports for Team Foundation Server to operate correctly.
Details: Setup has detected a SQL Server 2005 Reporting Services IIS application pool on this computer and cannot continue.
Workaround: Before running setup again, remove the Reporting Services application pool by opening Internet Information Services Manager, expanding the Application Pool node, and then deleting the pools for Reporting Services.
Details: The service accounts must have the "Log on as a service" permission set to Allow.
Workaround: Verify that "Log on as a service" is allowed for both service accounts.
Details: Team Foundation Server application tier single- or dual-server installation fails with error code 28804 or 28805. Further inspection of the installation logs will indicate that the problem occurred with the CreateDS custom action, and that the “operation you are attempting requires a secure connection (HTTPS).” This is probably due to Report Server being automatically configured to require SSL connections when an SSL certificate is required for the default Web site. Team Foundation Server installation cannot automatically configure the server for SSL-only connections. This is a post-installation configuration operation.
Workaround: For single server, open %ProgramFiles%\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\RsReportServer.config. Change the "SecureConnectionLevel" value from “2” to “0.” On the Team Foundation Server installation error dialog box, click Retry, or restart the installation. For dual server, click Cancel. Go to IIS Manager and configure the default Web site so that it does not require a secure channel (SSL) connection, and then re-run the application tier installation.
Details: After upgrading from the trial edition to the workgroup edition, trying to connect to the server from Team Explorer causes a TF53011 error: "The Team Foundation Server returned the following error: The request failed with HTTP status 403: TF53011: domain\user is not a licensed user...". This error appears because upgrading from the trial to the workgroup edition does not create the Licensed Workgroup Users group.
Workaround: After upgrading to workgroup edition, re-run the Team Foundation Server setup (application tier installation or single server installation), in repair mode.
Details: If you use different editions of SQL Server on the data tier and application tier, some combinations (for example, SQL Standard on the application tier and SQL Developer on the data tier) may cause setup failure.
Workaround: Use the same edition of SQL on both the application tier and data tier computers in a two server configuration.
Details: Team Foundation Server needs SQL Server 2005 (64-bit) installed on a 64-bit operating system. If SQL Server 2005 (32-bit) is installed on a 64-bit operating system, the System Health Check for the Team Foundation Server data tier setup will fail.
Workaround: Use SQL Server 2005 (64-bit) on a 64-bit operating system.
Details: Uninstalling and reinstalling the Team Foundation Server data tier does not add the required registration stored procedure to the Team Foundation Server Integration database, which causes the application tier installation to fail.
Workaround: Repairing the Team Foundation Server data tier installation will insert the required stored procedures, allowing the application tier to install successfully.
Details: The Web page that appears after installing Team Foundation Server Proxy contains incorrect information. In the XML example for configuring the proxy, an extra space appears in the value for the Uri element of the Server node of the proxy.config file,
Workaround: When you open the proxy.config file, you can copy the example, but be sure to remove the extra space after http://. For more information about configuring the proxy, see "How to: Enable Source Control Caching for Team Foundation Server Proxy" in the Team Foundation Server Administrators Guide.
Details: You cannot upgrade from any previous versions of Team Foundation Server to the Team Foundation Server code name “Orcas” version.
Workaround: None.
Details:
During the System Health Check, you receive the following error message:
Workaround: Download the ASP.NET 2.0 QFE hotfix here. See the Microsoft Web page KB913393 for more information.
Details: Visual Studio code name “Orcas” Team Explorer setup does not install the .NETFX35 runtime on a 64-bit operating system. This causes the installation to fail.
Workaround: Run the file dotNetFx35Setup.exe before you install Visual Studio code name “Orcas” Team Explorer. The file can be found in the folder \Proxy\WCU\dotNetFramework on the installation media.
Details: If you find that you must change the service accounts you provided during a previous installation of Team Foundation Server, make the changes using the security setting options available in Team Explorer or using the TFSAdminUtil command-line utility before you uninstall Team Foundation Server. Changing the service accounts using tools other than those provided with Team Foundation Server could lead to unexpected results. For example, changes to the accounts using Windows Services Manager and Internet Information Services (IIS) Manager are not automatically registered in Team Foundation Server.
Workaround: We recommend that you change the accounts after reinstalling or repairing Team Foundation Server if it is possible. If you must change the accounts before Team Foundation Server is uninstalled, create the accounts and then update the service accounts for the application pools of Windows SharePoint Services and Report Server. You can use Internet Information Services (IIS) Manager to update the application pools.
We recommend that you use domain accounts for the service accounts. If you chose a single-server deployment and you must use local accounts, make sure that you include the prefix "computername\" before the account name. For example, the Installation Guide uses "domain\TFSSERVICE" as a placeholder for the services account. If you want to change to a local account by that name, you must specify the prefix.
Details: When you uninstall Team Foundation Server and then try to reinstall on a single server or on the application-tier of a dual-server deployment, you must use the same service account that was used to install originally.
Workaround: To determine the service account that was used, open Services Manager, sort by “Log on as,” and then locate the services for Team Foundation Server at the bottom of the list. Examine the “Log on as” value for the services at the bottom; such as TFSServerScheduler. That value indicates the service account you must specify during the reinstallation.
Details: The following two scenarios result in package load failure errors:
Workaround:
Download and run the TFCRegFix file.
Open the TFCRegFix folder and choose one of the following options:
If you receive package load failure errors from an instance of Visual Studio 2005,
run the Whidbey_TFC_Uninstall_Cleanup.reg file.
— Or —
If you receive package load failure errors from an instance of Visual Studio code name
“Orcas,” run the Orcas_TFC_Uninstall_Cleanup.reg file.
Details: Upgrading using a CD with the full Windows Server 2003 SP1 installation, replaces the shared file mscoree.dll on a computer that has the .NET Framework 1.1 mscoree.dll file. Any applications compiled against the .NET Framework 2.0 will not run after the service pack is installed.
Note This does not occur when updating Windows Server 2003 with just the service pack. This is a problem when you upgrade with a CD that contains Windows Server 2003 and Windows Server 2003 SP1 bundled together.
Workaround: After you install the Service Pack, the .NET Framework must be repaired.
† Required for creating Microsoft Visual Studio Tools for the Microsoft Office System projects. When you create an Office project, Visual Studio tries to install any required PIAs that are not installed. If the PIAs were not set to “Installed on first use” during Office installation, you might need the Office installation media and administrative rights to install them. You can now either create Excel, Word, and Outlook projects or manually install the PIAs (see the following section).
‡ Required for Microsoft Office integration with Visual Studio 2005 Team Explorer.
To manually install the required Primary Interop Assemblies (PIAs)
You can manually install the PIAs by following these instructions if you are running a full edition of Office 2003. Follow similar steps for stand-alone versions of Excel, Outlook and Word, but note that not all the PIAs are available.
Details: If you add a Windows user or group and only set to Allow any Version Control permissions at the server or project level, such as the "Administer Shelved Changes" permission, they will not be added to the Team Foundation Valid Users group. If they are not a member of the Team Foundation Valid Users group, they cannot connect to Team Foundation Server.
Workaround: Because the Team Foundation Valid Users group cannot be manually changed, you must either add the user or group to an existing group (to inherit permissions of the existing group) or explicitly grant the user or group another server-level or project-level permission (for example, View Server-level Information) in addition to the Administer Shelveset permission. This extra permission will add them to the Team Foundation Valid Users group.
Details: When you use TfsAdminUtil to change the TFSReports service account, the final message generated by TFSAdminUtil ChangeAccount is incorrect. However, this message is relevant when you change the TFSService account.
Workaround: None. Ignore the message. Do not add the TFSReports service account to the Team Foundation Service Accounts group.
Details: If the Visual Studio IDE and Team Foundation Server are installed on the same computer, and you uninstall Team Foundation Server, the Visual Studio IDE may be broken. You may see various errors when you try to build a project in the Visual Studio IDE.
Workaround: Repair or reinstall Visual Studio from Control Panel.
Details: Users attempting to connect to Team Foundation Server Workgroup Edition receive the following error: TF31001: Team Foundation cannot retrieve the list of team projects from Team Foundation Server. The Team Foundation Server returned the following error: The request failed with HTTP status 403: Domain\User is not a licensed user...
Workaround: Workgroup Edition limits access to Team Foundation Server by checking that the user is a member of the "Team Foundation Licensed Users" application group. This is a special server-level application group with no permissions, and is used only by the Workgroup Edition. A Team Foundation Server administrator must add the user to this group in order for them to have access to Team Foundation Server. Note that the user still needs to be added to another Team Foundation Server application group to be granted permission to access the server and have various levels of functionality.
Details: After upgrading from Workgroup Edition to the Full Edition, when opening the server-level groups dialog box (Server->Team Foundation Server Settings->Group Membership), the "Team Foundation Licensed Users" group is still present on the server.
Workaround: The full edition of the server ignores the "Team Foundation Licensed Users" group. Note that this group cannot be removed because it is a special application group.
Details: Reinstallation fails if you are using a different service account than when you installed Team Foundation Server.
Workaround: If you need to change the service account, reinstall with the original service account and then run TfsAdminUtil ChangeAccount to change the service account.
Details: After renaming a single-server computer, Team Foundation Server no longer works, even after running TfsAdminUtil ActivateAT and TfsAdminUtil RenameDT. The NT event log will contain numerous errors that suggest that the remote server name could not be resolved. The issue is that the Web service–to-Web service calls will still be using the old single-server computer name.
Workaround: When renaming the single-server computer that contains the application tier and data tier, you need to update the values for TfsNameUrl and TfsName on the top-level web.config under (%ProgramFiles%\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\). You also need to update the BisDomainUrl and change its name to TfsNameUrl in TfsServerScheduler.exe.config file.
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 username and password in the Local Intranet Zone.
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
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.
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')".
Workaround: None.
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 <appSettings> section:
<appSettings>
<add key="ProcessType" value="Full" />
</appSettings>
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.
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.
The steps:
Details: In Windows Vista, the default Arabic–Saudi Arabia calendar has changed from Hijri to Um Al Qura. Reports using the Um Al Qura dates will sometimes have incorrect data because the two calendars are different.
Workaround: In your Windows Vista client, change the calendar from Um Al Qura to Hijri.
Details: When you open work items from Team Explorer in Microsoft Office Excel 2003, you may receive the error TF86001: Team Foundation was unable to load the Office Add-In. You may also receive the error TF80042: The document cannot be opened because you do not have Microsoft Excel 2003 or one of its components installed. These errors are caused when you install Team Explorer before you install Microsoft Office Excel 2003. The Microsoft Visual Studio 2005 Tools for Office Run Time will not be configured to work correctly with Team Explorer and must be repaired.
Workaround:
You must repair the Microsoft Visual Studio 2005 Tools for Office Run Time to correct this issue.
Details: After changes are made to My Favorites, such as adding, removing, or renaming documents, if you click Refresh in Team Explorer, the changes are lost. Changes to My Favorites are not saved to disk, even when Visual Studio is closed. Restarting Visual Studio will use the My Favorites layout that you originally created.
Workaround: None.
Details: After reconfiguring or restoring Team Foundation Server, Team Explorer may have difficulty connecting to the server. The error "TF31005: Team Foundation cannot retrieve the list of team projects because it cannot connect to Team Foundation Server <server name>" displays. This issue occurs because of locally cached data that is no longer synchronized with Team Foundation Server.
Workaround: Either wait for Team Explorer to automatically update (within two hours), or manually clear the local cache.
To manually clear the local cache:
Details: If the date format in Microsoft Project does not include time data, there could be a mismatch between the time displayed in a Microsoft Project task, and the time displayed in the same work item in Visual Studio.
Workaround: Use a date format in Microsoft Project that shows both the date and time.
To change the date format in Microsoft Project:
Details: Although they are not listed in the error message, ‘[‘ and ‘]’ are not valid symbols for names in the New Team Project wizard.
Workaround: Do not use ‘[‘ or ‘]’ when naming your team project.
Details: Because of a known limitation in Windows SharePoint Services, team project portals that contain Chinese, Japanese, and Korean Extension A and B characters are not supported. Therefore, the same characters are not permitted in team project names.
Workaround: None.
Details: On computers with security update 896358 installed, downloaded Compiled Help Module (CHM) files cannot be opened.
Workaround: See KB902225.
Details: When Team Explorer is installed and you select the Help menu and click About Microsoft Visual Studio, the Product ID numbers for the products installed may not appear in the dialog box.
Workaround:
On the computer that has Team Explorer installed, run the following commands:
Note: Although Registry Editor enables you to inspect and modify the registry, normally you do not need to do so, and making incorrect changes can break your system.
Details: If you installed Microsoft Project 2007 Beta2TR and have not run it before, you get an error when you try to export items from Team Explorer to Project. When you try to run Project for the first time, Office 2007 launches a dialog box asking you to sign up for services such as Office Online Help, System Health, and the Customer Experience Improvement program. This dialog box interferes with the loading of the Team Foundation Server add-in in Project.
Workaround: Click OK on the error dialog. Perform one of the following steps:
Details: If you add a user to the <ALLOWEDVALUES> list for the Assigned to field in a work item type, the new user may not appear in the Excel list. This occurs because the user list in the Excel cache has not been updated.
Workaround:
Close the Excel workbook, re-open the file, and click Refresh to update the user list.
— Or —
Add a new list object to the file. For more information, see the section “To connect a work item list to Team Foundation” in the topic How to: Connect to Team Foundation from Microsoft Excel or Microsoft Project.
Details:
In an Excel list object, if you try to delete a Team Foundation Server column by right-clicking the column and clicking Delete, the column will not be deleted.
Then if you try to attempt any additional list operations, such as selecting or editing a cell, the following error appears:
TF80069: Team Foundation encountered an error while updating data in the application.
Workaround: Use the column chooser dialog box to remove the column. For more information, see How to: Add or Remove Columns in the Work Item List.
Details: When you cut and paste a list object that is bound to Team Foundation Server, the following error appears two times: TF80069: Team Foundation encountered an error while updating data in the application. After you close the error dialog box, the Excel list is unusable. Additional list operations, such as selecting or editing a cell, result in the error TF80069.
Workaround: None.
Details: Team Foundation Server code name “Orcas” is designed to run side-by-side with previous versions of Team Foundation Server.
Workaround: None.
Details: If you install Visual Studio 2005 Team Foundation side-by-side with Visual Studio code name “Orcas” Team Foundation, the Team Foundation Server add-in for Microsoft Office will be registered once for each version. This causes the following error when you try to open Team Foundation Server bound Microsoft Excel files from Team Explorer:
Workaround: Save the Microsoft Excel or Microsoft Project file locally on your computer and then open it.
Details: When you run remote tests from Team Foundation Build, the user account used to run the build must be a member of the TeamTestControllerUser or TeamTestControllerAdmins local security accounts on the Team Test Load Agent controller computer. Also, if you use Windows Firewall (or another third-party firewall solution), MSBuild must be able to access remote computers.
Workaround: Add the user account used to run the build to the TeamTestControllerUser or TeamTestControllerAdmins local security account on the Team Test Load Agent controller computer. Also, add MSBuild to the Windows Firewall exception list on the Team Foundation Build computer.
Details: If you change the account used to run the Team Build Service, you must grant the new user account some additional permissions.
Workaround: The Team Build Service account must have write permissions to the ASP.NET temp folder on the build computer.
Details: If you delete an existing team project on Team Foundation Server, and then create a new team project with the same name, you will be unable to create new build definitions. This problem occurs because data in the local cache is not updated when the team project is deleted.
Workaround: Restart Visual Studio on the computer where you experience this issue. Or reset IIS on the application-tier computer by running iisreset at the command prompt.
Details: In Team Foundation Server code name “Orcas” Beta 1, you must perform two additional steps after you add the SolutionToPublish item in the TfsBuild.proj file for the build definition.
Workaround:
Perform these additional steps after you add the SolutionToPublish item in the TfsBuild.proj file:
Details: When a build fails, the CreateNewWorkItem task is started but fails with error TF42097. A work item will not be created or saved for the build failure.
Workaround:
Locate the following code in the file TfsBuild.Proj:
<WorkItemFieldValues>System.Reason=Build Failure;System.Description=Start the build using Team Build</WorkItemFieldValues>
Replace “Build Failure” with the bolded text shown below:
<WorkItemFieldValues>System.Reason=ビルド エラー;System.Description=Start the build using Team Build</WorkItemFieldValues>
Details: VSSConverter cannot migrate subfolders in a Visual SourceSafe database that contains older files that were restored from an archive containing files that predate their parent folders. VSSConverter works in chronological order and cannot migrate files in this condition because the parent folders are not created before the files they contain. Move or rename operations can make the problem worse.
Workaround: None.
Details: In Visual SourceSafe, time stamps are recorded to the nearest second. Sometimes, a file or folder operation may have occurred within milliseconds that resulted in what appears to be a name collision based on the recorded time stamp when in fact the events occurred sequentially. When VSSConverter tries to re-create the sequence of events, it encounters the naming collision that did not actually occur in Visual SourceSafe because it tries to perform the operation at the same time.
Workaround: None.
Details: When a Visual SourceSafe folder has been moved or renamed many times, VSSConverter may not be able to determine the current name of the folder. Such folders, and their contents, are not migrated correctly. In the migration report, you will see the following errors: "The item already exists." and "The item could not be found in workspace."
Workaround: None.
Details: Visual SourceSafe Converter does not migrate source control bindings for Visual Studio solutions. You may receive error messages related to source control bindings when you open a Visual Studio solution after migration.
Workaround: After migrating a Visual SourceSafe database, you must manually change the source control bindings for each Visual Studio solution that was migrated. For more information about manually migrating source control bindings, see the latest version of the Team Foundation Administrators Guide.
Details: VSSConverter combines multiple actions into a single changeset to improve the migration performance. The time stamp for the changeset is incorrect.
Workaround: None.
Details: In some scenarios, VSSConverter cannot migrate the version history of files and folders correctly. When migration is complete, VSSConverter performs an additional step to affix the latest version, PINNED, and Pinned_Latest label on Team Foundation. When fixing mismatches, you may not see any output (feedback) in the console and the VSSConverter may appear to have stopped working. This is not an indication that anything is wrong and is expected behavior. After migration, the history of files that are fixed may be incorrect. Also, you may see empty folders in Source Control Explorer caused by the fixing these mismatches. The summary of the mismatch fix process can be found in summary section of migration report.
Workaround: None.
Details: In the Japanese Edition of Visual Studio code name “Orcas” Team Foundation Server, the VSSConverter will not work.
Workaround: None.
Details: You can subscribe to text or HTML e-mail check-in alerts. The check-in e-mail you receive has links to different files in the solution you are checking in. If you subscribed to text e-mail alerts, clicking a link to various file types (for example, .aspx, .cs, or .sln) might display a "Page not Found," "Index was out of Bounds," or "Path Longer than 260 Characters" error message.
Workaround: Use HTML e-mail check-in alerts instead of text e-mail check-in alerts.
Details: Creating team projects, running CQConverter.exe or VSSConverter.exe, checking in files, and other Team Foundation Server network related activities are running unnecessarily slow.
Workaround: The client network card configuration may be causing slow network performance. For more information, see the knowledge base article The effects of using auto detect settings on cluster network interface card.
Details: If you edit XML, .XSL, .WIQ, or .RDL files using Notepad and save using CRTL+S, the default encoding used is ANSI. This will cause problems if the files contain non-ASCII characters.
Workaround: When editing any .XML, .XSL, .WIQ or .RDL files in a process template, make sure to save them with the "UTF-8 with signature" encoding (if editing with Visual Studio) or "UTF-8" (when using Notepad). Other editors might vary in behavior and you should make sure the files are saved with a UTF-8 encoding and a Byte Order Mark (BOM or signature) at the beginning of the files. The presence of the BOM can be detected by checking the first three bytes of a file. They should be EF BB BF (hex).
Details: This message should read as follows: The configured "from address: $1" for project alerts is not a valid or recognized e-mail address. Users will not receive project notification e-mail messages until the "emailNotificationFromAddress" property in the application-tier services web.config file is changed to a valid e-mail address.
Workaround: Reconfigure the e-mail services notification so that it contains a valid e-mail address.
Details: During installation, if the SMTP server is not specified, the installation will default to the application-tier server. If the “emailNotificationFromAddress” is not set, then the application event log will list the error, “Invalid default ‘From’ address.”
Workaround: To correct this problem, edit the Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\Services\web.config file to either specify a valid "emailNotificationFromAddress" value, or if project alerts are not being used, specify an empty “smtpServer” value. In the web.config file, change the following line:
<add key="smtpServer" value="<hostname>" />
to:
<add key="smtpServer" value="" />
Details: After you insert an ID bound listobject, if you reset the List toolbar, and then click anywhere outside the listobject, a COM exception is thrown. The error message "TF80069: Team Foundation experienced an error when updating the data in the application" displays every time that you click outside the listobject.
Workaround: Save your changes to the Excel worksheet on the local computer, close, and then reopen Excel. You can publish your changes and continue to use the Excel worksheet without the error displaying again.
Details: Team Foundation command-line tools run in the context of the current user. If you are not authorized to access the Team Foundation Server, you receive a message saying that you are not authorized to access the server. In most cases you will not be prompted to supply alternate credentials.
Workaround: Use the "runas" functionality to provide alternative credentials that are authorized to access the Team Foundation Server. Note that this is only available on Windows XP and Windows Server 2003. One of the tools that prompts for alternate credentials (if you are not authorized to access the Team Foundation Server) is tf.exe. However, you must first use Team Explorer to prompt for alternate credentials by trying to connect to Team Foundation Server before tf.exe will connect properly.
Details: Running the TfsAdminUtil SID command to display information about a specified account using the domain\account format will always return zero matches even if the specified domain\account exists in the system. This is contrary to the help information provided by TfsAdminUtil, which specifies incorrectly that the domain\account format must be used.
Workaround: Specify the account name without the domain qualifier, and TfsAdminUtil SID will return all users in the system with that account name.
Details: Users cannot perform a case-only rename on a folder if they have any items locked under the folder.
Workaround: Rename the folder to something different, perform a check-in, and then rename the folder to the original name with the desired case.
Details: If Team Foundation source control stored encoding for a file is a DBCS codepage (such as Shift-JIS), the command-line difference command (tf difference /noprompt) will not ignore case correctly when specified by using /ignorecase.
Workaround: If the file contains no double-byte characters, use the /type parameter to specify an SBCS codepage (for example, /type:ASCII). If the file does contain double-byte characters, either avoid using the /ignoreCase parameter, or configure a third-party diff tool (using "tf difference /configure") which correctly supports case-insensitive comparisons in DBCS codepages.
Details: If the Visual Studio Team Foundation Server plug-in is not associated with the Visual Studio IDE, some source control features will not be available. For example, when you right-click inside the working area of Source Control Explorer, “No Commands Available” is displayed.
Workaround: Associate the Visual Studio Team Foundation Server plug-in with the Visual Studio IDE by following these steps:
Details: When you rename a project folder in Visual Studio using Solution Explorer, files in that folder, such as datasets or resources, may be marked read/write and have changes written to them without performing a check-out. This issue affects any files that have a custom tool assigned to them and do not have a custom tool namespace.
Workaround: When renaming a project folder, you are prompted with the name of each file that is being modified. After the project folder is renamed, manually check out those same files.
Details: You create a file with an alternate data stream. However, when you add it to version control and check it in, the alternative data stream is lost.
Workaround: None.
Details: In version control, permissions are based on the path name rather than the item. If you delete a file and add another file in the same location with the same name, the two files will always have the same permissions. Similarly, if you have permissions to a file, and then the file is renamed and you are denied permissions to the renamed file, you still have permissions to all of the file versions and contents before the rename.
Workaround: If you rename items in version control, you must apply permissions changes to all names the item has had.
Details: In some cases, the Team Foundation Server does not synchronize with Active Directory or Windows Users and Groups. The hourly background synchronization does not work.
Workaround: A full synchronization will occur if one of the following takes place:
Details: If you have pending changes on your local computer that might conflict with the shelveset changes, the pending changes will block the unshelve /move command. The /move option deletes the shelveset even if the unshelve command is not successful.
Workaround: None.
Details: Field names that start with a number (for example, "2005Field") are truncated to include the number only (for example, "2005").
Workaround: Enclose fields that start with a number in square brackets (for example, "[2005Field]").
Details: When you use the Contains operator to query a long-text field, work item tracking performs a SQL Server full-text query on the work item database. The full-text query excludes SQL noise words such as “a”, “of” and non-alphanumeric characters. An empty result list is returned when you use this kind of query that contains SQL noise words.
Workaround: Remove SQL noise words from the query.
Details:
If you open a work item or a query results window in Visual Studio code name “Orcas” Team Foundation
Server and click Print, the work item or query results will not print. Instead, the following error
will be printed:
Cannot access a closed stream.
Workaround: None.
Details: In both MSF for CMMI Process Improvement and MSF for Agile Development projects, the links to the Exit Criteria and Issues List reports on the team project portal site point to incorrect reports. If a user runs these reports, they will see the Work items report instead.
Workaround: Open these reports from the Reports folder on the Windows SharePoint Services portal instead of using these links.
Details: On some operating systems, Windows SharePoint Services does not handle URLs that contain certain Unicode characters properly. This can cause the team portal and the process guidance to only display partially.
Workaround:
Details: The following items are missing: All Quality of Service Requirements, All Scenarios, Project Checklist, Untriaged Bugs, and All Issues. These Microsoft Excel files correspond to queries in the Team Queries folder and can be used to view query data in Excel.
Workaround: Right-click the query you want to view in Excel and then click Open in Microsoft Excel.
Details: When multiple Visual Studio solutions are associated with the same team project, setting a unit test check-in policy for that team project will cause check-ins to fail.
Workaround: Do not set a unit test check-in policy for a team project that has more than one Visual Studio solutions associated with it.
Details: When you change the link to test results from the bug form, the bug form throws an exception if the test results have not been published.
Workaround: If you receive this exception, remove the invalid link from the bug form. To avoid this exception, publish the results before creating the bug or do not change the link.
Details: Deleting a build that has tests published against it will cause the Coverage Analysis Service to write an event log warning.
Workaround: Ignore the event log warning.
Details: Trying to publish test results when the Visual Studio user is not recognized by Team Foundation Server will fail, even though Team Foundation Server does not ask you for valid credentials when it tries to publish test results.
Workaround: Run Visual Studio as a user recognized by Team Foundation Server.