SITE INDEX


Service.lck (also mistakenly called Service.ick)

There are several error message that revolve around problems with the Service.lck file. This is a file that FrontPage creates regarding read/write permissions. That file can get corrupted, preventing you from accessing your web. Also copying a web, instead of publishing it can cause the Service.lck file to take on "Read Only" attributes, preventing you from opening a file or saving changes.

Do not panic!! The solution is simple .... the hard part is identifying that your problem is connected with the Service.lck file. Below are some of the error messages you may receive.

  1. The server extensions were unable to access the file "Service.lck". Please check the file permissions.
     
  2. Server Error: Cannot open file ".........\_vti_pvt\service.lck" for reading
    or
    Server Error:
    Cannot open file ".........\_vti_pvt\service.lck" for writing
     
  3. Server error:  Web name is busy. Please try again
    or
    your computer appears to stop responding (hang) during the initial publishing process

 

Creating a new Web
When creating a new web you may get the error message:

The server extensions were unable to access the file "Service.lck". Please check the file permissions.

This happens if the Service.lck file has got damaged.

To rectify this, you have a choice of three options:

  1. Locate the Service.lck file with Windows Explorer and delete it. Close down Front Page, then try again. Sometimes this will not work, depending on why that file got damaged in the first place. If it does not work, then you have the following two options:
  2. Create your new Web in a different folder. If you are trying to create it in the My Webs folder ... make a new folder outside of the My Webs folder, perhaps call it My Webs2 ... then create your new Web in that.
  3. Totally delete the contents of the My Webs folder before creating a new Web.

Back to top
 

Accessing a web
You receive one of the following two messages:

  • Server Error: Cannot open file ".........\_vti_pvt\service.lck" for writing.
  • Server Error: Cannot open file ".........\_vti_pvt\service.lck" for reading.

This will happen if either:

  1. The Service.lck file is damaged - this can happen if FrontPage shuts down unexpectedly or a network connection terminates incorrectly.
  2. Or there is a problem with permissions on the Service.lck file in the Web you are trying to access - a possible cause being that you are trying to access a web that has been copied to a location, rather than published to that location.

To rectify this, you must locate the Service.lck file and delete it.

The _vti_pvt folder is a hidden folder, so make sure that you can view hidden files and folders - on the Tools menu of any folder, click Folder Options. On the View tab, click to select the Show hidden files and folders check box, and then click to clear the Hide file extension for known file types check box. You will now be able to locate the the Service.lck file and delete it. Next time FrontPage is opened, it will create a new file.

Back to top
 

When you try to publish a FrontPage Web to a Web server
you may experience either or both of the following -

You receive the following error message:

  • Server error: Web Web name is busy. Please try again.
  • Or your computer appears to stop responding (hang) during the initial publishing process.

This problem can occur if the connection to the server is interrupted during the publishing process.

Try one of the following two methods:

  1. Cancel the publishing process.
  2. Check your network connection to make sure it is working okay.
  3. Start the publishing process again.

if that doesn't work, then try the following:

  1. On the server delete the following two files:
    \Web Root\Web Name\_vit_pvt\Service.lck
    and
    \Web Root\Web Name\_vit_pvt\frontpg.lck
  2. Now try publishing the web again.

Both the Service.lck and Frontpg.lck files deny access to a web on the destination server during publishing. If the connection is interrupted - those files can continue to deny access.

 

 

Back to Top