How to troubleshoot Visual Studio .NET installation

View products that this article applies to.

This article was previously published under Q319714

For a Microsoft Visual Studio 2005 version of this article, see 904732 (http://support.microsoft.com/kb/904732/ ) .

SUMMARY

This step-by-step article describes best practices for troubleshooting Visual Studio .NET installation and, if you experience problems during the installation, describes general steps for how to locate log files. More specific errors and problem are addressed in other Microsoft Knowledge Base (KB) articles.

Most installations of Microsoft Visual Studio .NET products occur as expected. The Microsoft Windows Installer is used to install these products. This is the same installation engine that you will use to deploy applications that you have developed in Visual Studio .NET.

Because of this, the installation should go smoothly, create the required log files, be self healing if damaged (resiliency), and perform complete rollbacks if potential problems are detected.

Best practices steps can prevent many problems. Consider using best practice installation methods for all installation, including service packs (SPs).

Back to the top

MORE INFORMATION

Steps to best practice installation methods

Best practice installation methods

Best practice installation methods for computers that are running Windows NT (including Windows NT 4.0, Windows 2000, and Windows XP) have the following three criteria:

Use the Local Administrator account.
This prevents both permissions issues and rights issues. The Local Administrator account is the maintenance account. Use this account when you install and remove programs.
Stop all required services and programs.
Many programs, particularly antivirus and other monitoring programs, interrupt the installation process.
Clear the System\Temp folder.
The installation wizards use the System\Temp folder heavily. If the installation leaves corrupted files or folder there, the installation re-applies the corrupted versions instead of going to the installation source for fresh copies.

Use the Local Administrator account

By default the Local Administrator is named Administrator. However, you can rename this account for security reasons. To view the name and to change the password, follow these steps:

Right-click My Computer. (On a computer running Windows NT 4.0, use the User Manager instead of these steps. Domain Controllers do not have access to Local Users and Groups.)
Click Manage.
Expand Local Users and Groups.
Click Users.
In the Details pane, locate the Administrator account. Typically, this account is named Administrator, and the description is Built-in account for administering this computer/domain.
To change the password, right-click the account, and then follow the on-screen instructions.

Stop all required services and programs

To stop the services and the programs, follow the steps for your operating system:

Windows NT 4.0:
1. Click Start, point to Programs, click Administrative Tools, and then click Services.
2. Stop all non-Microsoft services, including services for antivirus programs and other monitoring programs.
Windows 2000:
1. Click Start, point to Settings, click Control Panel, double-click Administrative Tools, and then double-click Services.
2. Stop all non-Microsoft services, including services for antivirus programs and other monitoring programs.
Windows XP:

Windows XP has a utility that is named MSConfig that prevents services and programs from starting for the installation session. For more information about how to run this utility, click the following article number to view the article in the Microsoft Knowledge Base:
310353 (http://support.microsoft.com/kb/310353/ ) How to perform a clean boot in Windows XP

Delete the contents of the System\Temp folder

Click Start, click Run, type %temp%, and then click OK. This command opens the System\Temp folder.
Delete the contents of this folder. If any contents are important (should not be deleted), move these items to another folder.

Back to the top

Installation

Windows Component Upgrade (WCU) in Visual Studio .NET 2002 or Visual Studio .NET Prerequisites in Visual Studio .NET 2003, gives the prerequisites for the Visual Studio .NET products. Depending on your operating system, different components are installed and the installation process requires a different number of restarts.

The destination computer should never have had any Beta or Release Candidate Visual Studio .NET product installed on it. If these product have been installed, it is a good idea to rebuild the computer (reformat the hard disk, and then install the operating system again) to verify that these products have been removed completely.

The executable file for Visual Studio .NET is named Setup.exe. This file is located in the root folder of Disk 1 of the CD-ROM or DVD-ROM installation media. This file appears in the installation dialog box. You must click 1 (the first selection, which is the WCU or Prerequisites) before you can click 2 to install Visual Studio .NET.

Setup prompts you for the WCU or Prerequisites disk, and then returns to the numbered installation media. For more information about WCU, see the "References" section of this article.

By default, verbose logging is turned on for the Visual Studio .NET installation. The log file is named VSMsiLog*.txt (* represents four alphanumeric characters in the file name, for example, VSMSILogA1d1.txt). The file is approximately 40 megabytes (MB).

Back to the top

Component files and logs

The following table lists each component, its location on the installation media, and the log file that is generated. Many of these log files are placed in the System\Temp folder, and then moved to the \Program Files\Microsoft Visual Studio .NET\Visual Studio .NET(Edition Name)\Logs folder when the installation is completed.

Microsoft Visual Studio .NET 2002

Collapse this tableExpand this table

Component	Location on WCU CD-ROM	Log or logs generated
Windows NT 4.0 Service Pack 6a	NTSP6a\sp6i386.exe
Windows 2000 Service Pack 2	Win2kSP2\W2KSP2.exe	Appended to `Windows Directory`\Setuplog.txt (errors in Setuperrorlog.txt)
Microsoft Windows Installer 2.0 (for Windows 98)	WindowsInstaller\2.0\InstMsiA.exe	Create log by using "Msiexec -I `.msi Path`:\.msi /lv `Output Path`:\log.txt" (after you extract the .msi file from the .exe file)
Microsoft Windows Installer 2.0 (for Windows 2000 and Windows NT)	WindowsInstaller\2.0\InstMsiW.exe	Create log by using "Msiexec -I `.msi Path`:\.msi /lv `Output Path`:\log.txt" (after you extract the .msi file from the .exe file)
Microsoft Windows Management Instrumentation	WMI\Wmicore.exe
Microsoft FrontPage 2000 Web Extensions Client	Weccom.msi	Documents and Settings\`UserName`\Local Settings\Temp\MSI*.log (using verbose logging)
Microsoft FrontPage 2000 Server Extensions Service Release 1.2	FrontPageServer\Fpse2k.exe	Documents and Settings\`UserName`\Local Settings\Temp\MSI*.log
Setup Runtime Files	Bootstrap.msi	Documents and Settings\`UserName`\Local Settings\Temp\MSI*.log
Microsoft Internet Explorer 6	IE60\Ie6setup.exe	`Windows Directory`\Active Setup Log.txt
Microsoft Data Access Components 2.7	MDAC27\Mdac_typ.exe	`Windows Directory`\Dasetup.log
Microsoft Jet 4.0 Service Pack 3	Jet\Jetsetup.exe	Documents and Settings\`UserName`\Local Settings\Temp\dotNetfx.log; Netfx.log
Microsoft .NET Framework	dotNetFramework\dotnetfx.exe	Documents and Settings\`UserName`\Local Settings\Temp\dotNetfx.log and netfx.log
Visual Studio .NET	Setup\Vs70uimgr.exe	Documents and Settings\`UserName`\Local Settings\Temp
Windows Component Update		Documents and Settings\`UserName`\Local Settings\Temp\Baseventlog.txt; Baserrorlog.txt; DepCheckData.txt

Microsoft Visual Studio .NET 2003

Collapse this tableExpand this table

Component	Location on WCU CD-ROM	Log or logs generated
Windows NT 4.0 Service Pack 6a	NTSP6a\sp6i386.exe
Microsoft Windows Installer 2.0 (for Windows 98)	WindowsInstaller\2.0\InstMsiA.exe	Create log by using "Msiexec -I `.msi Path`:\.msi /lv `Output Path`:\log.txt" (after you extract the .msi file from the .exe file)
Microsoft Windows Installer 2.0 (for Windows 2000 and Windows NT)	WindowsInstaller\2.0\InstMsiW.exe	Create log by using "Msiexec -I `.msi Path`:\.msi /lv `Output Path`:\log.txt" (after you extract the .msi file from the .exe file)
Microsoft FrontPage 2000 Web Extensions Client	Weccom.msi	Documents and Settings\`UserName`\Local Settings\Temp\MSI*.log (using verbose logging)
Setup Runtime Files	Bootstrap.msi	Documents and Settings\`UserName`\Local Settings\Temp\MSI*.log
Microsoft Internet Explorer 6	IE60\Ie6setup.exe	`Windows Directory`\Active Setup Log.txt
Microsoft Data Access Components 2.7	MDAC27\Mdac_typ.exe	`Windows Directory`\Dasetup.log
Microsoft .NET Framework	dotNetFramework\dotnetfx.exe	Documents and Settings\`UserName`\Local Settings\Temp\dotNetfx.log and netfx.log
Windows Component Update		Documents and Settings\`UserName`\Local Settings\Temp\wcuerror71.txt; wcuevent71.txt; DepCheck71.txt

You can prevent many corrupted file issues and media reading issues by doing a flat install. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

322950 (http://support.microsoft.com/kb/322950/ ) Error messages when you cancel setup of Visual Studio .NET or the MSDN Library

Back to the top

REFERENCES

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

888470 (http://support.microsoft.com/kb/888470/ ) Another installation program starts when you try to install Visual FoxPro, Visual Studio .NET, or prerequisites

For more information, visit the following Microsoft Web site, click Visual Studio .NET (2002) or Visual Studio .NET (2003) in the list of Microsoft products, and then click Go :

Advanced Search and Help

http://support.microsoft.com/gp/gsssearchhelp (http://support.microsoft.com/gp/gsssearchhelp)

For more information about Visual Studio .NET and installation, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=gp;en-us;vssetup (http://support.microsoft.com/default.aspx?scid=gp;en-us;vssetup)

Back to the top