TFS SP1 Installation Problems

For a while now people are struggling with some TFS SP1 installation issues. The majority of issues come down to a tool called TFSQuiesce.exe, that is responsible to "shutdown" TFS while performing the SP1 upgrade and restart it when it is done. Most issues with it are that for some reason, it does not always shutdown all services and it does not always restart them properly - leaving your server in an inoperable state. The good news is that it is almost always easy to recover from.

Customer Scenarios

The following scenarios describe the vast majority of issues seen around SP1.

	Issue	Customer Impact	Workarounds/Next Steps
1	SP1 fails to install on a SQL Cluster	Blocked from installing SP1 or any other DT patches.	None. Look for a patch/work around coming in the next couple of weeks.
2	SP1 install fails and: TFS databases in single-user mode IIS in state where remote connections are declined	AT won’t start an errors reported in Event Log. Http 403 forbidden error with browsers TF2101 message from TE (can't connect)	To get running (without SP1): Databases must be manually placed back in multi-user mode. Use SQL Management Studio; right click on each TFS database; select properties; Select the Options page; At the very bottom there is an item called "restrict access" - set it to "multi_user". There is a KB article in the works and should be published soon. IIS must be manually configured to accept remote connections - See section 6.9 of the SP1 Known issues doc below. To install SP1: Manually put remaining databases in single-user mode and retry installation. Use SQL Management Studio; right click on each TFS database; select properties; Select the Options page; At the very bottom there is an item called "restrict access" - set it to "single_user". This will not always work if other people are trying to use the database at the same time.
3	SP1 install succeeds but leaves IIS in state where remote connections are declined	Http 403 forbidden error with browsers TF2101 message from TE (can't connect)	IIS must be manually configured to accept remote connections - See section 6.9 of the SP1 Known issues doc below.
4	Users can’t uninstall SP1 Beta after installing Quiescing	The Quiescing logic breaks the Beta from uninstalling but you can’t uninstall Quiescing from Add/Remove programs because it doesn’t appear there if SP1 Beta is installed. (A chicken and egg issue.) The SP1 RTM will not allow you to install if the SP1 Beta is installed.	Run a manual uninstall operation from the command-line. See the steps at the bottom of this post... Uninstall TFS SP1 Beta - using Add/Remove Programs.
5	SP1 fails to install	These error are usually due to changes in configuration after RTM installation that our setup does not handle well. In some cases the customers are left with an unusable server.	Requires a review of the install logs for more details on the specific error and then ultimately identify the configuration change that broke the installer.

Here is a link to an SP1 Known Issues page. Most of these "issues" aren't new problems with SP1 but rather just common issues that people run into with TFS and what you can do about them.