Conference iosg::all-in-1_v30

3139.0. "Server log file errors......" by BIGTOY::ROGERSD (Rorey Davenport lives) Fri Aug 13 1993 09:53

Hi, 

I have a very large installation that currently uses TeamLinks and the IOS file
cabinet. The IOS file cabinet is the only storage cabinet used. TeamLinks users 
when connecting to their filecabinets where hanging, in the 
SYS$MANAGER:OAFC$SERVER.LOG the following error appears....

%OAFC-E-INTERR, Internal error in File Cabinet Server  Message:
FCS has access violated, please submit an SPR.

Stopped and started server - no change, stopped and started ALL-IN-1 - this
fixed it.

Now the customer has logged this call with me. The Account Manager wants this 
call raised as a CLD asap, I was hoping that this could be avoided. I will
include  some of the log file 

TeamLinks 1.1 (not sure if it's patched)
ALL-IN-1 IOS 3.0-1

regards

darrin rogers
Sydney CSC

4-AUG-1993 14:05:00.70  Server: TMVAX1::"73="  Error: %OAFC-E-DRAWERDOESNOTEX,
 Drawer does not exist
 Message: GsmAddDrawertoFileCab; Drawer level error, continuing operation

 4-AUG-1993 14:06:07.83  Server: TMVAX1::"73="  Error: %OAFC-E-INTERR,
 Internal error in File Cabinet Server
 Message: FCS has access violated, please submit an SPR.

 4-AUG-1993 16:55:07.11  Server: TMVAX1::"73="  Error: %OAFC-E-INTERR,
 Internal error in File Cabinet Server
 Message: FCS has access violated, please submit an SPR.

 5-AUG-1993 10:23:34.41  Server: TMVAX1::"73="  Error: %MCC-E-ALERT_TERMREQ,
 thread termination requested
 Message: CsiCacheBlockAstService; Error from mcc_astevent_receive

 5-AUG-1993 10:23:44.43  Server: TMVAX1::"73="  Error: %MCC-E-ALERT_TERMREQ,
 thread termination requested
 Message: SrvStopServer; timeout; not all tasks run to completion

 5-AUG-1993 10:24:55.53  Server: TMVAX1::"73="
 Message:  Startup for File Cabinet Server V1.0-2 complete


 5-AUG-1993 10:36:34.41  Server: TMVAX1::"73="  Error: %MCC-E-ALERT_TERMREQ,
 thread termination requested
 Message: SrvTimeoutSysMan;  receive alert to terminate thread

 5-AUG-1993 10:37:11.17  Server: TMVAX1::"73="
 Message:  Startup for File Cabinet Server V1.0-2 complete

 5-AUG-1993 11:21:55.86  Server: TMVAX1::"73="  Error:
 %OAFC-W-BUFFOVFL, Client buffer not big enough for requested information
 Message: CsiEndFunction; Error putting EOC on out stream

 5-AUG-1993 13:32:17.49  Server: TMVAX1::"73="  Error:
 %OAFC-W-BUFFOVFL, Client buffer not big enough for requested information
 Message: CsiEndFunction; Error putting EOC on out stream

 5-AUG-1993 14:11:23.20  Server: TMVAX1::"73="  Error:
 %OAFC-E-DRAWERDOESNOTEX, Drawer does not exist  Message:
 GsmAddDrawertoFileCab; Drawer level error, continuing operation

** Following message repeated several times **

 6-AUG-1993 19:24:41.20  Server: TMVAX1::"73="  Error:
 %OAFC-W-BUFFOVFL, Client buffer not big enough for requested information
 Message: CsiEndFunction; Error putting EOC on out stream

 9-AUG-1993 09:08:50.97  Server: TMVAX1::"73="  Error:
 %OAFC-E-INTERR, Internal error in File Cabinet Server
 Message: FCS has access violated, please submit an SPR.

    You might find this to be a known problem anyway... I'd try ICF9 as a
    starting point - if they haven't got that already.
    
    Also try getting some more details on the ACCVIOs by running FCS
    interactively to get the VA and PC values - there is no hope of analyzing
    the problem without this information.
    
    Paul.

    
    re .0
    
    Not alot here that I think is serious, outside of the acc vio :-)
    
>4-AUG-1993 14:05:00.70  Server: TMVAX1::"73="  Error: %OAFC-E-DRAWERDOESNOTEX,
> Drawer does not exist
> Message: GsmAddDrawertoFileCab; Drawer level error, continuing operation

    Means someone tried to add a drawer to FILECAB.DAT and the drawer
    physically does not exist.  Usually as a result of ADR, is coming from
    TL it probably means they are doing the add drawer to filecab, and gave
    a syntactically correct name, but the drawer they want is named
    something else.
    
 >4-AUG-1993 14:06:07.83  Server: TMVAX1::"73="  Error: %OAFC-E-INTERR,
 >Internal error in File Cabinet Server
 >Message: FCS has access violated, please submit an SPR.
 >
 >4-AUG-1993 16:55:07.11  Server: TMVAX1::"73="  Error: %OAFC-E-INTERR,
 >Internal error in File Cabinet Server
 >Message: FCS has access violated, please submit an SPR.

    Only bad things here, but as Paul said, hard to go on.
    
 >5-AUG-1993 10:23:34.41  Server: TMVAX1::"73="  Error: %MCC-E-ALERT_TERMREQ,
 >thread termination requested
 >Message: CsiCacheBlockAstService; Error from mcc_astevent_receive
 >
 >5-AUG-1993 10:23:44.43  Server: TMVAX1::"73="  Error: %MCC-E-ALERT_TERMREQ,
 >thread termination requested
 >Message: SrvStopServer; timeout; not all tasks run to completion

    Server is shutting down. There should have been more of these, leads
    me to think possible memory corruption.
    
 
 >5-AUG-1993 11:21:55.86  Server: TMVAX1::"73="  Error:
 >%OAFC-W-BUFFOVFL, Client buffer not big enough for requested information
 >Message: CsiEndFunction; Error putting EOC on out stream

    
    This (and all the rest of them), means that the FCS is processing 
    a request and is building the return TLV encoded stream. Problem is
    that the buffer, supplied by the client side, is not big enough to 
    hold all the data.  There is a known bug in the system management
    stuff that will cause this (only from VMS), has to do with getting
    connected user info and having X number of people connected (sorry
    forget what X is).  From the PC, never seen it. The correct action
    is one of two things (both for the TL code to do):
    
    1) Detect the error and make the request again with a bigger buffer
    
    Or
    
    2) Make the request again, but requalify the request to makethe 
       information returned smaller (note this either may not be possible
       or could lead to the same error if you don't restrict the 
       question enough.)
    
    --Bob