jeffery.dowell at duke.edu
Fri May 8 09:22:07 EDT 2015
Just to close the loop on this one. We found that the conflicting DLL (Krb5_32.dl) was put into C:\windows\sysWOW64 by a Library program called ALEPH. Apparently it is a somewhat commonly used Library system so this knowledge might help others who run into similar issues.
From: Jeffrey Altman [mailto:jaltman at secure-endpoints.com]
Sent: Monday, May 4, 2015 1:51 PM
To: Jeffery Dowell; Kerberos at mit.edu
Subject: Re: gssapi32.dll
On 5/1/2015 3:32 PM, Jeffery Dowell wrote:
> Here are the properties on the file:
> Kerberos v5 - MIT GSS / Kerberos v5 distribution
> Version 18.104.22.168
> Product Name: MIT Kerberos v5
> Size: 372KB
> Date modified: 10/17/2009
This is really old. It predates KFW 3.0.
> It is actually found in C:\windows\sysWOW64 on very few of our computers.
SysWOW64 is the directory used to hold files the were written to
System32 by 32-bit processes on 64-bit Windows.
> The ones that do have the file in that directory had the error message.
That makes sense because the DLL is in the search path and gssapi32.dll
is not linked to krb5_32.dll with an assembly manifest. Therefore, the
first matching file on the PATH will be used.
More information about the Kerberos