Groups | Blog | Home
all groups > visual studio .net setup > may 2006 >

visual studio .net setup : Visual Studio 2005 on a Windows 2003 application server


SHEBERT
5/29/2006 8:41:01 AM
I'm trying to install "Visual Studio Team Edition Software Developers" on a
"Terminal server" in "application server" mode on a Windows 2003 server.

But I get the error "at least one component has an install path set to a
mapped drive. Installing to mapped drives is not supported" when I select any
type of installation (DEFAULT, FULL or even CUSTOM)

I see that a few components are trying to be installed on "u:\Program
Files\Common Files\" where U: is a network drive.

Those components do not allow me to change the path.

After investigation, it is the registry field "COMMONFILESDIR" in
HKLM\Software\Microsoft\Windows\CurrentVersion that contains "u:\Program
Files\Common Files\" instead of "C:\Program Files\Common Files\".

This is the first "application server" on Windows 2003 in our company; all
other "application server" has the registry field "COMMONFILESDIR" set to
"C:\Program Files\Common Files\"

Don’t know if it's a bug with the installation of "visual Studio 2005" or
with our application server
timmac NO[at]SPAM online.microsoft.com
5/30/2006 12:43:23 AM
I have seen this before, when the subst command is used. The Windows
Installer Engine does not understand the subst command, and so you will see
the error like you were seeing here.


Cheers,
Tim Macaulay, MCSD, MCSD.NET, MCAD, MCP
Microsoft Product Support - ADSI, Visual Studio, MSI
This posting is "AS IS" with no warranties, and confers no rights
SHEBERT
5/30/2006 7:21:02 AM
Hi Tim,

I did not use the "SUBST" command. and there is no "SUBST" defined either.

[quoted text, click to view]
AddThis Social Bookmark Button