[OpenAFS] Problems with 1.3.61 in Windows 2000

[James Burns]

I just tried 1.3.62. It no longer crashes, but makes login take about 5 
minutes. I haven't tried disabling the dll in the registry yet. When it 
did finally start up, it says that the server service started, but when 
trying to configure it I get "Failed to determine the current 
configuration of this machine. Error: Unknown code d 43 
(1067)(0x0000042B)" The client seems to be stuck in the starting state. 
The afsd_init.log shows:

11:52:11 PM: Create log file
11:52:11 PM: Created log file
PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;C:\JDK1.2\BIN;C:\GRAVIS\CORESO~1;C:\PROGRA~1\MCAFEE\MCAFEE~1\MCAFEE~1;F:\cygwin\bin;C:\Program Files\Common Files\Roxio Shared\DLLShared;"C:\Program Files\Symantec\Norton Ghost 2003\";C:\Program Files\Executive Software\Diskeeper\;C:\Program Files\OpenAFS\Client\Program;C:\Program Files\OpenAFS\Common
3/24/2004 11:52:12 PM: osi_InitDebug code 1719
3/24/2004 11:52:12 PM: --- begin dump ---
a - dumping scache - cm_currentSCaches=0, cm_maxSCaches=0
a - dumping cm_hashTable - cm_hashTableSize=0
a - Done dumping scache.
3/24/2004 11:52:12 PM: --- end   dump ---
3/24/2004 11:52:12 PM: UnhandledException : code : 0x80000003, address: 0x77fa144b


--# FV EIP----- RetAddr- FramePtr StackPtr Symbol
  0 .V 77fa144b 00401536 007aff78 00000000 DbgBreakPoint
  1 .V 00401536 7c2e02f7 007affa4 00000000 
  2 .V 7c2e02f7 00000000 007affec 00000000 StartServiceCtrlDispatcherW +1739 bytes
EXCEPTION_BREAKPOINT - continue execution ...

Which seems to be the same error as I was having before.

-James

On Tue, 23 Mar 2004, Jeffrey Altman wrote:

> I just performed a quick audit of the afslogon.c code and fixed several 
> obvious
> problems including the referencing of uninitialized char[] buffers when 
> generating
> strings with sprintf() that most definitely could be the cause of the 
> problem.
> 
> I have uploaded test builds to
> 
>     /afs/athena.mit.edu/user/j/a/jaltman/Public/OpenAFS/
>     http://web.mit.edu/~jaltman/Public/OpenAFS/
> 
>     OpenAFSforWindows-20040323-01.exe
>     OpenAFSforWindows-DEBUG-20040323-01.exe
> 
> Please try them out.
> 
> Jeffrey Altman
> 
> 
> Jeffrey Altman wrote:
> 
> > Fact: the afslogon.dll is loaded by winlogin.exe whenever the 
> > "TransarcAFSDaemon"
> > is listed within 
> > HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\ProviderOrder 
> > "Order".
> > This is true whether or not Integrated Logon is being used.
> >
> > Fact: the afslogon.dll has not been touched by anyone since the 1.2.8 
> > distribution
> >
> > Fact: the 1.3.50  and higher versions of OpenAFS are compiled using 
> > the VS.NET 2003
> > compiler including the buffer overrun detection option.  The 1.2.x 
> > versions were compiled
> > with the VC++ 6.0 compiler which did not have buffer overrun detection.
> >
> > Hypothesis: There are buffer overruns taking place within afslogon.dll 
> > which have always
> > been there and which are only triggered in some environments.  
> > However, previously
> > they were never caught.  Now when they are caught an exception is 
> > thrown which is
> > causing winlogin.exe to halt. 
> >
> > Please install the DEBUG version of the installer from 
> > http://web.mit.edu/~jaltman/Public/OpenAFS/
> > and get me a crash log.  Hopefully this will point out the cause of 
> > the problem.
> >
> > Jeffrey Altman
> >
>