Hello, I try to update a word file with Office 2010 and save on the shared network drive. But when another user tries to open it on his computer using Office 2007 he cannot see the updates.

We are also experiencing this issue with Excel and PowerPoint 2010 x86. A user will save their changes to the network share and close Office and if another user opens within 2-3 minutes the changes will not be visible.

Has anyone any ideas?

We use an EMC Celerra for file shares which is up to date and EMC have been engaged but cannot find any issues...

Help!

I realize this thread is a little old, but I have just come across this problem today as well.

I have a shared network folder (with shared sub-folders) on our Windows Server 2003 in a workgroup environment, which our staff accesses. This morning one of our staff members updated some photos within a MS PowerPoint file and saved it to the network share, the PPT file showed up correctly on her PC, but when I pulled the file from two, separate PC's the file size was unchanged from the original (reporting 44.4 MB, when the updated file reported 47.x MB) and the new photos she added were not displaying in the PPT file.

The users who regularly create and modify the files on the network share all were recently upgraded to identical Dell OptiPlex PC's running Windows 7 Pro, all using MS Office 2010 Pro. Previously there had been no problems using their old XP PC's in the same shared folders, using a mixture of Office 2003/2007.

I wonder if this has to do with the Microsoft Sync center messing things up, some sort of temporary storage of the files or other caching method between the server and client. I even tried opening up the file via OpenOffice and the file in question was still not updated to the last saved version. Very concerning.

I received no error messages when trying to save the updated ppt via PowerPoint 2010 to the server, nor when opening the file.

So far, all I have accomplished is disabling Microsoft Sync Center from startup, deleting the temporary files stored by MSSC. I also intend on restarting the server when I can get to that point before or after office hours. Any clue as to what is going on?

I've scoured the Internet in search for answers, but so far this forum topic is the closest thing I've found matching the behavior I am seeing, but it looks like this topic has died.

I have noticed that the folders on the shared drive are reporting as read-only for some reason though, despite not making any modifications server-side and the users in question haven't reported any 'access denied' issues one would expect when folder/file attributes are marked as read-only.

We are still experiencing this issue but cannot find any documented resolution.

Current thinking is that it is a Windows Explorer issue... When we disable the 'Details Pane' within Explorer in Windows 7 from 'Organize > Layout' we do not experience the 'read-only' issue.

Please try this too and let me know!

Thanks for the tip. I've disabled the Details Pane. My users are currently saving the files from within Office itself and not manually moving the files from their local documents folder, for instance, to the server using Windows Explorer, so I am unsure whether Windows Explorer is a factor or not. However they are using Windows Explorer to open the file, vs opening it from within Office. I may have to give that a try and see if the results are different.

Yes, I think that is the key - opening from within Explorer and still having Explorer open in the background.

cannot access network share on server 2003 using office 2010 suite. All other programs like wordpad work fine. i have set the trust setting to allow network access and added the path tho the trust settings. any ideas??????

I know this is an older post, but I hope this will help someone that encounters this problem.

We had a user that was unable to access the changes in an Excel file and the date modified did not match the date modified on the server where this file was saved.

I opened the Sync Center on the computer that was having the problem and found there was a conflict with this file. After clicking on resolve in the Sync Center and selecting the newest version option, the problem went away.

Hopefully that helps!