Does Publisher 2003 allow for saving files to a Network drive?

[briangw]

Users are having issues saving Pub 98 files to the network and I found that
it was not designed for that. Has that changed for 2003?

 

[Brian Kvalheim [MSFT MVP]]

briangw wrote:
|| Users are having issues saving Pub 98 files to the network and I
|| found that it was not designed for that. Has that changed for 2003?

What happens if you give the users Admin powers.
--
Brian Kvalheim
Microsoft Publisher MVP
http://www.publishermvps.com

This posting is provided "AS IS" with no warranties, and
confers no rights.

 

[briangw]

We're not allowed to do that here. Being a financial insitution, we have
everything locked down as tight as possible. So, I assume that's a big no, eh?

 

[Brian Kvalheim [MSFT MVP]]

Hi briangw ([email protected]),
in the newsgroups
you posted:

|| We're not allowed to do that here. Being a financial insitution, we
|| have everything locked down as tight as possible. So, I assume
|| that's a big no, eh?

Right, I understand that. However, can you TEST it to see if it allows you
to do so? If it doesn't allow you to do so, we would then require to do more
troubleshooting.
--
Brian Kvalheim
Microsoft Publisher MVP
http://www.publishermvps.com

This posting is provided "AS IS" with no warranties, and
confers no rights.

 

[briangw]

I did give overall local admin access to one of the users (see my posting
below, "Publisher 98 error message") to test it out and she was able to save
locally without error, but received that common error when trying to save the
file to the network. I'm going to try the "temp" admin access test first to
see if I can resolve the issue on my test account

I'm going to test that out on Publisher 98 today, with my test account
(regular user access) and some network access. I read in an earlier posting
that giving admin access to temp files will resolve the issue for local
saving. So, if it works for me, I will give it to the user and ask her to
save locally and steer away from network saving.

But, I need to know the answer to my original question. Is this still and
issue with 2003, because if it is, I don't want to tell the group to purchase
new software that's going to behave the same way.

 

[briangw]

Well, I granted admin access to c:\windows\temp, c:\temp, and c:\documents
settings\[my test id]\local settings\temp and that still didn't work. I'm
getting the error even if I save locally. I've tried both our MSI and CD
installations. Any other ideas?

 

[Mary Sauer]

Did you ever read the Pubntwk.hlp file on the 98 setup disk?

--
Mary Sauer MS MVP
http://office.microsoft.com/

Well, I granted admin access to c:\windows\temp, c:\temp, and c:\documents
settings\[my test id]\local settings\temp and that still didn't work. I'm
getting the error even if I save locally. I've tried both our MSI and CD
installations. Any other ideas?

I did give overall local admin access to one of the users (see my posting
below, "Publisher 98 error message") to test it out and she was able to save
locally without error, but received that common error when trying to save the
file to the network. I'm going to try the "temp" admin access test first to
see if I can resolve the issue on my test account

I'm going to test that out on Publisher 98 today, with my test account
(regular user access) and some network access. I read in an earlier posting
that giving admin access to temp files will resolve the issue for local
saving. So, if it works for me, I will give it to the user and ask her to
save locally and steer away from network saving.

But, I need to know the answer to my original question. Is this still and
issue with 2003, because if it is, I don't want to tell the group to purchase
new software that's going to behave the same way.

 

[briangw]

Yes, I spoke with our server group and they don't want to test that, but I
resolved the issue. I just granted my test account Power User access and full
admin access to the temp dirs and now there are no errors on saving on/off
the network.

Did you ever read the Pubntwk.hlp file on the 98 setup disk?

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

Well, I granted admin access to c:\windows\temp, c:\temp, and c:\documents
settings\[my test id]\local settings\temp and that still didn't work. I'm
getting the error even if I save locally. I've tried both our MSI and CD
installations. Any other ideas?

I did give overall local admin access to one of the users (see my posting
below, "Publisher 98 error message") to test it out and she was able to save
locally without error, but received that common error when trying to save the
file to the network. I'm going to try the "temp" admin access test first to
see if I can resolve the issue on my test account

I'm going to test that out on Publisher 98 today, with my test account
(regular user access) and some network access. I read in an earlier posting
that giving admin access to temp files will resolve the issue for local
saving. So, if it works for me, I will give it to the user and ask her to
save locally and steer away from network saving.

But, I need to know the answer to my original question. Is this still and
issue with 2003, because if it is, I don't want to tell the group to purchase
new software that's going to behave the same way.


:

Hi briangw ([email protected]),
in the newsgroups
you posted:

|| We're not allowed to do that here. Being a financial insitution, we
|| have everything locked down as tight as possible. So, I assume
|| that's a big no, eh?

Right, I understand that. However, can you TEST it to see if it allows you
to do so? If it doesn't allow you to do so, we would then require to do more
troubleshooting.
--
Brian Kvalheim
Microsoft Publisher MVP
http://www.publishermvps.com

This posting is provided "AS IS" with no warranties, and
confers no rights.

 

[briangw]

Take that back. It still does not work. My users are still getting the error.

Yes, I spoke with our server group and they don't want to test that, but I
resolved the issue. I just granted my test account Power User access and full
admin access to the temp dirs and now there are no errors on saving on/off
the network.

Did you ever read the Pubntwk.hlp file on the 98 setup disk?

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

Well, I granted admin access to c:\windows\temp, c:\temp, and c:\documents
settings\[my test id]\local settings\temp and that still didn't work. I'm
getting the error even if I save locally. I've tried both our MSI and CD
installations. Any other ideas?

:

I did give overall local admin access to one of the users (see my posting
below, "Publisher 98 error message") to test it out and she was able to save
locally without error, but received that common error when trying to save the
file to the network. I'm going to try the "temp" admin access test first to
see if I can resolve the issue on my test account

I'm going to test that out on Publisher 98 today, with my test account
(regular user access) and some network access. I read in an earlier posting
that giving admin access to temp files will resolve the issue for local
saving. So, if it works for me, I will give it to the user and ask her to
save locally and steer away from network saving.

But, I need to know the answer to my original question. Is this still and
issue with 2003, because if it is, I don't want to tell the group to purchase
new software that's going to behave the same way.


:

Hi briangw ([email protected]),
in the newsgroups
you posted:

|| We're not allowed to do that here. Being a financial insitution, we
|| have everything locked down as tight as possible. So, I assume
|| that's a big no, eh?

Right, I understand that. However, can you TEST it to see if it allows you
to do so? If it doesn't allow you to do so, we would then require to do more
troubleshooting.
--
Brian Kvalheim
Microsoft Publisher MVP
http://www.publishermvps.com

This posting is provided "AS IS" with no warranties, and
confers no rights.

 

[briangw]

I did find that Publisher 2003 does not have this problem, in case anyone
wanted to know.

Take that back. It still does not work. My users are still getting the error.

Yes, I spoke with our server group and they don't want to test that, but I
resolved the issue. I just granted my test account Power User access and full
admin access to the temp dirs and now there are no errors on saving on/off
the network.

Did you ever read the Pubntwk.hlp file on the 98 setup disk?

--
Mary Sauer MS MVP
http://office.microsoft.com/
http://msauer.mvps.org/
news://msnews.microsoft.com
Well, I granted admin access to c:\windows\temp, c:\temp, and c:\documents
settings\[my test id]\local settings\temp and that still didn't work. I'm
getting the error even if I save locally. I've tried both our MSI and CD
installations. Any other ideas?

:

I did give overall local admin access to one of the users (see my posting
below, "Publisher 98 error message") to test it out and she was able to save
locally without error, but received that common error when trying to save the
file to the network. I'm going to try the "temp" admin access test first to
see if I can resolve the issue on my test account

I'm going to test that out on Publisher 98 today, with my test account
(regular user access) and some network access. I read in an earlier posting
that giving admin access to temp files will resolve the issue for local
saving. So, if it works for me, I will give it to the user and ask her to
save locally and steer away from network saving.

But, I need to know the answer to my original question. Is this still and
issue with 2003, because if it is, I don't want to tell the group to purchase
new software that's going to behave the same way.


:

Hi briangw ([email protected]),
in the newsgroups
you posted:

|| We're not allowed to do that here. Being a financial insitution, we
|| have everything locked down as tight as possible. So, I assume
|| that's a big no, eh?

Right, I understand that. However, can you TEST it to see if it allows you
to do so? If it doesn't allow you to do so, we would then require to do more
troubleshooting.
--
Brian Kvalheim
Microsoft Publisher MVP
http://www.publishermvps.com

This posting is provided "AS IS" with no warranties, and
confers no rights.

 

[Brian Kvalheim [MSFT MVP]]

How did you find that out?

I did find that Publisher 2003 does not have this problem, in case anyone
wanted to know.

Take that back. It still does not work. My users are still getting the
error.

Yes, I spoke with our server group and they don't want to test that,
but I
resolved the issue. I just granted my test account Power User access
and full
admin access to the temp dirs and now there are no errors on saving
on/off
the network.

:

Did you ever read the Pubntwk.hlp file on the 98 setup disk?

--
Mary Sauer MS MVP
http://office.microsoft.com/
http://msauer.mvps.org/
news://msnews.microsoft.com
Well, I granted admin access to c:\windows\temp, c:\temp, and
c:\documents
settings\[my test id]\local settings\temp and that still didn't
work. I'm
getting the error even if I save locally. I've tried both our MSI
and CD
installations. Any other ideas?

:

I did give overall local admin access to one of the users (see my
posting
below, "Publisher 98 error message") to test it out and she was
able to save
locally without error, but received that common error when trying
to save the
file to the network. I'm going to try the "temp" admin access test
first to
see if I can resolve the issue on my test account

I'm going to test that out on Publisher 98 today, with my test
account
(regular user access) and some network access. I read in an
earlier posting
that giving admin access to temp files will resolve the issue for
local
saving. So, if it works for me, I will give it to the user and ask
her to
save locally and steer away from network saving.

But, I need to know the answer to my original question. Is this
still and
issue with 2003, because if it is, I don't want to tell the group
to purchase
new software that's going to behave the same way.


:

Hi briangw ([email protected]),
in the newsgroups
you posted:

|| We're not allowed to do that here. Being a financial
insitution, we
|| have everything locked down as tight as possible. So, I
assume
|| that's a big no, eh?

Right, I understand that. However, can you TEST it to see if it
allows you
to do so? If it doesn't allow you to do so, we would then
require to do more
troubleshooting.
--
Brian Kvalheim
Microsoft Publisher MVP
http://www.publishermvps.com

This posting is provided "AS IS" with no warranties, and
confers no rights.