Publisher - Read file

Jethro

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

Mary Sauer

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@dont.hit> wrote in message
news:478c011f$0$5171$4c368faf@roadrunner.com...
>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
>
>
>

Jethro

Darn good question. I shall investigate and reply.

In the meantime I am following a hunch regarding font substitutions. I noted
a font sub warning when the file was loaded. My thinking is that either a)
Publisher will not permit font subs being saved back to the original or a
licensed font has crept in and the license won't permit a save for some
reason. Could I be barking up the wrong tree?

Thanks for taking the time.

Kindest

David



"Mary Sauer" <mary-sauer@mycolumbus.rr.com> wrote in message
news:ejMKBc2VIHA.1204@TK2MSFTNGP03.phx.gbl...
> 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@dont.hit> wrote in message
> news:478c011f$0$5171$4c368faf@roadrunner.com...
>>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
>>
>>
>>
>
>

Jethro

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@mycolumbus.rr.com> wrote in message
news:ejMKBc2VIHA.1204@TK2MSFTNGP03.phx.gbl...
> 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@dont.hit> wrote in message
> news:478c011f$0$5171$4c368faf@roadrunner.com...
>>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
>>
>>
>>
>
>

Mary Sauer

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@dont.hit> wrote in message
news:478d2f73$0$10956$4c368faf@roadrunner.com...
> 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@mycolumbus.rr.com> wrote in message
> news:ejMKBc2VIHA.1204@TK2MSFTNGP03.phx.gbl...
>> 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@dont.hit> wrote in message
>> news:478c011f$0$5171$4c368faf@roadrunner.com...
>>>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
>>>
>>>
>>>
>>
>>
>
>