"There is no web named..." error message when you open a disk-based Web in FrontPage 2000 (818050)


The information in this article applies to:

  • FrontPage 2002 Server Extensions from Microsoft
  • Microsoft FrontPage 2002 Service Pack 2 (SP-2)

SYMPTOMS

When you open a disk-based Web that is located at the root of a drive or mapped drive in FrontPage 2002, you may receive the following error message:
Server error: There is no web named "DriveLetter"
NoteDriveLetter is the drive or mapped drive that contains your FrontPage Web.

CAUSE

This problem may occur after you install Microsoft Office XP Service Pack 2 (SP-2).

RESOLUTION

Service Pack Information

This problem is corrected in Office XP Service Pack 3.To resolve this problem, obtain the latest service pack for Microsoft Office XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

307841 How to obtain the latest Office XP Service Pack

Hotfix Information

A supported fix is now available from Microsoft, but it is only intended to correct the problem described in this article. Only apply it to systems that are experiencing this specific problem. This fix may receive additional testing to further ensure product quality. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Office XP service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Client Update

The Global version of this fix should have the following file attributes or later: 
   Date         Time   Size       File name     
   --------------------------------------------
   04-Apr-2003  19:03  4,025,192  Fp5autlop.msp
After the hotfix is installed, the Global version of this fix will have the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. 
   Date         Time   Version      Size       File name     
   --------------------------------------------------------
   06-Jan-2003  19:04  10.0.4803.0    137,824  Fp5amsft.dll     
   09-Aug-2002  03:20  10.0.4406.0    952,904  Fp5autl.dll      
   09-Aug-2002  03:20  10.0.4406.0    604,744  Fp5awec.dll      
   03-Apr-2003  07:13  10.0.5201.0  1,382,984  Fp5awel.dll      
   24-Oct-2002  18:44  10.0.4622.0  4,254,280  Fpeditax.dll     
   24-Jan-2003  01:04  10.0.4921.0    834,120  Owssvr.dll

Full File Update

The Global version of this fix should have the following file attributes or later: 
   Date         Time   Size       File name     
   --------------------------------------------
   04-Apr-2003  21:59  9,554,684  Fp5autlff.msp
After the hotfix is installed, the Global version of this fix will have the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. 
   Date         Time   Version      Size       File name     
   --------------------------------------------------------
   12-Jun-2002  21:07  10.0.4205.0    105,032  Cfgwiz.exe       
   06-Jan-2003  19:04  10.0.4803.0    137,824  Fp5amsft.dll     
   12-Jun-2002  21:07  10.0.4205.0     36,424  Fp5areg.dll      
   09-Aug-2002  03:20  10.0.4406.0    952,904  Fp5autl.dll      
   09-Aug-2002  03:20  10.0.4406.0    604,744  Fp5awec.dll      
   03-Apr-2003  07:13  10.0.5201.0  1,382,984  Fp5awel.dll      
   12-Jun-2002  21:07  10.0.4205.0     27,208  Fpadmdll.dll     
   24-Oct-2002  18:44  10.0.4622.0  4,254,280  Fpeditax.dll     
   12-Jun-2002  21:07  10.0.4205.0    395,848  Fpmmc.dll        
   24-Jan-2003  01:04  10.0.4921.0    834,120  Owssvr.dll       
   12-Jun-2002  21:07  10.0.4205.0    346,696  Owstimer.exe
This fix is a post-Office XP Service Pack 2 (SP-2) fix. To install the fix, you must have Office XP SP-2 installed. For additional information about Office XP SP-2, click the following article number to see the article in the Microsoft Knowledge Base:

325671 OFFXP: Overview of the Office XP Service Pack 2

Additionally, you may have to install Windows Installer 2.0 to install this fix. For additional information about the Windows Installer requirement for post-Office XP SP-2 fixes, click the following article number to see the article in the Microsoft Knowledge Base:

330537 OFFXP: Office XP Updates and Patches Released After September 2002 May Require Windows Installer 2.0


STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Office XP Service Pack 3.
Modification Type:MajorLast Reviewed:4/7/2006
Keywords:kbQFE KBHotfixServer kberrmsg kbbug kbfix KB818050
©2004 Microsoft Corporation. All rights reserved.