%1!0.0s!A FrontPage %2!.64s! component was unable to create the image %3!.192s!.
3) An internal error may have occurred in the web server, preventing the FrontPage Server Extensions from processing this request.
An error occurred in the web server that made it impossible for the FrontPage Server Extensions to process this request. (HTTP Error %1!d!)
An unexpected error occurred accessing your FrontPage web files. Authors - if authoring against a web server, please contact the webmaster for this server's site. WebMasters - please see the server's %1!.128s! for more details.
An unexpected error occurred accessing your FrontPage web files. Authors - if authoring against a web server, please contact the webmaster for this server's site. WebMasters - please see the server's system log for more details.
An unexpected error occurred reading the anonymous user name.
An unexpected internal error occurred when calling QuerySecurityPackageInfo() during NTLM authentication.
An unknown WinSock error has occurred (code %1!d!).
Any delay has probably been caused by your TCP/IP configuration. With this configuration, you can expect that FrontPage will take this long to start up every time.
Authoring is disabled for this server. Use the Server Administrator to enable authoring.
Could not enable %1!-.450s! privilege. Error %2!d! generated.
Could not send mail: MAPI error number %1!d!.
Error %1!d! closing registry key %2!-.450s!.
Error %1!d! creating backing store for key %2!-.450s!.
Error %1!d! creating the registry key %2!-.100s! under key %3!-.100s!.
Error %1!d! deleting a registry key %2!-.100s! under key %3!-.100s!.
Error %1!d! deleting backing store for key %2!-.450s!.
Error %1!d! deleting registry value %2!-.450s!.
Error %1!d! getting registry value %2!-.450s!.
Error %1!d! getting size for registry value %2!-.450s!.
Error %1!d! opening registry key %2!-.450s!.
Error %1!d! restoring key %2!-.450s!.
Error %1!d! searching registry values.
Error %1!d! setting registry value %2!-.450s!.
Error adding user: a user named '%1!.100s!' already exists.
Error changing password for '%1!.100s!': previous password is incorrect.
Error chowning file, %1!-.450s!.
Error connecting to server - server cannot be reached at this time.
Error creating the navigation bar icon. Its url would be !1.400s!.
Error during NTLM authentication - could not generate an authorization token.
Error during secure communication with web server. The server may not support the correct version of the SSL protocol.
Error executing program, %1!-.450s!.
Error getting key change notification for registry value %1!-.450s!.
Error initializing access control: can't inherit access control settings from the root web because it is missing the AuthUserFile and AuthGroupFile directives.
Error initializing access control: unable to access ACL for root web: %1!.400s!.
Error initializing access control: unable to create group file: %1!.400s!.
Error initializing access control: unable to create password file: %1!.400s!.
Error line %d: %s
Error listing domains: AB logon failed.
Error listing domains: AB provider init failed.
Error listing domains: could not get AB provider dll.
Error listing domains: creating new support object failed.
Error occurred while retrieving the list of users from the system.
Error reading access control for the %1!.60s! web: access control files are inconsistent or missing.
Error reading from SMTP host '%1!.400s!'.
Error removing user: a user named '%1!.100s!' does not exist.
Error renaming the registry key %1!-.100s! - a key named %2!-.100s! already exists.
Error restarting server process %1!d!.
Error retrieving %1!.200s! - the connection timed out or was aborted by the server.
Error setting up pipe to subprogram %1!-.200s!: the %2!-.200s! system call failed.
Error starting Microsoft Personal Web Server.
Error stopping Microsoft Personal Web Server.
Error updating a navigation bar image for page !2.400s!. Recalculating the links for this web should fix the problem.
Error updating access control for the %1!.60s! web: when modifying a web so that it uses its own access control settings, you must specify a username and password for the initial administrator.
Error updating access control for the %1!.60s! web: you cannot change the realm name for a web that inherits its access control settings from the default web.
Error updating access control: unable to update the access control settings for the following webs that inherit their settings from the %1!.100s! web: %2!.100s!
Error updating navigation bar image. Unable to load the background image %2!.100s! for theme %1!.100s!.
Error updating the list of administrators: you cannot remove the last administrator.
Error updating the list of permitted IP addresses: you cannot remove the last administrator-level IP address, because it would make the server inaccessable.
Error updating the navigation bar text for !1.200s!.
Error updating user list: the following users already exist: %1!.200s!
and the following users do not exist: %2!.200s!
Error writing to SMTP host '%1!.400s!'.
FrontPage has prepared your server to receive your web content, but the destination server requires that you manually restart it before continuing the publish process. Please restart the server and then publish the web again. If you are unsure how to restart your server, consult your web server's documentation.
FrontPage is unable to establish a secure connection with the server, because the server's SSL certificate is either invalid, or issued by an untrusted certificate authority.
FrontPage is unable to establish a secure connection with the server. The server does not support the security options that FrontPage uses.
FrontPage was unable to restrict browse access to only registered users since the groups, %1!.250s!, contains the account used by your Microsoft Internet Information Server to implement Anonymous Logons. Please remove this group from the list of registered groups and try again.
G[SYNSTREAM] Syntax error in input stream: expected %s, got %s
HTTP error (400): the HTTP server could not parse the request.
HTTP error (403): the HTTP server will not allow access to the requested url.
HTTP error (404): the specified URL %1!.300s! does not exist.
HTTP error (404): the specified URL does not exist.
HTTP error (500): the HTTP server encountered an internal error and could not process the request.
HTTP error (502): an invalid response was received from a gateway or proxy server.
HTTP error (503): the HTTP server is unable to handle this request at the current time. Please try again later.
Internal Winsock error (WSAEACCES).
Internal error in WebSite registry structure: %1!-.400s!.
Parse error in file %1!-.450s! line %2!d!.
Parse error in file %1!-.450s! result is %2!-.450s! .
Read error on file %1!-.450s!.
Start Search
System Error %1!d! opening the service %2!-.450s!.
System Error %1!d! opening the service manager database.
System Error %1!d! while trying to query service %2!-.450s!.
System Error %1!d! while trying to start service %2!-.450s!. You might need to manually restart service.
System Error %1!d! while trying to stop service %2!-.450s!.
The server is too busy to process the request at this time. Please try again later. (HTTP Error 503)
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 server may not have the FrontPage Server Extensions installed, your machine's IP address may not have access to the server, or you may have specified an invalid proxy server. (HTTP Error 403)
The tool has made a request that the server did not recognize. You may have specified an invalid proxy server. (HTTP Error 400)
The web server does not support the POST method. (HTTP Error 405)
The web server is not configured to support any of the authentication schemes that FrontPage supports - unable to login to the web server.
This is not really an error - you should never see this message (WSAEDISCON).
This is not really an error - you should never see this message (WSAEWOULDBLOCK).
To allow all users to have browse access to your web, anonymous logons must be enabled on your Microsoft Internet Information Server. You can enable anonymous logons by editing the password authentication method under the Directory Security tab of the web server's properties in the Microsoft Internet Information Server's Internet Service Manager.
To allow all users to have browse access to your web, anonymous logons must be enabled on your Microsoft Internet Information Server. You can enable anonymous logons using the Microsoft Internet Information Service Manager's WWW server Properties command.
To allow all users to have browse access to your web, anonymous logons must be enabled on your Microsoft Personal Web Server. You can enable anonymous logons by editing the password authentication method under the Directory Security tab of the web server's properties in the Microsoft Personal Web Server's Internet Service Manager.
To allow all users to have browse access to your web, the account used for anonymous logons by your Microsoft Internet Information Server must be enabled in Windows NT. Please use the Windows NT User Manager to enable the account and try again.
To allow earlier versions of the FrontPage Explorer and Editor to open and modify FrontPage webs on this server, you must enable Basic Authentication on your web server. Enable Basic Authentication now?
To complete the FrontPage installation, the Netscape Server must be restarted. Would you like to restart the server now?
To complete the FrontPage installation, the WWW Service of the Microsoft Internet Information Server must be restarted. Would you like to stop and restart the server now?
To complete the FrontPage installation, the WWW Service of the Microsoft Personal Web Server must be restarted. Would you like to stop and restart the server now?
Unable to access configuration for Microsoft Internet Information Server.
Unable to access configuration for Microsoft Personal Web Server.
Unable to change access control for this web, because it inherits the access control of the root web. Please change the access control on the root web.
Unable to complete transaction - the server requested authentication information (userid/password) using an authentication scheme (%1!.30s!) that is unsupported by FrontPage.
Unable to connect to a server at '%1!.200s!' on port %2!d! (socket code %3!d!)
Unable to connect to the server (HTTP Error 500).
Unable to connect to the specified web server - the host is not reachable.
Unable to connect to the specified web server - the hostname could not be found.
Unable to connect to the specified web server - try again shortly.
Unable to determine a suitable temp directory.
Unable to determine the Windows system directory.
Unable to determine the Windows user directory.
Unable to interpret the contents of this page. The problem occurred because %1 is not installed on your system. This resource is necessary in order to interpret pages with the %2 character set.
Unable to post files to %1!.200s! using WebPost (code %2!d!).
Unable to read configuration for Microsoft Internet Information Server.
Unable to read configuration for Microsoft Personal Web Server.
Unable to read configuration information for Microsoft Internet Information Server: CloseHandle Error.
Unable to read configuration information for Microsoft Internet Information Server: Error code %1!ld!
Unable to read configuration information for Microsoft Internet Information Server: ImpersonateLoggedOnUser Error.
Unable to read configuration information for Microsoft Internet Information Server: OpenThreadToken Error.
Unable to read configuration information for Microsoft Internet Information Server: RevertToSelf Error.
Unable to read configuration information for Microsoft Personal Web Server: Error code %1!ld!
Unable to read version number for Microsoft Internet Information Server: Error code %1!ld!
Unable to read version number for Microsoft Personal Web Server: Error code %1!ld!
Unable to recalculate links for %1!.200s!.
Unable to update the information in the Office document %1!.200s!.
Unable to write configuration for Microsoft Internet Information Server.
Unable to write configuration for Microsoft Personal Web Server.
Unable to write configuration information for Microsoft Internet Information Server: Error code %1!ld!
Unable to write configuration information for Microsoft Personal Web Server: Error code %1!ld!
Unexpected HTTP error code: %1!d!
Unknown server error number: %d
Visual Source Safe failure. Verify that you have write access to the Visual Source Safe repository. A %1!.200s! error occurred while operating on file %2!.200s!
Visual Source Safe failure. A %1!.200s! error occurred while operating on file %2!.200s!
Visual Source Safe projects must be absolute (they must start with $/).
Warning: Your FrontPage web content is stored on a FAT file system. When authoring is enabled, anyone will be able to author and administer your FrontPage web. To enable FrontPage's access protection, uninstall the FrontPage server extensions, reconfigure your Microsoft Internet Information Server to use an NTFS partition and reinstall the FrontPage server extensions.
Warning: to control which users can author and administer your FrontPage web, Dynamic Configuration Files need to be enabled. Would you like to enable them now?
Write error on file %1!-.450s!.
You can now start using FrontPage.
You need to install version %1 or higher of the Microsoft Web Publishing Wizard on your computer. Unable to publish your web.
[GENERIC] Generic error number %d
%s
[LOCK] Unable to lock memory
[OVFLOW] Overflow error ->
%.*s <
- (%u max characters)