• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

If someone solve this...

glideFX

Member
Situation:

We have several samba shares, one of them is used as "home" by windows server 2012. By "home" I mean:
- Active direcory users and computers
- Properties of a user
- TAB Profile
- SECTION Home folder, Connect [H:] \\our.domain\home\username (home is the sahre)

The problem is with OSX and Office 2011
Connecting to the samba share and trying to open a docx / xlsx / pptx file returns the following message

Code:
'home:username:filename.xlsx' could not be found

check the spelling of the file name.. bla bla

If you are trying to open the file from your list of most recenty used files.. bla bla


Some behaviors

- Some Macs are able to open any file but only for a random period of time.
- When the error message begins to appear the only way to make it work again is reboot (and then works again for some time)
- If the file is copied to the desktop it opens correctly
- The problem never appeared on the other samba shares, defined exactly the same way
- Complete office 2011 uninstall and reinstall didn't solved anything
- The same file opened with Numbers works perfectly, all the time
- The problem is the same with OSX 10.9 and 10.8.
 
there is a bug in office 2011 causing the problem reported in the first post when a network volume is called "home"...
 
there is a bug in office 2011 causing the problem reported in the first post when a network volume is called "home"...

Yea, you said that, but how did you solve the error? Was their a bugfix put out by MS?
 
I said we have a share called 'home' and we have problems with office 2011 files; I didn't said there is a bug when the share is called 'home' because if you say that you also have the solution 😀

Anyway the solution was change the share name because even if it's a known bug since 2011 Microsoft seems not interested to fix it..
 
Back
Top