Question : Office 2007 can't save to network share.

I have been experiencing this same issue with an Office 2007 user. There are two places that I have seen this issue arise and the tests that I have done. I have been looking for an issue for some time and am convinced that this is specifically a Office 2007 problem.

1st location I see the problem: While in Outlook 2007 saving attachments to a network folder. If I try to save directly from an email by right-click and click save as I get the error cannot save the attachment and it put a 0 KB file with the same name just empty.

2nd If I open the attachment in Word 2007 and click Save as à Word Document  .docx with button Maintain compatibility with word 97  2003  check box I get the error \\servername\sharename\userfolder\folder\test.docx is currently in use, try again later . It again create a 0 KB file called test.docx . If I try save as again , it asks it I want to overwrite the file with the same name. If you click yes it saves it fine.

I have also seen then problem in other 3rd party software using the My recent documents 
Server shares have been on both Windows 2003 R2 and Windows 2000 sp 4 .

Client is windows XP Pro SP 3
Office 2007 SP 1
Symantec Antivirus 10.1
I hope this helps find a resolution. I have read many many reports of this problem and they all have to do with Office 2007.

Cheers

Answer : Office 2007 can't save to network share.

I finally found the solution to the Outlook 2007/Office 2007 getting an error when saving to share on 2003 server. I added the user to the Share permissions with full control and this resolved my issue.

I got help from another posting that said this.

Zoppo:
Hi Wyandotte,

it may be this is related to a known problem with Win32 API function 'ReplaceFile' (I'm not sure if Excel/Word use it, but I know that often applications first write data to a temporary file and later use 'ReplaceFile' to create the wanted file).

You can find info about that problem here: http://support.microsoft.com/kb/274487/en-us

A solution would be to either give the user 'Full Access' to the share on the server (not the directory-security, the share-access rights) or to add the user to the local administrator group on the server ...

Hope that helps,

ZOPPO