Can't save files to SBS2003 network with Office 2008 on 10.6

[spacedog3k]

I sent in this posting to MacWindows.com and today this tip was posted.

"I had similar problem under Mac OS X 10.5.8; Disabling autosave/autorecover solved the problem."

As I said before, mysteriously my Office install is no longer having problems so I can't test this. If anyone here gets a chance to test this please post your success or failure here.

Thanks,

- Craig

 

[Mopo]

I tried this and it did not solve the issue.

 

[Mopo]

Un-joined my Mac from AD and all the problems went away. I can now access the
share using a "connect to server" smb://server/share and all is well again.
Any idea what the difference is between connecting via SMB to the network
share and connecting to the the share via AD? It is my understanding that
while joined to AD the connection to the share is still SMB based, but
perhaps the data is sent differently?

 

[BSUK]

I'm astounded.
This problem still exists even after updating to 10.6.1 and Office 12.2.1
Come on MS and Apple!! This is a major serious issue that needs resolving.

Feel free to ask for any further details, or let me know if I can be of any
assistance in troubleshooting this.

BSUK.

 

[Diane Ross]

This problem still exists even after updating to 10.6.1 and Office 12.2.1
Come on MS and Apple!!

This is not an official Microsoft forum. We are your peers here and can't do
anything to help with this. Send feedback to Microsoft.

When working in Office, you can use the ³Send Feedback² option under the
Help menu in all of the Office applications or visit

<http://www.microsoft.com/mac/suggestions.mspx>

You do not get a reply, but they do read the feedback.

 

[ajm]

Hello,

I was wondering if anyone besides me has encountered a problem saving Office 2008 documents to a Windows server (SBS2003 SP2, not RC2 in my case) in 10.6.

After upgrading to 10.6 everything seemed to be fine with my Office installation until I tried to save a document that I had opened from a network share. When trying to save a document opened from a Windows share I receive the following error message:

Word cannot save 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

The error in Excel is similar, I have not tried PowerPoint but I would expect the same message.

Needless to say the disk is not write protected and the file is not read only. I can open and edit other files in the same folder in different applications, I can even open Word docs in TextEdit and overwrite the file but Office 2008 will not save the file. If I try to save the file to my local drive after the error message is displayed, Office crashes.

I am connecting to the share through the network browser in the sidebar but have also tried the Connect to Server menu and tried both smb and cifs connections. Neither works.

I have removed and reinstalled Office 2008 and run the updates to 12.2.1, I have reboot several times, repaired disk permissions and run a disk check, all to no avail.

I am trying to connect with a MacBook Pro 2.4 GHz with 4GB or RAM running 10.6

Anyone else having this problem? Anyone else having success?

- Craig

Hi

I had exactly the same issues as you describe. Strangely enough I used the 'Snow leopard cache cleaner' tool and ran the cache cleaner on a medium setting, selecting all suers and system caches. I had to run this twice and you need to restart however after this all the issues with saving MS documents disappeared and I am no able to save files to network shares as I used to.

Hope this helps

Andy

 

[MikeVNS]

Hi Craig

I have the exact same problem , also only since upgrading to Snow Leopard
I can save Docx and xlsx files , but not doc or xls to network shares

Have you found a solution yet ?

 

[Greg_Churm]

Hi Craig

I have the exact same problem , also only since upgrading to Snow Leopard
I can save Docx and xlsx files , but not doc or xls to network shares

Have you found a solution yet ?

I have exactly the same problem. You can copy files to the share, Pages can save files to the share but Office 2004 can not. This is on two iMacs, one upgraded from 10.4.11 and the other from 10.5.8.

 

[dnies65]

I am running Office 2008 and OS 10.6.1 and accessing files on a Windows 2007 Server and I am a domain admin.

I am able to open Office docs from the share and I can save them once, but after that they become read only.

Also I can save a new document to the server share, but as soon as I save the file it is marked read only.

I have verified that MS Office apps are the only programs experiencing this issue and the same user account does not have the issue when accessing shares with OS 10.5 and Office 2008.

Tried the Snow leapard Cache Cleaner and disabling autosave, but neither solution worked.

Anyone else get this resolved?

 

[spacedog3k]

Hi everyone. I have a case open with MS and they are asking about Symantec Anti-Virus on my server. I was wondering if everyone here has an AV client on their computer or server? If not please reply letting me know so I can pass that info along. If so do you have a Symantec product or is it something different?

 

[Howard Brazee]

Hi everyone. I have a case open with MS and they are asking about Symantec Anti-Virus on my server. I was wondering if everyone here has an AV client on their computer or server? If not please reply letting me know so I can pass that info along. If so do you have a Symantec product or is it something different?

My work supplies us with eTrust for both Windows and Mac and requires
us to use it with our home computers as well as our work computers.

--
"In no part of the constitution is more wisdom to be found,
than in the clause which confides the question of war or peace
to the legislature, and not to the executive department."

- James Madison

 

[Carole]

Yes. I am having a similar problem. It won't save almost any documents and
gives me the same error messages. I did find something that seems to work.
It may help (or not) in your situation.
Click on a icon of a document or folder without opening it.
Go to the menu bar across the top of the screen to FILE
Under FILE find GET INFO
This brings up a window. At the bottom is a box entitled "Sharing &
Permissions."
Click the lock icon in the bottom left to unlock it.
Change the privileges to Read & Write for everyone listed there. On my
computer there are three options: one with my name, staff, and everyone.
Staff and Everyone was set at Read Only.
I have had to do this with every folder and document, which is very tedious,
but seems to work.
Hopefully it will work for you.

--Carole

 

[MAC]

Hello, has anybody found a solution to the problem in the meantime or has
received a note of Microsoft regarding the problem?

 

[Rob Schneider]

there were clues in the other replies. did you try anything from what
was suggested?

--rms

www.rmschneider.com

 

[roadtek]

It's been quit a while since anyone replied to this case.
I did some testing and found out the following.
If you connect to your smb share via 10.6x "connect to" command, you won't
be able to save a .doc (same fpr .xls) into this share.
If you install an evaluation copy of Thursby DAVE and do the smb connect
wiith DAVE and try to save this .doc onto the smb share, it will work.
Of course this is no solution to the problem, but I think it's easy to
understand that Apple causes the problem and I have contacted my sales rep to
escalate this to the support dep of apple and have them to do a follow up on
this problem.
regards

Oliver

 

[MAC]

Yes, I have tried it all but nothing has worked. It doesn’t help to change
the authorization manually. When opening and saving the data later on the
problem reoccurs. The data is being saved as write-protected automatically.

 

[MAC]

Anybody found a solution, meanwhile?

Yes, I have tried it all but nothing has worked. It doesn’t help to change
the authorization manually. When opening and saving the data later on the
problem reoccurs. The data is being saved as write-protected automatically.

 

[Crazy_African]

By any chance are these machines bound to active directory? I have this
issue, but it is only on 10.6 machines that are bound to the network. Here is
my issue:

I am having an issue where I can open a docx from a Windows 2003 share, make
a change and save it. The save takes, but the doc immediately becomes
(Read-Only). I can quit Word and re-open the docx, but it stays as
(Read-Only) until I do one of the following three things:

1. Get info on the docx and look at the permissions (No need to change
anything. Just look.)
2. In Terminal, run "ls -l" on the document's location
3. Disconnect the share and connect to it again.

All three restore the ability to save, but only once. Saving turns it into
read only again until you do one of the three steps above.

I can unbind the computer from the domain, de-activate the AD plugin and
delete all local copies of AD accounts, leaving only the local accounts.
After a restart, the problem is gone. Unfortunately, I have to be that
drastic. Unbinding alone does not work. Unbinding and de-activating the
plugin doesn't work. The accounts need to be deleted. Similarly, no AD
accounts, but a bound system is enough to cause the issue. Does this seem
similar?

 

[BSUK]

For anyone's info who may be struggling with this, there is a "fix" that has
been reported.

Set the ownership on the top level folder to "NT-AUTHORITY\NETWORK SERVICE"
You don't need to push the ownership down to the child folders, just the top
level folder needs to be changed.
Mysteriously, when you do this the problem disappears. I have no idea why.
I hope this is of some use to people.


BSUK.

 

[BSUK]

Set the ownership on the top level folder to NT-AUTHORITY\NETWORK SERVICE
This fixes the problem.

BSUK