Problems installing VSTS 2005 Dec. 2004 Refresh

I am sure you also have played with VSTS, but not sure if you are having problems with VSTS Dec 2004 Refresh bits up on MSDN. I am installing this natively (not on VMWare/VirtualPC, etc.) running Windows 2003 Enterprise Edition with VS.NET 2003, SQL Server 2000, SQL Server 2005 (Beta 2), and usual suspects like Office 2003, etc. During the installation process when I get to installing Visual Studio (see screen shots below), aftre going about 60-70% of the way I get an error – “Product: Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English — Error 1304.Error writing to file: Microsoft.VisualStudio.Windows.Forms.dll.  Verify that you have access to that directory.” Now everything seems to be ok to me, I am logged as God (Domain Admin) on the box and there is enough disk space as well, so not sure what is causing this.

Here are the screen shots (you can click on them to see the full resoultion):

When I look at the logs here is the error from there. You can download the complete installation log from here.

[01/07/05,08:41:31] Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English: CRootComponent::SetMsiLogFileName(): Setting MSI Log Name to:C:\Documents and Settings\Administrator\Local Settings\Temp\VSMsiLog2838.txt
[01/07/05,08:41:31] Setup.exe: AddGlobalCustomProperty
[01/07/05,08:59:13] vs70uimgr: Entering DisplayMessage() method.
[01/07/05,08:59:14] vs70uimgr: DisplayMessage_START:Error 1304.Error writing to file: Microsoft.VisualStudio.Windows.Forms.dll.  Verify that you have access to that directory.
[01/07/05,09:04:00] vs70uimgr: DisplayMessage_END:Error 1304.Error writing to file: Microsoft.VisualStudio.Windows.Forms.dll.  Verify that you have access to that directory.
[01/07/05,09:04:00] Setup.exe: AddGlobalCustomProperty
[01/07/05,09:04:00] Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English: ***ERRORLOG EVENT*** : ERROR:Error 1304.Error writing to file: Microsoft.VisualStudio.Windows.Forms.dll.  Verify that you have access to that directory.
[01/07/05,09:04:00] vs70uimgr: Entering DisplayMessage() method.
[01/07/05,09:04:00] vs70uimgr: DisplayMessage_START:The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2350.
[01/07/05,09:04:01] vs70uimgr: DisplayMessage_END:The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2350.
[01/07/05,09:04:01] Setup.exe: AddGlobalCustomProperty
[01/07/05,09:04:01] Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English: ***ERRORLOG EVENT*** : ERROR:The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2350.
[01/07/05,09:04:02] Setup.exe: AddGlobalCustomProperty
[01/07/05,09:04:02] Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English: ***ERRORLOG EVENT*** : ACTION FAILURE:Action ended 09:04:02: InstallFinalize. Return value 3.See MSI log for details.
[01/07/05,09:09:26] Setup.exe: AddGlobalCustomProperty
[01/07/05,09:09:26] Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English: ***ERRORLOG EVENT*** : ACTION FAILURE:Action ended 09:09:26: INSTALL. Return value 3.See MSI log for details.
[01/07/05,09:09:36] Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English: CRootComponent::Install(): Finished MSI Installation
[01/07/05,09:09:36] Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English: MsiInstallProduct return code: 1603.
[01/07/05,09:09:36] InstallReturnValue: root_comp, 0x643
[01/07/05,09:09:36] Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English: CRootComponent::Install(): Setup Failed; MSIInstallProduct return value either ERROR_INSTALL_FAILURE or default.
[01/07/05,09:09:36] Setup.exe: AddGlobalCustomProperty
[01/07/05,09:09:36] Setup.exe: AddGlobalCustomProperty
[01/07/05,09:09:36] Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English: CRootComponent::Install(): Calling LaunchWatson()…
[01/07/05,09:09:37] Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English: CRootComponent::LaunchWatson() – Obtained CSetupWatson instance
[01/07/05,09:09:37] Setup.exe: GetGlobalCustomProperty({B8A13F14-4BDE-4EC4-A53C-8E51FBB8261F})
[01/07/05,09:09:37] Setup.exe: GetGlobalCustomProperty({4F8791EE-486F-44B5-952B-F28F9FD58BD0})
[01/07/05,09:09:37] Setup.exe: GetGlobalCustomProperty({710A502B-4669-405C-A985-BA21545509BA})
[01/07/05,09:09:37] Setup.exe: GetGlobalCustomProperty({710A502B-4669-405C-A985-BA21545509BA})
[01/07/05,09:09:37] Setup.exe: GetGlobalCustomProperty({AA62DF98-3F2C-11D3-887B-00C04F8ECDD6})
[01/07/05,09:09:37] Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English: CRootComponent::LaunchWatson() – Launching VS Watson
[01/07/05,09:10:34] Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English: CRootComponent::LaunchWatson() – Completed VS Watson launching to create manifest: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\vs_setup.dll.txt
[01/07/05,09:10:34] Setup.exe: GetGlobalCustomProperty({D530994B-CA3E-4CF3-AC2F-485962898182})
[01/07/05,09:10:34] Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English: CRootComponent::LaunchWatson() – Cleaning up the VS Manifest; some other Manifest is ready to be used.
[01/07/05,09:10:39] Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English: CRootComponent::Install(): Finished calling LaunchWatson()
[01/07/05,09:10:39] Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English: CRootComponent::Install(): Finished Brooklyn Component Installation
[01/07/05,09:10:39] Setup.exe: AddGlobalCustomProperty
[01/07/05,09:10:39] setup.exe: ***ERRORLOG EVENT*** : ISetupComponent::Pre/Post/Install() failed in ISetupManager::InstallManagerHelper() with HRESULT -2147023293.
[01/07/05,09:10:39] Setup.exe: AddGlobalCustomProperty[01/07/05,09:10:39] setup.exe: ***ERRORLOG EVENT*** : Component error string not specified in ISetupManager::AddToActionResultCollection()
 

If you look at the event log (you can see the entries being written above) and essentially it shows the same information. Here are the two entries there:

First Entry:

Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 11304
Date: 09/01/2005
Time: 12:08:26 AM
User: N/A
Computer: AMIT-D2E6YEDPFS
Description:
Product: Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English — Error 1304.Error writing to file: Microsoft.VisualStudio.Windows.Forms.dll. Verify that you have access to that directory.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 43 46 33 32 33 34 44 {CF3234D
0008: 30 2d 38 36 35 30 2d 34 0-8650-4
0010: 45 33 37 2d 41 34 42 45 E37-A4BE
0018: 2d 33 44 35 38 32 32 36 -3D58226
0020: 39 42 45 41 34 7d 9BEA4}

Second Entry:

Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 10005
Date: 09/01/2005
Time: 12:08:28 AM
User: N/A
Computer: AMIT-D2E6YEDPFS
Description:
Product: Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English — The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2350. The arguments are: , ,

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 43 46 33 32 33 34 44 {CF3234D
0008: 30 2d 38 36 35 30 2d 34 0-8650-4
0010: 45 33 37 2d 41 34 42 45 E37-A4BE
0018: 2d 33 44 35 38 32 32 36 -3D58226
0020: 39 42 45 41 34 7d 9BEA4}

Microsoft has a KB that talks about troubleshooting Visual Studio.NET installation, but that really not helpful in this context.

So, has anyone else seen it? Having talked to some of my buddies, it seems like they did not have an issue. I thought the extract of the ISO could be corrupt, so I extracted it again (though I did not download the 3.15 gb again) and I cannot think what the issue might be.

Published by

Amit Bahree

This blog is my personal blog and while it does reflect my experiences in my professional life, this is just my thoughts. Most of the entries are technical though sometimes they can vary from the wacky to even political – however that is quite rare. Quite often, I have been asked what’s up with the “gibberish” and the funny title of the blog? Some people even going the extra step to say that, this is a virus that infected their system (ahem) well. [:D] It actually is quite simple, and if you have still not figured out then check out this link – whats in a name?

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.