Aaron Stebner's WebLog

Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio

Visual Studio 2008 and .NET Framework 3.5 setup log files

Visual Studio 2008 and .NET Framework 3.5 setup log files

Rate This
  • Comments 66

The installers for the .NET Framework 3.5 and Visual Studio 2008 chain several different prerequisites and optional components behind the scenes.  If one of these setups fails, there are numerous possible causes due to the number of packages being chained behind the scenes.  The following provides a list of log files created by the setup wrappers for each product and the child packages that are chained in during installation. 

.NET Framework 3.5 setup log files

The following is a complete list of log files that can be produced during .NET Framework 3.5 setup.  This list may vary depending on what OS you are installing on, what processor architecture, and what prerequisite components were already installed on the system prior to running .NET Framework 3.5 setup.

Logs produced by the .NET Framework 3.5 setup wrapper:

  • %temp%\dd_dotnetfx35install.txt
  • %temp%\dd_dotnetfx35error.txt
  • %temp%\dd_depcheck_netfx*.txt

Logs produced by the packages chained during .NET Framework 3.5 setup:

  • RGB Rasterizer - %temp%\dd_RGB9Rast_*.txt
  • MSXML 6.0 - %temp%\dd_msxml6_*.txt
  • WIC - %temp%\dd_wic*.txt
  • .NET Framework 2.0 SP1 - %temp%\dd_net_framework20*.txt
  • .NET Framework 3.0 SP1 - %temp%\dd_net_framework30*.txt
  • .NET Framework 3.0 SP1 WCF custom action - %temp%\dd_wcf_retCA*.txt
  • .NET Framework 3.5 product MSI - %temp%\dd_net_framework35*.txt

Visual Studio 2008 setup log files

The following is a complete list of log files that can be produced during Visual Studio 2008 setup.  This list may vary depending on what OS you are installing on, what processor architecture, and what prerequisite components were already installed on the system prior to running Visual Studio 2008 setup.

In addition to the logs listed below, Visual Studio 2008 setup can produce the logs listed above for the .NET Framework 3.5 because the .NET Framework 3.5 is a prerequisite that is chained in during Visual Studio 2008 setup if it is not already installed on the system.

Logs produced by the Visual Studio 2008 setup wrapper:

  • %temp%\dd_install*.txt
  • %temp%\dd_error*.txt
  • %temp%\dd_depcheck*.txt
  • VSMsiLog*.txt - located in your %temp% directory during Visual Studio 2008 setup; moved to %ProgramFiles%\Microsoft Visual Studio 9.0\<product name>\Logs after a successful installation; left in %temp% after a failed installation and after uninstallation

Logs produced by the packages chained during Visual Studio 2008 setup:

  • Windows Installer 3.1 - %windir%\KB893803v2.log
  • .NET Framework 3.5 - see the full list of logs at the top of this post
  • Visual Studio 2008 64bit Prerequisites - %temp%\dd_prereq*.txt
  • Document Explorer 2008 - %temp%\dd_dexplore*90*.txt
  • Web Designer Tools - %temp%\SetupExe(*).txt
  • .NET Compact Framework 2.0 SP2 - %temp%\dd_netcfsetupv2*.txt
  • .NET Compact Framework 3.5 - %temp%\dd_netcfsetupv35*.txt
  • Visual Studio Tools for Office Runtime 3.0 - %temp%\dd_vstor*.txt
  • Visual Studio 2005 Tools for the 2007 Microsoft Office System Runtime - %temp%\dd_vsto_ret20*.txt
  • SQL Server Compact Edition 3.5 - %temp%\dd_SSCERuntime*.txt
  • SQL Server Compact Edition 3.5 Design Tools - %temp%\dd_SQLCEToolsForVS2007*.txt
  • SQL Server Compact Edition 3.5 For Devices - %temp%\dd_SSCEDeviceRuntime*.txt
  • Windows Mobile 5.0 SDK R2 for Pocket PC - %temp%\dd_WMPPC_5_0*.txt
  • Windows Mobile 5.0 SDK R2 for Smartphone - %temp%\dd_WMSP_5_0*.txt
  • Device Emulator version 3.0 - %temp%\dd_64bitEmulator*.txt, %temp%\dd_EmulatorForWinXP*.txt and/or %temp%\dd_Emulator*.txt
  • SQL Server 2005 Express Edition - %programfiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\*.*
  • Visual Studio 2008 Remote Debugger - %temp%\dd_rdbg*.txt
  • Windows SDK - %temp%\dd_winsdk*.txt
  • Visual Studio Performance Collection Tools - %temp%\dd_Performance_Collection_Tools*.txt
  • Crystal Reports - %temp%\dd_CrystalReports2007*.txt

Logs produced by the packages chained during Visual Studio 2008 Express Edition setups:

  • Windows Installer 3.1 - %windir%\KB893803v2.log
  • .NET Framework 3.5 - see the full list of logs at the top of this post
  • SQL Server Compact Edition 3.5 - %temp%\dd_SSCERuntime*.txt
  • SQL Server Compact Edition 3.5 Design Tools - %temp%\dd_SQLCEToolsForVS2007*.txt
  • Visual Studio 2008 Remote Debugger Light - %temp%\dd_ExpRemoteDbg*.txt
  • Windows SDK - %temp%\dd_winsdk*.txt
  • MSDN for Visual Studio Express Editions - %temp%\dd_MSDNExp*.txt
  • Silverlight 1.0 - %temp%\Silverlight*.txt

Logs produced by the MSDN for Visual Studio 2008 setup wrapper:

  • %temp%\dd_install_MSDN_VS_90*.txt
  • %temp%\dd_error_MSDN_VS_90*.txt
  • %temp%\dd_depcheck_MSDN_VS_90*.txt
  • VSMsiLog*.txt - located in your %temp% directory during MSDN setup; moved to %ProgramFiles%\MSDN\MSDN9.0\<product name>\Logs after a successful installation; left in %temp% after a failed installation and after uninstallation

Logs produced by Visual Studio 2008 SP1:

  • %temp%\Microsoft Visual Studio 2008 SP1*.* 

If you run into any issues while installing the .NET Framework 3.5, Visual Studio 2008 or MSDN for Visual Studio 2008 and plan to report setup issues to Microsoft via the product feedback site or the MSDN Forums, please locate and include any of the above log files if possible because it will make it easier for us to debug the failures and find root causes and workarounds.

<update date="10/4/2007"> Added a log file to the .NET Framework 3.5 list for the WCF custom action that I missed previously </update>

<update date="1/11/2008"> Added Silverlight log files to the list for VS 2008 Express Editions since it was added as a chained component between the time I wrote this blog post and the time that VS 2008 shipped. </update>

<update date="5/23/2008"> Added log file information for Visual Studio 2008 SP1 </update>

<update date="11/20/2009"> Fixed broken link to the product feedback site. </update>

 

  • Hi HeroicLife - We found a really strange issue where all self-extracting packages on HCM's system reported that they were not valid applications.  We were not able to reproduce this in our test lab, but HCM was able to re-download a different Visual Studio edition and it installed like expected.  Based on that, we think there may have been something wrong with the downloaded package.  Can you please try to download a new image of VS 2008 beta 2 and then install again and see if that helps?  If not, please contact me at http://blogs.msdn.com/astebner/contact.aspx and I will try to help further.

  • I previously wrote about a log collection tool that will automatically gather and cab up Visual Studio

  • I previously wrote about a log collection tool that will automatically gather and cab up Visual Studio

  • Details about the .NET Framework 2.0 setup packaging Available command line switches for .NET Framework

  • Aaron, why have you guys made our life awfull with vs 2008?

    I just wanted C++ and that is what I selected in custom install and I got all this junk bundled with the VS2008 itself:

    Microsoft .NET Framework 2.0 Service Pack 1 365.00 MB

    Microsoft .NET Framework 3.0 Service Pack 1 313.00 MB

    Microsoft .NET Framework 3.5  28.54 MB

    Microsoft Document Explorer 2008  26.27 MB

    Microsoft Visual Studio Web Authoring Componenet  25.00 MB

    Microsoft Windows SDK for Visual Studio 2008 Headers and Libraries 114.00 MB

    Microsoft Windows SDK for Visual Studio 2008 Reference Assemblies and IntelliSense   6.65 MB

    Microsoft Windows SDK for Visual Studio 2008 Tools  15.56 MB

    Microsoft Windows SDK for Visual Studio 2008 Win32 Tools  18.58 MB

    On top of that, there is no platform sdk, except for (gasp!!!) IA64?!? Come on guys, you got to be kidding?!? Where are x64 and x86 import libraries?

    What's with all this useless junk I literally got stuffed with instead of the ability for writing x86 and x64 Windows applications out of the box?

    Luckily I had a chance to try it and I uninstalled it because if I bought it and got stuffed like this I would be seriously pissed off. You really lost your edge when it comes to developer tools.

  • I often receive emails and blog comments from customers who are having trouble installing the .NET Framework

  • I often receive emails and blog comments from customers who are having trouble installing the .NET Framework

  • Hi Aaron

    I have been trying to install VS 2008 team Suite for a couple of days now and it is beginning to drive me around the twist.  I had VS 2005 which I have removed.

    The install gets to finish Dot.Net 3.5 and then fails at installing 64-bit prerequisites

    [01/27/08,09:51:22] Microsoft Visual Studio 2008 64bit Prerequisites (x64): [2] f:\setup\..\wcu\64bitprereq\x64\vs_bsln.exe could not be unpackaged because it is not a cabinet.

    [01/27/08,09:51:22] setup.exe: [2] ISetupComponent::Pre/Post/Install() failed in ISetupManager::InternalInstallManager() with HRESULT -2147467259.

    My PC is a Dell Precision Notebook (M90) with 4GB memory running Vista Business.  I have downloaded the VS2008 team suite ISO a couple of times to make sure that I did not have a corrupt download.  What am I doing wrong.  This should be a relatively straight forward simple process?

  • Hi Thylocene - Typically, this type of error means that the package is corrupt somehow.  It could be that your ISO was corrupted while you downloaded or while you burned it.  I'd suggest trying to re-download the ISO once more and see if you get better results.  You could also try to copy the contents of the ISO to your hard drive and install from there instead of installing from a DVD.

    If this doesn't help, please contact me using the link at http://blogs.msdn.com/astebner/contact.aspx and I can try to help you further from there.

  • Hi Aaron - Thanks for replying.  I have downloaded the ISO twice already.  I have managed to install vs2008 on XP but not Vista business.  What I did to get it installed was to extract all the contents of the ISO using UltraISO (which does not care if files are corrupt within the ISO) and then burn a new copy.  I found that the file \Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\VSTOR30\en\eula.txt was corrupt.  It extracted full of nulls!!!!

    I have tried all sorts of combinations to try to overcome the 64bit prerequisites error that I am experiencing.  At the moment I am down-loading the trial version in the hope that I may be able to get this installed on Vista Business and then maybe I will be able to upgrade it.

  • Hi Thylocene - I'm not sure how to explain that type of media corruption.  I tried to find a separate download location for the 64-bit prerequisite package for you to try, but it looks like that package isn't available separately.  If you don't have any luck with the most recent download you're trying, please contact me via http://blogs.msdn.com/astebner/contact.aspx and I can try to post a version of the 64-bit prerequisites package privately for you to try to see if you can get past that error and see if there will be any other installation problems hiding behind that.

  • Hi Aaron

    Good news.  I managed to get VS2008 installed with your help i.e. running the  64-bit prerequisites package that you had send me allowed me to get past the sticking point and complete the installation.

    I did a binary compare of the file that you sent me with the one on the ISO image (in the \WCU\64bitPrereq\x64 directory) and they were quite different.  I replaced this file with the one you send me, burned a new DVD and installed it on another system with Vista Business edition with no issues!

    Interestingly enough I had also downloaded the trial version of Team Suite which had exactly the same issue which leads me to believe that there is an problem with the original download ISO for X86 64-bit pre-requisites!

    Can this be looked at as it may save quite a bit of angst (an acute but unspecific feeling of anxiety; usually reserved for philosophical anxiety about the world or about personal freedom) for others with the same configuration as me.

    Thanks

  • Hi Thylocene - I’m glad to hear that the 64-bit prerequisites package (vs_bsln.exe) that I sent you allowed you to get past this issue and successfully install VS 2008.  I’ve sent this information on to the folks I know on the Visual Studio setup team to see if they can take a look at the ISOs that are currently posted for download.

  • http://blogs.msdn.com/astebner/archive/2007/07/31/4156781.aspx

  • A while back, I posted a list of instructions that can be used to enable Windows Installer verbose logging

Page 2 of 5 (66 items) 12345
Leave a Comment
  • Please add 8 and 2 and type the answer here:
  • Post