Re: Another victim of the Word-not-resaving-to-server problem
- From: Beth Rosengard <bethrosengard@xxxxxxxxxxxxx>
- Date: Fri, 06 May 2005 10:18:40 -0700
Hi "emerymat",
I assume you checked out this article (not that I expect it will help much):
<http://word.mvps.org/MacWordNew/Can%27tSaveToServer.htm>. (If using
Safari, hit Refresh once or twice; better yet, use another browser.)
The best I can do is escalate your post to Microsoft although in the case of
the can't-save-to-server issue with Novell Netware, the workaround
ultimately came from Novell.
As for updating to Tiger as a solution, I wouldn't advise it at this point.
We have received no feedback to date that this would help (it's too soon).
Have you asked Apple about this?
If I get any further information, I'll post back here and I would appreciate
it if you would do the same!
--
***Please always reply to the newsgroup!***
Beth Rosengard
MacOffice MVP
Mac Word FAQ: <http://word.mvps.org/MacWordNew/index.htm>
(If using Safari, hit Refresh once or twice or use another browser.)
Entourage Help Page: <http://www.entourage.mvps.org>
On 5/6/05 9:04 AM, in article
1115395489.830166.154110@xxxxxxxxxxxxxxxxxxxxxxxxxxxx, "emerymat"
<memery@xxxxxxxxxxxxxx> wrote:
> Hi!
>
> Here in my office we seem to be another victim of Word's inability to
> re-save an existing file to the file server. When a user hits save on
> such a file, they get one of the already discussed errors on this
> issue, and then are told they need to save to a new file name if they
> try to save again. However, as an interesting twist, the data is
> infact saved correctly. After this error occurs, when viewing the
> directory in the Finder, the file seems to have disappeared. But if
> you disconnect from the share and then reconnect, the file is back and
> does contain the changes from the seemingly-unsuccessful save.
>
> We are running Mac OS 10.3.9 and Office 2004 (Word version "11.1
> (040910)").
>
> Our file server is a Linux machine serving a share via the AppleShare
> protocol. I am not the SysAdmin of that machine, and so I do not know
> what versions/builds of OS, etc, are on the file server.
>
> I've already investigated a few solutions:
> 1. Turning Always Backup ON and Fast Saves OFF -- no fix
> 2. Checking the entire share's permissions that they are set to
> -rwxrwxrwx (read, write, and execute permissions on for owner, group,
> and all) -- these are set, no fix
> 3. I tried deleting the Temporary Items folder as suggested in another
> post, but when I used Word again, it reappeared. (Again, not being the
> SysAdmin on the Linux file server, I can't myself check in to how we
> could prevent non-root users from creating a new directory)
>
> So, a few questions:
> --First, any ideas?
> --Second, does this problem get fixed if we were to upgrade from 10.3.9
> to Tiger (10.4)?
> --Third, would the problem go away if we were to switch the share from
> being accesed via AppleShare to being accessed via NFS or SMB or some
> other protocol? (This is not an immediately achievalble solution since
> we still have a couple machines on the network that are on OS 9 that
> need access to the same files; I understand if the OS X machines were
> using something other than AppleShare and the OS 9 machines use
> AppleShare, we're likely to get corrupt files).
>
> Help!
>
.
- References:
- Another victim of the Word-not-resaving-to-server problem
- From: emerymat
- Another victim of the Word-not-resaving-to-server problem
- Prev by Date: Re: Images on left column of page not printing in Word 2004
- Next by Date: Re: Date not being updated in Word 2004
- Previous by thread: Another victim of the Word-not-resaving-to-server problem
- Next by thread: Controlling Word 98 in Classic with AppleScript
- Index(es):
Relevant Pages
|