|
Related Topics:
| Office 2004 Read Write problem - I've read the archives ad nauseam and still can not solve this problem. I am very in the MS Office for Mac and the trial version before I paid for it to see if it is what I want. After the download, I moved the Office icon to..
my imac will not read disks - my I mac will not read disks that it has been able to in the past- I have 0sx tiger.
my imac will not read disks - my I mac will not read disks that it has been able to in the past- I have 0sx tiger.
new problem - OF MS Office while dragging the icon of MS Office 2k4 to a hard drive i receive this error; The Finder canneot complete the operation becuse some data in could not be read or written. (Error code -36) and the option to close the..
Licensing problem - I am a student at Queen's in Canada and living in I have Office for Mac installed on my MacBook, and was working fine, until i tried to log on while connected to the residence network, which informed me that I could not proceed..
|
|
|
Next: General Discussion: Office 2004 won't update
|
| Author |
Message |
External
Since: Aug 01, 2008
Posts: 1
|
(Msg. 1) Posted: Fri Aug 01, 2008 1:31 pm
Post subject: Critical Read-Only Problem
Archived from groups: microsoft>public>mac>office (more info?)
|
|
|
We have our files shared via SMB on a Leopard 10.5 server (fully
patched). AFP is not turned on.
I'm using Office 2008, fully patched, on Leopard 10.5.4 clients.
Every file I open that's on the server, either Excel or Word (and
probably Powerpoint as well, haven't tried it yet) opens up as Read-
Only. It doesn't matter if I use File > Open or if I double click the
file directly from the Sharepoint.
The files are not read only, however. I can open up the same Word
document in say, Texteditor, make a change, and save it just fine. I
can rename or delete or move the file using the Finder, so I know I
have all the right permissions to it. I can open the same file in
OpenOffice and save it just fine. All my ACLs and permissions check
out from the server end. I can duplicate this problem on any client in
my network, with the majority of the files on the Leopard xserve.
If use the Finder to copy the same Word document to a share on a
Windows 2003 server, it opens up fine. If I use the Finder to copy the
same Word document to another location on the Xserve, it still opens
up as Read Only.
PC users that have Office 2003 also connect to the SMB shares on the
Leopard server and haven't had any problems. They are not trying to
open any of the same files - again, it's not about the file being
locked or set to read only, as other applications can open and save
the files, just not Word 2008 or Excel 2008.
Any ideas? This is.. well, infuriating that none of our Office 2008
clients can save to any Word or Excel files on our Leopard server! |
|
| Back to top |
|
 | |
External
Since: Jul 29, 2008
Posts: 108
|
(Msg. 2) Posted: Fri Aug 01, 2008 6:07 pm
Post subject: Re: Critical Read-Only Problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
phil.lochner.cc.DeleteThis@gmail.com wrote:
> Every file I open that's on the server, either Excel or Word (and
> probably Powerpoint as well, haven't tried it yet) opens up as Read-
> Only. It doesn't matter if I use File > Open or if I double click the
> file directly from the Sharepoint.
I don't support a Leopard Server sharing via SMB to Macs but do the
clients still create the hidden "._filename" files (the resource forks)
that you'd see when saving to a Windows share? If so, could these be
read only? You'd need to check permissions via Terminal.
--
bill
Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
YouTalk <http://nine.pairlist.net/mailman/listinfo/youtalk>
Twitter: follow <http://twitter.com/meck> |
|
| Back to top |
|
| |
External
Since: Aug 03, 2008
Posts: 2
|
(Msg. 3) Posted: Sun Aug 03, 2008 6:55 pm
Post subject: Re: Critical Read-Only Problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
On Aug 1, 4:07 pm, "William Smith [MVP]"
<meckli... RemoveThis @REM0VETH1S.comcast.net.INVALID> wrote:
> phil.lochner... RemoveThis @gmail.com wrote:
> > Every file I open that's on the server, either Excel or Word (and
> > probably Powerpoint as well, haven't tried it yet) opens up as Read-
> > Only. It doesn't matter if I use File > Open or if I double click the
> > file directly from the Sharepoint.
Thanks for your input, however there aren't any DS Store or ._filename
files in the folder. I can go into the server in Terminal and do a
chomod 777 filename.doc, and it'll still open up as Read Only. I can
even create a completely blank document, save it as Test.doc, and it
will immediately become Read-Only as soon as I save it!
Again, I don't think this has anything to do with the actual file
permissions of the file. I can open any of these files using vi or
OpenOffice or Text Editor and save them just fine. It's just Office
2008 that's creating this problem for me. I have uninstalled Office
and reinstalled it but unfortunately my Open License media came
preinstalled with SP1, so I can't narrow the problem down to SP1 or
not.
The problem also seems to exist on Tiger clients using a fully patched
Office 2008. I haven't had a chance to try it out with Office 2004
yet, however. My next step is to enable AFP sharing on the share and
see if that still gives me a problem.
Any other ideas?
>
> I don't support a Leopard Server sharing via SMB to Macs but do the
> clients still create the hidden "._filename" files (the resource forks)
> that you'd see when saving to a Windows share? If so, could these be
> read only? You'd need to check permissions via Terminal.
>
> --
>
> bill
>
> Entourage Help Page <http://entourage.mvps.org/>
> Entourage Help Blog <http://blog.entourage.mvps.org/>
> YouTalk <http://nine.pairlist.net/mailman/listinfo/youtalk>
> Twitter: follow <http://twitter.com/meck> |
|
| Back to top |
|
| |
External
Since: Jul 29, 2008
Posts: 108
|
(Msg. 4) Posted: Sun Aug 03, 2008 9:15 pm
Post subject: Re: Critical Read-Only Problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Phil wrote:
> The problem also seems to exist on Tiger clients using a fully patched
> Office 2008. I haven't had a chance to try it out with Office 2004
> yet, however. My next step is to enable AFP sharing on the share and
> see if that still gives me a problem.
>
> Any other ideas?
Nothing definitive. Leopard makes use of ACLs exclusively now and
doesn't support the old owner/group/everyone model.
If you were to connect as an administrator from the workstation to the
server, do you still see problems? The admin account should have Full
Access.
--
bill
Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
YouTalk <http://nine.pairlist.net/mailman/listinfo/youtalk>
Twitter: follow <http://twitter.com/meck> |
|
| Back to top |
|
| |
External
Since: Aug 03, 2008
Posts: 2
|
(Msg. 5) Posted: Tue Aug 05, 2008 3:19 pm
Post subject: Re: Critical Read-Only Problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
We figured it out today. POSIX permissions for the Everyone group were
set to "None" - apparently the Office 2008 programs aren't fond of
this choice. We use ACLs, so setting POSIX for Everyone to Read and
Write isn't a huge deal for us. We used the excellent "TinkerTool
System" program instead of the clunky WGM to inspect and edit our
permissions.
We also discovered that ACLs are not very happy during propagation
with group names that contains spaces. Therefore, "MYDOMAIN\Domain
Admins" was consistently rejected by TinkerTool System, but "MYDOMAIN
\Users" or any local group name worked fine. WGM always seemed to
error silently when I propagated these groups, which made for strange
Get Info lists, and unruly ACL behavior.
On Aug 3, 7:15 pm, "William Smith [MVP]"
<meckli....TakeThisOut@REM0VETH1S.comcast.net.INVALID> wrote:
> Phil wrote:
> > The problem also seems to exist on Tiger clients using a fully patched
> > Office 2008. I haven't had a chance to try it out with Office 2004
> > yet, however. My next step is to enable AFP sharing on the share and
> > see if that still gives me a problem.
>
> > Any other ideas?
>
> Nothing definitive. Leopard makes use of ACLs exclusively now and
> doesn't support the old owner/group/everyone model.
>
> If you were to connect as an administrator from the workstation to the
> server, do you still see problems? The admin account should have Full
> Access.
>
> --
>
> bill
>
> Entourage Help Page <http://entourage.mvps.org/>
> Entourage Help Blog <http://blog.entourage.mvps.org/>
> YouTalk <http://nine.pairlist.net/mailman/listinfo/youtalk>
> Twitter: follow <http://twitter.com/meck> |
|
| Back to top |
|
| |
External
Since: Aug 06, 2008
Posts: 6
|
(Msg. 6) Posted: Wed Aug 06, 2008 4:18 pm
Post subject: Re: Critical Read-Only Problem [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Unfortunately, I spoke too soon and this problem has not been figured out. I
ended up creating a new topic with some very specific information that I have
gleaned from about 8 hours worth of messing around with this problem.
"Phil" wrote:
> We figured it out today. POSIX permissions for the Everyone group were
> set to "None" - apparently the Office 2008 programs aren't fond of
> this choice. We use ACLs, so setting POSIX for Everyone to Read and
> Write isn't a huge deal for us. We used the excellent "TinkerTool
> System" program instead of the clunky WGM to inspect and edit our
> permissions.
>
> We also discovered that ACLs are not very happy during propagation
> with group names that contains spaces. Therefore, "MYDOMAIN\Domain
> Admins" was consistently rejected by TinkerTool System, but "MYDOMAIN
> \Users" or any local group name worked fine. WGM always seemed to
> error silently when I propagated these groups, which made for strange
> Get Info lists, and unruly ACL behavior.
>
>
>
>
> On Aug 3, 7:15 pm, "William Smith [MVP]"
> <meckli....TakeThisOut@REM0VETH1S.comcast.net.INVALID> wrote:
> > Phil wrote:
> > > The problem also seems to exist on Tiger clients using a fully patched
> > > Office 2008. I haven't had a chance to try it out with Office 2004
> > > yet, however. My next step is to enable AFP sharing on the share and
> > > see if that still gives me a problem.
> >
> > > Any other ideas?
> >
> > Nothing definitive. Leopard makes use of ACLs exclusively now and
> > doesn't support the old owner/group/everyone model.
> >
> > If you were to connect as an administrator from the workstation to the
> > server, do you still see problems? The admin account should have Full
> > Access.
> >
> > --
> >
> > bill
> >
> > Entourage Help Page <http://entourage.mvps.org/>
> > Entourage Help Blog <http://blog.entourage.mvps.org/>
> > YouTalk <http://nine.pairlist.net/mailman/listinfo/youtalk>
> > Twitter: follow <http://twitter.com/meck>
>
> |
|
| Back to top |
|
| |
|
FAQ
Search
Profile
Private Messages
Log in/Register/Password
Mac Forums
RSS | Data
Feeds | Advertise | Submit | Bookmark | Newsletter | Contact