[OpenAFS] Kerberos for Windows library krb5_32.dll is not available.

Jeffrey Altman jaltman@secure-endpoints.com
Thu, 23 Feb 2012 10:24:03 -0500

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

The 32-bit tools not being upgraded is not the failure.   That is the
result of a failure.  What is the failure?

32-bit tools does not have a cache size to set.  Or perhaps I am

On 2/23/2012 10:04 AM, Anders Hannus wrote:
> What is the failure that you are receiving during the install of the 32=
-bit tools?
> The 32-bit tools are not upgraded. I have however not tried this in a w=
hile. Maybe with 1.7.2 or so.
> The reason to include the regfile at the end is that I also found the a=
 new larger cache size are not used from the mst file then upgrading but =
the current one is used. For installation on a computer with no previous =
afs client the cache size is used though. Might be that my mst file is no=
t working as expected.
> /anders hannus
> Our upgrade script:
> ::Install 32-bit tools f=C3=B6r 32-bit compatibility
> msiexec /q /i "%~dp0openafs-32bit-tools-en_US-1-7-0600.msi" TRANSFORMS=3D=
"%~dp01.7_32bit_tools.mst" /norestart
> ::Install 64-bit client
> msiexec /q /i "%~dp0openafs-en_US-64bit-1-7-0600.msi" TRANSFORMS=3D"%~d=
p01.7.3_64bit.mst" /norestart
> ::If upgrading ensure that LTU settings are applied
> regedit /s "%~dp0AFS_settings_64-bit.reg"
> -----Original Message-----
> From: openafs-info-admin@openafs.org [mailto:openafs-info-admin@openafs=
=2Eorg] On Behalf Of Jeffrey Altman
> Sent: den 23 februari 2012 15:58
> To: Anders Hannus
> Cc: Anders Magnusson; openafs-info@openafs.org; Anders Nordin
> Subject: Re: [OpenAFS] Kerberos for Windows library krb5_32.dll is not =
> On 2/23/2012 9:42 AM, Anders Hannus wrote:
>> C:\>path
>> PATH=3DC:\oracleinstantclient;C:\Windows\system32;C:\Windows;C:\Window=
>> System32\W bem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program =

>> Files\MIT\Kerberos\bi n;C:\Program Files\OpenAFS\Common;C:\Program=20
>> Files (x86)\OpenAFS\Common;C:\Progr am Files (x86)\Microsoft=20
>> Application Virtualization Client;C:\Program Files (x86 )\Kaspersky=20
>> Lab\Kaspersky Anti-Virus 6.0 for Windows Workstations MP4\;C:\Progra m=
>> Files (x86)\OpenAFS\Client\Program;C:\Program=20
>> Files\OpenAFS\Client\Program
>> Thus the 32-bit version are used.
>> Why are the path this way?
>> We found that ugrading the afs klient (with msiexec /i newversion.msi =
/q TRANSFORMS=3DLTUcustom.mst) was not successful for 32-bit tools if the=
y was ugraded after the 64-bit client. Running the installation in the ot=
her order fixed the upgrade problem but left us with a path where the 32-=
bit files are found first.
>> /anders hannus
> The PATH is a result of the order of installation.
> What is the failure that you are receiving during the install of the 32=
-bit tools?
> Note that one of the benefits of the Heimdal package is that it include=
s both 64-bit and 32-bit components in the same installation.
> The OpenAFS installation requires a substantial rewrite to turn librari=
es into assemblies and perform 64-bit and 32-bit installation from the sa=
me MSI.
> Jeffrey Altman

Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

Version: GnuPG v1.4.9 (MingW32)