installing on windows 2000 server

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Gary E - 02 Sep 2005 04:51 GMT

Hey all

Trying to install dot net 1.1 on a windows 2000 server. Have SP4 on server,
IE is ver 6.0.

Every time I try to install, I get an error 1327. I have installed MDAC 2.7
thinking it would help, but nothing I have tried gets me past this error.

Anyone have a any suggestions about installing this one a W2K server? Is it
not recommended? This apparently is for a new Intuit Master Builder
installation.

Thanks for your help

Gary

Reply to this Message

Phil Wilson - 04 Sep 2005 19:56 GMT

If you search the kb for 1327 there are two or three articles about
installation problems related to invalid drive. Ignore the fact that they
talk about Visio or Office because this message is a generic Windows
Installer error that can happen to any MSI-based setup. You mention
installing .NET 1.1 and Intuit, but I'm assuming it's the Intuit one that
gets this message. You'll have to go to the Intuit folks to find out if they
support installing on W2K Server.

Signature

Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280

> Hey all
>
[quoted text clipped - 14 lines]
>
> Gary

Reply to this Message

Gary E - 07 Sep 2005 04:47 GMT

Phil

Thanks for the info. Apparently the problem was the remote installation of
the Server OS from a remote drive which no longer existed. It was the NET
1.1 installer that gives the message. It was always pointing to a U: drive.
I created (through NET USE) a U: drive, but that didn't work. The only way I
could get it to install was to edit the registry and change all references
to U:\program files\common files to c:\... . After doing that change it
worked, but was tedious

Thanks again

Gary

> If you search the kb for 1327 there are two or three articles about
> installation problems related to invalid drive. Ignore the fact that they
[quoted text clipped - 21 lines]
> >
> > Gary

Reply to this Message

Phil Wilson - 07 Sep 2005 16:49 GMT

That makes sense. Mapped drives (or subst drives) are user specific, so it's
easy to get that problem if you're not the installing user or the drive
mapping disappears. It's recommended to use \\Servername\ UNC paths when
installing to avoid these types of problem. --
Phil Wilson
[Microsoft MVP-Windows Installer]

> Phil
>
[quoted text clipped - 40 lines]
>> >
>> > Gary

Reply to this Message

installing on windows 2000 server

Free Magazines