Team Deploy is a free set of custom Team Build tasks for deploying MSIs to client PCs and servers.  Team Deploy 2.1 has been released and includes a number of fixes and a couple new features.

A special thanks to Jeremy Novak for creating the new CleanupPsExec task and multiple other fixes.  Here is the list of the changes:

• Moved Guidance and Installation from Word document to wiki site (and created a Troubleshooting section)
• Added -accepteula to all pstools calls so it won’t display the EULA dialog the first time it runs
• Added new CleanupPsExec task and test to clean up the PSTools service if it becomes stuck.
• Fixed spelling error in RemoteExecute task
• Added support to uninstalling 32bit apps on Windows 2008 64bit servers
• Changed property declarations to be auto-implemented
• Updated task required properties to have the Required attribute
• Created Team Deploy Installation Screencast
• Other misc fixes.

Team Deploy 2.1 can be found on CodePlex at http://teamdeploy.codeplex.com/.

-Mike

Today I completed the installation of Team Foundation Server 2010 beta 1.  I had previously started a couple times and run into a couple issue (mostly time) but didn’t get a chance to finish.  Tonight I finally worked through a couple issues and completed it.  I kept a few notes of the issues I encountered and what I did to resolve them.  If you run into any of these errors, I hope they help.

TFS Configuration Wizard Readiness Checks

When the configuration wizard completed, I had errors in Reporting Check and SharePoint Check.

Reporting

Here is the error

TF255275: The following Web service for SQL Server Reporting Services could not be accessed: http://myserver/ReportServer/ReportService2005.asmx

Problem was I installed Report Services in Integrated Mode.  It only supports Native.

Here are the steps to fix the error:

1. Deleted the ReportServer databases
2. Recreated the ReportServer database in Native mode.

SharePoint

We are planning on using this server for multiple things and we installed SharePoint 2007 on before I started the installation of TFS 2010 beta 1.  I thought that TFS would simply install the extensions to any compatible SharePoint installation on the server.  Apparently, TFS must install and configure SharePoint on the machine before the verification will allow you to continue. 

Here is the error

TF255282: Windows SharePoint 3.0 cannot be installed error on server.  The program is already installed on this server.

The fix is easy.  Simply, go to Add/Remove programs and uninstall.   However I do want MOSS 2007 to be install on it.  Once, I have a backup made after VSTS 2010 finishes installation.  I am going to try uninstalling WSS 3 and reinstalling MOSS 2007.

After fixing these two bugs, the Readiness Checks completed successfully.  Clear sailing from here?  Not quite.   When the configuration tool completed, it displayed the following error.

Windows NT user or group '.\tfsservice' not found. Check the name again.

Installation log details:

TF255356: The following error occurred when configuring the Team Foundation databases: Error occurred while executing servicing step Setup Warehouse for component TfsWarehouse during Install: Windows NT user or group '.\tfsservice' not found. Check the name again.. For more information, see the configuration log. (Error occurred while executing servicing step Setup Warehouse for component TfsWarehouse during Install: Windows NT user or group '.\tfsservice' not found. Check the name again.) ---> Microsoft.TeamFoundation.Framework.Server.CollectionServicingException: Error occurred while executing servicing step Setup Warehouse for component TfsWarehouse during Install: Windows NT user or group '.\tfsservice' not found. Check the name again. ---> System.Data.SqlClient.SqlException: Windows NT user or group '.\tfsservice' not found. Check the name again.

The system allowed me to enter a dot for the server name instead of the actual server name and then display the error.  I would classify this more as a user error but it would be nice to prevent or allow configuration tool, to lookup the actual server so it will complete.  I logged an error with Connect.  I will see how they rate it.

For the fix, fortunately I took a snapshot of server right before I ran this.  I restored to the previous step and restarted the configuration tool.   For the service name, I entered: <myserver>\TFSService and everything worked.

It finally completed with a Success message!!!  

While I have been typing this, I started the TSVS 2010 Beta 1 Installation.  It is really slow (knock on wood), but so far it hasn’t caused any errors.

Thanks,

Mike