[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference abbott::teamlinks_windows

Title:TeamLinks for Windows
Notice:Kit and ECO locations: See replies to note 8.o note 8.
Moderator:ORION::chayna.zko.dec.com::tamara::eppesAN
Created:Mon Aug 28 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2238
Total number of notes:9650

2182.0. "Login with a blank username" by KERNEL::BURDENI () Thu May 08 1997 06:31

    I have a customer with a similar problem to Note 1010.  When trying to
    login, if the Username or password field is left blank, and a
    connection is attempted, Infoman appears to hang.
    
    When logging is turned on, the error is trapped and the user is able to
    correct his mistake and login.
    
    He is using 2.7 of TeamlinksMailworks 1.3a and Pathworks 4.1.  I
    suggested that this version of Pathworks should be upgraded. 
    The A1MAIL$CONNECT process is touched, (goes up .2 of a CPU second), and
    then the Teamlinks process hangs. There are no messages whatsoever in 
    the Security log for Mailworks.
    
    Any ideas how I can troubleshoot this further ? 
    
    Ivan.
T.RTitleUserPersonal
Name		DateLines
2182.1I believe it was a DECnet problem.XANADU::x400it.zko.dec.com::manana::roughtThu May 08 1997 13:2015
A few years ago we were able to reproduce a problem that sounds like the
one you are describing.  We had proof (at least we thought so) that it
was a DECnet problem.  The TeamLink's engineer who was working it with the Pathworks
group is long gone, so I am not sure what the final resolution was.  I 
believe it was a timing issue of some sort.  By turning on logging, the
extra IO changes the timing enough to avoid the problem.  Since we heard
only a few reports of this problem and have not heard of it in a couple
of years, I expect it was fixed (or became a non problem) in a later 
release of Pathworks.  The version of Pathworks they are using (V4.1)
sounds about right for the time we saw the problem.

My suggestion is either upgrade Pathworks, run with loggin turned on, or
tell users not to do that.

						Dave
2182.2I will recommend a PWRKS upgrade.KERNEL::BURDENIFri May 09 1997 06:567
    Thanks for that,
    	I guessed it could be a timing issue of some sort, though could not
    think of a way of proving anything.  But your suggestions seem more
    than reasonable.   I will recommend the Pathworks upgrade.
    
    Cheers
    Ivan.