[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::networker

Title:	NetWorker
Notice:	kits - 12-14, problem reporting - 41.*, basics 1-100
Moderator:	DECWET::RANDALL.com::lenox

Created:	Thu Oct 10 1996
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	750
Total number of notes:	3361

406.0. "NSR client, AXP 150, NT 4, install" by BRSADV::WARICHET (What goes around, comes around) Thu Feb 13 1997 23:39

    I'm installing NSR client (latest version) on AXP 150, 64 MB
    NT 4.0 SP1.
    While installing: when Installshield reaches 65%, pop-up
    
    Setup Initialization Error
    Set up is unable to decompress and copy program files: Error 112
    
    Shortly after, pop-up:  Application error.
    ISSET_SE cause general protection fault in module <unknown>
    
    There is plenty of disk space, GPF is usually a DLL conflict, any
    pointer ?
    
    Thanks
    /RW

T.R	Title	User	Personal Name	Date	Lines
406.1	Hello !	BRSADV::WARICHET	What goes around, comes around	`Thu Feb 20 1997 23:45`	4
	Hello ! Anybody there ?
406.2		DECWET::LENOX	Do I really want to know?	`Fri Feb 21 1997 08:01`	15
	where did you get the kit you are installing and if it was over the network give the full file name & location and steps you took to copy the kit. I haven't had trouble installing the 4.3 kit onto NT 4.0 SP1, but I haven't tried just the client piece (Mark has though), and I haven't tried this on a jensen recently. I'll see what I can clear up to check this out, but if I don't have any problems, I would suspect that your kit was incorrectly copied, you've gotten the intel bits by mistake, or something is wrong with your NT system.
406.3		DECWET::LENOX	Do I really want to know?	`Fri Feb 21 1997 10:37`	9
	Well the jensen in our lab died and took NT with it, it will be a while until we have time to reinstall it (there is a queue). However the kit installs on my avanti with NT 4.0 SP1 which has never had NSR installed. Giving us the data I asked for would be the best way to start. thx
406.4	I think it's AXP150 specific	BRSADV::WARICHET	What goes around, comes around	`Fri Feb 28 1997 02:37`	27
	re .2 > where did you get the kit.. I got the kit from FTP to slugbt.zso.dec.com, Kit /pub/networker/kits/NT_Server as stated in note 12.3 steps: ftp slugbt.zso.dec.com user anonymous pw [email protected] cd /pub/networker/kits/NT_Server/4.3 bin get Alpha.zip > I would suspect that your kit was incorrectly copied ... In fact I had the same idea, so I got v 4.2a, installed it, with same problem: 12.2 ftp.zso.dec.com /pub/networker/kits/V4.2A (ftp access) > something is wrong with your NT system... Mmmmh, could be, but system works file and NT backup are OK Any pointer on how to diagnose ? NB: I HAD a previous version working, which expired, so I decided to install v 4.3 :-( Thanks again /RW
406.5		DECWET::LENOX	Why is DECdirect so out of date?	`Fri Feb 28 1997 07:51`	16
	When you put your previous kit on what kind of system did you have (i.e. NT4.0 but hadn't put SP1 on, NT3.51 but then did an upgrade later, etc..)? Was the previous version that installed ok the NSR Client version 3.51, or 4.2A? I'm curious what you mean the client 'expired'... client's don't 'expire' licensing wise, I'm assuming you mean that NT 4.0 wasn't supported but want to make sure I understand what you mean. thanks, Amy
406.6		DECWET::KOWALSKI	Time's not for saving	`Fri Feb 28 1997 09:05`	4
	Try setting up an account or session with very minimal PATH. Sounds like your initial suspicion may be correct, there's a DLL conflict. Clean out your TEMP and TMP directories, too.
406.7	Still error 112 Installshield 65%	BRSADV::WARICHET	What goes around, comes around	`Sun Mar 02 1997 23:46`	23
	re .5 >When you put your previous kit on what kind of .. >Was the previous version that installed ok It was NSR 4.2a on NT 3.51 Then I upgraded NT from 3.51 to 4.0, installed SP1, then realized that NSR didn't work anymore, so installed NSR 4.3 to support NT 4 & Win 95 >I'm curious what you mean the client 'expired'... client's don't >'expire' I can't formulate it better, I remember having seen a message with the word 'expired'. But it was the SERVER anyway, I only installed NSR server but, trying to solve my problem, I installed the client only, same failure Always error 112 when Installshield reaches 65% What is the meaning od "error 112" ? re .6 >minimal PATH. Good idea, but still error 112 Thanks again /RW
406.8	Error 112	BRSADV::WARICHET	What goes around, comes around	`Thu Mar 20 1997 02:38`	2
	Any idea about error 112 ?
406.9	From IS3's documentation	DECWET::KOWALSKI	Time's not for saving	`Thu Mar 20 1997 08:01`	7
	Error 112 Setup is unable to decompress and copy all the program files needed to proceed with the installation. Contact your software vendor. Make sure that you have TEMP environment variable. Also make sure there is enough disk space where TEMP directory is located.
406.10	Still error 112	BRSADV::WARICHET	What goes around, comes around	`Fri Mar 21 1997 04:36`	14
	Thank you for the tip. I've made several attemps, by creating the TEMP dir on different disks, and pointing the environment variable to that location, no luck, still error 112. One thing is worth mentionning, the problem is reproducable, happens each time, same place, and each time after error 112, I get a pop-up saying ISSET_SE cause general protection fault in module <unknown>16EF:0213"some garbage char here"SSET_SE will close I think I've a DLL version conflict, but are unable to diagnostic Any pointer ? /RW
406.11		DECWET::KOWALSKI	Time's not for saving	`Fri Mar 21 1997 07:21`	6
	Have you previously installed on this system the version of InstallShield which is provided on the MSVC distribution? Since that product and the product NetWorker uses are completely different products, that might be the cause of the conflict.