Tuesday, April 25, 2006

VSTS TF Server Known Issues

1. Team Foundation Server is unavailable over the Internet through HTTP, when you use Basic or Digest authentication.
Team Foundation client applications, such as Team Explorer, access Team Foundation Server functionality through a collection of Web services hosted on Internet Information Services (IIS) 6.0. The initial RTM release of Team Foundation Server only supports Integrated Windows Authentication. This allows for clients to use their Windows credentials to access this functionality. Basic and Digest authentication are not supported currently.
Workaround: You can use a virtual private network (VPN) if your scenario requires accessing Team Foundation Server from outside the local intranet. Alternatively, and subject to your own risk analysis, you may opt to expose your Team Foundation Server to the Internet and require encrypted connections (for example, HTTPS using SSL/TLS); however, you may be held back by proxies on the client side of the equation, such as those provided by Internet Service Providers (ISPs).

2. Team Foundation Japanese Edition - Links within text e-mail Team Foundation alerts received for check-ins can display error messages.
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.

3. Slow Network Performance.
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" (http://support.microsoft.com/kb/174812).

4. Encoding for XML, .XSL, .WIQ, and .RDL files.
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).

5. You receive the following error in the event log: "Unrecognized default notification from address."
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.

6. SMTP Server Invalid default 'From' address error in event log.
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:
" />

7. Resetting Microsoft Excel's List toolbar item causes exception.
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.

8. Team Foundation command line tools do not prompt for alternate user credentials.
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 will get 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.

9. TfsAdminUtil SID command does not allow the domain\account format to list account information.
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.

No comments: