Could someone explain to me why the United States spends more money killing people than taking care of it's own?
The tax rebate is Bush's and his cronies way of bailing out big corporations using tax payers' money, it is NOT to help poorer America.
Why is there money to help big corporations, killing people, but when it comes to Social Security, the money is running out? Why don't they bail out Social Security? My measly $300 rebate has already gone to Big Oil. Yours most likely will end up in some big corporation's pockets too and our children will have to pick up the tab.

Ephesians 2:17  "So Christ came and preached the Good News of peace to all---to you Gentiles, who were far away from God, and to the Jews, who were near to him."

Another great site for Office Support and Help is

Rick Selby's
Microsoft's FrontPage Errors
2002-03

Site Visitors 
To find a topic on this page, Click Edit on the Toolbar, Find (on this page), type in keyword

If you are planning on upgrading to Vista, there are hardly any drivers available. They are not the same as XP and most likely you will not be able to find drivers for your hardware at this time. Check with your manufacture for Vista drivers before you upgrade or you may be out of luck for a while until someone comes up with drivers. This is another repeat of XP SP 2.

Three things to remember when you are working with computers.
• First thing is "YOU CAN DO IT".
• Second take your time, a little mistake can cause a big problem.
• Third all answers are only a question away.


TABLE OF CONTENTS
• An error occurred accessing your windows Sharepoint Services files when opening or saving files
• You receive a "Documents in this folder are not available" error message when you try to open a Web folder in Internet Explorer
• HTML Is Reformatted When Component Properties Are Modified In Html View In FrontPage
• "Unable To Retrieve Folder Information From The Server" Error Message When You Try To Run An Executable In A Root Folder
• ASP Error 0178: 80070005 When You Attempt To Connect To Database Results Page
• Error Message Appears Editing Web Page On A Sharepoint Portal Server
• Database Error Messages When You Disable Session State In FrontPage 2002 Server Extensions From Microsoft
• Web Sites Do Not Open In Microsoft FrontPage After You Configure FrontPage Server Extensions 2002 On An Apache 1.3.19 Or Later Web Site
• Web Clients Receive "Cannot Run The FrontPage Server Extensions On This Page" Error Message When They Submit A Feedback Form
• "Fatal Exception 0e" Error Message During FrontPage Installation
• You Receive An Error Message When You Click Next In A Paged Data View In FrontPage 2003
• You Receive An Error Message When You Try To Start FrontPage 2003
  Microsoft FrontPage 2002 and FrontPage 2000 version of this article, see 321486 in the Microsoft Knowledge Base
• Error Message: Database Results Error [Microsoft][ODBC SQL Server Driver][Named Pipes]Access Denied
• "The Folder '/' Is Marked Executable" Error Message When You Save A Page To A Folder On A Web Site Based On IIS In FrontPage 2002 & 03
• "Server error: Cannot close file /_vti_pvt/service.cnf" error message when you try to publish Web in FrontPage
• Portal site stops responding and you receive a "The page cannot be displayed" or "Cannot find server or DNS error" error message when you access a portal site in SharePoint Portal Server 2003
• You receive a "You are not authorized to view this page" error message when you click Help on a single sign-on administration page in SharePoint Portal Server 2003
• You receive a "The virtual server referenced here is not in the config database" error message when you unextend a virtual server in SharePoint Portal Server 2003

An error occurred accessing your windows Sharepoint Services files when opening or saving files
• If you receive the above error when opening or saving a file, this error will appear if you are not opening a file in the Web Folder with the blue circle
• Same way with saving a file, this error will appear if you try to save the file in another folder
• All files and subfolders must be saved in the Web Folder with the blue circle

You receive a "Documents in this folder are not available" error message when you try to open a Web folder in Internet Explorer
Error Message
• In Microsoft Office FrontPage 2002-2003, when you try to open a Web folder, you receive the following error message:
  Documents in this folder are not available. The folder may have been moved or deleted, or network problems may be preventing a connection to the server.
  Note:If this error keeps reoccurring check for spyware. Spyware will cause this problem.
Solution
• FrontPage 2002
  • In Control Panel, double-click Internet Options
  • Click the Connection
  • In the list of connections, click the connection that you are using to access the Internet
  • Click Settings
  • Type the URL for a DAV-compliant proxy serve in the Address box
  • Type the associated port number in the Port box
  • Restart your computer
  FrontPage 2003
  • In Control Pane, double-click Internet Options
  • Click the Connections
  • In the Dial-up and Virtual Private Network setting list, click the connection that you are using to access the Internet
  • Click Settings
  • In the Proxy server Virtual Private Connection Settings dialog box, in the Address box
  • Type the URL DAV-compliant proxy server
  • In the Port
  • Click OK two times, and then restart your computer
  More Information
  • For additional information about Distributed Authoring and Versioning (DAV) and Microsoft FrontPage read the following articles in the Microsoft Knowledge Base:
    • 221600 Working with Distributed Authoring and Versioning (DAV) and Web folders
    • 289698 FP2002: Error saving ASP file on IIS Web server using WebDAV
    • 289697 FP2002: Error message attempting to open a Web on a WebDAV server

HTML Is Reformatted When Component Properties Are Modified In Html View In FrontPage
Symptoms
• When you change the tag properties of a Microsoft FrontPage component in HTML view, the HTML code is reformatted to the original HTML.
• You may receive the following error message when you return to Normal view:
  The contents of a FrontPage component have been modified. These contents will be overwritten when you save this page.
Solution
• If you want to make modifications to the FrontPage component settings, use the component properties in Normal view. Or, if you want to customize properties of the component that might not be exposed in the user interface, edit the file in another text editor, such as Notepad

"Unable To Retrieve Folder Information From The Server" Error Message When You Try To Run An Executable In A Root Folder
Symptoms
• In Visual InterDev 6.0, when you try to run an executable in the root folder of a Web page through the FrontPage 2002 Server Extensions, you may receive the following error message:
  Unable to retrieve folder information from the server. An HTTP error occurred. The server could not complete your request. Contact your Internet service provider or Web server administrator to make sure that the server has the FrontPage Server Extensions installed, and that the Web application exists on that server.
• Additionally, Execute permissions for the whole site (including _vti_bin) are then set to None Cause
  • This issue may occur when you select all items in the list of subnodes after you are prompted to make a selection -- for example, when you follow these steps:
    • Open Internet Services Manager
    • Select the Web project
    • Open the Properties for the project
    • On the Home Directory tab, click Scripts and Executables for the Execute permissions
    • Click OK or Apply to display the list of subnodes that currently are not inheriting the root permissions. By default, nothing is selected
    • Select all subnodes in this list
    • You receive the error message described above in the Symptoms
  More Information
  • The _vti_bin child node inherits its Execute permissions from the Web root.
  • When you subsequently open a project with Visual InterDev for the Web site, Visual InterDev sends a request to the server to set Execute permissions on the root of the Web to "None" for increased security.
  • Because all the previously selected subnodes are now inheriting this setting from the root, no executables can be run in any _vti_bin folders, and therefore, the FrontPage Server Extensions cannot run the executable as expected
  Solution
  • To prevent this problem, do not select _vti_bin to inherit the root permissions
  • When you set the Scripts and Executables permissions to the root of a program, a list of child nodes is displayed.
  • You can decide which of these child nodes will inherit the permissions of the root.
  • To permit the FrontPage Server Extensions to work with these permissions settings, select any child node in the list for the root except_vti_bin
  • All _vti_bin folders in that list must not inherit their application settings from the root application Workaround
    • To work around this problem, create a separate folder for the executable
    • In Internet Services Manager, apply Scripts and Executables permissions only to the folder
    • Make sure that the folder does not contain any subnodes
    • If a list of subnodes appears that contains any _vti_bin folders, clear the selection of these folders to prevent these nodes from inheriting the root permissions

ASP Error 0178: 80070005 When You Attempt To Connect To Database Results Page
Symptoms
• When you attempt to browse to an Active Server Page (ASP) database results page created in Microsoft FrontPage, you may receive an error message similar to the following
  Server object error 'ASP 0178 : 80070005'
  
  Server.CreateObject Access Error
  
  /_fpclass/fpdbrgn1.inc, line 99
  
  The call to Server.CreateObject failed while checking permissions. Access is denied to this object.
Solution
• To resolve your issue, reset the NTFS permissions on the "%ProgramFiles%\Common Files\System" folder.
  • Open Windows Explorer
    • To do this, right-click Start
    • Click Explore on the shortcut menu
    • In Folders view, expand the "%ProgramFiles%\Common Files\System" folder
    • Right-click the folder and click Properties on the shortcut menu
    • Click the Security tab
    • Add Everyone to the existing permissions
    • Give at least Read permissions to Everyone
    • Apply these new settings to all files and subfolders
    • Click OK
  More Information
  • For additional information how to troubleshoot ASP/IIS errors when you work with the database connectivity features of FrontPage, read the articles in the Microsoft Knowledge Base listed below
    • 265161 FP: Errors Appear When You Attempt to Connect to Database Results Page
    • 219170 FP2000: Error Browsing Database Results Pages After Publishing from Disk-Based Web
    • 315453 FP: ASP Error 0177: 800401f3 When You Attempt to Connect to Database Results Page
    • 315456 FP: Error: Unable to Open Jet Temporary Key When You Attempt to Connect to Database
  • For additional information how to troubleshoot IIS permissions, read the articles in the Microsoft Knowledge Base
    • 185874 How to Troubleshoot Permissions in Internet Information Server 4.0
    • 309051 HOW TO: Troubleshoot ASP in IIS 5.0

Error Message Appears Editing Web Page On A Sharepoint Portal Server
Symptoms
• In Microsoft FrontPage, when you attempt to open a Web folder on a Web server running SharePoint Portal Server 2001, you receive an error message similar to the following: Microsoft FrontPage
  The Web server at "http://localhost" does not appear to have the FrontPage server extensions installed.
Cause
• You cannot edit a SharePoint Portal Server in FrontPage.
• SharePoint Portal Server creates a virtual server when you install it
• This server does not use FrontPage Server Extensions
• Microsoft does not recommend installing the FrontPage Server Extensions in this case
• SharePoint Portal Server uses Web Distributed Authoring and Versioning (WebDAV) to allow remote client connectivity
Solution
• To edit or connect to sites running on a SharePoint Portal Server, use Web Folders
More Information
• Read RFC 2518 - HTTP Extensions for Distributed Authoring -- WEBDAV
  ftp://ftp.isi.edu/in-notes/rfc2518.txt
• You may install the FrontPage Server Extensions to the root folder of the Web site
• However, the portal section, which is contained in the Exchange Store, will not be accessible through FrontPage

"Error Removing One Or More Users" When Adding User As A Browser On An Apache Server
Symptoms On the FrontPage 2000 client, when you attempt to add a user as a browser on an Apache Web Server running the FrontPage 2002 Server Extensions, you receive the following error message:
Server error: Error removing one or more users: the following user names do not exist: ' '.
You are unable to add the user.
Solution
• Add the user as an Author and then demote the user to Browser

Database Error Messages When You Disable Session State In FrontPage 2002 Server Extensions From Microsoft
Error Message
• When you try to browse a database results page that was created by using FrontPage on a Microsoft Internet Information Services (IIS) Web server, you may receive an error message similar to one of the following
  Microsoft VBScript runtime error '800a000d'
  Type mismatch: 'Session'
  /_fpclass/fpdbrgn1.inc, line 204
  • error '8002802b'
    Element not found.
    /_fpclass/fpdbrgn1.inc, line 204
  • Database Results Error
    [Microsoft][ODBC Microsoft Access Driver] '(unknown)' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.
Solution
• Start Internet Services Manager, follow the steps for your version of IIS
  • For IIS 4.0
    • Click Start
    • Point to Programs
    • Click Windows NT 4.0 Option Pack
    • Click Microsoft Internet Information Server
    • Select Internet Service Manager
    • Continue to the next step, Enable Session State for the affected application.
  • For IIS 5.0
    • Click Start
    • Point to Programs
    • Click Administrative Tools
    • Click Internet Services Manager
    • Continue to the next step, Enable Session State for the affected application.
  • For IIS 5.1
    • Open Control Panel
    • Double-click Administrative Tools
    • Double-click Internet Information Services
    • Continue to the next step, Enable Session State for the affected application.
• Enable Session State for the affected application
  • To do this, follow the steps for your configuration
    • For a Web site
      • Right-click the Web site
      • Click Properties
      • Click the Home Directory tab
      • Click Configuration
      • Click the App Options tab or the Options tab
      • Check the Enable session state box
      • Click OK
      • Click OK to close the Web site's properties dialog box
    • For a subweb
      • Right-click the folder for the subweb
      • Click Properties
      • Click the Directory tab
      • Click Configuration
      • Click the App Options tab or the Options tab
      • Check the Enable session state box
      • Click OK
      • Click OK to close the subweb folder's properties dialog box
• Quit Internet Services Manager
• Note: You may have to restart your Web services to reflect these changes
References
• For additional information on configuring session state options in IIS and related errors, read the articles in the Microsoft Knowledge Base
  • 242425 Using Session Objects with Session State Disabled Returns Error
  • 308164 HOW TO: Create and Configure Active Server Pages (ASP) Web Applications in Windows 2000
  • 244465 HOW TO: Turn Off ASP Session State in Active Server Pages and IIS

Web Sites Do Not Open In Microsoft FrontPage After You Configure FrontPage Server Extensions 2002 On An Apache 1.3.19 Or Later Web Site
Symptoms
• After you configure the Microsoft FrontPage Server Extensions 2002 on an Apache 1.3.19 or later Web site, the Web site does not open in Microsoft FrontPage
Cause
• This problem occurs if you use your _default_ Web site while you are specifying both a unique Fully-Qualified Domain Name (FDN) and any port other than port 80
• This problem occurs because of the way that FrontPage names the CNF files that are used when you open FrontPage-enabled Web sites
  For example, virtual hosts may be defined in your Httpd.conf file similar to the way that they are defined in the following example:
  <VirtualHost _default_:8080>
  DocumentRoot /webdocs/public_html
  ServerName www.example.com
  </VirtualHost>
• If you use this example, FrontPage Server Extensions 2002 creates a file in your /usr/local/frontpage/ folder that is named We8080.cnf
• However, FrontPage Server Extensions 2002 creates a file that is named www.example.com:8080.cnf instead
• Because FrontPage has to find a CNF file with the correct naming format, an error occurs when you try to open the Web site with the FrontPage client
Solution
• Use one of the following methods to work around this problem
  • Use the correct naming format to rename the incorrectly named CNF file so that FrontPage can locate the file that it needs when you open the Web site
  • For example, if you use the example that is mentioned in the "Cause" section of this article, you would rename the www.example.com:8080.cnf file to We8080.cnf
  • Create a symbolic link to the CNF file that FrontPage created
  • If you use the example that is mentioned in the "Cause" section of this article, use the following syntax to create a symbolic link
    ln -s www.example.com:8080.cnf we8080.cnf

Web Clients Receive "Cannot Run The FrontPage Server Extensions On This Page" Error Message When They Submit A Feedback Form
Error
• Web clients receive an error message similar to the following example when they try to submit a feedback form that is on your Web page:
  Cannot run the FrontPage Server Extensions on this page: "http://www.example.com/subfolder/feedback.htm"
Solution
• To resolve this problem, follow these steps
  • Open your Web in FrontPage
  • In the folder list, expand the _private folder that is in the root of your Web site
  • Locate the Feedback.txt file
  • If you cannot locate this file, follow these steps
    • On the File menu, click New
    • Click Page or Web.
    • The task pane opens
    • Under New from template
    • Click Page Templates
    • On the General tab, click Normal Page
    • Click OK
    • Switch to HTML view
    • Delete all the HTML code
    • On the File menu, click Save
    • Locate and then double-click the _private folder that is in the root of your Web
    • In the Save as type box, click All Files (*.*)
    • In the File name box, type Feedback.txt
    • Click Save
  • Open the page that contains the feedback form
  • Right-click the form
  • Click Form Properties
  • Note: that the File name field shows that the results will be saved to the relative path of _private/Feedback.txt, which does not exist
    • For example, if you saved the feedback page to a subfolder named Test in the root of your Web site, this path is /Test/_private/Feedback.txt
  • Click Browse
  • Locate and then double-click the _private folder that is in the root of your Web
  • Click the Feedback.txt file
  • Click OK
  • Save the form page
  More Information
  • By default, the Save Results component in the Feedback Form template saves the results to a text file named _private/Feedback.txt in the root of your Web
  • By default, if you save the feedback page to a subfolder, the Save Results component points to a _private folder relative to the subfolder--a _private folder that does not exist--instead of to the _private folder in the root of your Web

"Fatal Exception 0e" Error Message During FrontPage Installation
Symptoms
• When you try to install Microsoft FrontPage 2002, the installation process starts, but after the Windows Installer Preparing to install dialog box appears, you may receive the following error message:
  A fatal exception 0E has occurred at memory location.
  Solution
  • To resolve this issue, use one of the following methods.
    • Method 1: Selective Startup
      • Click Start
      • Click Shut Down
      • In the Shut Down Windows dialog box, click Restart
      • Click OK
      • Press and hold down the CTRL key until the Startup menu appears
      • Select Step-by-step confirmation
      • Be sure to allow no system files to load
      • After Windows starts, install FrontPage 2002
    • Method 2: Install from Your Hard Disk
      • Copy the contents of the FrontPage 2002 CD-ROM to your hard disk, keeping all of the folder names intact
      • Install FrontPage from the hard disks.
        • Click Start
        • Click Run
        • In the Run dialog box, click Browse
        • In the Browse dialog box, browse to the location of the FrontPage files that you copied to the harddrive above
        • Click Open
        • In the Run dialog box, click OK
        • Follow the instructions of the Installation Wizard to complete the installation

You Receive An Error Message When You Click Next In A Paged Data View In FrontPage 2003
Error Message
• In Front Page 2003, when you browse to a page that contains a data view and then click Next, you may receive the following error message
  An error occurred while processing the data for this request. Contact the server administrator for more information.
Cause
• This problem occurs because views that are created in Microsoft SQL do not have primary keys defined by default, and the paging function requires a primary key
Solution
• Make sure that your stored procedures or views in SQL contain primary keys

You Receive An Error Message When You Try To Start FrontPage 2003
For a Microsoft FrontPage 2002 and FrontPage 2000 version of this article, see 321486 in the Microsoft Knowledge Base
Error Message
• When you try to start Microsoft Office FrontPage 2003, you may receive one or both of the following error messages:
  • Runtime error 440.
    Automation error
  • FPECOM Runtime error 5.
    Invalid procedure call or argument.
Cause
• This behavior may occur if the following conditions are true
  • The Microsoft bCentral Commerce Manager Add-in for FrontPage 2003 is installed on your computer
  • The entry for the add-in in the Microsoft Windows registry is damaged
Solution
• To resolve this issue, delete the bCentral Commerce Manager Add-in registry entry and remove the add-in from your computer
• To do this, follow these steps in the order that they appear
  • Part 1: Delete the bCentral Commerce Manager Add-in Registry Entry
    • Note: Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
      • Click Start
      • Click Run
      • In the Open box type
        regedit
      • Click OK
      • Locate and then click the following registry key:
        HKEY_CURRENT_USER\Software\Microsoft\Office\
        FrontPage\Addins\FPEcom.AddIn
      • On the Edit menu, click Delete
      • When you are prompted to confirm the deletion, click Yes
      • On the File menu, click Exit to quit Registry Editor
      • Restart your computer
      • Start FrontPage 2003
      • Do one of the following
        • If you do not receive the error message, the issue is resolved. Continue to "Part 2: Remove the bCentral Commerce Manager Add-in"
        • If you receive the error message continue to troubleshoot this issue, and then continue to Part 2: Remove the bCentral Commerce Manager Add-in"
      • Click Start
      • Click Run
      • In the Open box type
        regedit
      • Click OK
      • Locate and then click the following registry key
        HKEY_CURRENT_USER\Software\
        VB and VBA Program Settings\fpecomm
      • On the Edit menu, click Delete
      • When you are prompted to confirm the deletion, click Yes
      • On the File menu, click Exit to quit Registry Editor
      • Restart your computer
  • Part 2: Remove the bCentral Commerce Manager Add-in
    • Note: Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
      • Click Start
      • Click Control Panel
      • Click Add or Remove Programs
      • In the Currently installed programs list, click bCentral Commerce Manager Add-In for Microsoft FrontPage
      • Click Change/Remove
      • When you are prompted to confirm the removal, click Yes.
  More Information
  • To use the add-in, you must reinstall it. For more information about the Microsoft bCentral Commerce Manager Add-in for FrontPage 2003 and for instructions about how to download and install it, visit the following Microsoft Web site:
    • FrontPage 2002/2000 Add-in version 2: bCentral Commerce Manager
      http://office.microsoft.com/downloads/2002/fpecommenu.aspx
    • For more information about Microsoft bCentral, visit the following Microsoft Web site: Microsoft bCentral Home Page
      http://www.bcentral.com/default.asp

Error Message: Database Results Error [Microsoft][ODBC SQL Server Driver][Named Pipes]Access Denied
Error Message
• When you use the Database Results Wizard in Front Page 2003 to add a database to a Web page, when you click Finish, you receive the following error message
  Database Results Error [Microsoft][ODBC SQL Server Driver][Named Pipes]Access denied.
Cause
• This problem may occur if you select Microsoft Active Server Pages (ASP) technologies as the technology to connect to an external Microsoft SQL Server, and have Microsoft Data Access Components (MDAC) 2.5 or earlier installed on that server
Solution
• To solve this problem, download and install MDAC 2.7 or later on your SQL server
• To download MDAC 2.7, visit the following Microsoft Web site
  http://msdn.microsoft.com/library/default.asp?url=/downloads/list/dataaccess.asp

"The Folder '/' Is Marked Executable" Error Message When You Save A Page To A Folder On A Web Site Based On IIS In FrontPage 2002 & 03
Error Message
• In Microsoft FrontPage, when you save a page to a content folder on a Web site based on Microsoft Internet Information Services (IIS), you may receive the following error message
  Server error: The folder "/" is marked executable. You are not allowed to put files into an executable folder on this server.
• Note: This error message may vary, depending on the folder to which you are saving
• You may receive this message multiple times with different folder names
Cause
• This problem may occur if the content folder you are trying to save a file that is configured to allow executable programs to run. You cannot save files to a folder that is set to run executable files
Solution
• Configure the Web site to allow only scripts in the content folder to run
• Start Internet Services Manager
• To do this, follow the steps for your version of IIS
  • For IIS 4.0
    • Click Start
    • Point to Programs
    • Click Windows NT 4.0 Option Pack
    • Click Microsoft Internet Information Server
    • Click Internet Service Manager
    • Continue to next step
  • For IIS 5.0
    • On the Windows Start menu
    • Point to Programs
    • Click Administrative Tools
    • Select Internet Services Manager
    • Continue to next step
    For IIS 5.1
    • On the Start menu
    • Point to Settings
    • Click Control Panel.
    • Double-click the Administrative Tools icon
    • Double-click the Internet Information Services icon
    • Continue to next step
• Right-click the Web site that you want to change
• Click Properties on the shortcut menu
• Click the Home Directory tab
• Configure the execute permissions for scripts only
• Click Apply
• If you are prompted about Inheritance Overrides (meaning that several subfolders are configured with different execute permissions), do not select any _vti_bin path in any subfolder.
  • If you do, you will not be able to access your Web site from FrontPage.
  • You can override permissions settings on any folder that does not need execute permissions
• Click OK to close the Properties dialog box
Workaround
• To work around this problem, configure the FrontPage Server Extensions to allow Web authors to upload executables
  • Warning Do not use this type of configuration on a production Web server.
  • If you know and trust the Web authors, you can use this type of configuration to allow Web authors to upload executable files on a development Web server
  • To allow Web authors to upload executable files to a Web Server based on IIS, follow these steps
    • Start Internet Services Manager
    • To do this, follow the steps for your version of IIS
      • For IIS 4.0
        • Click Start
        • Point to Programs
        • Click Windows NT 4.0 Option Pack.
        • Click Microsoft Internet Information Server
        • Click Internet Service Manager
        • Continue to next step
      • For IIS 5.0
        • On the Windows Start menu
        • Point to Programs
        • Click Administrative Tools
        • Select Internet Services Manager
        • Continue to next step
    • Right-click the Default Web site
    • Click Properties on the menu that appears
    • Click the Server Extensions 2002 tab
    • Click Settings to open the Change Configuration Settings Web page
    • In the Security Settings section
    • Click to select the Allow Authors to upload executables check box
    • Click Submit
More Information
• For additional information about configuring the security settings for FrontPage Server Extensions and SharePoint Team Services from Microsoft, read the following article in the Microsoft Knowledge Base
  310932 F002: Where to find the Administrator's Guide for SharePoint Team Services

"Server error: Cannot close file /_vti_pvt/service.cnf" error message when you try to publish Web in FrontPage
Error Message
• When you try to publish your Microsoft FrontPage Web to an HTTP server, you may receive an error message that is similar to the following, where path is the path to your Web server
  Server error: Cannot close file /path/_vti_pvt/service.cnf
Cause
• This issue may occur if your Web has reached the allowable size limit on the Web server set by your Internet service provider (ISP).
• This can occur under either of the following conditions
  • The files that you want to publish exceed the size limit on the server set by your ISP
  • Old log files in your Web are not removed
    • Your ISP may create a folder in your Web that contains log files to store information about your account activity
    • These log files can become quite large over a period of time
  • The server that is hosting your site is out of space
Resolution
• Contact your ISP to clean up the log files in your Web, or to clear up some space on the server

Portal site stops responding and you receive a "The page cannot be displayed" or "Cannot find server or DNS error" error message when you access a portal site in SharePoint Portal Server 2003
Symptoms
• You may experience one or more of the following symptoms when you try to access a portal site on your server farm:
  • Only portions of the Web pages of your portal site appear in your Web browser, and the portal site stops responding (hangs). For example, graphics and other Web page components are missing from the Web pages in the portal site.
  • You receive error messages that are similar to the following:
    • The page cannot be displayed.
    • Cannot find server or DNS error.
. Cause
• This problem occurs if both the following conditions are true
  • Your server farm either provides or uses shared services
  • A front-end Web server in your server farm contains more than 64 portal sites. The maximum number of Web sites that are supported on any one server in a server farm that provides or uses shared services is 64
Solution
• Add the MaxEndpointsDWORD value to the following registry key on the front-end Web server
• Then set the value to the number of Web sites (less than or equal to 100) that you want
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
  Services\HTTP\Parameters
• The MaxEndpoints registry value represents both the number of IP (Internet Protocol) address and the port number pairs that are available on the server
• Follow these steps to add the MaxEndpoints registry value
  • Click Start
  • Click Run
  • In the Open box type
    regedit
  • Click OK
  • Locate, and then click the following registry key
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
    Services\HTTP\Parameters
  • On the Edit menu
  • Point to New
  • Click DWORD Value
  • Type MaxEndpoints
  • Press Enter
  • On the Edit menu
  • Click Modify
  • Under Base, click Decimal
  • In the Value data box, type the number of Web sites that you want
  • Click OK
    Important: Make sure that you specify a number that is less than or equal to 100
  • Quit Registry Editor
  • Restart the server
More Information
• The following limits apply to the number of portal sites that are supported on a server farm
  • If the server farm is not part of a shared services environment, the server farm supports up to 15 portal sites
  • If the server farm either provides or uses shared services, the server farm supports up to 100 portal sites. However, Microsoft Internet Information Services (IIS) limits the number of Web sites that are running on one server to 64
    • For more information about how to administer and configure server farm deployments of Microsoft SharePoint Portal Server, see the Microsoft Office SharePoint Portal Server 2003 Administration Guide
    • The Microsoft Office SharePoint Portal Server 2003 Administration Guide (Administrator's Help.chm) is located in the Docs folder in the root of the SharePoint Portal Server 2003 CD
      • For more information about SharePoint Portal Server, visit the following Microsoft Web site
        http://www.microsoft.com/sharepoint/server/default.asp

You receive a "You are not authorized to view this page" error message when you click Help on a single sign-on administration page in SharePoint Portal Server 2003
Error Message
• When you turn on the Microsoft Single Sign-On service on your server farm deployment of Microsoft Office SharePoint Portal Server 2003, and you click Help on any one of the single sign-on administration pages in SharePoint Central Administration, you are prompted to enter your user name and password three times
• After you do so, you receive the following error message
  You are not authorized to view this page
  
  HTTP Error 401.1 - Unauthorized: Access is denied due to invalid credentials.
  Internet Information Services (IIS)
Solution
• Access the single sign-on Help topics that you want in the Microsoft Office SharePoint Portal Server 2003 Administration Guide (Administrator's Help.chm)
• The single sign-on Help topics are listed in the "Managing Single Sign-On and Application Definitions" section of the "Administration" chapter of the Microsoft Office SharePoint Portal Server 2003 Administration Guide (Administrator's Help.chm)
• To view the Microsoft Office SharePoint Portal Server 2003 Administration Guide, do one of the following
  • Click Start
  • Point to Programs
  • Point to SharePoint Portal Server
  • Click SharePoint Portal Server Administrator's Guide
  • Double-click the Administrator's Help.chm file in the Docs folder in the root of the SharePoint Portal Server 2003 CD
More Information
• For more information about Microsoft SharePoint Portal Server, visit the following Microsoft Web site
  http://www.microsoft.com/sharepoint/server/default.asp

You receive a "The virtual server referenced here is not in the config database" error message when you unextend a virtual server in SharePoint Portal Server 2003
Error Message
• When you delete a portal site that is extended on more than one virtual server in your server farm, and then you unextend a virtual server that hosts the portal site, you may you receive the following error message, even though the virtual server is unextended successfully:
  The virtual server referenced here is not in the config database.
Cause
• This issue may occur if both of the following conditions are true
  • Your server farm deployment of Microsoft Office SharePoint Portal Server 2003 has more than one Web front-end server, and the portal site that you want to delete is extended on more than one virtual server
  • You delete the portal site before you unextend all the virtual servers that host the portal site on the Web front-end servers in your server farm
Solution
• The symptoms that are described in the "Error Message" section of this article do not affect the functionality of SharePoint Portal Server 2003 or Microsoft Windows SharePoint Services
• The virtual server is unextended successfully, and you can safely ignore the error message that appears after you unextend the virtual server
• To verify that the virtual server is unextended, follow these steps
  • Start SharePoint Portal Server Central Administration
  • On the SharePoint Portal Server Central Administration page, in the Portal Site and Virtual Server Configuration area, click Extend an existing virtual server from the Virtual Server List page
  • On the Virtual Server List page, in the list of virtual servers, verify that Extend appears next to the name of the virtual server that you unextended
    • To avoid this issue, unextend all the virtual servers that host the portal site on the Web front-end servers in your server farm before you delete the portal site
More Information
• For more information about how to delete a portal site, see the "Deleting a Portal Site" topic in the "Managing Portals" section of the "Administration" chapter of the Microsoft Office SharePoint Portal Server 2003 Administrator's Guide
• For more information about how to extend virtual servers, see the "Extending Virtual Servers" topic in the "Managing Sites" section of the "Administration" chapter of the Microsoft Office SharePoint Portal Server 2003 Administrator's Guide. The Microsoft Office SharePoint Portal Server 2003 Administrator's Guide (Administrator's Help.chm) is located in the Docs folder in the root of the SharePoint Portal Server 2003 CD
• For more information about SharePoint Portal Server, visit the following Microsoft Web site
  http://www.microsoft.com/office/sharepoint/prodinfo/default.mspx
• For more information about Windows SharePoint Services, visit the following Microsoft Web site
  http://www.microsoft.com/windowsserver2003/technologies/sharepoint/default.mspx