Hi,
since 1.7.1 something has happened that causes aklog to complain.
Environment:
Windows 7 x64 Enterprise
OpenAFS 1.7.6
MIT Kerberos for Windows (64-bit) 3.2.2
C:\Users\kexaklog
Kerberos for Windows library krb5_32.dll is not available.
It did work in 1.7.1.
Is this due to
On our 64-bit workstations (Windows 7 Business) it is there. If you
expect a krb5_64.dll: It does not exist. Both, the KfW 32 and 64 bit
version does have krb5_32.dll.
Mit freundlichen Grüßen
Michael Richter
Anders Magnusson ra...@ltu.se schrieb am Thu, 23.02.2012 um 12:40:
Well, it isn't
Hum, it looks like this:
C:\Program Files\MIT\Kerberos\bindir krb5*.dll
Volume in drive C is LTUWin7
Volume Serial Number is B827-4DC5
Directory of C:\Program Files\MIT\Kerberos\bin
2010-09-08 15:26 156 576 krb5cred.dll
2010-09-08 15:26 134 560 krb5cred_en_us.dll
We use a simple modification of this file:
-
http://www.secure-endpoints.com/binaries/mit-kfw-3-2-2/kfw-amd64-3-2-2.msi
And got this:
C:\Program Files\MIT\Kerberos\bindir krb5*.dll
Volume in Laufwerk C: hat keine Bezeichnung.
Volumeseriennummer: 8A2F-020F
Verzeichnis von C:\Program
32-bit aklog.exe requires krb5_32.dll.
64-bit aklog.exe requires krb5_64.dll.
Which are you using?
On 2/23/2012 3:04 AM, Anders Magnusson wrote:
Hi,
since 1.7.1 something has happened that causes aklog to complain.
Environment:
Windows 7 x64 Enterprise
OpenAFS 1.7.6
MIT
C:\path
PATH=C:\oracleinstantclient;C:\Windows\system32;C:\Windows;C:\Windows\System32\W
bem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\MIT\Kerberos\bi
n;C:\Program Files\OpenAFS\Common;C:\Program Files (x86)\OpenAFS\Common;C:\Progr
am Files (x86)\Microsoft Application
On 2/23/2012 9:42 AM, Anders Hannus wrote:
C:\path
PATH=C:\oracleinstantclient;C:\Windows\system32;C:\Windows;C:\Windows\System32\W
bem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program
Files\MIT\Kerberos\bi
n;C:\Program Files\OpenAFS\Common;C:\Program Files
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 while.
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
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
misunderstanding.
On 2/23/2012 10:04 AM, Anders Hannus wrote:
What is the failure that you are receiving during the
There are no changes between 1.7.1 and 1.7.6 to the installer scripts.
On 2/23/2012 11:08 AM, Anders Nordin wrote:
Another Anders here,
Ok something in the path seems to have changed some version(s) ago. This
error seems to be because the x86 is before the 64-bit version in the path?
If
As I asked before, what was the error?
Use the msiexec log to tell you.
On 2/23/2012 2:29 PM, Anders Nordin wrote:
Yes you are correct. I checked our installscript for 1.7.1 and that installs
64-bit first and 32-bit tools afterwards, which explains why it works.
The reason why we switched
On Tue, 21 Feb 2012 10:32:12 +0100
Åsa Andersson sp...@csc.kth.se wrote:
Can you provide the SalvageLog for one of these runs? That is, for the
salvage that you did right after the 'inconsistent length' error.
Here is a typical example:
-
[...]
02/17/2012 13:41:07 CHECKING
12 matches
Mail list logo
