Conference abbott::teamlinks_windows

2057.0. "V3 - EFT1 - Startup Error with CFCDEBUG" by WKOL10::STETSON (Think Digital Software!) Thu Mar 13 1997 08:04

    Environment: Windows 95 with Service Pack 1
    		 TeamLinks V3.0 EFT1
    		 Running in Online/Disconnected mode - no network
    		   connection.
    
    In order to provide more complete information on the problem described
    in note #2055, I edited OFFICE.INI to uncomment the CFCDEBUG line at
    the top of the file.  I then restarted TeamLinks to see if I could
    recreate the scenario in #2055.  I did get a started InfoMan window,
    but before the local file cabinets appeared I got the following dialog
    box:
    
    	TeamLinks Common File Cabinet
    
    !	Attribute not supported by the 
    	file cabinet service.
    
    			OK
    
    I cliked the OK button and got the same dialog.  I got the same dialog. 
    I repeated this cycle 13 additional times (this number is the number of
    local file drawers I start with!).  The dialogs stopped coming and my 
    local drawers appeared in the now complete InfoMan window.
    
    I then clicked on the File Cabinet Connect button I got
    the spinning hourglass for 30 seconds or so, but I did not have
    activity on the Lights applet in the Tray.  I attempted to move the
    mouse cursor but it was frozen in place.  I tried CTRL-ALT-DEL to no
    avail.  I ended up power cycling to restart the system.
    
    The top few lines of my OFFICE.INI file follows:
    
    [TeamLinks]
    ;
    ;CFCLOGOPTIONS=NEWLOG LOG
    ;
    ;The following is the line I was using this morning to debug - 3/13/97
    ;
    ;CFCLOGOPTIONS=log=e:\temp\tlcfc.log NEWLOG TRACE POPUP STAYOPEN
    ;
    Templates=Telex PROFS SNADS X400F11 X400F12 X400F13 OpenVMS UMC X400
    X400_MNEMONIC X400_NUMERIC X400_TERMINAL IBM_SNADS
    Version=T3.0
    VersionID=T300000
    TeamLinksPath=D:\TEAMLINK
    
    I'm reasonably confident that this is related to the CFCDEBUG options I
    selected (I've added the comment immediately above the actual line used
    for CFCDEBUG.).
    
    I did attempt to start TeamLinks with the CFCDEBUG line commented OUT
    and it starts right away without dialogs and I do, in fact, have 14
    Local File Cabinets showing in InfoMan.
    
    Please advise if additional information is required.
    
    THANKS!!
    
    Rick
    
    
    

The attribute not supported error is a benign error.  Most (all?) of the 
file cabinets do not support all of the attributes that TeamLinks ask the
file cabinet service providers to retrieve.  Everytime TeamLinks asks for
an attribute that is not supported, this error will get logged (with TRACE)
or displayed in a POPUP (with POPUP).  I would suggest removing the POPUP 
option from the log options.  This should reduce the noise. 

						Dave

Your log file path suggest that it may be a redirected drive, is
this the case ?  If it is I suggest that you change it to a directory
on your hard disk.  If this is not possible, please wait more than
30 seconds to give up.  I just tried putting my log file on a file
service.  It worked, but I experienced a couple delays of well over
30 seconds (a few minutes in one case).  

						Dave 

    re: .2
    
    Dave,
    
    No, this system has three hard drives - 2-0.5mb IDE and 1-2gb SCSI. 
    TeamLinks is installed on the IDE drive that is not the boot drive -
    Drive D:.  System is on C:.
    
    Does that change your assessment?
    
    THANKS!!
    
    Rick