[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

3021.0. "Upgrade to v3.0, some users have no MAIN drwaer !" by HTSC19::SIMONLAU () Mon Jul 19 1993 11:32

    Hi,
    
    
    A customer running VMS 5.4-2 has just upgraded his ALL-IN-1 v2.4 to
    ALL-IN-1 v3.0 found that some of the users after log in have no
    drawer al all ! ( couldn't access their old mails ! ) While others can
    access their old mails from the MAIN drawer.
    
    What's gone wrong with these users ??
    
    ( the customer pointed out that during post-installation, a message
      indicating "insufficient memory" was found, but he had igored it and
      continued the post-installation. Would it be the cause of this
      problem ? )
    
    
    Your input would be appreciated.
    
    Thanks a lot.
    Simon
      
T.RTitleUserPersonal
Name
DateLines
3021.1re-seed!IOSG::STANDAGEMon Jul 19 1993 11:4618
    
    Simon,
    
    By the sounds of it, the partition seeding was not fully completed.
    This is part of the automatic postinstallation tasks that takes place
    during the upgrade to V3.0.
    
    Depending on how many users haven't got their MAIN drawers, you may
    like to re-run the seeding script for all users:
    
    <DO OA$LIB:OAFC$PART_SEED.SCP
    
    Then take a look at the seeding log file which resides in OA$LOG.
    
    
    Kevin.
    
    
3021.2Check the FCS first perhaps.IOSG::STANDAGEMon Jul 19 1993 11:4813
    
    Simon,
    
    Incidently, the "insufficient memory" may have been returned from the
    File Cabinet Server, and this would explain why the seeding was not
    completed. 
    
    So, before running that script from the managers account you may want
    to ensure the FCS is happily running and not logging a problem.
    
    Kevin.