Support

Support



Help with IIS 4 and iHTML

NOTE: The following procedure is handled by the iHTML install now. This document is provided in case this needs to be checked manually. This was a problem because IIS 4.0 did not correctly update the new metabase.bin file when starting up.

To get iHTML working with IIS 4.0:

1) Delete all the registry keys associated with your script extensions. Clear the whole section out at:

HKEY_LOCAL_MACHINE/SYSTEM/ CurrentControlSet /Services/W3SVC/Parameters/Script Map. Don't delete the key, just all the values except for the default one. Don't worry -- they are not used.

2) Go into the Internet Service Manager. Starting at the global level, delete all the entries for the script type that doesn't work. These can be found by:
a) Right clicking on the machine name, choosing Properties. Edit Properties for "WWW Service" Go to "Home Directory" tab, "Configuration" button, then remove all those duplicate applicaton mappings. Leave the .ihtml c:\ihtml\ihtml.dll entries (whatever mime types you want to continue to work with iHTML)

b) Do the same thing at the virtual server and directory levels.

c) Restart the service, or your machine. Don't just stop and start the virtual servers, actually run "Net Stop W3SVC" and "Net Start w3SVC" or do it from the services control panel.

Permissions Issues with IIS and iHTML

Since iHTML becomes a part of the web server, it effectively runs under the permission level of the web server. Therefore, the web server user, typically IUSR_servername must have the necessary permissions to get to the resources it needs. iHTML needs to have read/write and execute permissions on any directories in which .ihtml files reside. It may also need permissions to any .MDB files if using MS Access as the database for a site.

The easiest way to get iHTML running with IIS is to give the IUSR_servername user administrator rights. You can back these down once you have experimented with setting the correct permissions you need to have the site run the way it needs to. It is also necessary to set the directories, files and subdirectories with Windows Explorer and the MMC web manager to have read/write and execute permissions.

Initially, three directory mappings are installed on IIS.

/ihtml/ this is the main directory and has the index.htm page to get to the test files and online docs.

/ihtml_config/ this is the configuration directory that is used to modify settings in iHTML. Effectively, all these settings can also be changed in the registry. It would be wise to password protect this directory.

/merchant/ this is the Merchant 1.x directory for a sample store.

The above three directories should have read/write and execute permissions. Remember when testing iHTML out , you must use the HTTP protocol or the pages won't get processed by iHTML. So, to see if iHTML is running on the server after installation, in the browser type

http://localhost/ihtml/index.ihtml
or
http://127.0.0.1/ihtml/index.ihtml