FP1: Runtime WebBot Fails on IIS w/Multiple Home DirectoriesID: Q155281
|
If you are running Microsoft Internet Information Server (IIS) with more than
one home directory, and at least one home directory is defined as a
virtual server, the run-time WebBot components may not function.
NOTE: This problem only affects Internet Information Server, version
2.0.
A Web server passes identification information about the server in a Common
Gateway Interface (CGI) parameter called Server_Name. While IIS 1.0 passes the
Internet Protocol (IP) address in this parameter, IIS 2.0 passes the server
name.
When the FrontPage Server Extensions for IIS are installed, FrontPage needs to
know the IP address specified in the World Wide Web service properties (that is
how the registry keys are stored). From this information, the [Port <ip
address>:<port>] section is created in the Frontpg.ini file. When IIS 2.0 passes
a server name other than the IP address, FrontPage looks for the [Port
<name>:<port>] section in the Frontpg.ini. If it does not find it, FrontPage
looks for just the port. If FrontPage does not find that either, FrontPage puts
an error log in the event viewer and fails.
Note that if FrontPage does find the [Port 80] section it may not be
the section it should find because the non-virtual server on port 80
could (and should) have a different document root than the virtual
server that initiated the WebBot run-time activity.
http://127.0.0.1This would change a link on that page defined as feedback.htm to be evaluated by the server as
http://127.0.0.1/feedback.htmThis workaround has proven effective for the following WebBot components running on a TCP/IP configuration that uses WINS resolution:
Confirmation Field
Discussion
Save Results
Search
To see if this workaround will succeed on your server, alter one of
the links to a fully qualified link to an IP address and test the
functionality of run-time WebBot components on that link.
http://www.microsoft.com/frontpage/wpp/exts.htmNOTE: Because the Microsoft Web site is constantly updated, the site address may change without notice. If this occurs, link to the Microsoft home page at the following address:
http://www.microsoft.com
Microsoft has confirmed this to be a problem in the products listed at the beginning of this article. This problem was corrected in Microsoft FrontPage 97 for Windows with Bonus Pack.
This is fixed in FP 97 because the WebBot components call LOCAL_ADDR instead of SERVER_NAME. LOCAL_ADDR returns the IP address, leaving our registry and ini entries serviceable.Additional query words: 1.10 Internet Information Server fp multi-home multi-host
Keywords : kbdta fpiis
Version : windows:1.1
Platform : WINDOWS
Issue type : kbprb
Last Reviewed: July 22, 1999