Team System Web Access 2008 SP1

Amidst all the .Net 3.5 SP1 and VSTS 2008 SP1 excitement, Team System Web Access (TSWA) got pushed aside. Not to be left behind, the TSWA team announced their SP1 recently.

Installing it this morning, I encountered this error:

"Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel."

I posted to the forums about this and it turns out one must uninstall first and then re-install. Maybe I'm the odd one out but I can't recall ever uninstalling to apply a service pack. Regardless, here are the steps I followed:

1. Note IIS settings/configuration:

2. From Add/Remove Programs, remove Visual Studio Team System Web Access. Keep all your settings:

3. Kick off the TSWA MSI installer.

4. When you encounter the existing site conflict, configure to leverage/use the existing site and application pool:

5. I chose Windows authentication but choose whatever is appropriate for your environment:

Afterwards, it took a while for the IIS pool to spin up but TSWA was back and better than ever.

Comments

Anonymous said…

Thank you for the heads up :-D Worked like you described. Good job.

Friday, September 12, 2008 4:06:00 PM

Anonymous said…

Thanks for the info. Does this require SP1 of TFS2008?

Thursday, October 09, 2008 10:37:00 AM

Jeff Hunsaker said…

@anonymous [Does this require SP1 of TFS2008?] Not that I'm aware of...however, every time I've installed TSWA SP1, I've previously applied TFS2008 SP1. Not sure why you wouldn't apply both. (No reference to requiring TFS2008 SP1 in the TSWA 2008 SP1 System Requirements)
Jeff...

Tuesday, October 14, 2008 8:18:00 AM

Rollback a Ooops in TFS with TFPT Rollback

Rhut roe, Raggie. You just checked in a merge operation affecting 100's of files in TFS against the wrong branch. Ooops. Well, you can simply roll it back, right? Select the folder in Source Control Explorer and...hey, where's the Rollback? Rollback isn't supported in TFS natively. However, it is supported within the Power Tools leveraging the command-line TFPT.exe utility. It's fairly straightforward to revert back to a previous version--with one caveot. First, download and install the Team Foundation Power Tools 2008 on your workstation. Before proceeding, let's create a workspace dedicated to the rollback. To "true up" the workspace, the rollback operation will peform a Get Latest for every file in your current workspace. This can consume hours (and many GB) with a broad workspace mapping. To work around this, I create a temporary workspace targeted at just the area of source I need to roll back. So let's drill down on our scenario... I'm worki...

Switching the Parents to Ubuntu...?

I spent a half hour or so recently on the phone walking my Mom through a technical issue. Tentatively, I diagnosed her issue as a hard drive failure. She brought it over on her last visit and sure enough, the Dell XPS 450 from circa 1999 sounds like a bad coin-operated laundry at full capacity. I was aghast to discover she's running Windows 98. Ugh. Also, her recovery disk is just that--for recovery. I don't believe I'll be able to re-install Win98 on a new hard drive. That, coupled with the end of Microsoft (and Dell) support for Win98, got me thinking about Linux. (and she's not intense about her computing needs...and she doesn't want to spend much money...) I've been reading good things about switching one's parents to Ubuntu. Any thoughts out there?

VSTS Tester Demo Follow-ups

Last week, I delivered a VSTS 2008 Tester Edition demo to a prospective client. Following up on a few questions to which I didn’t know the answer: Q. Can I use Subversion with TFS? A. I get this question all the time from developers. It’s a perfectly valid question. The answer is no…but yes…sort of. The version control repository (and all data) must remain SQL Server. Yes, it’s proprietary. Further, if you plan to use TFS in your software development environment, but choose not to leverage it for version control, it severely limits the usefulness of the information elicited from TFS (because you’re not feeding in the crucial VC data). If you’re not leveraging VC in TFS, you’re probably not leveraging Team Build either. That said, while a fully-integrated TFS for ALM and SCM is the ideal, there’s a compelling argument to leverage TFS as a repository for requirements, scenarios, test cases, functional and load testing as well as defect tracking. TFS is an excellent repository to s...

Effective Thoughts

Search This Blog