Microsoft Knowledge Base Email Alertz

When you perform a Check Server Extensions, the following error message occurs:

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 201529 - Last Review: February 19, 2007 - Revision: 1.1

FP2000: Check Server Extensions Reports Content Folder Not Found

This article was previously published under Q201529

On This Page

SYMPTOMS

When you perform a Check Server Extensions, the following error message occurs:
PROBLEM: Content folder "C:\Inetpub\Wwwroot\Web" not found.
where C:\Inetpub\Wwwroot\Web is the location of the missing folder; this may be different for you.

CAUSE

This problem may be caused by one of the following:
A subweb's folder is deleted without using the FrontPage client or FrontPage Administration tools. For example, if you delete the folder of a subweb in Windows Explorer from a DOS command prompt or a UNIX command prompt.

-OR-

A Web is created on a separate volume and the volume is not currently available.

RESOLUTION

If you suspect that first cause above is the reason for the error message, determine if the Web referenced in the Check Server Extensions is off of the root Web or if it is a nested subweb. For example:

If the Check Server Extensions message appears as "PROBLEM: Content folder "C:\inetpub\wwwroot\web" not found", and C:\inetpub\wwwroot is the assigned location for this virtual server, then this is a subweb to the root web.

-OR-

If the Check Server Extensions message appears as "PROBLEM: Content folder "C:\inetpub\wwwroot\web\web2\web3" not found", and C:\inetpub\wwwroot is the assigned location for this virtual server, then this is a nested subweb.
Based on whether the Web referenced in the error message is a subweb of the root or a subweb of another subweb (nested subweb), you will need to edit a configuration file to remove the listing for the non existent Web.

For a subweb off of the root Web:

Use the Windows NT Explorer or UNIX command prompt and go to the content location of the root Web. In the content area of the root Web, (parent directory to the subweb), you will find the _vti_pvt folder. In this folder, the Services.cnf file is located. Open the file in a text editor such as Notepad to view a list of Webs for this virtual server. Remove the listing for the Subweb that was identified by the error message and save the file. For example:
Before:

/
/subweb1
/subweb2
/subweb3


After:

/
/subweb2
/subweb3


where /subweb1 is the Web identified by the Check Server Extensions.

For a nested subweb:

Use the Windows NT Explorer or UNIX command prompt and go to the content location of the partent subweb. In the content area of the parent subweb, locate the _vti_pvt folder. Open the Services.cnf file in a text editor such as Notepadto view a list of Webs that reside below the subweb. Remove the listing for the subweb that was identified by the Check Server Extensions and save the file. For example:
Before:

/
/subweb1
/subweb2
/subweb3

After:

/
/subweb2
/subweb3

where /subweb1 is the web identified by the error message.
Note: You cannot edit this file to create new subwebs or add subwebs. Also, after you remove the listing for the subweb, you may need to remove the virtual directory listings in the Web server that referenced the subweb (if any exist).

APPLIES TO
  • Microsoft FrontPage 2000 Server Extensions
Keywords: 
kbprb KB201529
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate