Re: Can't Save to Server issue has come back even though UIDs of local users are unique

Actually, none of our systems have had any updates whatsoever since
mid-August. We're using Word 11.2 (060202).

On Oct 18, 1:28 am, "John McGhie [MVP - Word and Word Macintosh]"
<j...@xxxxxxxxxxx> wrote:
Hi David:

Microsoft issued an 11.3 patch for Office that may have arrived
automatically on the client workstations. It seems to have broken a few
networky-things.

Check the About item on the Word menu of one of the workstations. If you
see "Version 11.3 build 060914" that's it. No point looking in Entourage,
it was not updated: it will still show 11.2.5.

I have escalated this to the developers, we'll see what they say.

Sorry to be no help at all.

On 18/10/06 4:33 AM, in article
1161110021.910480.286...@xxxxxxxxxxxxxxxxxxxxxxxxxxxx,



"daviddi...@xxxxxxxxx" <daviddi...@xxxxxxxxx> wrote:
Clients: OSX 10.4.7 (mounting shares via AFP)
Server: OSXS 10.3.7

When we recently migrated to Tiger for our client systems, we
immediately experienced the "can't save to server" issue that is
described at the Word MVPS site
(http://word.mvps.org/Mac/CantSaveToServer.html). I was able to resolve
the issue by changing the local user accounts to unique UIDs. Nothing
has changed in terms of OS or software on neither client nor server
throughout the entire time.

Just recently (last two weeks), the issue seems to have reappeared.
I've been doing some testing and by all appearances, the issue is
identical to when the local UIDs were not unique (eg. I'll open and
close the same file and sometimes it will open as "Read-Only" while
sometimes it will not).

I have verified that the local users do in fact have unique UIDs and
further, I analyzed the ".TemporaryItems" directory on the sharepoints
and I see directories for each of the UIDs (eg. "folders.50000",
"folders.50001", etc.)

What is strange is that the issue appeared to be resolved several weeks
ago but has reappeared even though there has not been any software
changes to neither client nor server. This would lead me to believe
that there is more to the issue than simply UIDs of local users.
However, I haven't seen any postings regarding this issue reappearing
after then fix was posted.

Any ideas on what is going on or how I can look into this further? TIA.--

Please reply to the newsgroup to maintain the thread. Please do not email
me unless I ask you to.

John McGhie <j...@xxxxxxxxxxx>
Microsoft MVP, Word and Word for Macintosh. Business Analyst, Consultant
Technical Writer.
Sydney, Australia +61 (0) 4 1209 1410

.

Relevant Pages