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>

 

  • A while back, I posted a set of instructions that can be used to try to resolve .NET Framework installation

  • A while back, I posted a set of instructions that can be used to try to resolve .NET Framework installation

  • Events Visual Studio Team System Chat: April 9 on Charles Sterling&#39;s blog Resources Team System Community

  • I often get questions from fellow employees or customers who find my blog regarding how to troubleshoot

  • Hi, Aaron

    I have the same problem with vs_bsln.exe as Thylocene while trying to install the german VS 2008 prof. trial on a german Vista Ultimate 64-bit. Is there now a separate download location for that file ?

    Thanks

  • Hi GFries - No, there is not a separate download for this file.  In many of the cases I've heard from customers in the past of this problem, even after they manually replaced the file vs_bsln.exe with a copy from somewhere else, they often ran into other corrupted setup files later in the installation process.

    I have been suggesting that customers try one of the following to fix this type of corruption if they run into it:

    1.  Try burning the ISO to a DVD and installing from there instead of mounting it and installing from the mounted copy

    2.  Try a different mounting software if it isn't an option to burn the ISO to a DVD

    3.  Try to re-download the ISO

    Hopefully one of the above will help.

  • A while back, I posted a list of possible log files for .NET Framework 3.5 and Visual Studio 2008 setup

  • Setup and deployment is a tricky business. Machines can be in many different and often unforeseen states

  • Recently, beta versions of Visual Studio 2008 SP1 and the .NET Framework 3.5 SP1 were released (see announcement

  • Visual Studio (以下 VS ) 製品のインストールで生成されるセットアップログファイルを収集するツールを紹介したいと思います。 VS 製品のセットアップは .NET Framework ランタイムを始め複数のコンポーネントをインストールするため、

  • Hello,

    I'm currently integrating .NET 3.5 SP1 installation into our SW distribution.

    After reading many blog entries I created an installation point and I am now installing using the "setup.exe /q /norestart /lang:" method.

    My problem is that all logfiles are written as described in this article. It seems that there is no way to use the chaining installer AND to get the logfiles in a different location.

    I also tried to change the TEMP variable (USER and SYSTEM) before starting setup.exe but it still writes to the User TEMP.

    Is there any (undocumented) way to change the location of the logfiles?

    Thanks

    Michael

  • Hi Steiger - The .NET Framework setup should be using the GetTempPath API to retrieve the location that is used to create the log files.  It should work to change those environment variables to change the folder that the logs are created, but you may need to reboot for the environment variable changes to take effect.

    There isn't a way to change the name/location of these log files if you are installing using the setup EXE like you describe.  If you need the logs to go to a different location for some reason, the only way I know of would be to run each of the individual MSIs directly with msiexec.exe and pass in the logging switch when doing that.

    I'd be curious to know what kind of scenarios you are running where you need to control these log file names/locations though.  Can you explain that a bit better?  Also, if this is an important scenario to you, I encourage you to report this as a bug at http://connect.microsoft.com/visualstudio/ for the team to consider this in the next version of .NET Framework setup.

  • こんにちは、フォーラム オペレータの服部です。 僕は、MSDN フォーラムの英語版 FAQ コンテンツの翻訳を担当しているんですが、原文の翻訳だけではなかなか不十分なところがあります。 というのも、紹介されているリンク先の情報がすべて英語になってしまうためです。

  • 再びこんにちは! 今日は僕の頭の中で動いている CPU の調子がすこぶる快調なので、英語スレッドの日本語版をもう 1 つ紹介してみようと思います。 これは、米国マイクロソフト社に勤務する Heath Stewart

  • PingBack from http://justindevine.wordpress.com/2008/11/30/visual-studio-2008-sp1-installation-errors-and-error-code-1603/

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