Re: email forms fail with FronPage Error please report details to webmaster

From: Harikumar H [MSFT] (harikumh_at_online.microsoft.com)
Date: 11/24/04 

Date: Wed, 24 Nov 2004 23:23:34 GMT

Hi

NOTE: The steps below should be tested in order, and you need to test form
functionality after each step. Proceed to the next step only if the problem
is not
resolved.

1. Create a new form and add an e-mail address only [without filename] and
test it.
This will isolate any issues related to the previous form.

2. Check if SMTP server settings are correctly configured. The following KB
articles explain how to configure for FPSE 2000 and 2002:

   196489 - How to set up FrontPage 2000 forms for e-mail on Internet
Information
Server
   http://support.microsoft.com/default.aspx?scid=kb;en-us;196489

   305675 - How to set up server-side settings to use e-mail features on
forms with
FrontPage 2002
   http://support.microsoft.com/default.aspx?scid=kb;en-us;305675

3. Check if the SMTP server works correctly with the SMTP commands and the
e-mail
address specified in the form configuration (Sometimes the Relay might not
have
been configured). To test this, use the steps in the following KB Article:

   153119 - XFOR: Telnet to Port 25 to Test SMTP Communication
   http://support.microsoft.com/default.aspx?scid=kb;en-us;153119

If the SMTP server is the "Default Virtual SMTP Server" on the Web Server,

4. Configure the SMARTHOST to point to the actual SMTP Server. To do this,
follow
these steps:

   a. Right click on the Default SMTP Virtual Server and select Properties.
   b. Click on the Access Tab and click the Relay button
   c. Add the computer which the SMTP server to the list
   d. Restart the SMTP Virtual Server

5. Anonymous access is disabled in the SMTP server. FrontPage uses
anonymous access
to send e-mails when a form is submitted. Also you should enable anonymous
access
in the Default SMTP Virtual Server. To do this, follow the steps:

   a. Right click on the Default SMTP Virtual Server and select Properties.
   b. Click on the Access Tab and click the Authentication button
   c. Enable Anonymous access.

6. Run Check server health with all repair options enabled through the
SharePoint
administration web site. This is useful if there is a permissions issue on
the web
site. Please note that all manually set NT permissions on the Web would be
replaced with as set through the FPSE User Interface

More Possibilities:

7. The .HTM and .HTML extension is mapped to some DLL in the Application
configuration of the web server master properties or in the Application
configuration of the web site where the form is located. Remove the
mapping
through IIS manager. To do this, follow the steps:

   a. Start Internet Services Manager.
   b. Right-click the machine name, and then click Properties on the
shortcut
menu.
   c. Click on the Edit button in the Master Properties
   d. Click on the Home Directory Tab and click on the Configuration button
in the
Application settings heading.
   e. Remove the mapping for .HTM and .HTML from the list of App Mappings.

This change will only affect for the new sites created after this change.
You need
to remove the mapping from the existing virtual sites so that form in these
sites
work.

8. The error message appear because certain accounts in the Access Control
Lists
(ACL’s) are deleted or the account’s friendly names are not resolvable from
their
security ID’s. To resolve this, follow the steps:

   a. Navigate to the folder where the home directory of the site is
pointing to.
   b. Right click on the folder that contains your web content and select
Properties.
   c. Click on the Security Tab.
   d. Look for accounts that do not display a friendly name but instead
display
something like - S-1-5-21-124525095-708259637
   e. Select the unresolved accounts or groups and then click Remove.
Usually it
is best to remove all accounts except the System and Local Administrators
with Full
Control.
   f. Select ‘Apply to all subfolders and files’ check box and then click
Ok.
   g. Do the Check Server health with all the Detect and Repair check boxes
enabled.

ADDITIONAL INFORMATION:
====================
For additional information, please see the following KB article:

319306 - Web site users receive an error message that says the mail server
is unavailable
http://support.microsoft.com/?id=319306

--------------------

| I'm sure this is not a problem with a form though because at the same time
| it started happening on all forms located on all sites hosted on this
| server. Plus it works if we set the forms to just save to a file rather
| than sending e-mail. This is almost definitely STMP related, either with
| the STMP Virtual Server settings on this machine, access rights to use
STMP,
| the network itself, or something along those lines. That's why I'm trying
to
| find a log or something that tells me at which point it's failing. For
| example, how can I find out if the FP extension is even able to
communicate
| with the SMTP server, and if it is, what sort of error or message is being
| returned?
|
|
| "Bjørn B. Larsen" <bjorn.b.larsen@iet.ntnu.no> wrote in message
| news:co21mu$7hq$1@orkan.itea.ntnu.no...
| > "Pcspcs" <pcs@nospam.com> wrote in message
| > news:uVcAycd0EHA.3708@TK2MSFTNGP14.phx.gbl...
| > >
| > > [ ... ]
| > >
| >
| > I have exactly the same problem. But it is worse. It sometimes work the
| way
| > it is supposed to. When I try it myself there is no problem.
| >
| > FrontPage 2003, Windows server 2003, IIS6 with FPExtensions.
| >
| > I got a set of data from one person who draw my attention to the
problem.
| It
| > failed when I used the same dataset. Then I changed the items one by one
| > till it finally behaved correctly. I then put back the old data item by
| item
| > until the form was complete with the original data but this time it did
| not
| > fail.
| >
| >
| > --
| > ----------------
| > Have a nice day!
| > Bjørn BL.
| >
| >
|
|
|

Hope this helps

regards

Hari
MSFT

This posting is provided "as is" with no warranties and confers no rights