Saving Word 2008 onto Network Home

[sdahlin]

I've been banging my head against this off and on for over 2 days
now. I know it's an old issue (the .TemporaryItems fix worked with
Office 2004), but I can't get rid of it.

We have over 900 users, all with networked homes shared via afp from a
server running 10.5.4. Users can save a Word (version 12.1.1)
document the first time, but the second time they hit save, we get the
classic "Word cannot save this document due to a naming or permissions
error on the destination volume" error.

All of our networked home directories were moved to a new server last
month (new xserve), and when this error came back the first time I
redid the .TemporaryItems fix. This didn't fix anything in 10.5.

Any and all assistance would be greatly appreciated.

- Steve Dahlin

 

[John McGhie]

We have nothing other than this to offer:
http://word.mvps.org/Mac/CantSaveToServer.html

Before doing that, run "Repair Permissions" on a machine and see if that
fixes it. It probably won't.

Sorry: It appears this is a hard one: there is no sign of a fix to it yet.
Make sure Office is fully updated (there was a patch came out today...)

Cheers

I've been banging my head against this off and on for over 2 days
now. I know it's an old issue (the .TemporaryItems fix worked with
Office 2004), but I can't get rid of it.

We have over 900 users, all with networked homes shared via afp from a
server running 10.5.4. Users can save a Word (version 12.1.1)
document the first time, but the second time they hit save, we get the
classic "Word cannot save this document due to a naming or permissions
error on the destination volume" error.

All of our networked home directories were moved to a new server last
month (new xserve), and when this error came back the first time I
redid the .TemporaryItems fix. This didn't fix anything in 10.5.

Any and all assistance would be greatly appreciated.

- Steve Dahlin

--

Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Microsoft MVP, Word and Word:Mac
Nhulunbuy, NT, Australia. mailto:[email protected]

 

[sdahlin]

Thanks for your quick reply.

No, unfortunately the latest update to 12.1.2 didn't fix any of our
issues. Neither did repairing the permissions. Since these are
Active Directory users, the all have a unique user id.

Is no one else having this issue? With all the money we spent to
upgrade to 2008, I'd hate to see us have to try to get everyone to use
Pages.

Thanks again for the reply, if nothing else it helped me narrow it
down.

 

[John McGhie]

No, not everyone is having this problem. Only the users on a network

Sorry! Microsoft blames Apple. Apple blames Microsoft. You know the
finger-pointing game? I wonder if anyone has managed to make it Cisco's
fault yet?

I believe this is OS X version-dependant. If you have any flexibility in
that area, that's the next thing to try.

If you find an answer PLEASE share it in here

Sorry.

Thanks for your quick reply.

No, unfortunately the latest update to 12.1.2 didn't fix any of our
issues. Neither did repairing the permissions. Since these are
Active Directory users, the all have a unique user id.

Is no one else having this issue? With all the money we spent to
upgrade to 2008, I'd hate to see us have to try to get everyone to use
Pages.

Thanks again for the reply, if nothing else it helped me narrow it
down.

--

Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Microsoft MVP, Word and Word:Mac
Nhulunbuy, NT, Australia. mailto:[email protected]

 

[Curtis]

This is happening to me too, and about 800 other people on my network. It's
totally unacceptable.

Has anyone tried to unmount and run diskwarrior on the affected volume?

 

[Curtis]

Well, the .TemporaryItems folder creation worked, so far. I'll keep you
updated if anyone's checking this.

 

[John McGhie]

Hi Curtis:

We're checking. Every day.

More detail would be very helpful: not everyone in here has your level of
technical skill. It would be great if you added enough detail so the
secretary at some small startup company can do it by herself.

Cheers

Well, the .TemporaryItems folder creation worked, so far. I'll keep you
updated if anyone's checking this.

--
Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Microsoft MVP, Word and Word:Mac
Sydney, Australia. mailto:[email protected]

 

[Curtis]

John,

While I would strongly suggest that the administrative assistant does not
have access to the sudo password, the fix is pretty easy. I implemented it
on Friday and could no longer replicate the problem. Monday (tomorrow) will
be the real test to see if it works well.

When using network homes, the directory containing the user folders is
mounted. At the root level of that directory, M$ uses a folder called
..TemporaryItems to write and cache certain things. Leave it up to M$ to
hard-code a cache to the network instead of something like /tmp on the local
machine. Anyway, if the path to the home directory is
/Volumes/DirHost/username, you would create .TemporaryItems at the root level
of the DirHost directory.

To make it easy and if you have access to it, open terminal from the machine
hosting the network homes. If you don't have physical access, you could
always SSH in. In terminal, navigate to the DirHost directory (or whatever
your user home directory is called) and type this:

sudo mkdir .TemporaryItems
sudo chmod 1770 .TemporaryItems

Of course you'll have to know the root password, etc. You could also change
the group ownership to .TemporaryItems (sudo chgrp group_name) if all of your
users belong to the same group, but i haven't done that yet. I'm sure it's
more secure, but i wanted to see if this would work first. Plus I have a
pretty extensive AD/OD setup going on, so i didn't want to throw the group
ownership variable in the equation just yet.

I hope this works for you!! Please let me know how things go.

Curtis

 

[Curtis]

Also, here's some system info of what we have:

Network homes are hosted on xraid connected to 10.5.4 xserve bound to AD.
The clients are all 10.5.4 and Office versions range from 12.1.1 to 12.1.2.

Curtis

 

[sdahlin]

John,

While I would strongly suggest that the administrative assistant does not
have access to the sudo password, the fix is pretty easy.  I implemented it
on Friday and could no longer replicate the problem.  Monday (tomorrow)will
be the real test to see if it works well.

When using network homes, the directory containing the user folders is
mounted.  At the root level of that directory, M$ uses a folder called
.TemporaryItems to write and cache certain things.  Leave it up to M$ to
hard-code a cache to the network instead of something like /tmp on the local
machine.  Anyway, if the path to the home directory is
/Volumes/DirHost/username, you would create .TemporaryItems at the root level
of the DirHost directory.  

To make it easy and if you have access to it, open terminal from the machine
hosting the network homes.  If you don't have physical access, you could
always SSH in.  In terminal, navigate to the DirHost directory (or whatever
your user home directory is called) and type this:

sudo mkdir .TemporaryItems
sudo chmod 1770 .TemporaryItems

Of course you'll have to know the root password, etc.  You could also change
the group ownership to .TemporaryItems (sudo chgrp group_name) if all of your
users belong to the same group, but i haven't done that yet.  I'm sure it's
more secure, but i wanted to see if this would work first.  Plus I havea
pretty extensive AD/OD setup going on, so i didn't want to throw the group
ownership variable in the equation just yet.

I hope this works for you!!  Please let me know how things go.

Curtis

I did try the .TemporaryItems folder (the Office 2004 fix), but still
came up with the same errors. Out of desperation, I've made this
folder at the root level of the share and the root level of the user's
home directory, neither of which worked.

We're running the latest version of everything (OS 10.5.4 and Office
12.1.2).

I'm glad you got it to work, but I'm still working on it.

 

[John McGhie]

Hi Curtis:

Many thanks for your detailed explanation.

I was actually asking on behalf of the other people who come here, who need
this information.

Every now and again, I try to chase a Mac Network Administrator in here to
field these questions, but their distaste for NTP tends to the pathological.

I do not have the ability to work with this problem: I don't use network
homes on my network (of three computers...) and the server is a WinTel
box...

At work we use Citrix sessions on WinTel servers...

Thanks for your effort.

Also, here's some system info of what we have:

Network homes are hosted on xraid connected to 10.5.4 xserve bound to AD.
The clients are all 10.5.4 and Office versions range from 12.1.1 to 12.1.2.

Curtis

--
Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Microsoft MVP, Word and Word:Mac
Sydney, Australia. mailto:[email protected]

 

[sean32767]

John,

While I would strongly suggest that the administrative assistant does not
have access to the sudo password, the fix is pretty easy.  I implemented it
on Friday and could no longer replicate the problem.  Monday (tomorrow)will
be the real test to see if it works well.

When using network homes, the directory containing the user folders is
mounted.  At the root level of that directory, M$ uses a folder called
.TemporaryItems to write and cache certain things.  Leave it up to M$ to
hard-code a cache to the network instead of something like /tmp on the local
machine.  Anyway, if the path to the home directory is
/Volumes/DirHost/username, you would create .TemporaryItems at the root level
of the DirHost directory.  

To make it easy and if you have access to it, open terminal from the machine
hosting the network homes.  If you don't have physical access, you could
always SSH in.  In terminal, navigate to the DirHost directory (or whatever
your user home directory is called) and type this:

sudo mkdir .TemporaryItems
sudo chmod 1770 .TemporaryItems

Of course you'll have to know the root password, etc.  You could also change
the group ownership to .TemporaryItems (sudo chgrp group_name) if all of your
users belong to the same group, but i haven't done that yet.  I'm sure it's
more secure, but i wanted to see if this would work first.  Plus I havea
pretty extensive AD/OD setup going on, so i didn't want to throw the group
ownership variable in the equation just yet.

I hope this works for you!!  Please let me know how things go.

Curtis

Thank you Curtis for this -- totally driving me nuts.

Just one think to add to people who are having problems with this as
Curtis wrote. I followed the instructions to a T and no luck. I did a
chgrp groupname .TemporaryItems and it worked perfectly! Obviously
change groupname to whatever group your users are in.