The issue shows itself in a number of manifestations:
Issue One:
Server error: The server extensions were unable to access the file "somefile.lck". Please check the file permissions.
Solution(s):
First, recalculations won't work. Deleting the files won't work. Standard restart server doesn't work.
What seems to work:
If local workstation, try copying web site contents to a new folder on the harddrive WITHOUT copying any of the LCK files in the vti_pvt folders. Then abandon the old site and have FrontPage open the "new" site. (Note: always use Open Web even for local web sites.)
If on a server, updating the user to access on the offending vti_pvt file won't fix it. However, if you change the permission on the file to grant the EVERYONE "group" modify access, that work. (This is scary since EVERYONE would then be able to modify the file. Not particularly advisable if a public web server.)
1. - Go to the web root directory
2. - Open the folder _vti_pvt
3. - Right click on the file frontpg.lck
4. - Go to Security
5. - Click add User
6. - Add the user: Everyone
7. - Give the Everyone user Modify rights to the frontpg.lck file.
8. - Restart the World Wide Web Service or restart the web server.
9. - All users should be able to modify/delete/publish again.
______________________________
Issue Two:
Cannot write on the file at _viti_pvt/filename.lck because you read the web from a CDROM or the file is corrupt or missing.
Solution(s):
First, recalculations won't work. Deleting the files won't work. Standard restart server doesn't work.
If on the client, backup up the "regular" files with out the special vti-xxx folders, delete the original folder, and copy the site files to a new folder and then open the site again. (Note: always use Open Web even for local web sites.)
If on the server, "stop" the offending web site and restore the site folder from backup, or delete the web site and repopulate it. In other words, do the second standard MS software fix and reinstall from scratch. Specifically:
1. In the IIS MMC, find the root folder for the site/virtual site.
2. Delete the web site folder
3. Create a new web site folder
4. Create a new web site/virtual site in the IIS MMC
5. Have the client republish.
______________________________
Issue Three:
Server Error (Root) Web is busy. Please try again (keywords: "Root Web Is Busy")
Solution(s):
First, recalculations won't work. Deleting the offending file(s) usually works if you know which one(s) it is. Usually this happens because a transmission of an update failed during publishing (locally or to the server). Either the power went out and you client crashed, or the Internet connection to the server was interrupted. You have a partly written file that isn't accessible for FrontPage to read/update/delete. The other possibility is that a file as wrong permissions somehow due to a file being restored from backup. (e.g. I hosed a file, so I had my administrator restore the previous version of the file from last week.) When it was restored, the file still is only "read only".
If you know the files, you can remove them manually. This is easy if you only updating one file since the last time. This is unrealistic if you've done MANY edits on a large site.
For server based sites, the server administration can:
1. delete the _vti_pvt/service.lck file and stop and start the website
and if that doesn't work
2. the only other option is to basically re-set the web site again similarly to the Issue Two above.
(BTW. You might find that once you stop the site, the lck file is still locked! You have to shut down the whole IIS service to free it. Just stopping the one virtual site won't do it.)
______________________________
Issue Three:
Error Server Extensions unable to access the file Frontpage.lck please check permissions.
Solution(s):
If a local web site on a client's workstation, the file permissions have been changed or the LCK file is corrupted.
If on the server, the LCK file permissions are corrupted or the site has been "locked down" by the "Lock Down" wizard from Microsoft to secure the site. This convenient wizard has an option, Deny write access to anonymous users and applications. Unfortunately, that option when it secures the site seems to also lock the user trying to publish web site using FrontPage (with Extensions rather than FTP). In addition, ASP pages with code, no longer execute for the anonymous web visitor.
To fix the issue and to undo the lockdown:
Use the "Cacls.exe" command-line utility to remove the deny write access groups from the \inetpub\wwwroot\clientwebsite folder on the server. To do this, follow these steps:
1. Locate the client web site filder in the IIS MMC window
2. Right-click the folder, and then click Properties.
3. Click the Security tab, and then note the groups that are configured with deny write permissions. (Once should include the client - the groups are not exactly plain english, so you may have to cross reference with the groups list in users and groups.)
4. Click Start, click Run, type cmd, and then click OK.
5. At the command prompt, type cacls drive_letter:\inetpub\wwwroot /t /e/ c /r "group_name" where drive_letter is the drive where your system is installed, and group_name is the name of the group that you want to remove deny write permissions for on the wwwroot folder and its contents and subfolders.
______________________________
Issue Four:
Error: frontpage.lck (or service.lck if on server) cannot be found ...
(Issue may appear after MS Office service pack applied to workstation)
Solution(s):
If on local workstation, try deleting the file and re-opening the web site.
Alternately, you could start a new web site and import the old one. (FrontPage will warn you that the vti_xxx folders/files exist and that they won't be imported -- this is what we want!)
If on the server, have the administrator delete the offending file (frontpage.lck and service lck in the hidden vti_pvt folder) and stop and start the web site. Alternately, if the file is not corrupted, you could reset security so that anonymous has access to the files.
______________________________
Issue Five:
Error: Cannot open file for Reading/Writing
Solution(s):
This is either specific rights on a web page trying to opened or saved or just as likely an issue with frontpage.lck or service.lck in the hidden vti_pvt folder.
For rights on an actual web page, fix the permissions on the file. For the server, contact the administrator so they can delete the current service.lck (or frontpage.lck). Try the open or save again.
______________________________
Issue Six:
Error: Internal Server Error (when Publishing)
Solution(s):
This usually indicates an issue where the FrontPage software doing the publishing on the client's workstation has lost its mind. This is one of those cases where a "recalculate hyperlinks" should fix the problem.
previous page
|