| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 1024.1 | A few ideas... | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Fri Jul 10 1992 15:53 | 19 | 
|  |     Dan,
    
    The partition seeding must have gone wrong for the user's account. Have
    a look in the log file in OA$LOG.
    
    In any case, a possible cause is that there's something wrong with
    their profile record. Have a look at the language and directory fields
    and make sure they have sensible things in.
    
    Then delete the FILECAB.DAT file from their directory and get them to
    try again.
    
    If that doesn't work, you need to reseed the partition for that user.
    There's other notes in here teling you how to do that.
    
    Graham
    
    PS Oh, and please spell the name of the product ("ALL-IN-1") correctly,
    all in capitals - Thanks!
 | 
| 1024.2 | reseed | MCIS2::CLAYBROOK |  | Fri Jul 10 1992 18:22 | 9 | 
|  |     Sorry about the mis-spell.
    
    Is this what your talking about when you say reseed the partition and if so
    where in the managers account do I do this? Just trying to make sure.
    
    The language and dir. fields were okay so I didn't delete the 
    FILECAB.DAT.
    
                                                 Dan
 | 
| 1024.3 | I second Graham's idea | CHRLIE::HUSTON |  | Fri Jul 10 1992 18:38 | 17 | 
|  |     
    What usually causes this is that the drawer name in the filecab.dat 
    does not have a matching name in OA$DATA_SHARE:PARTITION.DAT. 
    I second Graham's suspicion that the seeding for this user went
    wrong someplace. 
    
    Check the log he mentioned, and see what it says for that user.
    You can use the partition seed tool to re-seed a single user.
    It sounds like either the seeding didn't go, or the seeding used
    the wrong name for the drawer.
    
    Another thing you could do to look at the drawer names is have
    the user do an IAD, this will show all the drawers in the partition
    that the user has access to. 
    
    --Bob
    
 | 
| 1024.4 | What they didn't explicitily say | AIMTEC::WICKS_A | DEC Mail Works for ME sometimes | Fri Jul 10 1992 19:21 | 15 | 
|  |     Dan,
    
    The log file GAP mentioned but didn't name is called
    OAFC$PART_SEED.LOG in OA$LOG.
    
    The way to reseed the user is from any ALL-IN-1 menu type 
    <DO OA$LIB:OAFC$PART_SEED.SCP
    but first you should type
    <GET #OAFC_SEED_USER="USERNAME"
    where you replace username with the actual username of course.
    
    Regards,
    
    Andrew.D.Wicks                                       
    
 | 
| 1024.5 | Unsuccessfull | MCIS2::CLAYBROOK |  | Fri Jul 10 1992 19:42 | 6 | 
|  |     Well I tried to reseed the partition and it didn't work, then someone 
    wanted me to try it again and I got this error:
    
    RMS Error has occurred. Refer to extended status for RMS error code
    
                                            Dan
 | 
| 1024.6 | Check protections ... | AIMTEC::VOLLER_I | Gordon (T) Gopher for President | Fri Jul 10 1992 19:51 | 13 | 
|  |     Dan,
    
    	Check the protection on the ALL-IN-1 Subdirectory directory file.
    
    	Eg:	$DIRECTORY/SECURITY [ALLIN1]MGR.DIR
    
    	Ensure that the SYSTEM has all access. If not the partition
    	seeding will fail. After setting the correct protection just run
    	OAFC$PART_SEED again as per Andrews instructions.
    
    Cheers,
    
    Iain.
 | 
| 1024.7 | Set the protection | MCIS2::CLAYBROOK |  | Fri Jul 10 1992 20:27 | 5 | 
|  |     Well I had to change the protection like you said and then I reseeded
    the partition again and I received the same error plus it said no such
    Drawer, which is what it says when you get into this account where the
    Empty Current Item Block is.
                                                      Dan
 | 
| 1024.8 | should do the trick ? | IOSG::STANDAGE | Oink...Oink...Mooooooooooooooooooooooooooooooooo | Sun Jul 12 1992 18:39 | 15 | 
|  |     
    
    Dan,
    
    Note 956 discussed the *exact* problem you are having. 
    
    In that instance, the FILECAB.DAT for the unfortunate user was deleted
    and that rectified the problem (as a new one gets created when the user
    re-enters ALL-IN-1)
    
    Give that a try...
    
    Kevin.
    
    
 |