[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

4335.0. "FCS hangs on edit from ONE drawer" by UTRTSC::SCHOLLAERT (Office WEBmaster) Mon Jul 11 1994 13:46

    Hello,
    
    Need some help. Big customer reports intermittent hangs on all of
    his ALL-IN-1 systems (3.0A). 
    
    Hangs occur when a users tries to edit a document from a shared
    drawer. Read still works fine. From this moment this drawer
    will hang all other users who try to edit a document. 
    
    File cabinet server does not loop, no errors in sys$manager:oafc*.log .
    All other shared drawers are still accessable. 
    
    Stop/start of the file cabinet server cures the hang.
    
    Customer does run ZAP (idle process killer)... I tried to reproduce
    the problem with $STOP/ID with no luck.
    
    Any troubleshooting hint is welcome.
    
    Regards,
    
    Jan

T.R	Title	User	Personal Name	Date	Lines
4335.1		IOSG::STANDAGE		`Mon Jul 11 1994 14:11`	20
	Jan, It's difficult to say what exactly has happened here for this particular case, but since V3.0A we have radically modified the server, especially with regards to drawer locking problems. Is this problem isolated to one particular drawer, or does it randomly occur on just about any drawer ? My initial response would be to try and encourage the customer to install TLC V2.1. Although they might not require all the things that are bundled with TLC, this product does include the very lastest server, which hopefully would ease if not resolve the problem completely. Kevin.
4335.2	need clarification	UTRTSC::SCHOLLAERT	Office WEBmaster	`Mon Jul 11 1994 14:36`	20
	Hello Kevin, >Is this problem isolated to one particular drawer, or does it randomly Random on all of his 40 systems. >My initial response would be to try and encourage the customer to >install TLC V2.1. Although they might not require all the things that Problem is that we encouraged this customer to upgrade to MUPA for the same reason. I want to avoid that the customer thinks we are just shooting in the dark... So if you can think of any extended troubleshooting to be sure TLC V2.1 fixes this problem... Regards, Jan (who is still not able to find TLC V2.1 on the net for this customer, (Note 4312.1)).
4335.3		IOSG::STANDAGE		`Mon Jul 11 1994 15:00`	34
	Jan, The object locking fixes were a progressive job, and certainly MUPA includes fixes for this, but TLC V2.1 completes the job. The server in this kit also runs over a completely different threads package, and this in itself may well resolve your particular problem. >>So if you can think of any extended troubleshooting to be >>sure TLC V2.1 fixes this problem... This problem is just about impossible to troubleshoot to any degree. Setting server tracing etc will not show much more than what you already know. Probably the best indication that TLC V2.1 probably fixes your problem is feedback we've already received from customers who have installed it on their production machines. We've received very positive feedback from US and UK sites regarding the stability of the FCS with TLC V2.1. Also note that the TLC V2.1 is completely different to MUPA regarding installation. There are no manual postinstallation tasks, it only takes ~40 minutes to install, and is only 12000 blocks in size. Incidently, the kit location is at : IOSG::TLCV21$SSB_KIT Thanks, Kevin.