AFS v.3.6_2.5 Base for Win2K

John W. Sopko Jr. sopko@cs.unc.edu
Wed, 31 Jan 2001 08:34:55 -0500


I believe this is related to the following issue:

"John W. Sopko Jr." wrote:
> 
> We had this problem. I opened a call with Transarc, TR-61250, the
> fix was to remove the value "TransarcAFSDaemon" from the following
> registry key:
> 
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\NetworkProvider\Order\ProviderOrder
> 
> ONLY remove the "TransarcAFSDaemon" value not the entire key! Our
> values were:
> 
>         :REG_SZ LanManWorkstation,TransarcAFSDaemon
> 
> Leave the LanManWorkstation value!
> 
> This has the side effect of disabling the obtain token at login,
> you have to obtain the token manually.
> 
> We did not know what was causing the problem, Transarc indicated that
> machines using GINA had this problem but we do not use GINA. I
> just checked with our Windows admin, the systems we were having problems
> with both have SMS on them.
> 
> I suspected there was a problem with the services.exe, I will get
> our admin to try the services.exe hot fix.
> 
> Bo Tretta wrote:
> >
> > Hi,
> >
> > The new AFS client 3.6 works great under Windows 2000 as does Microsoft
> > SMS 2.0.
> >
> > However, the issue is that if SMS 2.0 is installed, the provided AFS
> > installer hangs at setup /SMS.
> >
> > If the AFS client exists on a system, then the SMS client installation
> > may
> > fail to complete and hangs the computer.  If the install completes, upon
> > system restart, a window appears on top that indicates that
> > winnt\system32\services.exe terminated unexpectedly with status code
> > 128.
> >
> > I would like to know if Transarc or anyone else has received other
> > reports of this apparent conflict and can suggest a remedy.  I am
> > completely behind the AFS client
> > availability but this development throws a real kink into our protective
> > measures compliance and SMS deployment plans.
> > --
> > Bo Tretta
> >  PH#  :  3-4496
> >  M/S  :  600-174
> >  Note : "Opinions expressed herein have not been approved by JPL."
> 
> "Touretsky, Gregory" wrote:
> >
> > We have the same problem. We are working closely with IBM and MS to solve
> > it.
> > For now, we got a hotfix from MS (services.exe) that seems to be fine.
> >
> > Gregory Touretsky
> > IDC Computing / Systems Engineering Group
> > Unix Server Platforms
> > gregory.touretsky@intel.com
> > > (+) 972-4-865-6377, Fax: 04-865-5999
> > iNET: 465-6377, M/S: IDC-1B
> >
> 
> "Buhrmaster, Gary" wrote:
> >
> > Hi,
> >
> > We just recently identified this incompatibility, and plan to
> > report it as a bug to Transarc/IBM when our location reopens
> > at the beginning of the new year.
> >
> > So, you are not alone, and we do not have any bypass at
> > this time.
> >
> > Gary
> >
> > > -----Original Message-----
> > > From: Bo Tretta [mailto:botretta@jpl.nasa.gov]
> > > Sent: Thursday, December 28, 2000 2:49 PM
> > > To: info-afs@transarc.com
> > > Subject: SMS and Win2k AFS Client 3.6
> > >

Dinh Ly wrote:
> 
> Hello,
> 
> After installing this patch, the machine would reboot and a message would
> pop up stating that the services.exe unexpectedly shutdown and the machine
> would restart with an error code 128.  This happens every time until we go
> into safe mode to uninstall the client.  Any suggestions?
> 
> Thanks!
> -Dinh
> 
> -------------------------------
> Dinh Ly
> Qualcomm Inc.
> Corporate IT
> (858) 651-4366 Voice
> (858) 442-0722 Mobile
> (858) 636-9807 Pager

-- 
John W. Sopko Jr.               University of North Carolina
email: sopko@cs.unc.edu         Computer Science Dept., CB 3175
Phone: 919-962-1844             Sitterson Hall; Room 135
Fax:   919-962-1799             Chapel Hill, NC 27599-3175