Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Diagnosing   (RSS)

Updated log collection utility available for Visual Studio 2010 and .NET 4.0 Beta 1

Last Monday we shipped Visual Studio 2010 Beta 1 and .NET Framework 4.0 Beta 1 to MSDN customers, and made them publicly available Wednesday. More information about Visual Studio 2010 and .NET Framework 4.0 are available on MSDN , and Aaron Stebner has

Microsoft VS/.NET Log Collection Tool

Use collect.exe to gather Visual Studio and .NET setup logs for help diagnosing installation and update issues.

VS 2008 SP1 fails to install because of missing packages from the cache

Some customers are reporting that Microsoft Visual Studio 2008 SP1 is failing to install with the following error in the HTML log you can view from the error dialog. Patch (C:\Users\heaths\AppData\Local\TEMP\WebDesignerCore_KB950278.msp) install failed

Enable BITS Logging

Enable BITS logging for diagnostic information about download failures using BITS.

BITS Logging

Scripts to enable and disable BITS logging.
Posted by Heath Stewart | 3 Comments
Filed under: ,

Attachment(s): BITSLogging.zip

Visual Studio and .NET Log Collection Utility

How to obtain and use the Visual Studio and .NET Framework log collection utility, and how to provide logs and feedback.

MSIZap is not Uninstall

The tool msizap.exe that is available in the Windows SDK and elsewhere on the web (remember to always download from a trusted source) is a powerful but dangerous tool that is often used to quickly and casually, and can leave your machine in a corrupted

Debugging Custom Actions: Leaked Handles

Debugging custom actions isn't exactly the easiest action to do; Windows Installer spawns separate processes - remoting servers - to run in-process custom actions. Any opportunity to diagnose issues without debugging can be helpful. For example, an issue

Rebuilding the Installer Cache

During some operations upgrades internally, a problem arose on some machines where a patch for the Microsoft .NET Framework 2.0 would fail to install. I was looped into the thread to diagnose the issue and found that the Windows Installer package and

Cumulative Service Packs with MinorUpdateTargetRTM

How to create cumulative service packs easily to apply with Windows Installer 3.1 and newer.

Determine Which Files are Being Patched

How to determine which files are being patched with a custom action.

Why is My Feature Advertised?

Removing a component even through obsolescence or supersedence will cause patched features to appear advertised instead of installed, which causes them to not be patched.

Error 2262: Not Necessarily a Fatal Error

How to determine the source of Windows Installer error 2262.

Diagnosing Installation Errors

How to diagnose errors when installing, repairing or patching, or uninstalling a product using Windows Installer technology.

Setup Troubleshooting Guide Applicable for Patches, Too

A link to Aaron Stebner's troubleshooting guide for Visual Studio 2005 and .NET Framework 2.0 setup (and patching).
More Posts Next page »
 
Page view tracker