[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

4109.0. "File cab server stopped" by HTSC19::TONYLIU () Mon Apr 25 1994 12:39

 Hello,

 The file cabinet server of ALL-IN-1 V3.0 was always found to be stopped.
 It need to stop/id before restarting the file cabinet server.

 In the file sys$manager:OAFC$SERVER.LOG;1 ,it was found there were several
 such error message as:

 21-APR-1994 09:36:14.89  Server: BCBBAS::"73="  Error: %MCC-E-ALERT_TERMRREQ, 
 thation requested  Message: CsiCacheBlockAstService;Error from 
 mcc_astevent_receive
 21-APR-1994 09:36:16.26  Server: BCBBAS::"73="  Error: %MCC-E-ALERT_TERMR,
 thation requested  Message: SrvTimeoutSysMan; receive alert to terminate 
 thread
 21-APR-1994 09:36:31.31  Server: BCBBAS::"73="  Error: %MCC-E-EXISTENCE_ERROR,
 not exist
 21-APR-1994 09:36:47.94  Server: BCBBAS::"73="   Error: %MCC-E-EXISTENCE_ERROR,
 not exist

 22-APR-1994 03:02:44.56  Server: BCBBAS::"73="  Error: %DSL-W-SHUT, Network
 shuage: Shutting Down server, network failure.
 22-APR-1994 10:17:36.01  Server: BCBBAS::"73="  Error: %MCC-E-ALERT_TERMREQ,
 thation requested  Message: CsiCacheBlockAstService; Error from
 mcc_astevent_receive
 22-APR-1994 10:17:44.78  Server: BCBBAS::"73="  Error: %MCC-E-ALERT_TERMREQ,
 thation requested  Message: SrvTimeoutSysMan; receive alert to terminate thread
 22-APR-1994 10:17:44.78  Server: BCBBAS::"73=" Error: %MCC-E-ALERT_TERMREQ,
 thation requested  Message:SrvTimeoutSysMan; receive alert to terminate thread
 22-APR-1994 10:17:48.00  Server: BCBBAS::"73="  Error: %MCC-E-EXISTENCE_ERROR,
 not exist

 According to TIMA STARS,this may be the error message during shutdown
 of the file cabinet server.And therefore I cant conclude that any causes
 to the file cabinet server being stopped.

 Can someone kindly give me a pointer on how to troubleshoot this problem ?

 Thanks & Regards.

 Tony.




                                     
T.RTitleUserPersonal
Name
DateLines
4109.1%OAFC-E-SYSTEMERR ???HTSC19::TONYLIUWed Apr 27 1994 11:4336
    
    
 Hi,

 I have to add more information so that you can help me on it.

 I have enabled FCS trace & refresh the SYS$MANAGER:OAFC$SERVER.LOG.
 Today,the FCS was found stopped again and the following error message
 was displayed on the screen when I tried to invoke MGT MFC MS:

 %OAFC-E-SYSTEMERR, System error has occurred, refer to extended status for
 system error code

 The process BCBBAS$SRV73 existed when DCL command " $ show system" was
 issued & it was in the HIB state.

 I have checked SYS$MANAGER:OAFC$SERVER.LOG and found server startup message
 only. Additionally,I have checked the trace log & nothing special could
 be found.

 I have requested the customer to start the server in the foreground 
 according to note 2353.7 when the server was found stopped again.

 Can someone kindly tell me what I do against the message:

 >%OAFC-E-SYSTEMERR, System error has occurred, refer to extended status for
 >system error code

 I dont want how to followup this message.

 Thanks & Regards.

 Tony.

 
4109.2Configure and/or upgrade to MUPAIOSG::STANDAGEWed Apr 27 1994 12:4522
    
    Tony,
    
    Looking at the server log you posted in .0, it would appear that in one
    of the cases the network appears to be shutting down. When this happens 
    %DSL-W-SHUT is logged, and as DASL is shutting down the server has to
    aswell. 
    
    Your other problems could possibly be attributed to the server running
    out of resource. Could you possibly tell me how many users the system
    is supporting and whether you have already configured the server for
    this environment.
    
    Finally, I STRONGLY suggest they upgrade to MUPA as soon as possible.
    There are MANY FCS fixes with MUPA which will make the server far more
    robust. We have had customers in the past with problems similar to
    yours, and upgrading to MUPA has fixed them.
    
    
    Kevin.
    
    
4109.3FCS$SERVER quota too smallHTSC19::TONYLIUMon May 02 1994 09:3610
    Kevin,
    
    It was checked that the quota for FCS$SERVER was far below the
    standard one.I have informed the customer to enlarge those quota	
    and keep monitoring.If problem persists afterwards,I will persuade
    the customer apply the patch.
    
    Thanks & Regards.
    
    Tony.