Welcome to MSDN Blogs Sign in | Join | Help

Visual Studio and .NET Log Collection Utility

Setup and deployment is a tricky business. Machines can be in many different and often unforeseen states that cause setup to fail. But rarely will setup actually crash, and that is why setup logs are vital to diagnose install, repair, and uninstall problems.

Setup applications for Visual Studio and .NET may write to many different logs because the products are actually comprised of many different packages. Aaron Stebner had documented several log file names for Visual Studio 2008, but with our new and improved patch wrapper we may write even more log files. As we onboard new CTPs for great new features in Visual Studio the list of log files may also grow.

So our QA team has written a tool to collect all these logs for VS 2005 and 2008, and .NET 2.0 through 3.5 aptly named, collect.exe. The link below is an updated version of the old collect.exe that you should use when reporting bugs with setup.

Using the Collect Utility

If you encounter any setup issues, we will need all relevant logs. Please follow the instructions below to collect all those logs.

  1. Download collect.exe from the link  below.
  2. You may choose to save the tool for later use, or to run directly.
  3. The utility creates a compressed cabinet of all the VS and .NET logs to %TEMP%\vslogs.cab.

Reporting Setup Errors

There are several options for reporting setup errors, but you might consider first checking to see if the issue is a known issue. This will save you time and provide more immediate results. In most scenarios, there will be a link on the error page after setup completes. Clicking on this should provide a smaller log that highlights the errors encountered. To dig deeper, check out some of the tips provided on Aaron's blog and on my blog.

If you would like to report an error, be sure to collect logs as described above and choose from the options below.

  1. Search or post on MSDN Forums in .NET Framework Setup or Visual Studio Setup and Installation. This is a community-driven web site on which Microsoft employees also participate.
  2. Report installation issues or provide feedback for Visual Studio on Microsoft Connect. You may upload logs using Connect. This allows us to view and manage bugs, and customers to vote or provide additional details in a consistent manner.
  3. Upload logs using Windows Error Reporting. Both the MSDN Forums and Microsoft Connect will most often provide faster help.
Published Friday, May 09, 2008 9:41 PM by Heath Stewart
Attachment(s): Collect.exe

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

Monday, May 12, 2008 12:09 PM by Your Websites, Our Passion!

# Error installing Visual Studio 2008 SP1 Beta and Silverlight Tools Beta 1

Summary Microsoft Silverlight Tools Beta 1 for Visual Studio 2008 is not compatible with Visual Studio

Monday, May 12, 2008 9:44 PM by Developer Community Product Feedback

# Visual Studio SP1 Beta Feedback

Visual Studio SP1 beta is available for Download, it includes hundreds of bug fixes and customer-reported

Tuesday, May 13, 2008 12:28 PM by Small place on earth

# Visual Studio 2008 Service Pack 1 Beta a fost facut public.

Ieri dimineata a fost facut public VS 2008 SP1 Beta 1. Mai multe informatii despre ce contine SP1 se

Tuesday, May 13, 2008 3:19 PM by bharry's WebLog

# VS/VSTS/TFS 2008 SP1 Beta is now available

Sorry for being a bit late to the game...  I should have posted yesterday but I've been drowning. 

Wednesday, May 14, 2008 9:08 PM by Heath Stewart's Blog

# The Release of Visual Studio 2008 SP1 will Install over SP1 Beta

One of many improvements made to Visual Studio 2008 Service Pack 1 is that VS 2008 SP1 Beta customers

Wednesday, June 25, 2008 8:22 AM by Arne Garvander

# re: Visual Studio and .NET Log Collection Utility

That tool is difficult to use under Vista as common user. The output directory blinks on the screen for 1 second and it goes away. The output is not saved under %temp% but under the admin sccount.

Wednesday, July 02, 2008 1:46 PM by Heath Stewart

# re: Visual Studio and .NET Log Collection Utility

Arne, because our setup requires admin privileges the collection log must collect those logs (for the admin user); so, credentials (or acceptance of the UAC if you're already an admin) are required to collect admin logs and the CAB is placed in %TEMP% - which is now the admin's %TEMP% (as designed).

Friday, July 04, 2008 1:37 AM by bharry's WebLog

# VS/VSTS/TFS 2008 SP1 Beta の公開を開始

少し遅れてしまい申し訳ありません。昨日のうちに投稿するはずだったのですが、ゲームにはまってしまいまして...。既にご存知かと思いますが、2008 SP1 Beta をリリースしました。ぜひお試しいただき、フィードバックをお寄せくださいますようよろしくお願いいたします。TFS

Tuesday, July 08, 2008 9:10 PM by ディベロッパー製品開発統括部 Blog

# セットアップログ収集ツール

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

Leave a Comment

(required) 
required 
(required) 
 
Page view tracker