I installed Sql 2005 on a Win2003, Sp1 platform. Some problems but nothing too big. Next I attempted to install VS 2005 (June) CTP. The install faled and here's the error log:
[08/17/05,21:40:11]
>>>>
Microsoft .NET Framework 2.0: [2] Error code 1638 for this component means
"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.
>>>>>
"
[08/17/05,21:40:12] Microsoft .NET Framework 2.0: [2] Setup Failed on component Microsoft .NET Framework 2.0
[08/17/05,21:41:01] setup.exe: [2] ISetupComponent::Pre/Post/Install() failed in ISetupManager::InstallManagerHelper() with HRESULT -2147023293.
[08/17/05,21:41:02] setup.exe: [2] Component error string not specified in ISetupManager::AddToActionResultCollection()
>>>>>>
[08/17/05,21:41:16] VS70pgui: [2] DepCheck indicates Microsoft .NET Framework 2.0 is not installed.
>>>>>>>
[08/17/05,21:41:16] VS70pgui: [2] Unknown component status forMicrosoft Document Explorer 2005
[08/17/05,21:41:16] VS70pgui: [2] DepCheck indicates Microsoft Visual Studio 2005 Standard Edition - ENU was not attempted to be installed.
[08/17/05,21:41:16] VS70pgui: [2] Unknown component status for.NET Compact Framework 1.0 SP3
[08/17/05,21:41:16] VS70pgui: [2] Unknown component status for.NET Compact Framework 2.0
[08/17/05,21:41:16] VS70pgui: [2] Unknown component status forMicrosoft Visual J# 2.0 Redistributable Package
[08/17/05,21:41:16] VS70pgui: [2] Unknown component status forSQL Server 2005 Mobile Edition
[08/17/05,21:41:16] VS70pgui: [2] Unknown component status forMicrosoft Device Emulator version 1.0
Any idea what is happening I sure hope the finished product is a lot better than their betas!
TIA,
Barker
Sql 205/Visual Studio, June 2005 CTP, from MSDN install Problem
hiteshvasoya
Cleaning up really old threads...
The problem here was that SQL installed one version of CLR 2.0, and then VS tried to install a different version. That's not supported. The solution would have been to pick synchronized versions of SQL and VS. This issue was resolved when both RTM'd.
Paul