ActiveState Install to Win NT Fails

DaveMoore

unread,

Oct 19, 2001, 2:12:16 PM10/19/01

to

I haven't been able to get ActiveState Perl (or Python either,
for that matter) to install on Windows NT for several builds
now. MSIEXEC quits with "ActivePerl Build 629 ended prematurely
because of an error. Your system has not been modified." The
error is not identified.

If I run from the command line and ask for a log, the relevant
entries seem to be here:
MSI (s) (8E:AF): MainEngineThread is returning 1603
MSI (c) (42:A8): Back from server. Return value: 1603
Action ended 18:16:59: ExecuteAction. Return value 3.
MSI (c) (42:A8): Doing action: FatalErrorDlg
Action start 18:16:59: FatalErrorDlg.
Action 18:16:59: FatalErrorDlg. Dialog created
Action ended 18:17:07: FatalErrorDlg. Return value 2.
Action ended 18:17:07: INSTALL. Return value 3.

I'm running WinNT 4.0 SP5, and MSIEXEC 1.2. I'm using an
Admin account. Plenty of hard drive space, plenty of RAM.
No PERL-related environment variables or Registry entries.

I don't know the last version of PERL that worked for me,
but the last build of Python that works is 210.

I feel like I'm overlooking something obvious, but can't
find in the docs.

Help?

--
Dave Moore == djm...@uh.edu == I speak for me.
In the wrong hands, sanity is a dangerous weapon.

Mr. Sunblade

unread,

Oct 19, 2001, 2:27:05 PM10/19/01

to

"DaveMoore" <djm...@uh.edu> wrote in message
news:1kq0ttoi8uq08gsg1...@4ax.com...

> I haven't been able to get ActiveState Perl (or Python either,
> for that matter) to install on Windows NT for several builds
> now. MSIEXEC quits with "ActivePerl Build 629 ended prematurely
> because of an error. Your system has not been modified." The
> error is not identified.

Ack. Send this one to ActiveState. They've always gotten back to me with
problems, though sometimes it took a few days.

In the meantime, what about using their package install, which doesn't use
MSI, instead?

Regards,

Mr. Sunblade

DaveMoore

unread,

Oct 19, 2001, 2:39:42 PM10/19/01

to

On Fri, 19 Oct 2001 13:27:05 -0500, "Mr. Sunblade" <djb...@qwest.com>
wrote:

Dang, I knew I'd forgotten to say something. I tried that, and it,
too, fails silently. It's a perl script, so I suppose I could
comb through and pepper it with diagnostic prints, but since this
is the failsafe backup, it would be nice if it JUST WORKED. Also,
I'd like to have the uninstall capability.

If nothing turns up here, I'll pester ActiveState, and forward the
reply to the group.

Dave Crumbacher

unread,

Nov 15, 2001, 4:53:12 PM11/15/01

to

I'm having the same problem. Did you find an answer?

DaveMoore <djm...@uh.edu> wrote in message news:<pks0ttc8fllgd4bc4...@4ax.com>...

Bart Lateur

unread,

Nov 15, 2001, 5:41:37 PM11/15/01

to

Dave Crumbacher quoted:

>> >> I haven't been able to get ActiveState Perl (or Python either,
>> >> for that matter) to install on Windows NT for several builds
>> >> now.

Be sure to install it in a path with no spaces in the name. "c:\my
programs\perl" just won't do.

--
Bart.

henry.mc...@dphpc.ox.ac.uk

unread,

Nov 16, 2001, 9:01:37 AM11/16/01

to

which versions fail for you?

ActivePerl-5_6_1_625-TRIAL3-etc..zip works well for me, but 629 / 630 failed to install.