TFS SP1 Problems
Had to upgrade our Team Foundation to SP1 today, part of which required “KB919156″. What fun I had. The error I was getting was the following:
The application pool identity required by Team Foundation Server (TFSWSS) for the content virtual server is not using the Team Foundation Server service account. To proceed, you must exit setup, set the application pool identity (TFSWSS) to use the Team Foundation Server service account, and then run setup again.
That translates to “DDSetStatus:The content app pool must be configured to use the TFS service account” in the MSI log file if you enable logging.
After an hour of battling with it and googling with no real results other than “reinstall” (not an option) I solved my problems by doing the following:
Ensure all Sts* and TFS* app pools run under the account you want TFS to run under (e.g. NWTRADERS.MSFT\TeamServer) and ensure the MsiProperty.INI (located in C:\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Microsoft Visual Studio 2005 Team Foundation Server – ENU) has the correct values for VSTF_RS_USERID and VSTF_DOMAIN. E.g.:VSTF_RS_USERID=TeamServer
VSTF_DOMAIN=NWTRADERS.MSFT
This occurred in our setup because we’d intially used local SAM accounts to run the services for TFS and later migrated to AD ones. Even if you run the TFSAdminUtil MsiProperty.INI doesn’t get updated. Neat, eh?
[...] blocked the installation of TfsQuiesce on the application tier, but Dave Hope readily provided a solution for that! Published Wednesday, October 10, 2007 9:41 PM by [...]