I dont thing the problem is in the afs client. We found this problem only
occurs when opening a file that already has been opened by another user. We
upgraded to office 2003 and it takes alot of time before word gives any
response.
This only seems to happen on the "original" pc's, when trying from our own pc
everything works fine, word opens in read-only mode but that doesnt happen on
these pc's ?
Maybe it has something to do with the fact that they are also running the
netware client. Are there any known issues with this setup ? Should we run afs
before netware ? Maybe check some settings ?
-----Original Message-----
From: Jeffrey Altman [mailto:[EMAIL PROTECTED]
Sent: woensdag 14 november 2007 15:43
To: Hans Melgers
Cc: openafs-info@openafs.org
Subject: Re: [OpenAFS] MS Word crashing when opening files, 1.5.27 client
Hans:
Please follow the debugging section of the OpenAFS for Windows Release Notes.
In particular, use the SysInternals' Process Monitor to log the requests from
Word so that you can determine which requests are failing with 1.5.27 that
succeed with 1.5.25.
One change that went into 1.5.27 is support for retrying requests when the file
server responds to the client with EWOULDBLOCK / EAGAIN. In prior releases the
client would simply fail the request. In 1.5.27 the client retries the request
every two seconds up to 45 seconds until the request completes or the timeout
is reached. In the trace log it is the
cm_Analyze() messages will include the error number. Possible error numbers to
look for include:
UAEWOULDBLOCK 49733416L
UAEAGAIN 49733386L
EAGAIN 11L
Jeffrey Altman
Hans Melgers wrote:
>
> Hello,
>
> We just installed some XP machines with the latest 1.5.27 afs client.
> On several of them Word crashes badly when trying to open a .doc file
> on afs. Most of them running office XP but also seen on office 2003.
>
> I run 1.5.25 and havent seen the problem. Could this be a bug in the
> latest win client ? acl's are ok. Server is 1.4.4 on freebsd 6.2
> Anyone else seeing this behaviour ?
>
> In Filelog i only see some callback issues:
>
> Wed Nov 14 10:56:32 2007 CB: ProbeUuid for 213.46.24.222:17980 failed
> -01 Wed Nov 14 10:57:11 2007 CB: ProbeUuid for 213.46.24.222:17982
> failed -01 Wed Nov 14 10:58:08 2007 CB: ProbeUuid for
> 213.46.24.222:17987 failed -01 Wed Nov 14 10:58:18 2007 CB: ProbeUuid
> for 213.46.24.222:17976 failed -01 Wed Nov 14 11:01:25 2007 CB:
> ProbeUuid for 213.46.24.222:17995 failed -01
>
>
> Any help appreciated.
>
> Hans
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
