[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| 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 | 
4282.0. "ADN:"%RMS-E-CRE, ACP create failed" when archiving" by EVTAI1::MORVAN () Wed Jun 22 1994 12:33
    Hello,
    
    
    One of my customer have the following problem:
    
    Product : ALL-IN-1 3.0-1 French
    
    Problem description : 
    
    	Since three days  non privileged users cannot  archive documents
    any more. When they execute ADN option they get the message :
    
    
       %OA-W-ARCFAILOPEN, impossible d'ouvrir le fichier de sortie
            "ARCHIVE$AREA_00013:accountname-filename.ARCHIVE"
            RMS-E-CRE, acp file create failed
       %OA-I-LASTLINE, erreur d'archivage du document provenant des
    archives de l'utilisateur.
    
    	If he set trace on , he can read in a1trace.log:
    
    ![IO]     Opening ARCHIVE_SETS_DATA, File:OA$DATA_SHARE:ARCHIVE_SETS_DATA.DAT,
    !               Class: DATA, Mode: UPDATE
    ![IO]     Rewinding ARCHIVE_SETS_DATA, Key-of-ref: AREA_ID/0
    ![IO]     Getting record from ARCHIVE_SETS_DATA,Key:ARCHIVE$AREA_000028,Key-o
    !               f-ref: AREA_ID/0
    ![IO]     Getting field DIRECTORY from ARCHIVE_SETS_DATA, Value:
    RIRI:[ARCHIV.MA
    !               R_0494]
    ![IO]     Deaccessing ARCHIVE_SETS_DATA, File:
    OA$DATA_SHARE:ARCHIVE_SETS_DATA.D
    !               AT
    ![IO]     Closing ARCHIVE_SETS_DATA, File:
    OA$DATA_SHARE:ARCHIVE_SETS_DATA.DAT
    ![IO]     Opening ARC$ARCHIVE_TXT_DSAB, File:
    ARCHIVE$AREA_000028:B_MCGRESSETVGV
    !               LU7J5.ARCHIVE, Class: TEXT, Mode: BLOCK OUTPUT
    ![IO]     Status: ACP file create failed
    ![IO]     Closing ARC$ARCHIVE_TXT_DSAB, File:
    ARCHIVE$AREA_000028:B_MCGRESSETVGV
    !               LU7J5.ARCHIVE
    ![IO]     Status: invalid internal file identifier (IFI) value
    ![A1LOG]  Entry: %OA-I-LOGERROR, %OA-W-ARCFAILOPEN, Impossible d'ouvrir
    le fichi
    !               er de sortie
    "ARCHIVE$AREA_000028:B_MCGRESSETVGVLU7J5.ARCHIVE"
    ![A1LOG]  Entry: %OA-I-LOGERROR, -RMS-E-CRE, ACP file create failed
    ![SCRIPT] ARCHIVE_USER_DOCUMENT Line 30: .if OA$STATUS eq 0 then 
     DISPLAY (OA$_AR
    !               CERROR)\FORCE \GET OA$STATUS = 0
    !
    ...
    
    Only MANAGER (ie privileged account) can archive.
    
    No existing archive area can be accessed . We have found a workaround
    with the creation of a new archive area : the customer has created a
    new Area and non privileged user can archive again.
    
    We have checked disk quotas.They are large enough.
    Archive area and user's directory are on the same disk.
    A user can create a file on this disk.
    
    What does the error message :
    "invalid internal file identifier value (IFI)" means?
    I think it is the same as rms message : RMS-F-IFI
    
    Thanks for any help
    
    Genevieve MORVAN
    French TSC
        
                                                
| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 4282.1 | Broken file... | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Wed Jun 22 1994 13:57 | 12 | 
|  | <<<< What does the error message :
<<<< "invalid internal file identifier value (IFI)" means?
<<<< I think it is the same as rms message : RMS-F-IFI
    
    It's almost bound to be the same as the RMS error, which we are just
    passing back to you. I would think it meant there was something wrong
    with the file.
    
    What does the VMS Error Messages and recovery book say you should do
    now?
    
    Graham
 | 
| 4282.2 |  | EVTAI1::MORVAN |  | Wed Jun 22 1994 14:49 | 25 | 
|  |           
    I have found:                                                                      
                                                                                  
           Facility: RMS, VMS Record Management Services                          
                                                                                  
           Explanation: The internal file identifier field of                     
           the FAB is invalid. This error usually indicates that                  
           the file has not been opened for an operation that                     
           requires the file to be opened, or that the file is                    
           already opened for an operation that requires the file                 
           not to be opened.                                                      
                                                                               
           User Action: Check for a programming error. Verify the                 
           logic of the program to see that the file is opened or                 
           closed as required for the attempted operation.                        
          
    
    What can I look? Do you think it is OA$DATA_SHARE:ARCHIVE_SETS_DATA.DAT
    which is concerned ? It can explain why all old archive areas have the
    problem.
    
    Thanks for any help.
    
    Genevieve
    
 | 
| 4282.3 | File protection? | IOSG::MARSHALL | A glitch in reality | Wed Jun 22 1994 15:30 | 13 | 
|  | The IFI error occurs on a CLOSE operation because it still gets executed even
though the corresponding CREATE operation before it failed (ACP file create
failed).  This is, indeed, a (small) programming error in ALL-IN-1, but is not
the main problem here.  The real error is why the file
ARCHIVE$AREA_000028:B_MCGRESSETVGVLU7J5.ARCHIVE could not be opened.
Has the ownership or protection of the directory(-ies) in the logical
ARCHIVE$AREA_000028 been changed?  Has the ALL-IN-1 image been installed with
the wrong privileges?  Has the disk been mounted in some funny way?
Is the logical ARCHIVE$AREA_000028 pointing to the right directory?
Scott
 | 
| 4282.4 | all is good | EVTAI1::MORVAN |  | Thu Jun 23 1994 10:47 | 11 | 
|  |     Hello,
    
    
    Thanks for your input. But all the verification you have suggested are
    negative.(protections, disk, installed image...). The logical does not
    existe but it does not on my machine too.
    
    My last hope : the customer will restart ALL-IN-1 and tell me the
    result soon...
    
    Genevieve  
 | 
| 4282.5 | directory unextendable ? | UTRTSC::SCHOLLAERT | Office WEBmaster | Thu Jun 23 1994 11:44 | 11 | 
|  |     Hi, 
    
    Could it be that the disk is so fragmented that the directory
    containing the archive files is unextendable ?
    
    Try creating a file in it by hand.
    
    Regards,
    
    Jan
    
 | 
| 4282.6 | no pb with file creation | EVTAI1::MORVAN |  | Thu Jun 23 1994 12:12 | 3 | 
|  |     We have already tried this. No problem...
    
    Genevieve
 | 
| 4282.7 | pb solved with restart ALL-IN-1 | EVTAI1::MORVAN |  | Thu Jun 23 1994 13:44 | 9 | 
|  |     The problem has been solved with a shutdown and a restart of
    ALL-IN-1!!!
    
    Thank you for your help.
    
    Regards.
    
    Genevieve
    
 | 
| 4282.8 | Just a thought | SHRMSG::HOWARD | Yes it is | Thu Jun 23 1994 18:04 | 4 | 
|  |     I had a problem getting this error when ALL-IN-1 was starting.  The TSC
    suggested raising BYTLM and FILLM (via PQL_DxxxLM in my case).
    
    Ben
 |