|
| vs 2005 install fails |
|
|
|
|
| Messages |
|
Related Types |
This message was discovered on microsoft.public.dotnet.framework.setup.
Responses highlighted in red are from those people who are likely to be able to contribute good, authoratitive information to this discussion. They include Microsoft employees, MVP's and others who IMHO contribute well to these kinds of discussions.
| RedRock (VIP) |
| GOOD ANSWER |
Running fresh server 2003 (std ed) with current patches.
No other installs of any other products.
Install fail attempting to install .NET 2.0 Framework.
Help is necessary at this point.
error log content:
[07/23/04,15:31:37] Microsoft .NET Framework 2.0 Beta: [2] Error code 1603 for this component means "Fatal error during installation.
"
[07/23/04,15:31:37] Microsoft .NET Framework 2.0 Beta: [2] Setup Failed on component Microsoft .NET Framework 2.0 Beta
[07/23/04,15:31:40] setup.exe: [2] ISetupComponent::Pre/Post/Install() failed in ISetupManager::InstallManagerHelper() with HRESULT -2147023293.
[07/23/04,15:31:40] setup.exe: [2] Component error string not specified in ISetupManager::AddToActionResultCollection()
[07/23/04,15:31:47] VS70pgui: [2] DepCheck indicates Microsoft .NET Framework 2.0 Beta is not installed.
[07/23/04,15:31:47] VS70pgui: [2] Unknown component status forMicrosoft Visual J# .NET Redistributable Package 2.0 Beta
[07/23/04,15:31:47] VS70pgui: [2] DepCheck indicates Visual Studio 2005 Beta - English was not attempted to be installed.
[07/23/04,15:31:47] VS70pgui: [2] Unknown component status forMicrosoft Device Emulator version 1.0
|
|
|
| |
|
|
| |
| |
| RedRock (VIP) |
| GOOD ANSWER |
The problem is resolved.
Here are the details. We set up a completely new computer with a fresh install of Server 2003. Then all securith and service packs were installed all undeer the local Administrator account.
Following the MS best practices methodes the Administrator account name was changed. This action does not require a log-out or a restart.
Still loged in as the Administrator (remember the Administrator account name is now changed) an attempt to load the VS 2005 Beta 1 resulted in errors in the Windows Installer. In the MSDN KB article 315346 is information about the Windows Installer. A flash of understanding occured wihile reading the text although it does not specifically address the issue of changing the Administrator name.
Solution was simple, log off and log back on with the current Administrator name.
Best practice should be to perform a system restart following renamimg the local Administrator account. In this way all security descriptors will be current as well.
SyncPac CIO
|
|
|
| |
|
|
| |
|
| |
| RedRock (VIP) |
| GOOD ANSWER |
Additional information from event vewier:
Application log:
Source of error: MsiInstaller
event 1 (oldest) message:
Product: Visual Studio 2005 Beta - English -- Installation completed successfully.
event 2 (latest) message: (these are only a few seconds apart in time.)
Product: Microsoft .NET Framework 2.0 Beta -- Error 1719.The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
--
SyncPac Corp, CIO
"RedRock" wrote:
[Original message clipped]
|
|
|
| |
|
|
| |
|
|
|
|
|
|
|
|
BootFX
Reliable and powerful .NET application framework. |
|
|
|
|
|
|
