findinsite-ms Web.Config Options
Web.Config contains set up information for the findinsite-ms application.
Please do not change this file, apart from the
You usually control findinsite-ms using its Control Panel.
findinsite-ms stores its configuration information
in the work directory. If the default location for the work directory is not working or
is not appropriate, then you can change it by setting a work
appSettings parameter in
- see below for details of how to check it.
It is also a good idea to store your password,
license id and EmailFromPassword as appSettings parameters.
The supplied file
Web.Config contains a
<customErrors> section that tells ASP.NET
how to respond if there is a major error finding or processing a page. The supplied value
produces detailed error information, which will be useful when you are setting up
<customErrors mode="Off" />
Once happy with your installation, you can show 'friendly' messages:
<customErrors mode="On" />
The work appSettings parameter sets the work directory.
Before you start testing findinsite-ms, it is important to check that the
findinsite-ms work directory is in a suitable location.
By default, findinsite-ms tries to create a sub-directory
to use as the work directory - if you have installed findinsite-ms in directory
findinsite/ then the work directory will be
If this directory does not work, then findinsite-ms tries to use the application
directory as the work directory, ie
ASP.NET systems are often set up so that findinsite-ms does not have the file write
permission that is needed to create or use the work directory. Read how to set
file permissions - or consult the
instructions for various shared hosts.
findinsite-ms uses a work directory to store all its configuration information
and search database files. It is important that this directory is secure from
unwanted direct access, while still being available to findinsite-ms.
Finally, it is also a good idea to backup the contents of the work directory regularly.
Once the work directory is set up, all configuration changes will be stored so
that findinsite-ms will
remember them even if it is stopped and restarted.
The Control Panel General section displays the current work directory.
If this is not suitable then you need to change the work
If the current work directory is not suitable then you must make a suitable
(new) work directory and change the work appSettings parameter.
The Test work directory field of the
General section lets you prove that your new directory is usable by findinsite-ms.
(Some directories may not be readable or writeable by findinsite-ms.)
Changing appSettings parameters
The appSettings parameters are stored in the
Web.Config file. This is a text file (in UTF-8 format)
found in the application installation directory, eg
findinsite/ on your server.
Web.Config, you typically need to work with a local copy of the file, and then upload it to the server.
If you do not already have a local copy of the file (ie in the findinsite-ms runtime
directory), then use FTP or FrontPage Extensions to download it.
Web.Config to make the changes (eg in Windows Notepad). Upload the file using FTP or
FrontPage Extensions. Updating
Web.Config usually stops the findinsite-ms
application, so the next access will restart it to let you test any changes.
<appSettings> section is towards the end of
Web.Config. Add in an add tag with key
and value attributes to specify the parameter name and value, eg as follows:
<add key="work" value="c:\FindData" />
appSettings Parameter List
Here is a list of the appSettings parameters that you can set.
The letter case of the parameter names is ignored.
||The findinsite-ms license id
||The password that must be used for future findinsite-ms
Control Panel requests.
||The path of the work directory
||A default sub-directory
FindData is created
(Or the application directory is used.)
||The password used for SMTP email send authentication
||No password - SMTP authentication is not needed