HOMEPAGE SITE MAP CONTACT US english francais
Company
Solutions
Downloads
Support
Ordering Assistance
Knowledge Base
Tutorials
Documentation
Subscribe
Store

Running Enterprise Server on Win2003 and Windows XP SP2 - (404 File not found)

Last updated: Wednesday, November 22, 2006
TOC :: Up

I’m trying to reinstall Enterprise on Win2003 Server, and, during configuration, am having problems getting past the point where I start the web browser to configure the database. I type in ’http://localhost/ent’ and then get ’The page cannot be found; The page you are looking for might have been removed, had its name changed, or is temporarily unavailable’.

Article Details

Microsoft have made various changes to security in Windows 2003 and Windows XP Service Pack 2, in line with their new "Secure by default" philosophy. If you are having problem accessing your Enterprise Server running on Windows 2003 or Windows XP SP2, then you should check the following:

  1. IIS 6.0 is not installed by default on Windows 2003 server (with the exception of the Web Server Edition). You can add this with the Add/Remove Programs Control Panel applet (IIS is listed as subcategory under Application Server item).

  2. The WWW Publishing service is disabled after an upgrade from Windows 2000 - so if you upgraded to Windows 2003 from Windows 2000 then you will have to enable WWW Publishing.

  3. The default installation of IIS on Windows 2003 allows only static web pages to be served. The ability to run an ISAPI dll such as Enterprise Server must be enabled manually. In addition, by default, all unknown ISAPI and CGI extensions are prohibited. To modify this setting, use the Web Services Extensions node in the IIS Managers MMC snap-in.
    • Click on "Add a new Web service extension..."

 

    • Give the extension a name (e.g. Microforge.net Enterprise Server), then click "Add..."
    • Navigate to your Enterprise Server \ ISAPI directory, and add both EntISAPI.dll and EntServer.dll to your new Web Service Extension.

 

    • Check "Set extension status to Allowed" and click "OK"
    • Your Enterprise Server Virtual Directory should now be configured to allow the required dynamic content to run.

You can find further information about these changes at: