We had asked a contractor to take the time to install the Workgroup edition of TFS on a department server for evaluation. The contractor ended up leaving and the state of the TFS installation was unclear so I simply uninstalled TFS and initiated a re-install myself. SQL and Sharepoint seem to be fine. At this point the installation for TFS gives me an error while it is checking for pre-requisites and states that it can't install TFS because TFS is already installed on the server.

I of course had already successfully uninstalled it. It does not show up under Control Panel - Add, Remove Programs.

Does anyone out there no how I can get past this??

Thanks,

Dale

Can you check the event log for errors?, maybe there was some error uninstalling or something like that.

Also probably the databases were not deleted, so that's what TFS is checking, I would check also the existence of the TFS webservices.

Thanks for the ideas!!

I checked the event log and see alot of items regarding TFS prior to the uninstall however I don't see any errors or issues during the uninstall.

You were correct on the databases, so I manually deleted all of the databases that has a TFS in the name. I then tried the install again and received the same error.

I already had renamed the directory "Microsoft Visual Studio 2005 Team Foundation Server" under program files, and even went into regedit and renamed a few keys associated with TFS. I can't seem to find the remnant of TFS that the install program is checking for.

Is there any type of manual uninstall that I can attempt to run again or associated diagnostic.

Thanks!!

Was this a dual-server or single-server install? I would assume single-server based on "a department server" but wanted to verify.

The attempted install should have created a log file in %TEMP% (look for dd_vsinstall* and/or vsmsilog*). Those should help detail what's going on.

Yes, this is a single-server install

I found the files that you indicated and based on a quick look through them I found lots of items marked with Error or Issue but it wasn't clear to me as to how to interpret these. I probably need to stare at this longer.

I did find a file called dd_depcheck80.txt that looked like it indicated the VSCompsAlreadyInstalled info:

[10/04/06,08:49:15] Entering VSCompsAlreadyInstalled()
[10/04/06,08:49:15]
[10/04/06,08:49:15] DataFile Summary
[10/04/06,08:49:15] =================
[10/04/06,08:49:15] Component Data File: C:\Documents and Settings\TFSSETUP\Local Settings\Temp\SIT23320.tmp\baseline.dat
[10/04/06,08:49:15] Dependency File: C:\Documents and Settings\TFSSETUP\Local Settings\Temp\SIT23320.tmp\vs_setup.pdi
[10/04/06,08:49:15] Product to install: Microsoft Visual Studio 2005 Team Foundation Server - ENU
[10/04/06,08:49:15]
[10/04/06,08:49:15]
[10/04/06,08:49:15] Component Version Summary
[10/04/06,08:49:15] =========================
[10/04/06,08:49:15] Microsoft Windows 2003 Server
[10/04/06,08:49:15] entering CBlockAlways
[10/04/06,08:49:15] A 64-bit operating system is not supported
[10/04/06,08:49:15] entering CBlockAlways
[10/04/06,08:49:15] Windows 2003 Server Service Pack 1 Update Information
[10/04/06,08:49:15] This component uses the FileRegVerCheck version check method. It will compare a given version against the version of a regkey on your machine.
[10/04/06,08:49:15] Registry key being interrogated: HKLM,System\CurrentControlSet\Control\Windows; Value: CSDVersion; Version: 256.
[10/04/06,08:49:15] Version on user's machine: 256
[10/04/06,08:49:15] Version to be installed: 256
[10/04/06,08:49:15] Microsoft Windows Installer 3.1
[10/04/06,08:49:15] This component uses the FileVersionCheck version check method. It will compare a given version against the version of a file on your machine.
[10/04/06,08:49:15] The file to be verified is C:\WINDOWS\system32\msi.dll.
[10/04/06,08:49:15] Version on user's machine: 3.1.4000.2435
[10/04/06,08:49:15] Version to be installed: 3.1.4000.2435
[10/04/06,08:49:15] Microsoft Visual Studio 2005 Team Foundation Server - ENU
[10/04/06,08:49:15] This component uses the RegDwordCheck version check method. It will compare a DWORD against registry data on your machine.
[10/04/06,08:49:15] Registry key being interrogated: HKLM, SOFTWARE\Microsoft\VisualStudio\8.0\Setup\Microsoft Visual Studio 2005 Team Foundation Server - ENU; Value: InstallSuccess; Version: 1.
[10/04/06,08:49:15] Version on user's machine: 0.
[10/04/06,08:49:15] Version to be installed: 1.
[10/04/06,08:49:15]
[10/04/06,08:49:15]
[10/04/06,08:49:15] Installation Summary
[10/04/06,08:49:15] ====================
[10/04/06,08:49:15] TailorListForAlreadyInstalled()
[10/04/06,08:49:15] Microsoft Windows 2003 Server Component to be removed from installation list because it is marked "not to be installed".
[10/04/06,08:49:15] A 64-bit operating system is not supported Component to be removed from installation list because it is marked "not to be installed".
[10/04/06,08:49:15] Windows 2003 Server Service Pack 1 Update Information Later version or equal version of the component is on the machine.
[10/04/06,08:49:15] Microsoft Windows Installer 3.1 Component to be removed from installation list because it is marked "not to be installed".
[10/04/06,08:49:15] Microsoft Visual Studio 2005 Team Foundation Server - ENU
[10/04/06,08:49:15]
[10/04/06,08:49:15] Components that are already installed:
[10/04/06,08:49:15] gencomp8 ( Windows 2003 Server Service Pack 1 Update Information )
[10/04/06,08:49:15]
[10/04/06,08:49:15] ===========================
[10/04/06,08:49:15] End DepCheck Data session
[10/04/06,08:49:15] =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

Does gencomp8 provide the clue about what is already installed? It doesn't mean anything to me.

Thanks,

Dale

The following are the three product ID's that I could find that the pre-req checks look for when checking for previously installed instances of TFS. Removing registry keys with these values might unblock the setup.

459A3ED5-6529-475F-AFFF-55B7D7B6667B
14ECF4BB-6EC2-497E-BEEA-1D3D329198BF
05EB932D-00F0-432B-B82F-5D5C8B29C0F0

Thanks for the idea. I did a search using regedit, but I couldn't find any of these keys.

Dale

Dale:

You might try getting rid of the TFS databases from SQL. And maybe the TFS related App Pools and web site in IIS. The setup may block on one or both of those.

Wendell

FYI, the dep check looked fine - at the end it removes all the dependencies (already satisfied) and you're left (after the "tailoring") with just the TFS instance to install.

In terms of what's causing the installation to fail (because it believes TFS is already installed), that must be in another file. If it's too difficult to try and figure it out from the logs, one brute-force approach would be use to filemon and/or regmon from sysinternals to monitor what the setup program is doing, and when it fails the "already installed" check, you should be able to see what the recent filesystem and/or registry activity was to figure out where the offending piece is.

Of course, that's assuming the failing check is indeed in the filesystem or registry. Wendell's advice on killing the TFS web site (on port 8080) and app pool and also dropping the databases should help, as well.

Worst-case, clear %TEMP%, try another uninstall, then zip up the log files and send them my way (james.manning@) and we'll take a look at it.