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

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

3420.0. "Installation of 3.0 fails during a1 link" by VAXRIO::ABREU () Wed Oct 20 1993 18:28

    Hi,
    
      I'm working on an upgrade of ALL-IN-1 from 2.3 to 3.0 .. and the
    installation fails with the following messages :
    
%A1-I-A1LINK, Starting to link images

Building shared image modules
Shared image modules built
Linking the OA$MAIN image
Linking the Background Formatter
Linking the TM Server
%LINK-W-READERR, error reading NL:[]OAFC$CLIENT_SHR.EXE;
-RMS-E-EOF, end of file detected
%LINK-F-BADIMGHDR, bad image header
	in shareable image file NL:[]OAFC$CLIENT_SHR.EXE;
%PURGE-W-SEARCHFAIL, error searching for $255$DUA0:[SYS0.SYSUPD.A1030]TMSV.EXE;*
-RMS-E-FNF, file not found
Linking the OA$SUBMIT image
Linking the MAILCOUNT image
Linking the File Cabinet Server images
Linking the RSD housekeeping procedure
Linking the Impersonation Services images

%A1-I-A1LINKED, Finished linking images
%SET-F-SEARCHFAIL, error searching for $255$DUA0:[SYS0.SYSUPD.A1030]TMSV.EXE;
-RMS-E-FNF, file not found

%A1-E-RETRY1, Please correct any reported problems before attempting
%A1-E-RETRY2, to install ALL-IN-1.

Does someone have any idea how I can solve this problem . I've checked the
    image the installation complains about and it doesn't seem to have any
    problem with it. 
    
    
    Marcia
T.RTitleUserPersonal
Name		DateLines
3420.1First guessAIMTEC::WICKS_AU.S.A 2 England 0 - I was there!Wed Oct 20 1993 19:527
    Marica,
    
    is it possible that you've run out of file headers on the disk?
    
    regards,
    
    Andrew.D.Wicks
3420.2more infoVAXRIO::ABREUWed Oct 20 1993 22:339
    Hi,
    
     This doesn't seem to be a problem. We have already verified the disk.
    
     Any other ideas ?
    
    Thks,
    
      Marcia
3420.4image header problems of some kind, I think !!!GIDDAY::SETHIHolland 2-England 0,Andrew wasn't thereThu Oct 21 1993 07:1128
    Hi Marcia,
    
    Some people are going to mighty upset with that 800 line logfile, being
    posted in the conference.  A pointer to the file would have been a better
    bet !!!!
    
    From the logfile
    
    >%LINK-W-READERR, error reading NL:[]OAFC$CLIENT_SHR.EXE;
    >-RMS-E-EOF, end of file detected
    >%LINK-F-BADIMGHDR, bad image header<CR><LF>     in shareable image file 
    >NL:[]OAFC$CLIENT_SHR.EXE;
    
    Seems very odd this image is found in SYS$SHARE, I don't know why it's
    pointing to NL:.  I know that you have said that you checked the image,
    did you do an $analyze/image/header sys$library:OAFC$CLIENT_SHR.EXE ? 
    Did the analyses uncover any problems ?
    
    From a dir/full I get the following details:
    
    Size: 222/222, File attributes:    Allocation: 222, Extend: 0, Global
    buffer count: 0. 
    
    I suspect that the image header is corrupted in some way.
    
    Regards,
    
    Sunil
3420.5Why is linker looking at NL:SCOTTC::MARSHALLSpitfire Drivers Do It ToplessThu Oct 21 1993 12:0114
The image header isn't really corrupted!  I'm sure the image file is fine.

But the installation is trying to read a file from NL:, the null device.
All reads from this device return end-of-file, as the error message shows.
As the linker isn't expecting to see EOF at the start of an image, it complains
that the image header is corrupt (a slightly misleading error).

Your problem is to find out why the linker is looking on NL: for this file,
rather than in the proper directory.

Is your SYS$SHARE logical correctly defined?  Has anyone been tampering with
A1LINK.COM?

Scott
3420.6more infoVAXRIO::ABREUThu Oct 21 1993 14:1421
    Hi Sunil and Scott,
    
      Thanks for answering the note. First , I deleted the note with the
    log .. it's really big , I didn't realize that when I created it.
    
    The image doesn't seem to be corrupted because I analyzed it and had no 
    errors .. I used "analyze/image" and "analyze/rms" .. And according to 
    the logfile , the oafc$client_shr used is the one copied by the
    installation to the temporary directory.  Sys$share is
    "SYS$SYSRoot:[syslib]" and during the link of background fomatter and
    oa$main , some images from this directory are used with no problem
    because the link is successful.
    
    The only logical name defined to NL: is the EPC$SHR ... there is no
    symbol defined to NL: .. 
    
    Anyway , I'll try another kit oa A1 3.0 today. If you have any other
    idea ... please let me know.
    
     
    Marcia