Re: Publisher - Read file

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Firewall? Permissions?
Download FileMon and RegMon from
http://www.sysinternals.com/. Run them as administrator (when no
user is connected), start a TS session as a normal user and try to
run the application.

FileMon and RegMon will show you all "access denied" errors that
occur, so that you can give your users the necessary permissions on
a file-to file or Registry subkey basis.

--
Mary Sauer MSFT MVP
http://office.microsoft.com/
http://msauer.mvps.org/
news://msnews.microsoft.com

"Jethro" <reply@xxxxxxxx> wrote in message
news:478d2f73$0$10956$4c368faf@xxxxxxxxxxxxxxxxx
Mary, thanks for the question:

If Bob saves the file locally and tries to overwrite the server share file,
he is stopped. The file on the network share is locked somehow.

To recap, he can save locally or renamed in the share-folder but cannot
overwrite the original newsletter.pub file. So it is not server/network
permissions but a Publisher file locking issue.

We eliminated (we think) font substitutions as a cause.

I cannot see why the other 4 team members have no problems, but just Bob.

Any further thoughts?

Kindest

David



"Mary Sauer" <mary-sauer@xxxxxxxxxxxxxxxxx> wrote in message
news:ejMKBc2VIHA.1204@xxxxxxxxxxxxxxxxxxxxxxx
What happens if Bob copies the file to his local drive, does the edits, saves
and copies it back to the network server?

--
Mary Sauer MSFT MVP
http://office.microsoft.com/
http://msauer.mvps.org/
news://msnews.microsoft.com

"Jethro" <reply@xxxxxxxx> wrote in message
news:478c011f$0$5171$4c368faf@xxxxxxxxxxxxxxxxx
I have a mysterious situation that I need some help on, please. I have a
client who has a 6 employee office. The network is straightforward, a
workgroup with good practice sharing and permissions. Nothing locked down or
complex.

Everyone in the office contributes to a newsletter which resides on a server
network share. Everyone has read/write rights to the share. One guy, lets
call him Bob can open the newsletter, can save it to the share as another
name but cannot save it as the original name. Publisher/Windows tells him it
is read only.

No one else experiences this problem.

Let me recap. The PUB file has no read only attributes set. Bob can create
and edit and save a file he edits in the share folder. Bob cannot save the
communal document even when no one else has it open. He can save it as
another name.

Everyone uses Office 2003.

Anyone have any ideas?????

David









.

Relevant Pages

  • Re: Can not use network shares on Server 2003 standard edition wit
    ... Okay, I think that it is a permissions and or security issue, although I can ... The physical network topology, is working fine. ... are getting DCHP internal IP addresses, the Server has 2 NIC's which are ... passwords currently match the server's Users and passwords ...
    (microsoft.public.windowsxp.network_web)
  • Re: Users cant log in to sharted directory
    ... is a security issue as well, as the network is at a school for disruptive ... Apologies if this is going over old ground, but this server admin stuff is ... The shared directory has ... Permissions for the users directories is set as user/Administrator/full ...
    (microsoft.public.win2000.networking)
  • Re: How to determine what permissions are required for an assembly
    ... On the Web server, open Administrative Tools, and then double-click ... named permission set with only the required permissions to execute all the ... > I need an application to load signed assemblies from the network share. ...
    (microsoft.public.dotnet.security)
  • Re: How to Force Login Dialog Box when connecting to a computer?
    ... Leave everyone in the user right for access this computer from the network. ... logon/password that exists on the "server" in it's local users then the user ... can be granted seamless access to shares that they have permissions to. ... opens up and then users can see shared folders. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Backend not connecting
    ... Have a look at the permissions on the server mdb file that you are trying to ... > end to the backend on a network. ... The network configuration seems to be the ...
    (microsoft.public.access.setupconfig)