Word Save Problem Since Snow Leopard Upgrade
jayb...@officeformac.com
Operating System: Mac OS X 10.5 (Leopard)
Processor: Intel
Since upgrading to Snow Leopard last week, I am suddenly unable to save a document from Word to a Windows 2003 network file share. Previously, this had worked fine.
The error message I get is:
Word cannot save or create this file. The disk may be full or write-protected.
Try one or more of the following:
Free more memory
Make sure that the disk you want to save the file on is not full, write-protected, or damaged.
Memory is not a problem. This will happen even after a restart and nothing running but Word.
I can save the file to a local folder and then move it to the network share with no problem. I have full administrative access to the network file share.
Any ideas?
jobgeorg
jayb...@officeformac.com
I also see from browsing the list of similar questions on this site, this is a bug that's been around for a while. Why it was activated by my upgrade to Snow Leopard, I don't know.
John McGhie
To "save" a file, Word first writes out the Temp file, then re-names the
"old" file, then re-names the "new" file, then deletes the old file.
If you do not have rename or delete permissions, Word can't save.
I suspect that if you speak firmly to your system administrator, you will
find that either Snow Leopard is not correctly authenticating you so that
your User ID on the server does not have permissions, or that the server is
not assigning a unique Unix ID to your machine.
If either is the case, Word will be unable to save.
Cheers
On 3/09/09 3:55 AM, in article 59b7b...@webcrossing.caR9absDaxw,
"jayb...@officeformac.com" <jayb...@officeformac.com> wrote:
This email is my business email -- Please do not email me about forum
matters unless you intend to pay!
--
John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410
+61 4 1209 1410, mailto:jo...@mcghie.name
Snyder@discussions.microsoft.com Chris Snyder
I was able to save to the same network share under 10.5.
I can copy and rename files on the share just fine using Finder.
I experienced this problem first in Excel, when trying to save to a share at
/Volumes/data1/CompOp. The error dialog that came up said that "Microsoft
Excel cannot access the file 'data1:Compop'. Note the old HFS path notation
(colon) and the lack of Volumes in the path. Either or both of these things
could be trouble.
I don't think this is an admin issue, John. Have you actually tried saving a
file from Office 2008 to a network share? Did it work?
jayb...@officeformac.com
John McGhie
Yes, I have, and yes it does.
But the server I am saving to is Windows 2003 R2 server, and they respond
somewhat differently.
This issue is completely maddening, and Microsoft is giving very little
information out on what causes it. They keep saying it's a "Deadlock".
Well, yeah, we knew that...
Sorry, I can't be much help. But if you want to send me a fully documented
repro case, with all the software version numbers, I can fire that in and
see if we can get any further?
Sorry to be no use at all...
Cheers
On 11/09/09 3:14 AM, in article
8ACBA8C5-F6FA-45B1...@microsoft.com, "Chris Snyder" <Chris
u7st...@officeformac.com
John McGhie
"u7st...@officeformac.com" <u7st...@officeformac.com> wrote:
Yeah, I hear you. But I need DETAIL.
The situation is this: There are "sporadic reports" of this problem. But
nothing with enough detail to enable Microsoft to put someone on the job to
find the issue.
What Microsoft needs in order to solve it, is a customer they can work with
who can describe in detail what is happening. If that could be you, then
please send me an email from a real email address.
Until they can get enough detail to enable them to fully diagnose the
problem, they won't be able to fix it.
Cheers
u7st...@officeformac.com
> On 15/09/09 11:44 PM, in article 59b7b...@webcrossing.caR9absDaxw,
Grahm Eberhardt
I can Save As but not Save a file in Illustrator, Photoshop, Word,
Excel, etc. Sounds like a permissions issue involving the
aforementioned temp files. I've got my Network Admin guys looking
into it. If anybody has a fix, I'm all ears.
On Sep 16, 1:10 pm, u7str...@officeformac.com wrote:
> Let me know what detail it is you need, and I'd be happy to give it to you.
>
> > On 15/09/09 11:44 PM, in article 59b7b80...@webcrossing.caR9absDaxw,
> > +61 4 1209 1410, mailto:j...@mcghie.name
John McGhie
Senior Software Engineer in Test) to reconstruct your set-up closely enough
so that he can reproduce the problem .
1. What type of server are you using? (Software levels/patch levels...)
Anything other than OS X and the file system running on the server?
2. Simple mud-map of the folder design on the server
3. Mud-map of the network diagram between the server and the users (nodes,
sub-nodes, any NATs in there, etc)
4. How many concurrent users?
5. Software version and level on the user�s workstation?
6. Network protocols enabled (SMB, AFP etc?)
7. Anything other than Word or Excel running on the user boxes?
Particularly look for things such as �Helpers�: clip-board managers,
TypeItForMe, QuickKeys, SpellCatcher,etc...
8. Anything else you can think of!
That should be enough to get us going. Shaun will be back with some
detailed questions I am sure...
On 17/09/09 4:10 AM, in article 59b7b...@webcrossing.caR9absDaxw,
John McGhie
I have a "hunch" � let's try it...
I am GUESSING that OS X is running out of file handles because you never log
off?
Try logging off at the end of the day! That's what I do, and I have never
seen the problem, either on a Windows server or in Mac OS X.
A more advanced fix is to shut down the computer, count to ten, then bring
it back up again. This runs some Unix house-keeping tasks that do a more
extensive cleanup of the system. You should need to do this only when Apple
puts out an update that forces a restart.
Cheers
On 17/09/09 6:15 AM, in article
bdf81665-8abb-4fce...@g6g2000vbr.googlegroups.com, "Grahm
Eberhardt" <grah...@gmail.com> wrote:
--
+61 4 1209 1410, mailto:jo...@mcghie.name
MTR@discussions.microsoft.com Dan MTR
The Mac's in my office are having the same issue since our snow leopard
update last week. All permissions are set properly, Users simply are not able
to save via Office 2008 apps. Files must be saved locally then copied over.
Has any progress been made on this issue?
John McGhie
Just to set an expectation...
I don't think anyone in the Word or Office applications area is looking at
this issue.
I have not heard anything from the Microsoft engineer who was investigating
it, but I suspect he found that it's Apple's issue to solve.
It would be worth talking to a Network Engineer who knows how to run a trace
on the network to see what, exactly, is going wrong. Because it is a rare
condition that seems to affect only a small proportion of networks where the
configurations are done in a very specific way.
To see if I am correct, logon one of those users onto their workstation with
full (Network Administrator) rights. I think you will find the problem goes
away.
In which case, it's a problem with the permissioning of one of several
folders that Word uses while it has a document open. Chances are it is one
of the hidden folders, since the problem is not immediately apparent.
While working, Word holds up to 30 files open for each document it has open.
It needs to be able to read/write/rename/remove any of them. If the user
has been copying and pasting, Word does not release its lock on some files
while data remains on the clipboard.
Hope this helps
On 29/09/09 5:08 AM, in article
C99E7250-96D1-4135...@microsoft.com, "Dan MTR" <Dan
M...@discussions.microsoft.com> wrote:
--
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:jo...@mcghie.name
jrb
my network shares and then reconnecting with cifs. Since doing that the
problem has gone away.
John McGhie
Ooohhh!! That's a keepie :-)
How were the shares connected before?
You may have found the key that unlocks this puzzle...
{Grasping desperately at straws here...)
Cheers
On 2/10/09 3:16 AM, in article
DFE78401-DA25-4654...@microsoft.com, "jrb"
Jason
> What we need is to get enough detail to enable Shawn Larson (the Microsoft
> Senior Software Engineer in Test) to reconstruct your set-up closely enough
> so that he can reproduce the problem .
>
> 1. What type of server are you using? (Software levels/patch levels...)
> Anything other than OS X and the file system running on the server?
> 2. Simple mud-map of the folder design on the server
> 3. Mud-map of the network diagram between the server and the users (nodes,
> sub-nodes, any NATs in there, etc)
> 4. How many concurrent users?
> 5. Software version and level on the user¹s workstation?
> 6. Network protocols enabled (SMB, AFP etc?)
> 7. Anything other than Word or Excel running on the user boxes?
> Particularly look for things such as ³Helpers²: clip-board managers,
> TypeItForMe, QuickKeys, SpellCatcher,etc...
> 8. Anything else you can think of!
>
> That should be enough to get us going. Shaun will be back with some
> detailed questions I am sure...
>
>
> "u7str...@officeformac.com" <u7str...@officeformac.com> wrote:
> > Let me know what detail it is you need, and I'd be happy to give it to you.
>
>
> This email is my business email -- Please do not email me about forum
> matters unless you intend to pay!
>
> --
>
> John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
> McGhie Information Engineering Pty Ltd
> Sydney, Australia. | Ph: +61 (0)4 1209 1410
Hi John,
I too am experiencing problems with Mac:office 2008. I am working on
an exchange server 2007 environment. I have a macBook Pro, 4GB ram,
2.4 Ghz. Before I upgraded to os 10.6 everything worked fine. Now, I
get an error when I try to save as a backward compatible file (word,
excel) such as the **.xls format when I am saving to a network share
location. I've called apple support and they didn't know anything
about it, and I called mac:office tech support and they couldn't tell
me anything either. Here are the best answers I have for your
questions:
1. What type of server are you using? (MS exchange 2007)
Anything other than OS X and the file system running on the server?
(not applicable)
2. Simple mud-map of the folder design on the server (//eden/
officefiles/Publishing/PO Files/00 - PO Files/)
3. Mud-map of the network diagram between the server and the users
(I'm not sure how to give you this information. The server has a main
switch at the server, and then a secondary switch for my wing of the
building, and finally I have a switch at my desk that connects my
laptop and my phone. If I connect wirelessly it's the same setup,
except the wireless device is connected to the local switch for my
wing of the building)
4. How many concurrent users? (Typically 75)
5. Software version and level on the user¹s workstation? (Snow Leopard
10.6.1)
6. Network protocols enabled (Not sure)
7. Anything other than Word or Excel running on the user boxes? (It
happens whether there are other software running or not - I clean my
running programs and still there are problems, but here's a screenshot
of my current running programs
271 AirPort Base Station Agent jworf 0.0 4 912 KB Intel (64 bit) 22.6
MB
361 AppleSpell.service jworf 0.0 2 6.6 MB Intel (64 bit) 29.1 MB
2798 DashboardClient jworf 0.0 5 10.2 MB Intel (64 bit) 172.1 MB
2797 DashboardClient jworf 0.0 5 5.7 MB Intel 37.8 MB
238 Dock jworf 0.0 4 20.9 MB Intel (64 bit) 28.0 MB
240 Finder jworf 0.0 5 30.0 MB Intel (64 bit) 41.7 MB
256 fontd jworf 0.0 2 3.5 MB Intel (64 bit) 30.0 MB
277 iTunes Helper jworf 0.0 3 5.1 MB Intel (64 bit) 41.2 MB
234 launchd jworf 0.0 2 796 KB Intel (64 bit) 37.9 MB
40 loginwindow jworf 0.0 3 10.3 MB Intel (64 bit) 33.7 MB
6421 mdworker jworf 0.0 3 3.5 MB Intel (64 bit) 30.6 MB
244 pboard jworf 0.0 1 380 KB Intel (64 bit) 18.5 MB
278 Quıcĸsıɩⅴεʀ jworf 0.0 3 17.0 MB Intel 27.0 MB
6393 Safari jworf 0.0 8 76.0 MB Intel 75.5 MB
239 SystemUIServer jworf 0.2 3 16.0 MB Intel (64 bit) 61.5 MB
265 UserEventAgent jworf 0.0 3 4.1 MB Intel (64 bit) 32.6 MB
8. Anything else you can think of! (nada)
Also, when I got the apple site to report the bug, the site says there
was an error and the webpage won't show up (the site shows up, but
when I click the button to start entering the issue thats when it says
there is an error).
In addition to the problems mentioned above I am also experiencing
problems copying excel files from my local drive to the network share
(which I have full administrative privileges to). It allows me to copy
the file, but says the file that I copied has errors. Usually I'm able
to open the file, but once it totally corrupted the file.
I hope you can help.
Thanks,
Nos...@officeformac.com
I am having the same problem with Word 2004. One chapter in my PhD has embedded xl files and crashes on manual or auto save and no recovered document. File dates revert to US format in folders and keep changing. Changed the file to RTF then renamed on a different computer changed back to .doc made no difference. Please can someone help?
John McGhie
I have sent that off to Microsoft to see if they can add anything.
One user came up with an interesting work-around: he dismounted all his
network drives, shut down the AFP service, then reconnected them all using
SMB/CIFS.
Apparently it worked.
BTW: You are not saving to an "Exchange Server", both you and the Exchange
Server are using a "File Server" somewhere. It would be interesting to know
what that is: I am going to take a guess that it's Windows 2008.
Cheers
On 6/10/09 11:48 AM, in article
cf63fa60-703e-4a79...@y10g2000prg.googlegroups.com, "Jason"
<jaw...@gmail.com> wrote:
--
John McGhie
problem :-) You may be getting similar symptoms, but it's not the same
problem: Word 2008 has quite a different engine from Word 2004.
Given that, we need the same kind of detail about your problem as we have on
the 2008 one.
Have you checked your OS settings? It sounds as though some of the OS
settings Word relies on have not been set correctly.
Sorry: No enough detail to begin to help.
On 7/10/09 11:28 AM, in article 59b7b...@webcrossing.caR9absDaxw,
"Nos...@officeformac.com" <Nos...@officeformac.com> wrote:
--
lib...@officeformac.com
John McGhie
The server is not actually aware of the format of the file: all it knows is
that "My document.doc" and "My document.docx" are two DIFFERENT files.
The file server reads the entire string, including the path name, the
period, and the extension, as a single string.
So if the server is holding "My document.docx" locked for some reason, and
you save it as "My document.doc" it's two different files, and they will
indeed save independently.
Or do you mean that you opened "my document.docx", made a change and tried
to save and it wouldn't save. So then you saved it as "my document.doc",
reopened it, made a change, and saved, and this time it saved OK?
If that's what's happening, that's very strange.
Cheers
On 14/10/09 3:51 PM, in article 59b7b...@webcrossing.caR9absDaxw,
"lib...@officeformac.com" <lib...@officeformac.com> wrote:
> I saved the docx and xlsx as doc and xls and I was finally able to save on our
> server at work.
This email is my business email -- Please do not email me about forum
matters unless you intend to pay!
--
John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410
+61 4 1209 1410, mailto:jo...@mcghie.name
HMF
"Maintain"), which fixed the issue for me.
lib...@officeformac.com
lib...@officeformac.com
I will try it on the pptx files that were not saving on the server when I get to work.
John McGhie
OK, that's worth asking a hard question of your Network Administrator.
What are they doing differently for .docx and .xlsx files ?
You won't want to run in downgraded mode for too long: you lose quite a bit
of functionality downgrading a .docx to a .doc. Same with downgrading a
.xlsx to a .xls.
Cheers
On 15/10/09 12:45 AM, in article 59b7b...@webcrossing.caR9absDaxw,
"lib...@officeformac.com" <lib...@officeformac.com> wrote:
This email is my business email -- Please do not email me about forum
gbs
different cities. With or without admin access to the server. On both
Windows 2003 and 2007 server. All running Office 2007 Mac.
"John McGhie" wrote:
> It would be worth talking to a Network Engineer who knows how to run a trace
> on the network to see what, exactly, is going wrong. Because it is a rare
> condition that seems to affect only a small proportion of networks where the
> configurations are done in a very specific way.
>
> To see if I am correct, logon one of those users onto their workstation with
> full (Network Administrator) rights. I think you will find the problem goes
> away.
>
> In which case, it's a problem with the permissioning of one of several
> folders that Word uses while it has a document open. Chances are it is one
> of the hidden folders, since the problem is not immediately apparent.
>
>
John McGhie
How are you authenticating those users? Macs run on the Unix ID. The
default is "503". If they are not authenticating to the Active Directory,
they could have the same Unix ID on each user, which means the file server
thinks the same user is trying to open the file multiple times.
Sorry: You need a Network Engineer...
On 29/10/09 7:52 AM, in article
700AE4A1-D51E-486C...@microsoft.com, "gbs"
<g...@discussions.microsoft.com> wrote:
--
This email is my business email -- Please do not email me about forum
matters unless you intend to pay!
John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
SeanPT
Leopard. My experiences match this thread. It isn't a permissions error on
the server (SMB share in SBS2003) as files can be deleted and added in Finder
just fine.
"jayb...@officeformac.com" wrote:
> Version: 2008
> Operating System: Mac OS X 10.5 (Leopard)
> Processor: Intel
John McGhie
Word also needs "Execute" permissions to the folders involved (for the
document, the backup, and the Temp files).
A Word "Save" is actually a sequence of Write, Rename, Rename, Delete (which
is also a rename).
First it writes the file to a Temp file, then Renames the Current as the
Backup, then renames the Temp to the Current, then Deletes (re-names) the
Backup.
To test this, log the user on as a network administrator and try the
operation. I bet it succeeds...
Cheers
On 20/11/09 3:19 PM, in article
ADDE821B-057F-41F7...@microsoft.com, "SeanPT"
<Sea...@discussions.microsoft.com> wrote:
Jay2k1
I have the same issues. Let me tell you all some details.
I am a sysadmin. Our file server is a CentOS 5 (RedHat-like) Linux with
Samba on ext3 FS. The relevant smb.conf settings:
create mask = 0775
directory mask = 0775
force create mode = 0775
force directory mode = 0775
Most of the Mac users here still use Office X or 2004 and OS X 10.4 or 10.5.
Now we have a new Macbook w/ 10.6 (Snow Leopard) and Office 2008. I don't
know about Word or PPT, but when trying to save an Excel file on a Samba
share on the server, we get that error message that Excel cannot access the
file "sharename:path:otherpath:041A0200" or some other 8-letter random string.
Seems Excel creates a temp file, tries to write to that file and presumably
renames it afterwards. The file actually is created but has 0 byte.
Interestingly, when I try to save as 97-2004 file (.xls) it works
flawlessly. Just the default setting (.xlsx) keeps failing with the mentioned
error.
Also, as others said before, I can save new/existing/other files, rename
them, edit them, delete them etc. without any problem from within any other
application on that macbook. it's just the Office apps that show these issue.
Perhaps this helps the MS engineers track down the issue (different methods
used when saving another format?)
CTICompServ
> Just wanted to add that this problem also applies to Adobe products.
> I can Save As but not Save a file in Illustrator, Photoshop, Word,
> Excel, etc. Sounds like a permissions issue involving the
> aforementioned temp files. I've got my Network Admin guys looking
> into it. If anybody has a fix, I'm all ears.
>
What Adobe version are you having trouble with? I'm using Adobe CS3 and
don't have that problem.
Kent
CTICompServ
files to our Windows server volumes. It worked with Leopard but not with
Snow Leopard. I can, however, save docx and xlsx files to the same volumes.
Kent
CTICompServ
files to my home folder on a Windows volume.
CTICompServ
Kent
MTR@discussions.microsoft.com Dan MTR
We have had this issue since "upgrading" to Snow Leopard.
Connecting with SMB, AD Accounts Have "Full Permissions" to File Shares
Running on Server 2003 R2.
No Issues Previously on Leopard.
Effects Word and Excel files of doc, docx, xls, and xlsx
I've heard that NFS shares may work, but have yet to implement...
...Does this help anything. -Dan
Joshua
wrote:
For those who are still troubled by this problem....
I had the same problem of not being able to edit and save files on a
samba shared folder using links/aliases in the side bar etc that
existed before upgrading to Snow Leopard.
I am now able to save these files after disconnecting and reconnecting
to the samba shares and recreating the links/aliases. To be exact, I
ejected the mounted network folders and connected again using Connect
As in the finder window after navigating to the folder on the server.
My guess is that the Snow Leopard upgrade missed some updating on
previously saved links to network folders such that applications are
not able to save directly into the shared folders but users can move
the files manually into these shared folders.
jbassett
Had the issue with saving Microsoft Office 2008 files back to the shared
drive of a Microsoft Windows XP Home machine. Had not performed an update of
the Mac but had rebuilt the Microsoft Windows machine, only this time I had
placed the shared folder inside the users My Documents directory.
The work failed to save from the Mac but was saving fine when mounted on
another Microsoft Windows machine.
Turns out that prior to the Microsoft Windows rebuild, the share was at the
root of C:\. Whereas after the rebuild I placed the share in the users My
Documents directory. By moving the share back to the root of C:\ all is now
well.
My guess is that for some reason the Microsoft Windows share is superimposing
restrictions upon the shared folder if it is inside the home directory of
some particular user.
John McGhie
All of the folders on a Windows machine are restricted by the privileges of
the user ID that owns them.
Nothing should ever by in the root of the C drive in a modern Windows
Machine: that space is all owned by the System and would require you to pass
the Administrator password across the network, which is a security no-no.
The other reason is that the Windows disk format has a hard limit on how
many objects can be in the root of a drive.
In modern versions of Windows, all user data should be under a user ID
within "Documents and Settings". If you move stuff there, you would then
need to create a Share for that location, re-log the Mac on to that
location, and move the files in from the Windows machine so they pick up the
correct permissions.
Cheers
On 4/02/10 11:17 PM, in article a320e339d66d2@uwe, "jbassett" <u57993@uwe>
wrote:
This email is my business email -- Please do not email me about forum
matters unless you intend to pay!
--
Cpun
to a SMB share from Office 2008 and it gives me that error "This file is
write-protected."
All the users have the correct permissions set up and this issue doesn't
happen in Leopard or Tiger.
I just got off the phone with Apple and they had me try opening an Excel
document off the SMB share into Numbers and it was able to save onto the SMB
share with no problems, but when using Microsoft Office 2008 to save it, it
gives me the error "The file is write-protected."
Could this be a Microsoft thing or a Snow Leopard thing?
"John McGhie" wrote:
> .
>
Jim Gordon Mac MVP
the problem also affects Adobe products, so I am pretty sure it's a
problem that Apple will have to solve.
More info here:
http://word.mvps.org/Mac/CantSaveToServer.html
-Jim
--
Jim Gordon
Mac MVP
Co-author of Office 2008 for Mac All-in-One For Dummies
http://tinyurl.com/Office-2008-for-Dummies
dbayer
Client is running Word 2008 on Snow Leopard. System shipped with Snow
Leopard - this is not an upgrade. System is integrated with Active Directory
and user logs in using the AD account.
Server is running Windows Server 2003 R2 64-bit.
Word 2008 can save to the Windows server in .docx format with no problems.
The same file (or any other) saved to the same location in .doc format
generates this error. Saving the file to a Linux/Samba server works with
either format.
John_McGhie_[MVP]@officeformac.com
How are you connecting to that server? Word 2008 is generally fine with
Windows 2K3 servers, but you need an SMB connection, not AppleTalk.
Cheers
On 4/06/10 1:07 AM, in article
65A80318-5C7E-41FB...@microsoft.com, "dbayer"
<dba...@discussions.microsoft.com> wrote:
--
The email below is my business email -- Please do not email me about forum
matters unless I ask you to; or unless you intend to pay!
John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410 | mailto:jo...@mcghie.name