A recent install of Team Foundation Explorer errored out.  Opening the log file (from the link on the error screen) and scrolling to the bottom, showed the following:

[07/16/08,15:39:33] Microsoft Visual Studio 2008 Team Explorer - ENU: CRootComponent::Install(): Beginning Brooklyn Component Installation
[07/16/08,15:39:33] Setup.exe: ISetupManager::GetFullComponents()
[07/16/08,15:39:33] Setup.exe: ISetupManager::GetFullComponents()
[07/16/08,15:39:34] DepCheck: gencomp97,{12CDA52C-7A8F-4785-8A22-53C87393FEE0}
[07/16/08,15:39:34] DepCheck_Result: 1
[07/16/08,15:39:34] Microsoft Visual Studio 2008 Team Explorer - ENU: Install(): bAttemptInstall: 0
[07/16/08,15:39:34] Microsoft Visual Studio 2008 Team Explorer - ENU: Install(): Not attempting to call MsiInstallProduct()!!!! Baseline not met!
[07/16/08,15:39:34] Setup.exe: AddGlobalCustomProperty
[07/16/08,15:39:34] Microsoft Visual Studio 2008 Team Explorer - ENU: CRootComponent::Install(): Setup Failed; MSIInstallProduct return value either ERROR_INSTALL_FAILURE or default.
[07/16/08,15:39:34] Setup.exe: AddGlobalCustomProperty
[07/16/08,15:39:34] Microsoft Visual Studio 2008 Team Explorer - ENU: CRootComponent::Install(): Calling LaunchWatson()...
[07/16/08,15:39:34] Microsoft Visual Studio 2008 Team Explorer - ENU: CRootComponent::LaunchWatson() - Obtained CSetupWatson instance
[07/16/08,15:39:34] Setup.exe: GetGlobalCustomProperty - Property: {AA62DF98-3F2C-11D3-887B-00C04F8ECDD6} - PropertyName: Maintenance Mode - Value: 0
[07/16/08,15:39:34] Microsoft Visual Studio 2008 Team Explorer - ENU: CRootComponent::LaunchWatson() - Launching VS Watson
[07/16/08,15:39:34] Microsoft Visual Studio 2008 Team Explorer - ENU: CRootComponent::LaunchWatson() - Completed VS Watson launching to create manifest: C:\DOCUME~1\mmichael\LOCALS~1\Temp\vs_setup.dll.txt
[07/16/08,15:39:34] Setup.exe: AddGlobalCustomProperty
[07/16/08,15:39:34] Microsoft Visual Studio 2008 Team Explorer - ENU: CRootComponent::LaunchWatson() - Setting the property CustomCoreProp_WatsonManifestReady to use the VS Client Manifest.
[07/16/08,15:39:34] Microsoft Visual Studio 2008 Team Explorer - ENU: CRootComponent::Install(): Finished calling LaunchWatson()
[07/16/08,15:39:34] Microsoft Visual Studio 2008 Team Explorer - ENU: CRootComponent::Install(): Finished Brooklyn Component Installation
[07/16/08,15:39:34] UTILS::RunNGENAction: Started
[07/16/08,15:39:34] UTILS::RunNGENAction: starting "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ngen.exe queue pause"
[07/16/08,15:39:34] UTILS::RunNGENAction: ngen.exe returned 0
[07/16/08,15:39:34] Setup.exe: AddGlobalCustomProperty
[07/16/08,15:39:34] setup.exe: ***ERRORLOG EVENT*** : ISetupComponent::Pre/Post/Install() failed in ISetupManager::InternalInstallManager() with HRESULT -2147023293.
[07/16/08,15:39:35] Setup.exe: GetGlobalCustomProperty - Property: {7F82DEDD-12EB-439F-B7A3-8B4264E0C20D} - PropertyName: EnableRollback - Value:
[07/16/08,15:39:35] Setup.exe: GetGlobalCustomProperty - Property: {BD495746-4FBA-49F3-8EEB-D8B20EE75235} - PropertyName: Disable Rollback - Value:
[07/16/08,15:39:35] Setup.exe: ISetupManager::RunInstallFromList(IP_INSTALL) completed
[07/16/08,15:39:35] Setup.exe: GetGlobalCustomProperty - Property: {092114C2-997D-4D68-8F3A-8BC2584FD23B} - PropertyName: Quiet Mode Setup - Value:
[07/16/08,15:39:35] TFSUI: ISetupManager::GetGlobalCustomProperty() failed to find global prop in CProgressPage::RunningComponent()
[07/16/08,15:39:35] TFSUI: {4F8791EE-486F-44B5-952B-F28F9FD58BD0}

Working with Dhathri Potla, I identified two issues:

1. The HRESULT error indicates that there was a problem reading the media.  I had mounted and ISO file of Visual Studio 2008 with the TFC (Team Foundation Client) directory and attempted the install from there.  The ISO file itself was stored on a network share.  To avoid this error, copy the TFS directory onto the local drive.
2. “Baseline not met” indicates the prerequisites for TFC were not installed successfully.  Probably due to issue #1.

You can navigate to the TFS\WCU directory and manually install the prerequisites within each subdirectory and then retry the install.  However, as in my case, there prerequisites appeared to install correctly individually and yet the overall install log file showed that there were still prerequisites missing.  To address this, uninstall the prerequisites (like document explorer or Premier Partner Edition - PPE) and the re-run the TFS setup.exe.

Thursday, July 17, 2008 3:30:00 PM (Pacific Standard Time, UTC-08:00)      Comments [0]  Computer Related | .Net