Article ID: 908452
Article Last Modified on 12/3/2007
APPLIES TO
- Microsoft Visual Studio 2005 Professional Edition
- Microsoft Visual Studio 2005 Standard Edition
- Microsoft Visual Studio 2005 Team System Architect Edition
- Microsoft Visual Studio 2005 Team System Developer Edition
- Microsoft Visual Studio 2005 Team Foundation
- Microsoft Visual Studio 2005 Team System Test Edition
- Microsoft .NET Framework 2.0
For a Microsoft Visual Studio 2005 Express Edition version of this article, see 908451.
SUMMARY
This article contains the Microsoft Visual Studio 2005 Setup Issues Readme file.
MORE INFORMATION
This document lists issues that concern installation, uninstallation, repair, and other setup procedures.
For issues that are not setup related, please see http://msdn2.microsoft.com/en-us/vstudio/aa718685.aspx.
For the latest setup notes, see the online Visual Studio 2005 Readme at http://msdn2.microsoft.com/en-us/vstudio/aa718687.aspx.
1. All Visual Studio Products
1.1. System Requirements
| System Requirements for Installing Visual Studio 2005 | |
| Processor |
Minimum:
Recommended:
|
| Operating System |
Visual Studio 2005 can be installed on any of the following systems:
Installation of Visual Studio 2005 on the Intel Itanium (IA64) is not supported. |
| RAM1 |
Minimum:
Recommended:
|
| Hard Disk2 |
Without MSDN:
With MSDN:
or 2.8 GB of available space required on installation drive with a default MSDN install.
|
| CD or DVD Drive | Not required |
| Display |
Minimum:
Recommended:
|
| Mouse | Microsoft mouse or compatible pointing device |
Notes
1 Performance has not been tuned for minimum system configuration. Increasing your computer's RAM will improve its performance, especially when running multiple applications, working with large projects, or doing enterprise-level development.
For Visual Studio Tools for Office features, 256 megabytes of RAM is required. This requirement only applies to Microsoft Visual Studio 2005 Team Edition for Software Architects, Microsoft Visual Studio 2005 Team Edition for Software Developers, Microsoft Visual Studio 2005 Team Edition for Software Testers, and Microsoft Visual Studio 2005 Team Suite.
2 When you start the Visual Studio 2005 installer, the default installation location is your system drive, which is the drive that boots your system. However, you can install the application on any drive. Regardless of the application's location, the installation process installs some files on your system drive. Consequently, ensure that the above amount of space is available on your system drive regardless of the application's location, and ensure that additional space, as listed above, is available on the drive on which you install the application.
1.2. Uninstalling Previous Versions of Visual Studio 2005
If you have installed previous versions of Visual Studio 2005, such as Beta 2 or Community Technical Preview (CTP) builds of Visual Studio Team Suite, Visual Studio Standard or Visual Studio Professional, then you must uninstall in the exact order shown below before beginning to install any version of Visual Studio 2005:
- Go to the Control Panel and launch Add/Remove Programs
- Remove "Microsoft SQL Server 2005 Express Edition"
- Remove "Microsoft SQL Server 2005 Tools Express Edition"
- Remove "Microsoft SQL Native Client"
- Remove "Microsoft Visual Studio 64bit Prerequisites Beta" (This step is needed only if Visual Studio is installed on a 64-bit machine)
- Remove "Microsoft Visual Studio Tools for Office System 2005 Runtime Language Pack" (This step is not needed if you have only the English Edition)
- Remove "Microsoft Visual Studio Tools for Office System 2005 Runtime Beta"
- Remove "Microsoft Device Emulator 1.0 Beta"
- Remove "Microsoft .NET Compact Framework 2.0 Beta"
- Remove "Microsoft .NET Compact Framework 1.0"
- Remove "Microsoft Visual Studio 2005 Professional" or other related IDE installs such as (Visual Studio Professional/Standard/Enterprise Architect/Team Suite, etc.)
- Remove "Microsoft Document Explorer 2005 Language Pack" (This step is not needed if you have only the English Edition)
- Remove "Microsoft Document Explorer 2005" (This step is needed for post-Beta2 builds)
- Remove "Microsoft SQL Mobile 2005 Development Tools"
- Remove "Microsoft 64-bit SDK" (This step is only needed if Visual Studio is installed on a 64-bit machine)
- Remove "Microsoft Visual Studio 2005 Remote Debugger (x64)" (This step is needed only if Visual Studio is installed on a 64-bit machine)
- Remove "Microsoft MDAC 2.8 SP1" (This step is needed only if you are running Windows 2000)
- Remove "Microsoft MSXML 6 SDK and Parser"
- Remove "Microsoft Visual J# .NET Redistributable 2.0 Beta Language Pack" (This step is not needed if you have only the English Edition)
- Remove "Microsoft Visual J# Redistributable Package 2.0 Beta"
- Ensure all Visual Studio 2005 products have been removed from your system
- Remove "Microsoft .NET Framework 2.0 Beta Language pack" (This step is not needed if you have only the English Edition)
- Remove "Microsoft .NET Framework 2.0 Beta"
Notes:
- If you see an error removing J# .NET Redistributable Package 2.0 from Add/Remove Programs, please run "msiexec /x {9046F10C-F5E7-4871-BED9-8288F19C70DF}" from a command line window.
- If you see an error removing .NET Framework 2.0 from Add/Remove Programs, please run "msiexec /x {71F8EFBF-09AF-418D-91F1-52707CDFA274}" from a command line window
To download a tool that may help you clean your computer in preparation for installing Visual Studio 2005, please visit this link. Please Note: This tool is not supported or thoroughly tested by Microsoft. This is a free tool and you should use it at your own risk. No warranty or support is provided, expressed or implied.
If you have any problems after following these steps, or for more information about the uninstall process, please review the following page: Uninstalling Previous Versions of Visual Studio 2005.
1.3. Product Installation
1.3.1 Installation of Visual Studio 2005 on the Intel Itanium (IA64) is not supported.
Visual Studio 2005 does not support the Intel Itanium (IA64) processor.
To resolve this issue
If you need to develop Itanium applications, install Visual Studio on another computer and use the cross compilers to target the Itanium platform.
1.3.2 SQL Express installation fails when pre-released SQL Express components are not uninstalled
SQL Express component setup will fail if any of the following pre-released SQL Express components are left on the computer:
"Microsoft SQL Server 2005 Express Edition"
"Microsoft SQL Server 2005 Tools Express Edition"
"Microsoft SQL Native Client"
In most cases, setup only displays a list of Beta components detected on the targeted computer. However, SQL Express components will always appear in this list if any other Beta components are detected. In other words, these SQL Express components could appear in the list even after the user uninstalls them.
To resolve this issue
Ensure the matching .NET Framework Beta is on the computer before performing the following steps:
- Remove "Microsoft SQL Server 2005 Express Edition"
- Remove "Microsoft SQL Server 2005 Tools Express Edition"
- Remove "Microsoft SQL Native Client"
You may ignore the Beta warning message about these components if they were uninstalled previously.
1.3.3 Setup fails when installing from a mounted drive in a Virtual PC environment
When installing Visual Studio 2005 on a Virtual PC, setup fails because it cannot access certain files.
This happens when the drive is mounted using the CD Drive mount software provided with Virtual PC or your Visual Studio 2005 media is a DVD because the mounting software can only support 2.2 Gigabytes of data.
To resolve this issue
You can use a third-party DVD Drive mounting software. Alternatively, you can copy the contents of the Visual Studio 2005 DVD to your computer's hard drive, share the folder with your Virtual PC, and then direct Visual Studio 2005 installation setup to the folder.
1.3.4 Upgrade from previous releases of Visual Studio 2005
First of all, thank you for contributing to the release of Visual Studio 2005 by helping us to test our pre-release versions, such as Beta 1, Beta 2 or Community Tech Preview, and for installing this final-release version! However, final-release setup does not support uninstalling pre-release versions. For best results, it is recommended you install on a clean computer that has not had a pre-release version of Visual Studio 2005 previously installed on it. While it is not officially supported, we tried to ensure the scenario of uninstalling and reinstalling from Visual Studio 2005 Beta 2 to the released version has as few issues as possible. To uninstall Visual Studio 2005 Beta 2, you must uninstall in the order specified in section 1.2 of this readme file or use the uninstall tool. Most Beta 2 projects can be carried forward to the final release version. For details on any changes needed for forward compatibility, see this link.
To resolve this issue
If you have Visual Studio 2005 Beta installed and want to install the released version, you must uninstall in the order specified in section 1.2 of this readme or use the uninstall tool.
1.3.5 Installing Visual Studio 2005 using the runas command fails.
Unless you are logged in as an administrator, using the runas command to install Visual Studio 2005 is not supported and will fail. Running Visual Studio 2005 after it is installed is supported for non-administrators.
To resolve this issue
Log in as an administrator to install Visual Studio 2005.
1.3.6 Installing Visual Studio 2005 from CD fails. A network installation is requested.
The media that Visual Studio 2005 shipped on may be bad, preventing a successful installation.
To resolve this issue
Visual Studio 2005 setup may be run from a network share as an alternative to running setup from CDs or DVDs. The following procedure illustrates how to prepare Visual Studio 2005 for installation from a network share. The procedure refers to the Visual Studio 2005 CDs, but the steps are the same for DVDs.
- Create a folder (for example, VS2005) on the server.
- Create two subfolders, named VS, and MSDN within the top-level folder. For example:
VS2005\VS
VS2005\MSDN. - Copy the contents of the Visual Studio 2005 CDs into the VS2005\VS folder. Select Yes if prompted to overwrite any existing files.
- Copy the contents from all the CDs labeled MSDN Library for Visual Studio 2005 to the subfolder named MSDN. Select Yes if prompted to overwrite any existing files.
- Open Setup.ini in the VS subfolder using a text editor, such as Notepad.
In the [Documentation] section, change the line that starts with "DIR=" as follows:
[Documentation] DIR=..\MSDN
- Save your changes and close the file.
Note Completing this step prevents disk-swapping requests during setup and informs the setup program of the correct path to the MSDN Library CDs. - In the VS subfolder, open the Setup folder.
Open setup.sdb in a text editor, such as Notepad, and add the following lines to the end of the file:
[Product Key] XXXXXXXXXXXXXXXXXXXXXXXXX
Note XXXXXXXXXXXXXXXXXXXXXXXXX is the 25 digit product key, entered without dashes, found on the CD packaging.
- Save your changes and close the file.
Note Completing this step enables pre-populating the product key for the user who will install from the network share. Share the VS2005 folder on the network and set the appropriate security settings. The path to Visual Studio 2005 setup from the network looks like \\[servername]\VS2005\VS\setup.exe
Note Setup will fail if any path and file name combination exceeds 260 characters. The maximum length of a path in Visual Studio is 221 characters. You should copy files to a path with less than 70 characters. If you create a network share for a network image, the UNC path to the root installation location should contain fewer than 39 characters.
Note Setup might fail if the folder names in this path include embedded spaces, for example:\\[servername]\VS2005\MSDN\ \\[servername]\VS2005\Visual Studio\
1.3.7 Installing any edition of Visual Studio 2005 from an installation path that is longer 100 characters fails on Windows 2000.
When setup is launched from a path that is longer than 100 characters, setup fails due to a maximum path limitation in Windows 2000. Path length is not an issue on Windows XP or Windows 2003 Server.
To resolve this issue
When installing from a network, map the network path to a local drive and install from that drive. For example, if the path is \\computername\programs\test folder\development tools\external\Microsoft\Visual Studio 2005\beta release, you can map it to a network drive by doing the following:
- From the Start menu, choose Run.
- Type cmd and then click OK.
At the command prompt, type the following:
net use * “\\computername\programs\test folder\development tools\external\Microsoft\Visual Studio 2005\beta release”
Windows maps the network drive for you. The drive letter is displayed in the console window.
When installing from a local folder, copy the contents of Visual Studio to another folder on the computer that has a total path length of less than 100 characters.
Note: If you install Visual Studio from a CD or DVD, you will not encounter any path length issues.
1.3.8 Warning dialog appears when uninstalling MSXML 6.0.
To completely uninstall Visual Studio, you must manually uninstall MSXML 6.0 using Add or Remove Programs. During uninstall for MSXML 6.0, the following warning may appear:
To resolve this issue
You must manually uninstall all of the products listed in the warning before you uninstall MSXML 6.0.
Any SQL Server products that need to be uninstalled are listed on the final page displayed after Visual Studio is uninstalled. If products other than SQL Server are listed in the warning text, those products also will need to be uninstalled before you uninstall MSXML 6.0.
1.3.9 Installation path cannot accept non-ANSI characters on Japanese MUI OS.
On JPN MUI OS, when installing Visual Studio Team Suite to path with non-ANSI characters such as “c:\program files\噂 浬 詰 圭 構 蚕 十 觸 Microsoft Visual Studio 8”, a dialog box pops up saying “can't accept non-ANSI characters”.
This problem occurs on all JPN MUI OS (including Windows 2000, Windows 2003 and Windows XP series operating systems). It does not occur on JPN OS.
To resolve this issue
Use ANSI characters for the destination path.
1.3.10 Internet Explorer Script Error! An error has occurred in the script on this page.
This error, and "Could not complete the operation due to error 887600de", might be encountered while installing Visual Studio Standard on Windows 2000 with Service Pack 4. This error occurs on computers with low color depth. This error occurs on machines with low color depth.
To resolve this issue
Enable more colors:
- Cancel Visual Studio install.
- Right click on the desktop wallpaper.
- Click on Properties.
- Click the Settings tab.
- Adjust the Color Quality to a higher setting.
- Click OK
- Install Visual Studio again.
1.3.11 Load Test Agent installs only if controller is running.
Installation of Team Load Test Agent will fail if the specified controller is not running. To verify this problem, examine AgentConfigUtil.exe.log in \Program Files\Microsoft Visual Studio 8\Microsoft Visual Studio Team Suite\LoadTest directory.
To resolve this issue
Ensure that the controller is installed and the service is running, and then try the installation again.
1.3.12 Installing Microsoft Office 2003 Primary Interop Assemblies
You want to install the Microsoft Office 2003 Primary Interop Assemblies after you have finished installing Visual Studio 2005, but you do not know how to install them.
To resolve this issue
- On the installation media, navigate to the \setup folder.
- Open PIAInstall.htm and follow the instructions listed.
1.3.13 Antivirus applications that are configured to clean the Temp folder might cause setup to fail
If setup needs to reboot and your antivirus application is set to clean the Temp folder on launch, necessary setup files will be deleted and setup will fail due to a program-not-found error.
To resolve this issue
Before running Visual Studio setup, reset the antivirus application to leave Temp folder contents intact on launch or reboot. Reference your Antivirus help documentation for steps on how to do this.
1.3.14 Setup does not check disk space when auto-launching after selecting "reboot later".
When reboot later is selected and the available space on the hard drive is filled beyond the amount of space needed by setup, an out-of-space error will occur after reboot.
To resolve this issue
Ensure that enough disk space will be available by rebooting before installing or opening other applications. The required disk space is displayed when you select the location to install the product.
1.3.15 Removing the .NET Framework breaks SQL Server 2005 and MSDN Express Library.
You must uninstall SQL Server 2005 and MSDN Library before uninstalling .NET Framework 2.0 or you will encounter an error. You can install newer versions of SQL Server 2005 or MSDN Library only after removing all previous SQL Server 2005 components and MSDN library components, as listed below.
To resolve this issue
- From the Control Panel, select Add or Remove Programs.
- Select SQL Server 2005 components and click Remove to remove each component below.
- Remove "Microsoft SQL Server 2005 Express Edition"
- Remove "Microsoft SQL Server 2005 Tools Express Edition"
- Remove "Microsoft SQL server setup support files"
- Remove "Microsoft XML 6.0"
- Remove "Microsoft SQLXML 4.0"
- Remove "Microsoft SQL Native Client"
- Remove "Microsoft MSDN library"
- Select the .NET Framework 2.0 and click Remove.
- Install SQL Server 2005.
Note: If you remove the Beta .NET Framework 2.0 before removing all SQL Server 2005 components or MSDN Library, you must reinstall .NET Framework 2.0 before you can successfully perform the steps above.
1.3.16 After being uninstalled, SQL Server Express requires a reboot before it can successfully reinstall.
When all SQL Server Express components are uninstalled, and then SQL Server Express is reinstalled via Maintenance Mode (for VSTS, you will need to install MSXML 6.0 first), the reinstallation fails. No cause is written to the VS logs.
To resolve this issue
After uninstalling SQL Server Express, reboot the computer before reinstalling it.
1.3.17 Customers who wish to use Visual Studio 2005 Tools for Microsoft Office projects need to install Office and SP1 before installing Visual Studio Team System
The issue is that VSTO 2.0 features require an updated OtkLoader instead of the version that came with Office 2003.
When VSTS is installed, the VSTO runtime (which includes the updated OtkLoader) is installed. If Office is present at installation time, OtkLoader is updated and everything will function as expected. However, if Office is not present, OtkLoader cannot be updated. Users must then install Office SP1 and run VSTOR.EXE to update OtkLoader manually.
To resolve this issue
Run VSTOR.EXE to update the version of OtkLoader.
1.3.18 C++ Itanium Native Tools Setup Requirement for MFC and .NET Windows Forms Integrations
In order to develop applications that combine MFC and .NET Windows Forms you will need to follow an additional step.
To resolve this issue
Manually install mfcmifc80.dll to the Global Assembly Cache using the gacutil.exe.
1.3.19 C++ Tools for Itanium Setup Location for Itanium Redistributables
The redistributable files for Itanium are installed to the incorrect location during the Visual Studio Tools for 64-bit Setup (available only in Visual Studio Team System products).
To resolve this issue
You can find the Itanium redistributables in the Microsoft Visual Studio 2005\VC\Redist\x86 folder.
2. Microsoft .NET Framework
2.1. Product Installation
2.1.1 ngen.exe might fail with REGDB_E_CLASSNOTREG or RPC_S_SERVER_UNAVAILABLE.
ngen.exe occasionally fails with REGDB_E_CLASSNOTREG or RPC_S_SERVER_UNAVAILABLE. The failure usually happens if you issue consecutive ngen commands back to back. Retry or reboot might help as long as you wait 15 minutes or so between two ngen commands. However, reboot does not fix the general problem and you might encounter it again
To resolve this issue
Install DCOM 98 patch from here: DCOM98Patch
2.1.2 Installing SDK hangs at "setup is configuring the install…”.
Installation hangs for about an hour or more at "setup is configuring the install…” and then gives the error message "invalid directory…"
This problem is caused by a lack of available disk space.
To resolve this issue
Free up sufficient space on the disk drive.
2.1.3 x64 .NET Framework Language Pack 2.0 ProductVersion says 1.1.##### instead of 2.0.#####
When deployed thru Active Directory, the language pack version number is displayed in the Group Policy Object - Software installation table. This can be confusing when the product name states "2.0" but the version data says "1.1"
To resolve this issue
There is no known resolution.
2.1.4 Installing Windows Server 2003, followed by the .NET Framework 2.0, and then upgrading to Windows Server 2003 SP1 using a full CD, breaks .NET Framework 2.0 applications.
Upgrading using a CD with the full Windows Server 2003 SP1 installation replaces the shared file mscoree.dll on the user's computer with the .NET Framework 1.1 mscoree.dll file. As a result, applications compiled against the .NET Framework 2.0 will fail to run after the Service Pack is installed.
Note, this does not happen when Windows Server 2003 is updated with just the Service Pack.
To resolve this issue
After installing the Windows Server 2003 Service Pack, the .NET Framework needs to be repaired.
- From the Control Panel, select Add or Remove Programs.
- Select Microsoft .Net Framework 2.0.
- Click Change/Remove.
- When the dialog appears, select Repair and click Next.
- If prompted to do so, reboot the computer.
2.1.5 Installing on 64-bit OS when IIS 6 is in WoW64 mode will disable ASP.NET 1.1 in IIS.
Existing ASP.NET 1.1 applications will be disabled when the 64-bit .NET Framework 2.0 Beta 2 is installed on a 64-bit operating system that has IIS6 in WoW64 mode and ASP.NET 1.1 enabled. This happens because the Framework setup incorrectly maps the aspnet_filter to the 64-bit version and removes version 1.1 of the aspnet_isapi extension.
To resolve this issue
You must manually change IIS to use the 32-bit version of the aspnet_filter and reinstall the ASP.NET 1.1 ISAPI extension.
- Start Internet Information Services Manager (inetmgr.exe).
- Expand the local computer node, then click the Web Sites node.
- From the Action menu, select Properties.
- In the Web Site Properties dialog box, select the ISAPI Filters tab.
- In the list of filters, select the ASP.NET 2.0 filter and click Remove.
- Click Add and then enter the following:
Filter Name: ASP.NET_ 1.1.4322
Executable: C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_filter.dll
- Click OK.
- Under the Local Computer node, click the Web Service Extensions node.
- Under Tasks, click Add a new Web Service Extension.
- In the New Web Service Extension dialog box, enter the following:
Extension Name: ASP.NET v1.1.4322
For Required files, click Add... and then enter: C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll Check Set Extension status to Allowed.
Click OK.
2.1.6 x64 netfx SDK JPN has ProductVersion = 1.1.##### instead of 2.0.#####
When deployed thru Active Directory, the version number is displayed in the Group Policy Object - Software installation table. This can be confusing when the product name states "2.0" but the version data says "1.1".
To resolve this issue
There is no known resolution.
3. Smart Device Programmability
3.1. Product Installation
3.1.1 Installing PB after Visual Studio will duplicate smart device platforms.
Currently, installing PB after Visual Studio 2005 will duplicate platform entries in datastore. When Visual Studio is invoked later or restarted, duplicate platform entries will be eliminated based on Platform ID without respect to how the entry was added. As a result, changes made to datastore (e.g., emulator settings) before PB was installed might be lost as part of duplicate entry removal.
To resolve this issue
Change the settings of the affected platforms manually through Visual Studio.
3.1.2 Installing and uninstalling PB on a computer with Visual Studio 2005 affects Visual Studio
Uninstalling PB unregisters conman2.dll and some other dlls on which Visual Studio depends. As a result, Visual Studio smart device functionality might be impaired.
To resolve this issue
Repair-installing Visual Studio fixes the problem.
4. Source Code Control Integration
4.1. Product Installation
5. Crystal Reports
For additional information concerning Crystal Reports for Visual Studio 2005, please visit us at:
http://www.businessobjects.com/products/reporting/crystalreports/net/vsnet.asp
Keywords: kbinfo kbreadme kbsetup kbsettings KB908452
