[OpenAFS] Problems with 1.3.61 in Windows 2000

[James Burns]

I don't know, but that key didn't exist at all. The OS was a 98 -> 2000 
upgrade which still plagues me with weird stuff from time to time I think.

-James

On Thu, 25 Mar 2004, Jeffrey Altman wrote:

> The failure to have any RPC support on your machine at all is the cause 
> of the
> AFS Client Service failing to start.
> 
> Now the big question is "why did your system not have any RPC transport
> protocols installed"?
> 
> Jeffrey Altman
> 
> James Burns wrote:
> 
> >That worked perfectly. Thank you so much! Any idea about the server error? 
> >I'm figuring that it's some old file or registry entry, but I removed all 
> >the related ones I could find before installing 1.3.61.
> >
> >-James
> >
> >On Wed, 24 Mar 2004, Jeffrey Altman wrote:
> >
> >
> >>In particular, you should have this in the registry:
> >>
> >>      ----- cut here ---------
> >>      REGEDIT4
> >>
> >>      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\*RPC*\ClientProtocols]
> >>      "ncacn_np"="rpcrt4.dll"
> >>      "ncacn_ip_tcp"="rpcrt4.dll"
> >>      "ncadg_ip_udp"="rpcrt4.dll"
> >>      "ncacn_nb_tcp"="rpcrt4.dll"
> >>      "ncacn_http"="rpcrt4.dll"
> >>      ----- cut here --------- 
> >>
> >>
> >>
> >>Jeffrey Altman wrote:
> >>
> >>
> >>>Can you specify what keys, values and data are specified in the 
> >>>registry by
> >>>
> >>>       HKLM\SOFTWARE\Microsoft\Rpc
> >>>
> >>>and its children? 
> >>>
> >>>Jeffrey Altman wrote:
> >>>
> >>>
> >>>>RPC appears to be disabled on your machine.
> >>>>AFS requires the use of RPC.  There is no way that AFS could run on it.
> >>>>
> >>>>Error code 1719 is "There are no protocol sequences".  This is a windows
> >>>>error indicating that RpcServerUseAllProtseqs() has failed. 
> >>>>
> >>>>The reason that afslogon.dll is taking a while to succeed is that it is
> >>>>attempting to start the AFS Client Service which won't start.
> >>>>
> >>>>What policy has been applied to your machine that prevents the loading
> >>>>of RPC Protocols implementations for TCP/IP, NETBIOS, etc.
> >>>>
> >>>>Jeffrey Altman
> >>>>
> >>>>
> >>>>
>