File Permissions error

  • Thread starter Thread starter Keith Gregory
  • Start date Start date
K

Keith Gregory

Hi All. Long time...no Usenet but here goes. Oh yes, Happy New Year.

Problem: Have moved the contents of a web from my PDC (Windows 2003 SBS) to
a stand alone server on my network. (Windows 2000 Server) I am using
(still) FrontPage 98. The website views and runs perfectly over the web. No
problems there. But if I try to edit on the fly, (edit live) FrontPage
complains that the FrontPage extensions cant read "frontpg.lck". Here's the
exact error message in it's entirety:

"vermeer RPC packet
method=open service:3.0.2.926
status=
status=131165
osstatus=536870925
msg=The server extensions were unable to access the file "frontpg.lck".
Please check the file permissions.
osmsg=Permission denied" This is while trying to access it from any client
computer on the network with FrontPage installed.

I've set the permissions on the entire "vti_pvt" folder to grant full access
to every member, service, etc on the network but still receive this error
regardless. The file is not "read only". I've run into this before and was
always able to fix it with some simple permission changes. I'm not sure if
it has something to do with moving the content to a different computer or
what. I've tried reinstalling FrontPage on several clients with same result.
I have a feeling it might be something real simple and I'm going to feel a
little silly real soon but there it is. Thank in advance for any and all
responses.

Keith G
 
Delete the file.


--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer
 
Make sure it is not marked read only and that it has write permissions.
 
How did you move the web, did you publish it via FP?

Did you configure the FP 2000 extensions on the server prior to publishing, as you should never have
to adjust the permission manually, let the FP Server Admin application maintain the permissions.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================
 
Thanx Tom, but I've given the entire universe full access to this file while
trying to sort this out. Anything else come to mind?
Tom [Pepper] Willett said:
Make sure it is not marked read only and that it has write permissions.
--
Tom [Pepper] Willett
Microsoft MVP - FrontPage
----------
Keith Gregory said:
Thanks Steve, but maybe that was to easy. What would you do next? Same
error.
Click to expand...
Click to expand...
 
It wasn't until I manually moved the web to the standalone server that this
occurred. I can edit it just fine as long as the "home directory" is the
server that runs the IIS. As soon as I change the home directory to a copy
of the web located on the standalone server the problem occurs.
 
You need to publish the web between locations, after you have the FP extensions configured
correctly.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================
 
Back
Top