[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

3918.0. "FILECAB.DAT corrupt if created during a TeamLinks session" by BERN01::MUELLERS (Stefan A Mueller 761-4864) Wed Feb 23 1994 16:32

    After an ALL-IN-1 upgrade installation (V2.4 -> 3.0A) a user connected
    to the IOS File Cabinet before entering ALL-IN-1 with the VT interface.
    The FILECAB.DAT has been created but was unusable. The user couldn't
    see	her documents whether from TeamLinks nor from the VT. 
    
    After deleting the corrupt FILECAB.DAT and entering ALL-IN-1 using the
    VT everyting worked well.
    
    Is this a known problem?
    
    Stefan
T.RTitleUserPersonal
Name
DateLines
3918.1IOSG::STANDAGEWed Feb 23 1994 16:3511
    
    Stephan,
    
    Yes, we know of some problems if you connect to TeamLinks before
    entering IOS. Could you check the MUPA/TLC release notes, I thought
    we'd documented something about this.
    
    Thanks,
    Kevin.
    
    
3918.2Something is mentioned thereBERN01::MUELLERSStefan A Mueller 761-4864Wed Feb 23 1994 17:0013
    Yes, it is something documented in the MUPA release notes, section 2.12:
    
                  o  If the first access to a File Cabinet is made from
                     a non-ALL-IN-1 client, without previous access from
                     ALL-IN-1, the user's default drawer does not exist in
                     FILECAB.DAT and cannot be created. The File Cabinet
                     Server has been changed to automatically seed the
                     user's default drawer in FILECAB.DAT when the file
                     is created.
     
    
    But, this should be a solved problem ...
    
3918.3Are you sure you were running the new MUP FCS?IOSG::TALLETTGimmee an Alpha colour WinPad!Wed Feb 23 1994 20:491
    
3918.4?IOSG::STANDAGEThu Feb 24 1994 08:549
    
    ...and are you sure you converted SYSTEM_FOLDERS.DAT ?
    
    This is the way in which the server writes MAIN into Filecab.dat.
    
    
    Kevin.
    
    
3918.5No 100% sure ...BERN01::MUELLERSStefan A Mueller 761-4864Sun Feb 27 1994 20:5716
    .3 and .4:
    
    I am not 100% sure but 99%. SYSTEM_FOLDERS.DAT is converted by
    A1_MUPA030_POST_INSTALL.COM which would display an error message if
    either SYSTEM_FOLDERS.DAT or sys$system:oafc$convert_system_folders.exe
    isn't on the system. Because I didn't see this messages I assume it's
    done correctly. I will have a look at the customers system later.
    What's the difference beetween an V3.0 and a V3.0A SYSTEM_FOLDERS.DAT?
    
    The new FILECAB server image is created by A1_MUPA030_RELINK.COM, it
    could be, that I didn't stop and restart the File Cabinet server after
    the MUPA installation; there could be the problem...
    
    Stefan
    
    
3918.6hope this is itIOSG::STANDAGEMon Feb 28 1994 09:2114
    
    Stefan,
    
    Yes, converting system folders is a manual MUPA post installation
    tasks. The server reads this files at startup time and stores it
    internally, so you have to make sure the server is restarted after
    converting the datafile. 
    
    I got a call from a support centre on Friday, they had a customer with
    this exact problem. Stopping and restarting the servers did the trick.
    
    Kevin.