Re: Word Errors

From: John McGhie (john_at_mcghie.name)
Date: 10/24/04 

Date: Sun, 24 Oct 2004 17:37:54 +1000

Mark:

If you know what you are doing with SymLinks, you can alias the temporary
file locations the user needs to the system Temp folder on their local
machine, to which they can be given full access.

If you can work out how to do this, that would seem to be a solution worth
exploring. I am afraid I am not a Unix person, so I don't know how to do
this. But Corentin is, and he should be a long in a moment :-)

Cheers

On 20/10/04 4:33 PM, in article
8c68fd0.0410192233.780b7f42@posting.google.com, "Mark Tovey"
<getmark@sympatico.ca> wrote:

> "Word cannot save this file because it is already open elsewhere"
>
>
> Derrick Seymour <dseymour@mum.neric.org> wrote in message
>
>> Here is the second error I am receiving:
>>
>> Word cannot save this file because it is already open elsewhere.
>>
>> I have found no workarounds for this, let alone any information that could
>> explain how to fix it.
>>
>> Any help would be greatly appreciated.
>
>
>
> I'm experiencing the same issue with OS X Server 10.3.3.
>
> A few notes, which may or may not get us closer to a solution:
>
> - the error occurs only when you have a home directory on a networked
> drive
> - the error occurs only when you are logged into a non-administrative
> account
>
> Two equally unpalatable workarounds suggest themselves:
>
> - create local accounts for users who want to use Word.
> - give all users who need to use Word administrative priviledges.
>
> For one reason or other, Office generally does not deal well with
> users who have home directories on a server. Excel, for instance,
> experienced problems with this prior to the 2004 release (the problems
> were macro-related. There's a Microsoft KB entry on this:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;322237.
> You'll notice that the two suggested solutions in this document
> suggested by Microsoft are similarly impractical:
>
>> To resolve this issue, use either of the following methods:
>
>> • Move the Users folder back to the hard disk partition that contains Mac OS
>> X.
>
> -or-
>
>> • Reformat your hard disk to have a single partition.
>
>
>
> Unfortunately, upgrading to Word 2004 does not fix the "you cannot
> save this file" problem.
>
> Neither, as it turns out does installing the Office for 2004 for Mac
> Service Pack 1.
>
> (I've also upgraded my client machines to 10.3.5, which is supposed to
> improve access to home directories, also without effect.)
>
> In fact, it may not even be a purely Mac problem. I'm wondering if
> the roots of this go back
> further.
>
> Consider, for instance, in the Microsoft KB:
>
> Description of how Word creates temporary files
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;211632
>
> We learn some interesting things, especially that the location of
> temporary files is hardcoded -- quite possibly also the case on the
> Mac. I'm wondering whether this partly explains the fact that
> Administrative users do not have these save issues (ie. they may have
> permissions for directories on the server or on the local drive that
> non-Administrative users do not have, which somehow ameliorates the
> problem)
>
> There are two Microsoft KB entries that mention this error on a
> Windows version of Word. I'm trolling Windows docs for clues because
> there's probably still a certain amount of common code base, and also
> because I'm scraping the bottom of the barrel.
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;832874
>
>> If you open a document in Microsoft Word 2002 that was saved to DocsOpen (a
>> document management program), you may receive the following error message
>> when you try to > save your changes to the document: Word cannot save this
>> file because it is already
>> open elsewhere.
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;832287
>
>> This problem may occur if you have a mapped drive to the same location that
>> your
>> VBA macro is trying to save changes to the document.
>
> Also related to the DocsOpen program, only as accessed through a
> macro.
>
> I have a feeling that we're dealing with some legacy code in the
> ancient heart of Word that still doesn't deal gracefully with
> networked drives. Temporary files may also be a place to look.
>
> My next move is going to be to update to Server 10.3.5 and see if that
> addresses the problem.
>
> Any other thoughts, however small, on this problem would be terrific.
>
> Mark
>
> --
>
> Mark Tovey
> System Administrator
> Cognitive Development Lab
> Carleton University 

-- 
Please reply to the newsgroup to maintain the thread.  Please do not email
me unless I ask you to.
John McGhie <john@mcghie.name>
Consultant Technical Writer
Sydney, Australia +61 4 1209 1410

Relevant Pages

  • Re: Word Errors (Attn: Corentin)
    ... > file locations the user needs to the system Temp folder on their local ... >> I'm experiencing the same issue with OS X Server 10.3.3. ... >> users who have home directories on a server. ... as it turns out does installing the Office for 2004 for Mac ...
    (microsoft.public.mac.office.word)
  • Re: Psystar still kicking Apples ass
    ... Mac OS X systems, Psystar on Thursday has unveiled a pair of Xserve-like ... rackmount computers unofficially based on Apple's Mac OS X Leopard Server. ... without motherboard, interface cards, or hard drives. ... you, I've seen the insides of rack-mountable servers (Mac Xserve, ...
    (comp.sys.mac.advocacy)
  • RE: Move XP machines to new domain preserving home dirs?
    ... Log in to the client as local administrator, ... I have a very small client who runs Windows 2003 server on one machine, ... I had the machine set up with mirrored drives, ... the users still have their same home directories when they log in? ...
    (microsoft.public.windows.server.migration)
  • Problems Accessing Shares on 2003 Standard Server
    ... We have a domain member server we use for file serving on a Windows 2003 ... We share user's home directories and departmental directories. ... users systems who have mapped drives to this system will all lockup ... but you can not map a drive. ...
    (microsoft.public.windows.file_system)
  • Domain Controller Dies, How To Rejoin XP Systems to Domain?
    ... I have a very small client who runs Windows 2003 server on one machine, ... I had the machine set up with mirrored drives, but in this case, ... to get the XP client re-attached to the domain. ... users still have their same home directories when they log in? ...
    (microsoft.public.windowsxp.general)