Skip to main content

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.
Anonymous said…
Thanks for the info. Does this require SP1 of TFS2008?
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...

Popular posts from this blog

Get Your Team Foundation Server Hate On!

[Google ranking skyrockets... ;-)] I'm a big fan of TFS/VSTS. However, there are a good pocket of folks who take issue with the way TFS handles or implements a certain feature. Well this is your chance to vent! I'm planning a presentation around the "Top 10 TFS/VSTS Hates and How to Alleviate Them"...or something along those lines. But I need your help. Post a comment below detailing your dislike. If it's legitimate, I'll highlight it in the presentation and [hopefully] provide an alternative, resolution, or work-around. Thanks in advance! Update 7/19/2008: Version Control and Microsoft

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

Installing the .Net Framework 3.0 SP1 on Windows 2003 Server

I'm building an [automated] build server requiring the .Net 2.0 and 3.0 runtime. Unfortunately, at my client, they leverage a proxy server. The standard .Net 3.0 SP1 framework redist is really just a bootstrapper. Logged in as a local admin on the box, I didn't have the opportunity to authenticate the installation EXE with my domain credentials. So, the install kept timing out. Finally, I found this helpful post from Aaron Ruckman on how to download the very elusive, full framework package. It's here , BTW (x86). I finally get the full installation EXE downloaded to a fileshare, re-run the install and wham--" XPSEPSC: XPS must be installed..." Excuse you? This isn't an XPS ...it's a VM. I found a few MSDN posts here and here outlining the problem. I'm still not clear on what XPSEPSC does (Google yielded little) but you can download it here (x86) . After installing XPSEPSC, the framework installed without issue. Update : Somewhat related, there i