Tool to automatically collect and cab VS 2008 and .NET Framework 3.5 setup log files
I wrote a post yesterday with a list of the names and locations of all of the log files produced during Visual Studio 2008 and .NET Framework 3.5 setup. As you can see in that post, the list of possible log files is very long, and that makes it annoying when attempting to gather the logs and send them back to Microsoft so that we can help troubleshoot installation issues.
Fortunately, Sandhya, a colleague of mine, has written a tool that will automatically gather all of the VS 2008 and .NET Framework 3.5 setup log files it can find from your system and create a cab file containing them so you have a single compressed package that can be sent to Microsoft for troubleshooting purposes.
How to use the Collect tool
The tool can be downloaded from https://go.microsoft.com/?LinkId=8967043. It is a Win32 console application, so you can extract it from the zip file and double-click on it to run it. It will create a file named %temp%\vslogs.cab on your system after it has gathered all of the log files.
Note - after the tool finishes running, you can get to your %temp% folder to find the file vslogs.cab by clicking on the Start menu, choosing Run, typing %temp% and clicking OK.
What to do if the Collect tool does not work correctly on your system
If the tool encounters any problems, you can do the following to re-run it from a cmd prompt and see more detailed error information:
- Click on the Start menu, choose Run, type cmd and click OK
- Run collect.exe from the cmd prompt that appears
- When doing this, you will see information displayed in the cmd prompt with more details about which actions it is performing, what log files it found, etc
<update date="5/23/2008"> Updated link to log collection tool to point to the new location </update>
Comments
Anonymous
August 01, 2007
Tool to collect VS2008 and Fx 3.5 setup logsAnonymous
August 07, 2007
To collect the logs please follow the steps found on aaronste’s blog: Tool to automatically collect andAnonymous
August 20, 2007
My team owns the installation experience for Visual Studio 2008 and the .NET Framework 3.5. One difficultyAnonymous
August 20, 2007
PingBack from http://msdnrss.thecoderblogs.com/2007/08/20/how-to-report-an-installation-or-setup-problem-with-vs2008-beta-or-net-framework-35-beta/Anonymous
August 27, 2007
I just noticed this post on Bret Grinslade's blog that I wanted to link to here to help raise visibility.Anonymous
August 27, 2007
I just noticed this post on Bret Grinslade's blog that I wanted to link to here to help raise visibilityAnonymous
August 27, 2007
PingBack from http://testsubdomain.netmoviehost.com/report-vs-2008-or-net-framework-35-beta-installation-issues/Anonymous
August 27, 2007
PingBack from http://msdnrss.thecoderblogs.com/2007/08/28/report-vs-2008-or-net-framework-35-beta-installation-issues-directly-to-the-setup-team/Anonymous
November 21, 2007
I previously wrote about a log collection tool that will automatically gather and cab up Visual StudioAnonymous
November 21, 2007
I previously wrote about a log collection tool that will automatically gather and cab up Visual StudioAnonymous
December 04, 2007
We've been seeing some issues where VS 2008 crashes when creating a new WPF project. The underlying issueAnonymous
December 04, 2007
PingBack from http://msdnrss.thecoderblogs.com/2007/12/04/visual-studio-2008-rtm-crashing-when-creating-a-wpf-project/Anonymous
December 04, 2007
We've been seeing some issues where VS 2008 crashes when creating a new WPF project. The underlying issueAnonymous
December 10, 2007
Step 1. Follow Aaron Stebner's blog: http://blogs.msdn.com/astebner/archive/2007/08/01/4172276.aspx StepAnonymous
December 10, 2007
Step 1. Follow Aaron Stebner's blog: http://blogs.msdn.com/astebner/archive/2007/08/01/4172276.aspxAnonymous
December 10, 2007
.style1 { font-size: small; } .style2 { font-size: medium; color: #365F91; } .style3 { color: #365F91;Anonymous
May 09, 2008
Setup and deployment is a tricky business. Machines can be in many different and often unforeseen statesAnonymous
May 20, 2008
PingBack from http://www.ie16.com/debugging-net-framework-errors/Anonymous
May 20, 2008
PingBack from http://www.ie16.com/re-debugging-net-framework-errors/Anonymous
May 23, 2008
Recently, beta versions of Visual Studio 2008 SP1 and the .NET Framework 3.5 SP1 were released (see announcementAnonymous
September 09, 2008
The comment has been removedAnonymous
January 18, 2009
PingBack from http://www.keyongtech.com/2403113-problem-installing-visual-studio-2008-aAnonymous
May 06, 2012
i been getting errors everyday and not knowing how to fix it. this is outrageousAnonymous
May 06, 2012
Please Help me fix thisAnonymous
May 06, 2012
Hi Jennifer Victoria and Daniel Moth - Can you please provide more details about what types of errors you're seeing so I can try to help?Anonymous
June 12, 2012
My PC is giving some issue of getting NETframework 4.0.330319. what is that all aboutAnonymous
June 12, 2012
The comment has been removedAnonymous
August 05, 2012
The comment has been removedAnonymous
August 05, 2012
Hi Amit - This type of error is usually caused by a corrupt download. I'd suggest trying to re-download the Visual Studio installer that you're using in this scenario to see if that helps resolve this error.Anonymous
December 19, 2012
The comment has been removedAnonymous
December 20, 2012
Hi Prasanta - Can you please use the tool described at blogs.msdn.com/.../6458047.aspx to collect all of your setup log files, upload the file named %temp%vslogs.cab that this tool will create to a file server (such as http://skydrive.live.com), and then reply back here and provide a link that I can use to download your log files and take a closer look?