Error Creating Subweb Using 100+ Characters in Web Name

ID: Q185544

The information in this article applies to:

Microsoft FrontPage 97 for Windows
Microsoft FrontPage 98 for Windows

SYMPTOMS

When you create a subweb in Microsoft FrontPage and use more than 100 characters in the Web name, the following error messages appear:

FrontPage 98

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. For more specific
information click Details.

When you click Details, you see the following information:

404 Not Found
404 Not Found
/subwebnameauthor.exe was not found on this server.

FrontPage 97

The server may not have the FrontPage Server Extensions installed, or
the server may be misconfigured, or you may have specified an invalid
proxy server, or the web you are accessing may have been deleted.
(HTTP Error 404).

The above error messages are repeated several times, depending on what type of subweb is being created.

On the server running FrontPage Personal Web Server, when the Web server is stopped and restarted, the following error message appears:

Syntax error on line <X> of c:/frontpage webs/server/conf/srm.conf

A second message then appears:

Unknown keyword subwebname/_vti_bin/_vti_adm/.

The Web server will not start.

CAUSE

When a subweb is created, WinScriptAliases are created for that subweb. If the subweb name is longer than 100 characters, the FrontPage Personal Web Server is unable to parse the WinScriptAliases in the Srm.cnf file.

STATUS

Microsoft has confirmed this to be a problem in Microsoft FrontPage 98 for Windows.

WORKAROUND

To work around this problem, do the following:

Manually edit the file C:\FrontPage Webs\Server\conf\Srm.cnf and remove the three WinScriptAlias entries that refer to the 100-plus character subweb.

Manually edit the file C:\FrontPage Webs\Content\_vti_pvt\Services.cnf and delete the line containing \subweb.

Keywords : fp97 fp98
Version : WINDOWS:97,98
Platform : WINDOWS
Issue type : kbbug