This article was previously published under Q287399
This article has been archived. It is offered "as is" and will no longer be updated.
When working with Web folders and Microsoft FrontPage 2000 or Microsoft FrontPage 2002, you may experience one of the following symptoms:
If you try to open a Web, you receive the following error message:
The folder "http://Website" isn't accessible. The folder may be located on an unavailable volume or protected with a password.
If you try to open an existing Web location by double-clicking the Web folder in the Open Web dialog box, you receive the following error message:
The current operation cannot be completed because an unexpected error has occurred.
If you use a Web folder in My Computer\Web Folders (on Microsoft Windows 98 or Microsoft Windows Millennium Edition) or My Network Places (on Microsoft Windows 2000 or Microsoft Windows XP), you receive the following error message:
The folder you entered does not appear to be valid. Please choose another.
Additional symptoms you may experience include:
You cannot see any Web folders in the Open File dialog box.
When you try to create a new Web folder, the Web Folder Wizard finishes without errors but the Web folder is not created.
A problem with the installation of Web folders on the client is preventing the computer from communicating with other Web servers, including the local Web server.
These messages can indicate a problem with any of the following:
FrontPage Server Extensions
File/folder permissions at the Web server
Ask yourself the following questions to determine if Web folders are the source of the problem:
Can you open or publish Webs to different Web servers?
Do you have one FrontPage 2000 or FrontPage 2002 client computer?
FrontPage cannot open or publish Webs on Server A.
FrontPage cannot open or publish Webs on Server B.
FrontPage cannot open or publish Webs on Localhost.
Do you have two clients that have FrontPage 2000 or FrontPage 2002 installed?
If Client A and B cannot talk to Server A, but Client A and B can talk to Server B, the problem is with Server A and there may be a problem with the server.
If Client A cannot talk to Server A and B, but Client B can talk to Server A and B, the problem is with Client A and there may be a Web Folders issue.
Note Although this requires more resources, you should try to test more than one Web server and client to determine where the problem is.
Can you create a new Web folder on a remote Web server or on the local computer by using Network Neighborhood (Windows 98 or Windows Millennium Edition) or My Network Places (Windows 2000 or Windows XP)?
Can you open the web if you visit the site by using Microsoft Internet Explorer and click Edit on the toolbar?
Can you open the Web from the command line? To do this, follow these steps:
On the Windows Start menu, click Run.
In the Open box, type the following:
where example.microsoft.com is the URL of your Web server.
If you were able to open the Web site previously, can you open it in FrontPage by pointing to Recent Webs on the File menu, and then clicking the Web server?
If all of the above steps are true, then the problem is probably with the current installation of Web Folders on the client.
For more information about troubleshooting Web Folders, click the following article numbers to view the articles in the Microsoft Knowledge Base: